Versions Compared

Key

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

In this section, you can define flows based on events generated by partition actions (e.g. completing Price List calculation) or , by IM instance or by PM. Then you can react to these events by triggering selected logics or calculation flows on a partition or, in the case of integrations, you can trigger a route (of the type direct). This functionality is meant for system integrators to allow them to trigger real time and sequenced processing.

The flows are built using event listeners. These can trigger a process (Calculation Field Set, Calculation Flow, Data Load etc.), a calculation logic on a partition or , a direct route for IMs or another workflow. The listeners can be grouped in a multi-step workflow. Event payload can be used in the triggered calculation logic. The action (which generates events) can also be scheduled for a specific time or frequency.

...

Column

Description

Workflow

Lists all the workflows that are currently running. Users You can use the search box to filter specific workflows by name. In parentheses, you can find the Target information – where the workflow is running (a partition or an IntegrationManager instance).

Description

Provides a brief description of each running workflow.

Status

Allows users to filter workflows based on their current status using a drop-down menu. Displays the status of each listener (step) – active, queued, or executed.

Last Run

Shows the date and time when the workflow was last executed. Users can filter workflows by specific run dates using the search box.

Created At

Displays the date and time when the workflow was initially created. A search box is available to filter workflows by their creation date.