Question

6
Replies
462
Views
SOUVIK Mukherjee (MukherjeeSauvik)
Capgemini America INC.
Sr. Solutions Architect, LSA, Marketing & Decisioning Architect, Program Management
Capgemini America INC.
US
MukherjeeSauvik Member since 2007 8 posts
Capgemini America INC.
Posted: September 24, 2019
Last activity: September 25, 2019
Posted: 24 Sep 2019 9:31 EDT
Last activity: 25 Sep 2019 4:33 EDT
Closed

Case Locking Timeout- How far can it go?

Hi, I am looking to see is there any specific recommendation around how far one should go while changing the default case lock timeout from 30 min to more. currently it is set to 3 hrs, but client wants it to be 8 hrs due to the nature of the work processing.

I understand the aforesaid can be taken care via training and all where users can be educated to hit save periodically. However, I am interested to know what could be some of the implications (if any) on DB server and App server if we go beyond this time.

In my opinion, technically, I do not see any issue from Pega perspective per say, neither from DB perspective. However, would there be any significant impact on tomcat other than the fact that if session is active for 8 hours, the memory would be allocated for that requester for 8 hours?

Pega Platform Low-Code App Development Case Management
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.