Parent case not proceeds to next stage, although child cases were resolved
We have two child cases created parallelly. But sometimes although child cases resolved, the parent case is not progressing to the next stage. We use "wait" shape to wait till resolution of child cases. Do not know what caused the issue, because it happens randomly but every day. Below SR may be useful too. I would like to know whether it is released in 7.1.8. Our product version is CPM 7.1.3 on Pega 7.1.8
https://collaborate.pega.com/discussion/using-utility-after-wait-shape-not-working
Some of our configurations:
We have two child cases created parallelly. But sometimes although child cases resolved, the parent case is not progressing to the next stage. We use "wait" shape to wait till resolution of child cases. Do not know what caused the issue, because it happens randomly but every day. Below SR may be useful too. I would like to know whether it is released in 7.1.8. Our product version is CPM 7.1.3 on Pega 7.1.8
https://collaborate.pega.com/discussion/using-utility-after-wait-shape-not-working
Some of our configurations:
Accepted Solution
FECredit
VN
The issue caused by the wait shape. The team used two approaches to resolve this issue.
1. For existing cases that already in the production: Used an activity to manually run and resume child flow(s) for the issue cases.
2. The team discussed with pega support, and as a permanent fix used AllCoveredResolved ticket in both child flows.
Pegasystems Inc.
IN
Have you tried using tickets like Work-Cover-.AllCoveredResolved ?
Also what is the status of your child objects when they are resolved ? Is it Resolved-Completed or anything else ?
Infosys
GB
There are around 2000 cases are being created in production and only for 20 cases daily this issue is coming. The cases are not moved forward.
We cant use AllCoveredResolved ticket as it is already working in production. Need to figure out why it is in consistent.?
Any inputs will be much appreciated.
And.. Status for Child work object is also Resolved-Completed only.
AtoS
IN
We were facing same kind of issue in one of my previous project (Dev environment 7.1.6 ) .So we have used Agent for this issue and it was working fine.
Tetco
SA
Hi Kevin,
Can you please check what is the pxcoveredcount value in the clipboard for the parent case, if all child cases are resolved the pxcoveredcount should be 0, if it's not 0 then it means the child case assignments are not closed properly,
Please check and let me know your thoughts.
Accepted Solution
FECredit
VN
The issue caused by the wait shape. The team used two approaches to resolve this issue.
1. For existing cases that already in the production: Used an activity to manually run and resume child flow(s) for the issue cases.
2. The team discussed with pega support, and as a permanent fix used AllCoveredResolved ticket in both child flows.