Question
Infosys Limited
IN
Last activity: 11 Jun 2021 22:31 EDT
Understanding Object Locking when the browser closes abruptly
We have a report for the Manager where he will be able to see the amount of time spent by each user on a work object. For calculating the amount of time, report definition uses difference of CurrentSystemTime - pxCreateDateTime based on the condition that pxExpireDateTime>=CurrentSystemTime.
We noticed that sometimes the Manager is able to see the amount of time the user spends on a work object exceeds 30 mins.
Upon analysis we found the following -
(1) Browser is closed abruptly by user without logging off from the Pega application.
(2) when user session is idle for more than certain permitted time.
Scenario-User opens a work object and then abruptly closes the browser. Now when the manager opens the dashboard he is able to see that the particular user and the amount of time he has been on the work object despite the fact that the user has already closed the browser session. After 30 mins, the manager dashboard does not show the user and the work object due to default locking but, when the user opened the same work object after 40 mins, the manager is again able to see the user and the work object except this time he can see the time lapse property contains 40 mins. We traced the session which helped us understand when the user opened the same work object the pxExpireDateTime property is updated. Since the pxExpireDateTime is getting updated, it satisfies the condition in the report definition leading us to this scenario.
We have a report for the Manager where he will be able to see the amount of time spent by each user on a work object. For calculating the amount of time, report definition uses difference of CurrentSystemTime - pxCreateDateTime based on the condition that pxExpireDateTime>=CurrentSystemTime.
We noticed that sometimes the Manager is able to see the amount of time the user spends on a work object exceeds 30 mins.
Upon analysis we found the following -
(1) Browser is closed abruptly by user without logging off from the Pega application.
(2) when user session is idle for more than certain permitted time.
Scenario-User opens a work object and then abruptly closes the browser. Now when the manager opens the dashboard he is able to see that the particular user and the amount of time he has been on the work object despite the fact that the user has already closed the browser session. After 30 mins, the manager dashboard does not show the user and the work object due to default locking but, when the user opened the same work object after 40 mins, the manager is again able to see the user and the work object except this time he can see the time lapse property contains 40 mins. We traced the session which helped us understand when the user opened the same work object the pxExpireDateTime property is updated. Since the pxExpireDateTime is getting updated, it satisfies the condition in the report definition leading us to this scenario.
We would like to know if there is any fix for the above mentioned scenario.
Bluevoir
IN
My suggestion would be to configure idle session timeout or default locking timeout. A user session should get timed out if kept idle for 5 minutes.
This will release all the locks held by that user or alternatively, you can decrease the default locking timeout at the case level to some smaller value as the default is 30 mins.
Let me know your thoughts on these.