Is there way to override the Back to Back assignment flag ,which is configured on flow action tab . Our Case life cycle is designed to process the back to back assignments across the stages like assigment1 (stage1) ,assignment2 (stage2), assignment3 (stage3) and assignment4 (stage3) etc. and they gets created or skipped based on business conditions.
All assignments are configured to route the task to current operator . B2B flag is enabled on assignment1 .
As per specification ,On Post submission of assignment1 ,If system creates assignment2 then open it in perform mode for the same user and for the rest of the assignments which gets created in process should be opened in confirm mode .
I understand that ,Pega opens the b2b assignments in perform mode since B2B is enabled on assignment1 and all further assignments ,which gets created in process flow will be routed to current operator .
I have checked performcriteria decision tree which gets invoked if B2B is enabled .
If B2B flag is disabled on assignment1 then no issue with assignment3 and assignment4 as they opens in confirm mode by default, but how to opens the assigment2 in perform mode whenever it gets created.
Is it possible to override the B2B flag as true when system is creating assingment2? .
I can see only possible solution here is ,customize the decision tree to make it return false for assignment3 and assignment4 ,so that they can be opened it in confirm mode .However, it becomes maintenance issue whenever adding new assignment to process flow.
***Edited by Moderator: Pallavi to update platform capability tags***
I don't know of a way out of the box to do this dynamically. It sounds like you are going down the right path by tracing the process and seeing the pieces that you might be able to customize to get the behavior you're looking for. Certainly customizing the decision tree sounds like a workable approach.