Enabling users to simultaneously work on cases
By default, when a user opens an assignment for action, the system locks the case that the assignment belongs to and its parent case to avoid conflicts created by other users acting on those cases. The lock persists until the assignment is saved, canceled, or submitted. You can enable multiple users to simultaneously work on the same assignments and cases.
For information about locking cases, see Locking Cases.
Ensure you have a copy of the Pega Client Lifecycle Management for Financial Services case types in your implementation layer rulesets. Although it is not mandatory, it is recommended as well to have them in your class structure.
Copy the pyOptimisticLockingEnableParentLock application setting (Pega-ProcessArchitect ruleset) into your rulesets.
Enable the configuration for all the production levels. This activates advanced optimistic locking settings in the case type rule.
From the navigation panel, click
.Select pyOptimisticLockingEnableParentLock.
Select the check boxes to set the value to True.
Save the application settings.
Enable simultaneous work on your top-level case types.
In the navigation panel, click Case Types and select the case in which you want to enable simultaneous work.
Click the Settings tab.
Click
.Click the Advanced tab.
Select Allow multiple users.
Select the option Lock parent case when an action is performed on the case to ensure that there are no data integrity issues when two users work simultaneously on two cases from the same parent (for example, Local KYC cases).
Save the application settings.
- Optional:
If there are conflicts during the resolution of assignments, the system uses the pyShowConflict section (included in the pyCaseHeaderOuter section). If you have customized the default perform harnesses, you should update them and ensure that this section is included. The harnesses are:
- PegaCLMFS-Work.Perform
- PegaCLMFS-Work-Requirement.Perform
- PegaCLMFS-Work-Requirement.RequirementHarness
Previous topic Know Your Customer Engine Next topic Application performance