Log off current user

The Log off current user event action ends the current session after the completion of the current event processing. To be precise, the event action only causes the session to be logged off and not the event processing to be aborted immediately.

• Unless an error with rollback occurs or is triggered by an Abort event action, all data changes to entities (Create, Change, Delete) are still persisted in the context of the session. If there are existing flags via the Save changes later or Delete later event actions, the execution time of these event actions relative to the Log off current user event action has no influence on their effectiveness.
  
  

• If the session is aborted (after an error or the execution of an Abort event action), the session is closed after the associated error message is displayed. If the Process Exception or Semantic Exception error type is selected, a modal dialog appears, without waiting for confirmation before logging off the session. The user may see the dialog flash up briefly, but will not be able to read the message. The errors generated by other error types remain visible in the browser tab even after the end of the session (for a limited time).

►NOTE◄

• In the context of Tests, the session is not logged off. Instead, a notification of the 'Info' (INFO) type appears in Tests and event processing continues.

• If the Form designer is operated in test mode and a Log off current user event action is triggered in the context of triggered Event handling or in a Client workflow, only a notification of the 'Info' (INFO) type appears and the session is retained. However, the test mode is ended after all actions have been processed.

• If a notification is issued during testing, it is issued at the time the event action is executed, i.e. when the flag is created and not at the time of the 'simulated' logoff.
  

  • If the Log off current user event action is executed several times within the same event processing, this usually will not have any effect compared to a single execution.

  • However, when testing, several notifications will appear, which may be added to a chronological series of other notifications at different times.