We have a scenario where the users can launch another application from Pega. The user continues to work on the other application for more than 30 mins, when the user returns, the Pega application is timed out as the session timeout is set to 30 mins in the access group. We would like to have the Pega session to not timeout as long as the user is active on the other application. For this, we tried with capturing the event from the other application in Pega and then do a refresh of a lightweight section. This, however, did not work. Even though the section is Pega in refreshed every time an action is performed on the other application, the session timeout is not extended. Therefore, I would like to know on what other possibilities are available in Pega to fulfil this requirement i.e. to extent the timeout session based on some event.
Session timeout is controlled by Requestor idle time and not UI refresh events. A session is extended only when a valid HTTP request tied to the requestor session is processed.
Call a lightweight activity or service. This tiggers an actual server request and resets requestor idle timer.