...
- Enable Rollback: this setting controls whether the workflow immediately halts or rolls back executed steps when it encounters a failure condition, or is unable to find an appropriate Route at the end of a step.
- Debug Mode: this setting controls whether or not detailed debug output is shown at the end of workflow execution within the ACP GUI. It has no effect on execution via API calls.
Connectors
The ‘connectors’ link in the upper-right opens a window which can be used to define, edit, and import connectors to external API providers. In order to use an API service in an ACP Workflow, you must first define a connector to its service.
To edit an existing connector, click the ‘select’ drop-down and pick it from the menu.
To create a new connector, click the ‘select’ drop-down and pick the service type you would like this connector to be.
ACP currently supports the following connector types:
- 6connect ProVision
- 6connect ACP
- Google Compute
- Microsoft Azure
- Amazon AWS
- Kubernetes
You can define your own connectors to services not natively supported by ProVision by using the ‘Generic Connectors’ functionality, described in a later section.
Once you have picked a connector type, the form updates itself with the locations and credentials required to make calls against this service. The ‘test’ button at the bottom of the window verifies whether or not the supplied information validates against the API service, and the ‘apply’ button saves the new connector.
New connectors are automatically added to the current workflow.
The Step Listing
Workflows are represented as a series of steps (see ‘Getting Started 3. Connecting Steps’ from the examples library). Step headers in blue are initiators, and are executed first when the workflow is run.
...