Question1Replies823Views×Close popoverBinod Garg (BinodG12) Members Equity Bank Pty Ltd Members Equity Bank Pty Ltd AU View Profile BinodG12 Member since 2017 8 posts Members Equity Bank Pty Ltd Posted: January 24, 2018Last activity: January 25, 2018Posted: 24 Jan 2018 17:56 ESTLast activity: 25 Jan 2018 12:54 EST Closed AllCoveredResolved ticket does not work on End shape in a flowWe have the following scenario1. A parent case creates a sub case in a flow step . The sub case flow is a straight through flow which does not require a manual intervention and is resolved once the processing completes2. The parent case flow has a end shape(with a status of resolved-completed) with ticket "AllCoveredResolved" defined on the shape. 3. When the sub case is resolved , the expectation is that the parent case is resolved However we observe that sometimes the parent case is not resolved . I guess this is a very straight forward scenario . I looked at the PDN support article https://pdn.pega.com/support-articles/allcoveredresolved-ticket-does-not-work-end-shape-flow which talks about creating a utility shape before the end shape of the parent case flow to update the status of the parent case to "Resolved-Complete"and set the AllCoveredResolved ticket on the utility shape. However I do not understand the difference here . Thanks, Low-Code App Development Case Management ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Moderation Team has archived post This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question. Posted: 3 years agoPosted: 25 Jan 2018 12:54 EST×Close popoverCarissa Wenhardt (CarissaW_GCS) PEGA Principal Software Solutions Engineer Pegasystems Inc. US View ProfileCarissaW_GCS PEGA replied to BinodG12When the issue occurs and the parent case is not resolved, what do the pxCoveredCount and pxCoveredCountOpen properties show on the parent? Did they get updated properly?