"Do Not Lock" Option in subcase locking configuration
We can set parent case locking in the subcase locking configuration (subcase is instantiated as part of a parent case). The default option is to lock the parent case when the subcase is being worked on. This is the recommended approach for most use cases. However, there is a "Do not lock" option available in the locking configuration of the subcase that removes the locking of the parent case when a subcase is being worked on. This provides the benefit of simultaneously processing the parent case and sub case. The downside to this is that the changes to properties in the subcase is not reflected in the parent case.
If we have an arbitrary use case that requires:
- Simultaneous processing of both parent case and sub case
- Synchronization of referenced properties between sub case and parent case
How would we configure the locking options or provide alternative PRPC configurations to support both requirements?
Thank you in advance.
Accepted Solution
Pegasystems Inc.
FR
Hi,
Maybe you need to switch from our default to optimistic locking mechanism. You can have a look in here: https://collaborate.pega.com/question/optimistic-locking
Can we have more details concerning this requierement ? Is it a global one accross the application or just a one shot at the beginning of case life cycle ?
Pegasystems Inc.
US
Hello Paul,
I agree with lassm, optimistic locking might be a great approach. Another option would be to use queue for agent to queue the simultaenous updates. This will delay the changes and you need to make sure that you aren't having different users working off of/updating the same properties, since that could result in stale data overwriting fresh updates.
It would be easier to provide guidance with a clearer understanding of your use case.
Thanks,
Mike