Posted: 9 Feb 2016 23:00 EST Last activity: 10 Feb 2016 15:08 EST
Subcase unable to complete because parent case is locked
I am having an issue with subcases locking the parent work object. I have a parent case creating multiple subcases which are getting processed by a standard agent. Therefore, the parent case waits on the subcases to finish; this is being done with both a wait shape and the AllCoveredResolved ticket. Unfortunately, both of these methods require the status of the subcases to be updated (to some form of Resolved), and when the subcase updates its own status, my suspicion is that it locks the parent case to see if it can either resolve it or continue it (there may be other ootb reasons why it would need to do this). Now, none of this is an issue if I only have a single node working on these subcases, however I would like to enable more than one node for the sake of speed and this is where the problem lies. The agent on node 1 is updating its status while the agent on node 2 is also updating its status, this causes a "Cannot obtain a lock on instance pzInsKey, as Requestor Agent already has the lock" causing the object to not finish. Please advise on how else I can achieve my requirement other than only enabling one node. Is there an alternative to UpdateStatus that wont lock the parent case? Is there an alternate ticket I can use that doesnt go based off status? Any advice is much appreciated.
Unfortunately modifying the DetermineLockString activity to only allow for self locking did not work. I previously disabled parent case locking from the subcase locking scheme. My PRPC version is 7.1.7
Posted: 5 years ago
Posted: 10 Feb 2016 15:08 EST
Phani Sahukaru (sahup1)
Architect - Financial Services