Question
IN
Last activity: 30 Sep 2022 6:00 EDT
Created Stage wide optional action, It is accessible only from Admin user.
Created Stage wide optional action, It is accessible only from Admin user (PegaRULES:SysAdm4). Can you please tell us which access role or Privileges should i use for other user (Business user) that the can also access that ?
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
NCS Pte. Ltd
SG
Hi: @RaghavN2There is no such restriction by default. Please check if you have associated any privileges in the flow action rule. Also check if there are any restrictions to the class. Thanks
Updated: 28 Sep 2022 2:09 EDT
IN
@ArulDevan Thanks for the answer,
As i checked there is no restrictions to the class and if use PegaRULES:SysAdm4 for my custom user it is working fine.
Actually i am re-opening the case through stage-wide local action, Not happening through business user, But same user able to create the same case, Going up to resolved completed stage, and after that he is not getting Action-Add work->Reopen(stage-wide local action)
NCS Pte. Ltd
SG
Hi @RaghavN2: Can you clarify on few points?
Are you using OOTB action navigation?
Have you added reopen as a local action in your resolve stage? If yes, are you using default reopen functionality (or) do you have a custom action for reopen?
Are you trying to reopen the case after the case is resolved?
Suggestion: If Reopening the case is the requirement, use OOTB reopen functionality which is default available in workactionsreview navigation.
Thanks.
Updated: 28 Sep 2022 5:45 EDT
IN
@ArulDevan Thanks for the answer.
Are you using OOTB action navigation? Yes
Have you added reopen as a local action in your resolve stage? = Yes
If yes, are you using default reopen functionality (or) do you have a custom action for reopen? = Default one
Are you trying to reopen the case after the case is resolved? = Yes
Functionality is working fine, Admin user is able to do end-to-end flow.
Its is like reverse transfer, First user is transfering account from A to B (Resolved complted)
Next add work revert transfer( resolved -reverse transfer)
But business user not able to see Action-Add work->Reopen(revert transfer)
I
NCS Pte. Ltd
SG
Hi @RaghavN2: if i understand this correctly, Add work - revert transfer -> this will create a sub case. Now the sub case is resolved and you are trying to reopen the sub case (in this sub case type you have a stage level local.
Can you try to change the action from stage level to case level local actions and try?
Also can use live UI to check which navigation rule is used in your scenario?
Thanks
Updated: 28 Sep 2022 7:55 EDT
IN
@ArulDevan We dont have subcase, It is the continuation of previous case.
When i add it as Casewide optional action it is showing 2 times for Admin user, Nothing showing for Business user
NCS Pte. Ltd
SG
Hi @RaghavN2: Have you tried to check the Live UI for admin user and business user to check which navigation rule is called in both scenarios? Once you identified the navigation rule, check if they are same and if there are some visibility / privilege configured in the reopen item.
Thanks
IN
Hi @ArulDevan Business user doesn't have live UI capability and i add access role(PegaRULES:SysAdm4) to business user that Add work -> revert transfer is showing for him. (PegaRULES:SysAdm4) we can't give to Business user, and i created one custom access role and cloned this from PegaRULES:SysAdm4, in that case also it is not working.
NCS Pte. Ltd
SG
Hi @RaghavN2: Confused. The issue is with Reopen flow action or is it on Add work -> Revert transfer?
Is this Add Work -> revert work is a case or a flow action?
Thanks
Updated: 29 Sep 2022 0:39 EDT
IN
The issue is with Reopen flow action or is it on Add work -> Revert transfer? = it is on Add work -> Revert transfer
Is this Add Work -> revert work is a case or a flow action? = It is flow action
Updated: 29 Sep 2022 1:52 EDT
NCS Pte. Ltd
SG
Hi @RaghavN2: What is the navigation rule called when you try from admin user?
Also, have you validated the access roles granted for the business user? Does the access role granted to business user has access to the class in which the flow action is created?
Thanks.
IN
Hi @ArulDevan in tracer i could able to see @baseclass hasAdminRole this when rule validation, Sot it is restricting for other user, I there any solution for this? You alredy told in the previous comment there is no restriction for optional actions.
Updated: 29 Sep 2022 2:29 EDT
NCS Pte. Ltd
SG
Hi @RaghavN2: For the flow action to be visible, hasAdminRole will help for your admin ID. But for other users, you need to grant appropriate access in the access roles defined in the business user access group.
Solution will be giving right access in the access roles defiled in the access group of business user. As i stated earlier, check the class (where the flow action is created) is available in your business user access role with necessary access granted.
Open Business user access access group, open the access role in it -> check if the class is available in it.
Thanks
Updated: 29 Sep 2022 3:35 EDT
IN
@ArulDevan in when rule it is clearly mentioned with this role. Lib(Pega-RULES:Default).HaveRole(this,"PegaRULES:SysAdm4")
if the user has PegaRULES:SysAdm4 role then only it is accessible for user.
IN
Hi @ArulDevan It is referred in below navigation.
Navigation:
Displays the Actions menu for the Review harness
pyWorkActionsReview
IN
@@ArulDevan in Navigation role we had condition only accessible for admin user now added the business user access role to it , Now it is both admin and business user. It is working now. Is it the correct solution ?
NCS Pte. Ltd
SG
Hi @RaghavN2: I don't see such condition in the OOTB rule. I think the rule is customized in your application layer. Am i right? If so, i suggest to add a when rule / a privilege to modularize the code.
Can share a screenshot to verify( without confidential data )
Suggestion: Please edit your post to remove link of application :)
Thanks.
IN
@ArulDevan Yes indeed , Only in our application it is customized. Thank you for your help.