Case has been routed to a WB, how come the creator can still access it and approve/reject the Case?

General
1

Hello,

I have a simple flow that first creates an case, then system assigns it to a WB to approve or reject. I did not use the OOTB approve/reject shape but an assignment shape instead due to other requirements. But once the creator operator submit the case, it will show “Thank you! The next step in this case has been routed appropriately” but the creator still able to click on “Go” button under to do section.

Note, the creator operator does not have access to the WB.

What is the best approach to disable the creator to continue working on the case once it’s been routed?

Go button displayed under to do section.png
Go button displayed under to do section.png1899×548 54 KB

Thanks,

Su

2

@ChensuZ5 Can you please check whether workbasket is present in Operator ID.

3

@ChensuZ5 Could you check this similar question

4

access role.png
access role.png985×132 10.2 KB

I added privilege to the flow action and used access role. Instruction can be found below:

Securing an application using role-based access control | Pega Academy

After the change, the creator won’t be able to approve/reject the case since he doesn’t have the role to access my flow action. This is what the creator will see when they click on Go

unable to open the case.png
unable to open the case.png1317×419 24.7 KB