Workflows

In this section, you can define flows based on events generated by partition actions (e.g. completing Price List calculation) or by IM instance. 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. 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.

Examples of use:

• Trigger a Data Load to save prices to a price history table after an LPG recalculation.

• Trigger emails or other notifications when certain data or types of data are received.

• Integrate a data file into Product Master, trigger truncation, trigger Data Load to to Product Data Source, trigger update to add new products to LPGs automatically or update a Company Parameter and send a notification that new products were added and need attention.

• All of the above can also be done using an IM route which calls REST API and runs any required operation.

To see this section, you need to have the Partition Event Orchestration - use permission.

This section consists of three parts:

Workflows

Shows a list of existing workflows and their basic details. In the row menu you have the options to edit or delete the workflow.

Open

Running Workflows

Shows a list of currently running workflows and the status of each listener (step) – active, queued, executed. In the row menu you have the options to manually stop the workflow or restart it from the last executed step (useful in case of a stuck workflow).

Open

Workflow Log

Shows log entries for event workflows (event-orchestration). You have the option to use ELK queries (and save your own), set up a time filter and define which columns should be visible on the screen.