Initiator Conditions and Iteration

Initiator Conditions

The 6connect ACP system uses “initiator conditions” as a pre-routing system to determine, based on user-given data, which step is executed first.  This is particularly useful for data unification processes. For example, a Workflow can be configured to accept both a Customer Name or a Customer Id, but if a Customer Name is provided to start at a step which first looks up the Customer Id before proceeding to the main work.  

...

When the workflow is executed each condition is evaluated against the user-given data, from top to bottom, in order.  Once a matching condition is found the Workflow immediately proceeds to the indicated step.

Iteration Options

Each Step has an “Iteration Options” section which can be used to execute a single step multiple times.

...

In the case of a more complicated JSON structure (ex: [ { id: 123}, {id : 321 } ] ), the entire object will be provided to the variable.  If only part of the structure is required, it can be accessed using the same semantics used to navigate JSON trees elsewhere. In the above example “{id: 123}” will be passed to the input by default, but if the input is configured with “id”, then only the value “123” will be selected.  Likewise, if the object contained an array, then “2.id” will select the third item’s “id” parameter.

Workflows Executing Workflows

ACP ships with a self-referential “acp” connector type which is designed to include API calls generated by the ACP system itself.  This connector type can be found from the general list of connector types on the Connectors modal.

...