Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Unable to release lock of other user

SA-46436

Summary



User A is working on any case, and closes the browser without logging off.

Now, when the user B tries to open the same assignment where the user A has left, user gets a message saying "WO is being locked by other user".

So, the user is performing "ReleaseLock" which internally deletes the entries from sys_locks table and the expectation is when the user B opens that work object/assignment, then they should be able to do it.

But system gives message as requestor lock is been held from other session that is, by user A.


Error Messages



RequestorLock is still held on the work item.

Cannot obtain a lock on instance A-B-C, as Requestor H6DB31999395604CA68D015D536552B13 already has the lock.

Steps to Reproduce



1.Login with user A and open a work object in perform mode.
2.Login with user B.
3.Run "ReleaseLock" activity to release the lock on the work item that is held by user A.
4.Observe that though the entry from the System-locks table is removed, the lock is still held by the requestor.


Root Cause



This is an expected behavior and works as per the design.

Resolution

Release Lock button does not completely release the lock though there are no entries for that assignment in pr_sys_locks table as the requestor would still have the soft lock on it.

However, it is suggested that one user shouldn't release lock of other user as this might cause inconstencies in the assignment processing.

Hence it is suggested to implement the below as per the requirement:

1. Include optimistic locking enabled for the work objects. For enabling this feature, one might go to case type rule and in Advanced tab, select locking.

Now provide optimisitic as the case locking mechanism. Default case locking is something where when one user is working on the case, other user is not allowed to work on the same case and is provided with a screen saying "Work object is been modified by user A".

And optimisitc locking is mechanism which is most likely on "first come first serve", where both users get a chance to work on the work object parallely and the user who clicks on "Submit" (finishes the assignment) first obtains the lock.

Suppose userB has clicked on submit first and now user A clicks on submit, then user A is provided with a screen that user B has processed the assignment or the assignment is stale (with a valid message).

2. Create or modify timeout/locktimeout DSS setting to set the value in minutes after which the lock has to be released.

Published November 9, 2017 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us