Which locking strategy on the Purchase Request case type disables options on the Purchase Order case type?

The locking strategy that disables options on the Purchase Order case type is one that restricts access to the case. In this context, when a locking strategy allows multiple users, it often leads to a situation where various users can work simultaneously on the Purchase Request, which can create inconsistencies or allow actions than might conflict with the actions taken on the Purchase Order.

By allowing multiple users, you enable collaborative access, which can increase the likelihood of overlapping modifications or conflicting operations from different users. This can render certain functions on the Purchase Order case type inactive or cause them to behave unpredictively since multiple transactions might try to interact with the same data simultaneously.

In contrast, strategies like restricting access or allowing one user maintain control over the actions, ensuring that actions on the Purchase Order case type are systematically executed without interference from concurrent transactions on the Purchase Request. These are strategies that would ensure that options regarding the Purchase Order would remain properly controlled and reflective of the current state of the Purchase Request, thus confirming why allowing multiple users leads to disabled options on the Purchase Order.