Issue with pxCoveredCount while updating Parent Case from child case
Hello,
I am facing an issue related to pxCoveredCount. PFB detailed information on the same.
- We have a Parent case and multiple child cases. We created the Data model at the Parent Case level because each child case will require the Data model updated by the previous child case.
- Whenever a new child case is getting created, we create a Data model at Child case. The same will be mapped back to Parent case, before closure of the Child case.
- Problem comes when:
- From child case, we opened the Parent case using Obj- method (on a page, lets say ParentPage) and update the Data using Page-Copy and Obj-Save the Parent case.
- Then Child case status will be set to Resolved-xxxx status, which triggers Pega OOTB rules and updates the pxCoveredCount property of the parent case.
- pxCoverPage is hardcoded as Parent Page in Work-.Resolve activity. And it is decrementing pxCoveredCount by -1, which is throwing error while Execution. But the actual parent case page is ParentPage where it should have executed.
- Here, there are 2 instances of Parent page ( ParentPage and pxCoverPage) are out of sync, causing the issue.
Hello,
I am facing an issue related to pxCoveredCount. PFB detailed information on the same.
- We have a Parent case and multiple child cases. We created the Data model at the Parent Case level because each child case will require the Data model updated by the previous child case.
- Whenever a new child case is getting created, we create a Data model at Child case. The same will be mapped back to Parent case, before closure of the Child case.
- Problem comes when:
- From child case, we opened the Parent case using Obj- method (on a page, lets say ParentPage) and update the Data using Page-Copy and Obj-Save the Parent case.
- Then Child case status will be set to Resolved-xxxx status, which triggers Pega OOTB rules and updates the pxCoveredCount property of the parent case.
- pxCoverPage is hardcoded as Parent Page in Work-.Resolve activity. And it is decrementing pxCoveredCount by -1, which is throwing error while Execution. But the actual parent case page is ParentPage where it should have executed.
- Here, there are 2 instances of Parent page ( ParentPage and pxCoverPage) are out of sync, causing the issue.
Suggestions are required on below:
- If the case structure and Data model update approach is good? Or any changes required?
- Is there any other way to propagate data from Child to Parent?
- How to update ParentPage pxCoveredCount property, while it is being opened from Child case?
***Updated by moderator: Lochan to update Category***
Pegasystems Inc.
IN
Hi
please find below my inputs.
>> Is there any other way to propagate data from Child to Parent?
Try opening the pyWorkCover Page by Obj-Open, make the changes and save it by obj-save
>> How to update ParentPage pxCoveredCount property, while it is being opened from Child case?
pxCoveredCount property should not be manually updated as it keeps track of the number of child case currently open.
Infosys
IN
Thanks for the reply.
>> Is there any other way to propagate data from Child to Parent?
Actually, we have multiple child cases, where we are doing the same. Everywhere we hard coded the page name with "OrderPage". This code has also been propagated to higher environments. I can consider this as the last possible option. Is there any other way of doing this?
>> How to update ParentPage pxCoveredCount property, while it is being opened from Child case?
It was a typo, I was referring pxCoveredCountOpen property here.
Available
US
pxCoveredCount should not change at all... pxCoveredCountOpen should decrement when children are resolved. pxCoveredCount is the total covered case count, not subject to open or resolved status
Accenture
SG
Hi
please find below my inputs.
For this question - Is there any other way to propagate data from Child to Parent?
there is a Parameter Page "pyParentPageName" through which you can access Parent case page in child case and set data from child to parent.