...
| Table of Contents |
|---|
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.
...
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“2.id” id” will select the third item’s “id” parameter.
Workflows Executing Workflows
...
For example, imagine a situation where a Workflow integrates between some 3rd party billing software and customer information stored in 6connect ProVision. A simple workflow might accept user credentials (user names, account numbers, etc) and then verify them with ProVision, the billing software, or both. This simple workflow would return the user object on success, but an error on failure.
...