Question
Instellars
SG
Last activity: 21 Nov 2019 2:17 EST
Case dependency going to repair flow
We have requirement in a way that the flow parent case cannot move to resolve stage unless the child case is resolved. This seems to be working fine in dev but there are sometimes errors in PROD environement . The parent goes to repair assignment and keeps sitting on wait shape.
Following is the error on parent case : .pxInsName: Keys of Instance Value must be specified
Since this scenario is not frequent and reporducing in DEV, not able to guess the issue. Please suggest solution to fix/debug.
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
BPM Company
NL
What's your actual solution, could you provide screenshots?
Instellars
SG
attached screenshot
BPM Company
NL
Is it happening then AFTER you complete the child case? or during?
Instellars
SG
Once child case is resolved, the parent case goes to repair flow and gets stuck in wait shape
BPM Company
NL
But can you still see the case ID on the top of the screen? the pxInsName contains the id in the format WO-24.
Instellars
SG
Yes i can see case id and pxInsname has the value
Pegasystems Inc.
FR
Hello,
Have you tried to double check your log files? At that specific time can you see any specific error?
Instellars
SG
No new exceptions in logs were found
Pegasystems Inc.
FR
What PRPC version is it? Maybe you could use the AddCoveredWork activity instead of CreateWorkPage activity can you?
Instellars
SG
We are in 8.1.0 version. I am using the smart shape to created child case. Can you give me reason behind changing the pxAddChildWork which is OOTB to above activity. Since this issue is not reporducible in DEV.
Pegasystems Inc.
FR
Well,
Of course I'm not recommending to apply that change directly in Production. It is always difficult to work on a configuration when you have nothing to replicate and test against.
I've seen such issue generated in the past due to those activities. Could you trace in Production? Have you seen any patterns like mainly the same user having this issue or maybe passivation occuring?
Pegasystems Inc.
FR
Can this be helpful: https://community.pega.com/support/support-articles/issue-createworkpage-final-activity-new-version