Problems resolving child cases for pxCoveredCountOpen of Parent case
In our big application, we have several problems of wrong pxCoveredCountOpen values for Parent cases which cause errors while trying to resolve the covered children of these objects. I would like to have some answers on this subject :
1) Could you tell me all the locations in Pega where this property is updated (like for example, in Work- Resolve) so that I can understand how it should work ?
2) Would you have any idea as to why objects could end with wrong pxCoveredCountOpen ?
3) Knowing that we have these problems, how could we manage to close a child which cover has a wrong pxCoveredCountOpen ? I was trying to correct pxCoveredCountOpen of parent case with a obj-open - property-special etc... But in the case where the page is already somewhere in the clipboard it would not be sufficient... What do you think about it ?
***Updated by moderator: Lochan to add SR details***
Accepted Solution
Pegasystems Inc.
US
Pegasystems Inc.
US
Hello,
1) Could you tell me all the locations in Pega where this property is updated (like for example, in Work- Resolve) so that I can understand how it should work ? => For this query i think you can open pxCoveredCountOpen property and go to View References from Actions menu in order to see the reference rules
Regards
Mahesh
Pegasystems Inc.
US
Hello,
2) Would you have any idea as to why objects could end with wrong pxCoveredCountOpen ? => we had notices some issues with this count when we do force close of the work objects of parent/child cases
So it would be better if you share which Pega version you are using and how you are resolving your work objects of parent and child cases.
Thanks
Mahesh
Pegasystems Inc.
US
After my research found an existing bug BUG-295770 related to the wrong pxCoveredCountOpen which is found in Pega v7.1.9 and HFix-33247 has been provided, may be you can look into this bug.
Groupama
FR
Hi,
I've reproduced the problem on Pega 7.2.1 (which normally includes the mentioned HFix) using OOTB and standard functions. See SR-B41141 if you may access It. To reproduce, you create a case with one subcase. Have a standard agent change the status of the sub-case to Resolved. Reopen the subcase (for some reason the system puts its status from Resolved back to Open) and try to resolve it. You will get ther error message.
Rgds
Accepted Solution
Pegasystems Inc.
US
Upon reviewing the associated SR to this post, I see that SA-36650 Calling UpdateStatus via an agent doesn't fully update the case was created as a resolution. If you have the same question, please refer to this SA.
Upon reviewing the associated SR to this post, I see that SA-36650 Calling UpdateStatus via an agent doesn't fully update the case was created as a resolution. If you have the same question, please refer to this SA.