I created a new usergroup & for some reason that usergroup cannot print a batch detail report within the Batch Administrator screen. I tried searching this under the following link : http://www.tessituranetwork.com/Help_System/Content/Security/Table%20of%20Security%20Objects.htm as well as search the forums but couldn't find anything.
The only thing that came close to this was the Conts Batch Posting. I gave that user group full access to this but still I am unable to print. Does anyone know through experience how to grant access?
Sarah, I found these instructions in my files, perhaps you need to assign the new user group to the users manager button you want to give access to.
Normal 0 false false false EN-US X-NONE X-NONE
Batch Administrator SECURITY
In order to post batches access to the following security object must be granted:
· Conts Batch Posting: View rights allow users to post batches, Edit rights allow users to adjust control totals, and Add rights allow users to backdate the posting date.
In addition, in order to view, edit, and post the batches of other users, a user must be designated as the manager of the other users, which is set up from the Users screen by highlighting the intended manager and then clicking the Manager button to open the user group assignment screen.
Finally, access to the following system tables is required for batch set up:
· TR_BATCH TYPE
· TR_BATCH_TYPE_GROUP
· TR_BU
This is from the Tessitura Batch Administration Document
Thank you for this but I did all that and it's still not allowing me to even print while logged into that usergroup....
Hi Sera,
I know this is a late post. We recently ran into this issue ourselves. It was a new usergroup and we've found two items in security that fixed the problem. Security objects, Report Output and Report Viewer had N/A on both of these. We gave the group view rights and now the print is no longer greyed out.
Further testing revealed that revoking them to no's had no effect. It seems like an initial connection needed to be made through a yes or a no.
Thank you for this! I'm thinking we resolved the issue through the way you described - this was so long ago I can't remember!