timeout

A timeout occurs after an interval of inactivity. When a timeout occurs, various system resources are conserved to make them available to others.

Pega 7 enforces various timeout intervals as follows:

Saving requestors after access group, portal, and requestor timeouts

When a requestor session ends because an access group, portal, or requestor timeout setting was reached rather than by a logging off, the results depend on the value of the Initialization/persistrequestor/ setting in the prconfig.xml file or Dynamic System Setting. The system can passivate (save) the requestor's state and clipboard, allowing the processing to resume later. The system may challenge users who have not sent input during a period, forcing them to reenter an Operator ID and password.

See Understanding passivation and requestor timeouts.

Timeouts and custom authentication

If you implement authentication through an Authentication Service feature, you can replace the fixed authentication timeout interval with an algorithm of your choosing, defined through an activity.

Displaying a timeout alert

Pega 7 provides a standard section, pxSessionTimer, that you can include in a portal harness and configure by setting the TimeOutTime and TimeOutWarning properties. You also need to set the RedirectOnTimeout When rule to True to activate not just the alert, but the correct behavior (ending the session and logging the user out) when the value of TimeOutTime is exceeded.

When pxSessionTimer is included in a portal harness, and the value set in TimeOutWarning is exceeded, a modal dialog appears to alert the user that timeout will occur due to inactivity. A countdown display shows the time until timeout. The user can reset the clock by clicking an OK button included in the section.

Related Topics IconRelated terms