Access Restrictions And Context For Ticket Work Center Views
There are several work center views in the Service work center that share the same access context. This means that whichever access restriction is the most lenient will be applied to all the views sharing the same context. In order to ensure consistent access for your business users you have to apply the same access restrictions for these views in your business roles.
Here is the list of work center views sharing the same access context:
| Work Center View ID | Work Center View Name | Comment |
|---|---|---|
| SEOD_QUEUE_SADL_OWL | Queue | |
| SEOD_TICKETMD_SADL_WCVIEW | Tickets | current ticket view desktop and mobile enabled |
| SEOD_DESKTOP_NAVIGATION | Technical: Desktop Navigation | technical view – not visible to the end user |
| SEOD_TABLET_NAVIGATION | Technical: Tablet Navigation | technical view – not visible to the end user |
| SEOD_TICKET_SADL_WCVIEW | Tickets | old ticket view which can be unassigned |
Do you have any familiarity with Historic Restrictions on the Ticketing workcenters? For example, I have a situation org unit valid periods has ended.
I have devised and implemented restrictions on a business role to see a specific org unit ticket queue AND I want them to see tickets from a org unit ticket queue thats valid period has ended. I look on the Historic Restrictions TAB, looked for the ID of the no-longer valid org unit, I find it, but it has no name. I select the read/write options, YET i am presented with a SAVE ERROR of
"Access group ID [ID SEQUENCE] not valid for access context Service Unit"
Is this to be expected?