Posted: 9 Oct 2020 6:08 EDT Last activity: 9 Oct 2020 7:03 EDT
Object locking in case hiearchy
By default, in case hierarchy, when child case is locked, parent case is also locked. On the other hand, when parent case is locked, child case is not locked. Can someone tell me the logical reasoning why Pega specification is designed as such? What is the benefit of parent case being locked while child case is locked? Why not the other around?
* I know we can change the behavior not to lock the parent case. This question is to ask the background of this product design.
The locking mechanism can be changed but originally it was because after having updated your child case the system was also reporting statuses and other details to the Parent case concerning executed child.
Thanks. Parent case has child case status - "pxCoveredCount" and "pxCoveredCountOpen" and I understood that these need to be updated per child case update. Are there any other information than this? Also, if we change the behavior not to lock the parent, how exactly will the parent case update the status?