Flow configuration is done in two places in the Configuration section:

Calculation Flows

In Configuration > All Modules > Calculation Flows, you configure the flow engine itself.

The selected flow in the screenshot above has three actions (Flow Items), all of them are periodic and the repeat interval is defined by the Time Unit and Number of Time Units fields. The Time Unit can be: day, hour, minute. The Logic Name field identifies the logic which should be executed. The Target Date determines, which calculation logic and Company Parameters will be used for the calculation (based on their 'valid after' date).

Once the flow is deployed and successfully executed, it disappears from the list (only Drafts or flows with Flow Items with Periodic selected remain). The flow items are executed in the order that is displayed. If the items have not reached their “due date”, they are skipped. Only one flow at a time is executed.

If the calculation flow is executed and ends up with an error, it is rescheduled automatically. You can check the flow's execution status on the Job/Task Tracking page. The calculation flow can be identified by its name and typedId.

For more information on scheduling & prioritization of calculation flows and other advanced topics, see the subsequent section Managing Calculation Flows.

Calculation Flow Logics

In Configuration > All Modules > Calculation Flow Logics, you define the logic that should be executed by the flow engine.

When you select a logic and click the View/Edit Details icon, the following screen opens:

When defining a calculation flow logic, you can use any number of elements. In every element, there is a binding variable named 'actionBuilder' and through it you can specify which actions should be performed.

To help you with the action API, there is a section in Command Templates called 'Calculation Flow Examples'. For each action you can use, there is a menu item (CFS Action, Pricelist Action etc.).

In each menu item you have two possibilities:

• Full – Shows the action API example in the code editor.

• UI Helper – Shows a popup window which guides you through the definition of the action. UI Helper differs by the action type but usually consists of two panes: at the top you can choose on which object(s) you act on and then the bottom pane displays a fully working action you can copy and paste to the logic editor.