I have a requirement to hide Go / begin button to be displayed on custom condtions , as in constellation we cannot edit buttons
please let me know
The go button will appear if you have admin privileges though the assignment is assigned to another user or work queue.
If you validate from the end-user portal, the go button won’t appear if the next assignment is assigned to Work Queue or different users. If you still see the Go button, then your security requirements for the end-user portal are not implemented correctly.
Customizing Go button is not recommended.
We’ve scenario where case moves for approval to a queue where case creator will have an access,so we tried access when rules able to restrict the button but could see errors
I don’t see the Go button in the Approval step, though I’m the case creator. Please find the screenshot for your reference.
Thanks,
Hello! I’m facing same problem. The screenshot you have shared has the task assigned to a user and in that case the Go button is not visible to the case creator or any other user.
Can you confirm if you are able to hide the Go button when the case is assigned to a work queue? I think this is the original issue explained by @saikrishnaG6683
Kindly check the attached screenshots for clarification. ReviewApplication is the Work Queue and Reviewer is the User
Regards,
Saroj
Could you please confirm that you’re validating with the end user access group? and ensure the end user has the appropriate roles configured?
Both the screenshots are from the case creator’s (end user’s) portal which is mapped to it’s access group. All the roles and mapping are configured properly from App Studio.
Regards,
Saroj
In Pega constellation, we are trying to restrict access to certain assignments which is routed to particular user.
When the assignment is routed to a Work Queue, the “Go” button is correctly restricted based on Access Roles. I have configured the necessary roles, and the restriction works as expected.
However, when the assignment is routed to a specific user (Worklist), I have tried to apply the same restrictions using Privileges and When conditions in the Flow Action Security tab, but the “Go” button is still visible and accessible to the user. And when they click “Go” it is automatically launching the pyEdit Flow Action.
If I submits the pyEdit flow action, It throws the error which I mentioned below.
could no found a option to hide we have fixed this issue by adding a Access when privilege on flow action, by this update you can still see the go button , but does not allow user to open assignment.
Thank you for sharing the update. We will probably do the same to limit the assignment opening.
I hope Pega teams handle this issue in the next update.
@Saroj.Panda In work Queue apply roles. Any user with that role can see GO button otherwise not.