Posted: 5 Dec 2017 4:13 EST Last activity: 8 Dec 2017 0:41 EST
Lock is lost on the Parent Case when child case is closed.
At a point in the flow of my parent case, a screen displays the list of child cases. On-click of the child case, the child case is opened in a new tab. Once, I am done with child case, I close the tab and come back to parent case tab.
The moment I submit, it throws an exception "You have lost the ability to make this change because a change elsewhere has taken precendence over the change you made here."
Both the parent and child cases are configured with "default locking" mechanism and the parent case is locked when the child case is locked. I am not using any activity to acquire the lock or "Page-New" the flow-action. When I monitored the instances of "System-Locks", I realized that the lock on the parent case is released the moment the child case tab is closed. Not sure why this is happening and the issue is consistently reproduced.
PFA doc for the design and application screenshots.
We're instantiating the child cases by using the create-case smart shape where we selected "Create Child case(s)" on a page-list. The child case is opened in a new tab via the action "Open Work By Handle" and passing the "pzInsKey" configured on the repeating grid layout.
No. We're not modifying "pyShowCases" section. We've our own configured which is sourced from a Report Definition hitting the work pool table.
Also, one thing I forgot to mention in my original post. When I close the child case tab, I come back to the parent case tab. If I "refresh" via local action and submit, the issue isn't reproducible.
Activity Work- Cover- workUnlock is programmed to unlock both Child and Parent case at step no 2 Java Step
I think this is an expected behaviour. Child case gets committed (Changes has been saved to DB) and it would be good to refresh Parent in case child would have made some changes to pyWorkPage of Parent that could be lost without refresh.
Refreshing the parent again creates the lock Handle and hence you don't see any issue.