How to restrict case creation for an access group when using Cosmos?
Hi All,
How can we restrict case creation for a specific access group when using Cosmos?
Previously we were able to achieve this by using a privilege & adding it in the security section of the pyStartCase flow.
Using the above method for the other starting flow in the case type record does not restrict the case creation. Additionally there is no pyStartCase used in Cosmos.
Regards,
Petar Hr.
Louis Dreyfus Company
BG
Hi All,
Is there anyone that managed to achieve this restriction via privilege or access group?
Regards,
Petar
Updated: 19 Nov 2021 1:24 EST
Pegasystems Inc.
US
A work around for 8.5 which would be to go into App Studio and Channels, and create a New Portal interface. There one can edit which cases appear within the Create menu. This will require a portal for each access group.
For those on 8.6, this should be customizable via App Studio directly (for more info check Manage access for personas more efficiently in App Studio (8.6) | Pega).
Lventur
IN
By using cosmos OOTB code we will not be able to achieve this. Pega recommending to have a separate portal for each access group for specific reason's.
If we are having separate portal for each access group then by using app studio features easily we could achieve this restriction changes.
Now pega is not using pyStartCase flow also, so you would not be able to control case creation access by using privilege..
What you could do for achieving this is, you could save PortalNavigation section in to your ruleset and provide custom solution for restricting case creation access.