Closed
pxCoveredcount mismatch
the pxcoveredcount property value is sometimes not matching with the number of child cases present for a case.
This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.
the pxcoveredcount property value is sometimes not matching with the number of child cases present for a case.
Hello,
Do you have a replication path? Can you trace it maybe? Sometime this is due to manual reopen of child cases could you check that maybe.
It's happening frequently in Production only for few of the cases we could not reproduce them. Not sure what making that mismatch
I think you need to check history records for Parent and child and check if you can identify a sort of incorrect path.
Actually we using pyChangestage.. to change the stage of the child case after the Child Case is resolved. I observed this pychangestage is not considering as the child case as opened which is not updating the pxcoveredcountopen in Parent case
Good catch
here we need to open the parent case and update the covercount ? or any other way to achieve it?
Yes I think you will have to for those already broken ones
Question
Question Solved
Question
Discussion
Question
Question Solved
Question Solved
Question
Question
Question
Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.