Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

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.

Adjust time-out settings to reduce locking issues when users do not log off

Updated on May 2, 2019

Summary

How do you end a Process Commander session if a person "logs off" by closing the window rather than by orderly invocation of the Process Commander logoff activity?  We are experiencing locking issues that occur when a user opens a work item, makes modifications, and subsequently closes the window. 

This action keeps the user's session active until s/he either releases the lock or the lock is released by the system.  This normally is not an issue as long as the work object is not assigned to anyone else in the process.  If it is, when the next person tries to open the work item s/he gets message that the work item is locked.  Is there an out of the box solution to address this problem?


 

 

Suggested Approach

Your best approach is to try decreasing the value of the lock timeout specified in the relevant Data-Admin-System instance (typically "WFE").  See field "Lock timeout".  You will need to restart Process Commander for such a change to take effect.  After the time interval that you specify, the locks will go soft so that users still in the system will be able to access the formerly locked items.

Have a question? Get answers now.

Visit the Support 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.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us