Flow step properties

All flow steps share a common technical infrastructure and therefore they also share some common properties. The most important properties are explained in the following.

Step ID

Every step may define a unique step identifier - the step ID.

  • The step Id is used to reference a step and is, for example, used in the following situations:
  • The Loginapp UI references a step when a custom UI is configured.
  • The Loginapp Design Kit refers to steps by the step ID to customize the layout specifically for a step or when providing step-specific translations.
  • The goto and dynamic step activation features use step IDs to refer to steps.

Step activation and goto targets

Most (but not all) steps may be marked to require activation. Such steps are only executed if they are activated on another step.

  • A step may define which other steps it may activate.
  • A step may also provide a list of other steps - the goto targets - to which the end-user (or REST client) may jump.

Dynamic step activation and the goto concept are explained in separate chapters.

Conditions and tags

  • Each step may provide two types of conditions:
  • Pre-condition – the step is only executed if the pre-condition is fulfilled.
  • Skip condition – the step is skipped, i.e. not executed, if the skip condition is fulfilled.