Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Aim of this section

Shows how to create or edit an event workflow. 

Related sections

Event Workflows (Reference Manual)

Required permissions

Event Orchestration - use

...

  1. Click Add Source Event.

  2. Select Source Type (either Partition, Integration, or PFM) and Source Name (specific partition or IM instance). 

  3. Select which Event Type should trigger an action.

    1. At a partition, not all events happening there are supported, so always check out this list here first. 

    2. For integrations, only custom events (intentionally emitted by custom code in a route) can be selected.

  4. Optionally apply a Filter to the event records. It can be a multi-expression. Use a JSONPath value in the Parameter field. The JSON can be different for each use case—see the log to find out the correct values, for example $.jobName, $.trackerType, $.status.
    Example of the filter expression:

    filters01 .png

Skip Event

Here you can define specific events that allow workflows to bypass certain steps under predefined conditions.

Skip Events have a higher priority over standard Source Events, meaning that if a Skip Event is triggered, it will override any other events for that specific step. Skip Events follow the same structure and format as Source Events.

When a step in a workflow receives a Skip Event:

  • No Action Triggered: The step will not execute any associated actions.

  • Pass-Through to Next Step: The Skip Event passes to the subsequent step in the sequence.

  • Condition Fulfillment Check: For the next step to proceed, it must fulfill the conditions of the initial event in the Source Event section; otherwise, it will also be skipped.

You can:

  • Start a workflow with a Skip Event: Allows you to define conditions where the workflow starts, but certain steps can be immediately skipped.

  • Skip multiple steps: Each step evaluates the Skip Event condition, if met, the step will not execute and will be passed over, continuing the workflow without interruption.

  • Finish a workflow with a Skip Event: Ends a workflow when triggered. If the Skip Event condition is met, the workflow will bypass any remaining steps and finish.

Adding a Skip Event
  1. Navigate to Skip Event settings: Within the listener configuration, go to the Source tab and click Add Skip Event.

  2. Define Source Event parameters:

    • Source Type: Choose the type of integration, partition, or PlatformManager (PFM)

    • Source Name: Select the specific source instance.

    • Event Type: Specify the event type.

  3. Apply Filters:

    • Use filters to further define the conditions under which the Skip Event will be triggered. Set Parameter and Value pairs as needed.

Source Events Combination Logic

...