Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Leonardo Marinho Skubicz Campeol (Leonardo Campeol)
Cognizant

Cognizant
ES
Leonardo Campeol Member since 2018 4 posts
Cognizant
Posted: Jun 6, 2019
Last activity: Jun 26, 2019
Posted: 6 Jun 2019 17:21 EDT
Last activity: 26 Jun 2019 11:00 EDT
Closed
Solved

Locking not working properly

Hi,

I have a requirement to lock a case when it is opened by a user and remain with the case locked unless the same user unlocks it. I have used Pega's built in locking function. Its working properly only sometimes.

When it doesn't work, the case is locked when opened, but the lock is released when the user leaves the case.

I have traced both situations and noticed that, when it works, the trace runs on thread "PS1_Tabthread" and the parameter param.IsDCSPA is set to "false". When the problem occurs, trace is performed on "OpenPortal" thread and param.IsDCSPA is set to "true".

Both situations were tested under the same conditions and seems to happen randomly. I am using Pega 8.1.

***Moderator Edit-Vidyaranjan: Updated Platform Capability***

To see attachments, please log in.
Case Management

Accepted Solution

Posted: 5 years ago
Posted: 12 Jun 2019 5:40 EDT
Arun Kumar Mahanty (Arun_Mahanty)
Pegasystems Inc.
Principal Technical Solutions Engineer
Pegasystems Inc.
IN

If you're into the multi-node environment, then lock caching may cause an issue. Disable it by below prconfig setting

 <env name="database/lockcache/enabled" value="false"/>

You can have a look at below article once

https://community.pega.com/support/support-articles/work-object-lock-released-incorrectly

To see attachments, please log in.
Posted: 5 years ago
Posted: 6 Jun 2019 21:59 EDT
Srinivas B Y (SrinivasB9086)
Optum

Optum
IN

Hi,

Pega OOTB behavior is to release lock of a work object once the user closes it. The application also releases lock after a certain amount of idle time. The idle time can be configured as per: https://community.pega.com/support/support-articles/reagrding-lock-behaviour

To see attachments, please log in.
Posted: 5 years ago
Posted: 9 Jun 2019 21:30 EDT
Srinivas B Y (SrinivasB9086)
Optum

Optum
IN

Hi,

It depends on what stage the case is being accessed by users. Some cases have review stages where it might be possible for another user to access it. You can review the case life cycle of each stage and verify at design level.

To see attachments, please log in.
Posted: 5 years ago
Posted: 10 Jun 2019 2:27 EDT
Ujjwala Ponduri (UjjwalaP)
PEGA
Senior Solutions Architect, Launchpad Provider Success
Pegasystems Inc.
US

Please check if you have configured any custom lock timeout in the Case Type Settings. based on this value of the lock timeout lock gets released. 

To see attachments, please log in.

Accepted Solution

Posted: 5 years ago
Posted: 12 Jun 2019 5:40 EDT
Arun Kumar Mahanty (Arun_Mahanty)
Pegasystems Inc.
Principal Technical Solutions Engineer
Pegasystems Inc.
IN

If you're into the multi-node environment, then lock caching may cause an issue. Disable it by below prconfig setting

 <env name="database/lockcache/enabled" value="false"/>

You can have a look at below article once

https://community.pega.com/support/support-articles/work-object-lock-released-incorrectly

To see attachments, please log in.

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

Pega Collaboration Center 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