[PEGA 7.1.6] Why is Work Object Lock at Session-Level and Not Operator-Level?
Hello
The client has the titled question, as it seems having the lock at the session-level requires the operator to perform one additional click "End Other User Session" when another session of the same Operator ID has the lock, but provides no other benefit. Is their observation correct? Why is the lock at the session-level and not just at the Operator-Level?
Thank you!
Fran
Accepted Solution
StaidLogic
IN
Hi,
I believe below might be the reason for this.
- Update to Work object through browser are local to session till it is submitted to server and saved.
- By locking case by session, it prevents same case being submitted with different sessions.
- If it is locked by operator,one operator can open same case with many sessions at a time.
If one session details are submitted, making it a conflict for other sessions (like assignment not found..etc)
So locking of case based on session / requester is more appropriate than operator.
Hope it hepls.
Thanks,
Ananda Bhat
Pegasystems Inc.
IN
Hi Fran,
Can you please take a look in the below post. I find this similar to your query. Hope it answers.
Thanks,
Madhuri
Pegasystems Inc.
JP
Hi Madhuri,
This explains an issue with the Release Lock Button, but does not provide any information regarding why the locking is at the Operator-Level versus the Session-Level.
If you can assist with my question that would be greatly appreciated.
Fran
Virtusa
AU
Hi Fran,
Locks are held by a requestor (operator/system). When a user signs off, the locks held by that requestor are released.
However, locks are not released when a user closes a browser session by clicking the Windows close icon (rather than by logging out). This is designed keeping in mind, that the locks may be needed by another Thread of the same operator, or by another operator or a process.
Hope this helps!
Thanks,
Madhuri
Blue Rose Technologies GmbH
BE
Hello Fran,
This article will give you the information in detail why we keep work object level at session level.
Please let me know if you need further information.
Thanks,
Akshay
Pegasystems Inc.
JP
Thank you all for your replies, but I still do not see an explanation of why the lock is at requestor level and not operator level? Who made that design decision and why?
Accepted Solution
StaidLogic
IN
Hi,
I believe below might be the reason for this.
- Update to Work object through browser are local to session till it is submitted to server and saved.
- By locking case by session, it prevents same case being submitted with different sessions.
- If it is locked by operator,one operator can open same case with many sessions at a time.
If one session details are submitted, making it a conflict for other sessions (like assignment not found..etc)
So locking of case based on session / requester is more appropriate than operator.
Hope it hepls.
Thanks,
Ananda Bhat