This dialog is used to specify which ticket action is used to transition to the subsequent activity. Optionally, a name for this ticket action is stored, which will be displayed to the supporter as the ticket action name during ticket editing.

Both the ticket actions that have been set as permissible in the activity and the connection action will be displayed to the user during ticket processing. The special feature of the connection action is that it triggers the transition from one activity to the next when executed. The tasks of the new activity are now to be processed.

Note: Process activities can also be automatically switched on. This is the case, for example, if the ticket action Receive email or Reactivate order were selected as the connection.

Important: In general, only ticket actions that the user is actually allowed to perform can be displayed in ticket editing. This also applies to the connection actions, which is only displayed in addition to the already allowed ticket actions if the current user is allowed to use them. For example, the Advance Process (Prozess Weiterschalten) ticket action may only be used by supporters, not by end users.

If parallel tickets have been defined in the process, additional conditions can be set as triggers for the connection.

Conditions that can be selected are:

• All tickets completed: All parallel tickets have been finished
• Ticket done: A ticket to be selected has been finished
• Activity reached: The selected activity has been reached.
• Activity left: The selected activity has been exited.

The check of the conditions can be set to Strict, as well as Relaxed. The following applies:

• Strict: The selected condition must be reached as set.
• Relaxed: The selected condition can be overridden if it can no longer be reached by the process.

Note: In case of Activity reached and Activity left, if the process is currently in an activity that is after the selected activity, the condition also evaluates to true.

Example: A parallel ticket is finished before it reaches a specified activity. With the Lax selection, the condition to reach the specified activity is considered fulfilled, since it can no longer be reached. With the selection Strict this is not possible.

The optional editing text is entered in the editing step that the ticket action generates when it has been executed by fulfilling the conditions.