Back Forward timeout

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

PRPC 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/PersistUNP 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.

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.

Definitions lock, prconfig.xml file
Related topics Understanding passivation and requestor timeouts
About Access Groups
About Authentication Service data instances
About the System data instance

Up Definitions — T