Segment attributes can be made persistent by setting the IsPersistent property to Yes, so that the value is preserved throughout a session from transaction to transaction. For example, the identifier of the current customer being processed can be preserved across a number of transactions.

These attributes are called session data. The values of all session data are saved at the end of each transaction to the session data area of the user, and are restored at the beginning of the next transaction.

Glb.Work is a built-in session persistent attribute that is available for use. It is automatically saved and restored as session data.

By default, all session data is initialized when you connect to a new user session. That is, the values in the session data attributes do not carry over from one session to the next. However, if you set the Preserve Session Data Segment configuration property to True, then the values in session data will be preserved from one session to the next for that user. This does not apply to Component Enabler connections that use an anonymous user. Note that there is a performance overhead with this option.