Parallel User Access for Assignments in a Single Case

General
1

Hi Everyone,
Can we configure the system to allow multiple users to work on a single case by enabling assignment-level locking instead of case-level locking?

2

Hi @Mohamed_Siddiq_N : Please check this for the locking options provided OOTB in Pega.

It allows single user (Pessimistic) and multi user (Optimistic) mode of locking.

Please also note that Constellation apps will behave as Optimistic.

Thanks.

3

Thanks for sharing the details on locking options.

We understand that Pega supports:

  • Pessimistic locking → single-user access

  • Optimistic locking → multi-user access (default in Constellation)

However, in our current scenario (even with optimistic locking), users are still getting restricted when accessing different assignments within the same case, which seems like case-level locking behavior.

Could you please confirm if there is any approach or best practice to achieve true parallel access at assignment level within the same case?

Thanks

4

Hi,

You could try modeling the parallel work as child cases (sub-cases) instead of keeping multiple assignments within the same parent case. In this approach, each child case has its own lifecycle and lock, which allows different users to work in parallel with far less contention than if they were all updating the same case record.

5

With optimistic locking, there should not be any conflict when two users access the same case. If one user submits the assignment, the second user will be required to refresh before submitting. If both users are unable to access the case simultaneously, check the locking strategy under Case Type → Settings to ensure it is configured correctly.

6

Hi @Ramesh Sangili,

Thanks for the clarification.

We have verified that the locking strategy is set to Optimistic, and as expected, multiple users should be able to access the same case concurrently.

However, in our scenario, when one user starts working on an assignment, other users are not able to access different assignments within the same case, which appears to behave like case-level restriction.

7

Hi @Sheeba Elsi Selvaraj,

Thanks for the suggestion—that makes sense.

Using child (sub-)cases to model parallel work seems like a good approach to avoid contention, as each case will have its own locking context.

However, in our requirement, we are trying to achieve parallel processing within a single case (multiple assignments handled by different users simultaneously).