We have a situation that has been going on since 6.2, and with the upgrade to 7.2.2, we were hoping it would be resolved, however, it is still happening... We have a situation where upon attempting to resolve a case, an error is displayed because pxCoveredCountOpen has gone negative... For example, -3. I am a but puzzled as to how pxCoveredCountOpen could go negative. I could not find anything about this issue on the PDN.
***Edited by Moderator Marissa to update platform capability tags***
Have you configured anywhere in the flow to reduce the count of pxCoveredCountOpen property or manually setting the status to Resolved-Completed? In that case, the property value is not updated immediately and there by leads to inconsistency.
By default, activity Work-Resolve is responsible for decreasing the pxCoveredCountOpen property value when a child case is resolved.
I am facing a similar issue. pxCoveredCountOpen is changing to -1. There is no direct reference to this property to increment/decrement from any application code (App RSVs). The status is being changed by calling OOTB Work-UpdateStatus.
I thought a constraint should have been in place out-of-the-box on the allowed range of this property (& other px related Case Managment OOTB properties).
Any leads/suggestions on this issue are appreciated.
Thanks for the responses :-). I actually opened an SR for this, though as far as I know it has not been fixed. I am on a different team now so I am not directly involved at this point. I was not able to find anywhere in our app that these values were being set, and fully believed it to be a product defect. It is reassuring to find that others are also having this issue, and that reinforces in my mind that this is a product defect. While it is sporadic and only happens every once in a while, it is a problem. I have forwarded the information provided to my previous team. Thanks much for sharing! :-)
Apologies. I realize I misspoke on this one after checking my list of SRs. My intention was to file an SR after checking with the community to see if anyone else was experiencing the issue. Reason being I have filed several SRs which were withdrawn by Pega though the issues were quite serious because we were able to fix the cases through direct manipulation of the database or through an activity to repair the errors because they are issues which are sporadic and not easily reproducible.