In OutSystems Platform a Session is created after the first request the end-user establishes to the OutSystems server and allows to keep context during the end-user navigation. The session consists in the set of session variables defined in the eSpaces the end-user accesses during its interaction. The session variables can be used when you are implementing the business logic of your eSpace, for example, in user-actions, screen preparations, and screen actions.

The session is created on the server and can be shared by several eSpaces if you are using the Single Sign-On feature that enables an unified view of users and sessions by a set of eSpaces. See Single sign-on.

Session lifetime

The session begins on the first request of the end-user and ends explicitly when that end-user logs-out or automatically due to a session timeout. There are, however, some details specific to the channel used for the end-user interaction. Learn more about OutSystems Platform Session Lifetime.

When the session is created, in a Web, Mobile Web, or SMS interaction the On Session Start system action is called. See On Session Start.

Session time-out

The session time-out is a predetermined period of time during which the session exists without any user-interaction. This means that if during this period, after the last request, there is no user-interaction, the session ends.

In OutSystems Hub Server it is not possible to trap the session time-out event.

The default value for the session time-out depends on the application server:

Sessions in Consumer and Producer scenario

When a public action from a producer eSpace is invoked in a consumer eSpace, a producer session is created (with all the producer session variables) inside the consumer eSpace to keep its values between invocations. See Consumer and Producer eSpaces.

See Also

About session variables | Use cookies