Posted: 8 Aug 2017 15:03 EDT Last activity: 9 Aug 2017 14:21 EDT
GetNextWork not picking the right rule from Current application context
We are using the GetNextWork to pull the case from Workbasket or from Worklist based on the Yes/No click on the modal window.
On click we are calling the Pega OOTB "GetNextWork" button action.
When the user click on the button its bringing the right case from the current application. But if there is no case found in the Workbast or Worklist, pega showing the OOTB harness "NoAssignmentsAvailable"
If the user don't close that harness in the screen and try to do the "GetNextWork" again, pega stopped calling the "GetNextWork" from the current application and its calling the pega OOTB "GetNextWork" rule and all the related rules.
It looks after its shows the "NoAssignmentsAvailable" harness, pega loosing the current application context and executing the pega OOTB GetNextWork rules.If I close this harness and try to call "GetNextWork", its working fine.
We noticed that this issue happening only if the user having the access to more than one application. Is there any solution for this issue.
User having the access to multiple application and sharing the same Work Group.
User can switch the applications using the pega OOTB "Switch Application" function.
***Moderator Edit: Vidyaranjan | Updated SR details***
***Edited by Moderator Marissa to update categories***
While I haven't explicitly encountered this issue before, here are a couple of quick thoughts on things you might want to try to diagnose the problem (if you haven't tried them already):
Try comparing traces of the working and non working scenarios (you noted that the issue occurs only for users who have access to multiple applications). You can use the Pega-TracerViewer tool (Instruction video here) to help with the comparison.
Check the log to see if there are any errors on the 2nd attempt to click GetNextWork in the non-working scenario.
Use the Live UI tool to confirm that the same "NoAssignmentsAvailable" screen with the GetNextWork button is the same in both the working and non-working scenarios.