How to controle case type list on create menu on User Portal with D_StartingFlows
G'day,
Could you tell us how to control case type list on create menu on User Portal with D_StartingFlows? We're using only the User Portal on 8.4.2. Our client has several groups to which we apply several access groups. So one of groups can see a specific case type, but others cannot. The pyCreateCaseMenu menu rule retrieve the D_StartingFlows.pxResults. I've already created a when rule which controls who can do and others cannot. I, however, found that it's very difficult to change inside the Datapage because of several final rules and complicated logic. Please let us know a best way to control the case type list on the UserPortal.
Thank you in advance.
Accepted Solution
Updated: 6 Dec 2021 1:00 EST
Pegasystems Inc.
JP
@shimt I've successfully controlled visibility of case types list on the create menu on the User Portal. I've just missed my when rule. So everything is fine with a correct when rule set on the pyCreateCaseMenu rule.
Anyhow, thank everyone.
Aaseya IT Solutions
IN
@shimt This is best controlled through Privileges associated with the access groups.
You shouldn't change the datapage or anything else. You should associate privileges to control this.
Refer to the activity pzGetStartingFlowsFromApp
Pegasystems Inc.
JP
@Raju_Botu -san,
Thank you for your suggestion. You mean that we should NOT hide any specific case type on a create list, but we should set ARO to each classes which relates to each case type. Actually, I'll try to communicate to my client below. - We cannot hide any specific case type name on the create case list. - We, however, configure that some group cannot open some case types even they can see the case types on a create case type list.
My understanding is correct?
Aaseya IT Solutions
IN
@shimt There are two things here..
1. Case type shouldn't be displayed in the create menu for anyone - this is a simple configuration on the case design.
2. Case type should be displayed in create menu for few groups and not for others - this needs to be controlled through Priviliges and AROs
Lventur
IN
If you are using pega old version case type rule and in case type rule if you are having pyStartCase flow then you would be to achieve this functionality easily by ARO.
Please refer below mentioned article in which how to restrict the case creation option by ARO was clearly explained.
Access Deny & Privilege in Pega – Pega Knowledge Sharing (myknowpega.com).
If in case you are using latest feature of pega and in case type if you are not having pyStartCase flow then you would need to have custom logic for achieving this functionality.
In portal configuration wise pega recommend us to follow below mentioned points.
- Creating a portal and do all portal related configuration from app studio.
- Need to have a separate portal for each access group(s), instead of having single portal for all access group(s).
- Need to have separated page(s) created for all portal navigation links.
If in case you are having different portal for each access group, then removing the case creation option feature from app studio for the respective portal group alone will help you to achieve your business need.
If you are using pega old version case type rule and in case type rule if you are having pyStartCase flow then you would be to achieve this functionality easily by ARO.
Please refer below mentioned article in which how to restrict the case creation option by ARO was clearly explained.
Access Deny & Privilege in Pega – Pega Knowledge Sharing (myknowpega.com).
If in case you are using latest feature of pega and in case type if you are not having pyStartCase flow then you would need to have custom logic for achieving this functionality.
In portal configuration wise pega recommend us to follow below mentioned points.
- Creating a portal and do all portal related configuration from app studio.
- Need to have a separate portal for each access group(s), instead of having single portal for all access group(s).
- Need to have separated page(s) created for all portal navigation links.
If in case you are having different portal for each access group, then removing the case creation option feature from app studio for the respective portal group alone will help you to achieve your business need.
If you are not having different portal, as far I know you would be able to control this requirement only by providing custom solution by using D_StartingFlows data page. Inside this data page you would be able to find the extension activity pySortStartingFlows, in this activity you could build your custom solution.
Accepted Solution
Updated: 6 Dec 2021 1:00 EST
Pegasystems Inc.
JP
@shimt I've successfully controlled visibility of case types list on the create menu on the User Portal. I've just missed my when rule. So everything is fine with a correct when rule set on the pyCreateCaseMenu rule.
Anyhow, thank everyone.