Start nodes

Introduction to start nodes

The start node is the point where cases enter the workflow. A workflow must contain exactly one start node, which should be located outside any scope.

The start node should never be placed within a scope which has a time trigger as this could lead to the time trigger not being initialized correctly.

Available settings for start nodes

The following settings are available for start nodes:

• Path:
  Read-only. The path to the start node within the workflow. Used to reference the start node in scripts.

• Technical name:
  Mandatory. The technical name of the start node.

• Label:
  Optional. The localized name of the start node which is displayed in the case history in the Web Client.

• Description:
  Optional. The localized description of the start node.

• History visibility:

  Mandatory. Defines on which detail levels the execution of the element is shown in the case history in the Web Client.

  The possible values are:

  • Default
    The display of the execution depends on the global setting (see Case history) for the respective activity type:

    • Manual activity or activity with overlay executed
    • Activity executed after escalation
    • Automatic activity executed

    This is the default value.

  • Only high detail level
    The execution is displayed if High is selected.
  • Medium and high detail level
    The execution is displayed if Medium or High is selected.
  • All detail levels
    The execution is always displayed.
  • Hide on all detail levels
    The execution of the activity is never displayed.

• Skip update event:
  Mandatory. Defines whether the case is updated after executing the workflow element. By default, an update event is triggered to update the case. If there is a chain of elements, you should avoid triggering an update operation after every single element. Select this checkbox for all elements except for the last one to update the case only once, after the last workflow element.