Have you tried "Page-Unlock" (method) & "WorkUnlock" (activity) ?

Make sure it is not a best practise to release someone else lock. All the work will be lost which is done by other users & will bringinconsistent behavior

The Obj-Save with write now has a commit built in and you do not need the Commit step. And yes at the end of that activity the lock will be gone as a commit has happened. Be careful as any other locks with derfered saves will also be lost. This is why PEGA frowns upon using commits as it can cause issues in processing when the lock is lost in the middle of processing.

Hi,

Lock held by other user would be soft by 2 hours. After that you can access the work object normally, rt. Is there any specific reason, you want to over ride the lock in between two hours?

Regards,

-Vamshi

i open the wo - left the session - when the lock will be released from pr_sys_lock table automatically - whats the time frame?

some times it stuck in lockCache level. u need to remove the lock in cache level also.

How can we change the Default locking time of 2hrs to 20 mins ?

Refer https://community.pega.com/support/support-articles/reagrding-lock-behaviour

For Requestor timeout can be mentioned at Access Group data instance Access Control section->Authentication timeout -->number of seconds after which the system challenges idle browser sessions.

This timeout event does not cause session context or clipboard contents to be lost.

LockTimeout:- can be mentioned at different levels like Data-Admin-System instance defned under sysAdmin-->System instance

Case type rule you can provide under details tab or under Locking section can provide under input box of