What locking strategy is set on the Purchase Request case type if both cases lock until submission?

In the scenario described, the locking strategy set on the Purchase Request case type is designed to ensure that only one user can actively work on a case until it is submitted. This means that as soon as a user begins working on the case, the case is locked for that user, preventing other users from making changes or navigating into the case until submission is completed.

Setting the locking strategy to allow only one user aligns with the need for data integrity and consistency during the editing process. It prevents potential conflicts that could arise from multiple users attempting to modify the same information simultaneously. By locking the case, Pega ensures a smoother workflow and reduces the risk of errors that could occur if multiple users had access to edit the same case concurrently.

The other options would imply different behaviors: allowing multiple users would mean that several users could work on the case at once, potentially leading to inconsistent data and confusion. Allowing all users or having no specific locking strategy would not specify any protection against simultaneous edits, which is contrary to the intended behavior of locking cases until submission.