How to rectify Broken Processes flow in Pega?
Hi Guys,
I have gone through the existing PDN articles regarding broken process. I could not resolve my problem.
My problem scenario is:
In Case life cycle: Stage1 (All steps are executed properly),
Stage 2 > Step 1 activity is called, in that activity one step is written to assign to work list, due to no operator id in database [of course validation should have been done before calling assign to work list], process is broken and it is assigned to work basket and process is broken.
Later Operator ID value is updated in database table, Stage 2 > Step 1 Activity is pulling Operator ID properly from DB (through RD)
Now when I click on broken process 'Begin' or 'Restart problem flow from the begining' or 'Resume Problem flow' or Retry last step of problem flow', I am getting below error, What ever the activity is called in Stage 2 > Step 1, tracer activity is not coming, so, why it is not starting from where it was failed? how to fix this issue?
Flow: FDOAIFApproval_Flow
Step: (Assignment1)
Error: No routing information was provided for this assignment.
Thanks,
***Edited by Moderator Kayla to update General to Product***
Accepted Solution
Thryve Digital
IN
My problem is resolved.
Solution: FixProblemAssignments OOTB Activity in PegaProComm accepts workHandle as input parameter. we need to run this activity and pass pxLockHandle value which is on pyWorkpage of a case. FYI, Inside FixProblemAssignments OOTB Activity > Call FixBrokenAssignments is called.
Pegasystems Inc.
FR
Hello,
I might be wrong but that sounds like a custom error message I think. Can you trace it to check where this error message is coming from?
Updated: 27 Jun 2020 0:06 EDT
Accenture
US
This usually happens when some property on the clipboard is missing and your WO or Flow is looking for it. Although you have the operator NOW in your DB, the case 'may' not have the operator ID. That could be one reason.
Open the clipboard and check for missing property on the Work Object. Update the clipboard and execute an activity to SAVE the Work object. Then run the Flow and see if that solves the issue..
Otherwise, compare the clipboard of the broken case with the clipboard of a good case. That might give you a clue as well.
Accepted Solution
Thryve Digital
IN
My problem is resolved.
Solution: FixProblemAssignments OOTB Activity in PegaProComm accepts workHandle as input parameter. we need to run this activity and pass pxLockHandle value which is on pyWorkpage of a case. FYI, Inside FixProblemAssignments OOTB Activity > Call FixBrokenAssignments is called.