Posted: 17 Jun 2019 16:38 EDT Last activity: 26 Jun 2019 4:17 EDT
Reopen Parent/Child Functionality
Please let us know for the best design practice for reopening Child cases when we reopen a Parent Case.
Example : In Smart Dispute we have a Parent Claim (C-) case having 5 Child Dispute (D-) Cases, The requirement says when we withdraw a claim mistakenly we need to reopen the Claim as well as Dispute cases what would be best approach to reopen here?
Thanks for your reply, so when we re-open a Claim(Parent case) do we need to loop over all the Dispute(child work objects) and call Work-reopenWorkObject ? moreover when all the child work objects are resolved I think pxCoveredCountOpen will be having a value of 0 so how does that make significance when we reopen the cover/covered objects ?
Work- reopenWorkObject should increment is Cover's pxCoveredCountOpen.
Step 13 is Call UnResolveCover. Step 13 in that activity increments pxCoveredCountOpen.
As far as depth-first looping, note the logic in the pxIsInTree Function. This function is told to look in a list, e.g., pxResults, looking for some value within some particular property.
If the pxResults pagelist contains a property named ".pxResults", the logic pushes that ClipboardProperty onto the stack and keeps looking to see if there us another pxResults pagelist at a deeper level.
Eventually the answer is "no". At that point you decide what to do since you have hit "bottom".
Instead of a PageList you would have a ValueList named pxCoveredInsKeys.
When you hit bottom, you could try calling reopenWorkObject but that would be complex to do inside java.
What you could do instead is start with an empty ValueList and simply add each pzInsKey to it.
When you exit the java step you have a flatted ValueList of pzInsKeys to iterate.
For each pzInsKey in the ValueList Obj-Open-By-Handle as "pyWorkPage" then call reopenWorkObject passing "pyWorkPage" as the value for param.WorkPage.