Quick-Start Tutorial 1
Here are the steps needed to set up a complete, working ACP workflow. This tutorial assumes you have access to a working 6connect ProVision instance, but if not any other supported service can be used with minor conceptual tweaks.
Step 1: Open up a web browser and navigate to the login screen of the ACP installation. Your username and password will have been provided with your license information, or sent to you by your network administrator. Log in.
Step 2: Once you are logged in, select the “New Workflow” button from the center of the screen.
Step 3: Give your workflow a new name. New workflows are initially named “untitled”, and this name appears in the upper-left. Click “edit” and rename the Workflow “Tutorial Workflow.” Hit “close.”
Step 4: Configure a connector to your 6connect ProVision service. Click the “Connectors” button to the left of the “Save” button in the upper-right corner to bring up the Edit Connectors screen.
From the select box, pick “sixconnect.”
Name this connector “ProVision 1” and supply the URL for your ProVision instance and a valid username and password. Ue the ‘Test’ button to make sure the information is correct. Hit ‘Apply’ and then ‘Close.’
Step 5: Now it is time to add the first step of the Worfklow. From the “Add New Step” form in the main ACP area select the connector we have just made: “sixconnect - ProVision 1”.
The middle box of the form will pull in all the API Endpoint Families for this product. Pick ‘resources.’ The final box will pull in all of the specific endpoints belonging to that family. Pick “Get resources” and click the ‘+’ button to the right of the form.
The new step is added to the main ACP work area. An ‘Output’ step is automatically created below it.
Step 6: Click the blue ‘Get Resources’ step we just created. ACP has read in the API specification for this endpoint and will display forms for required and optional parameters. The ‘Get resource’ API call does not have any required parameters, so none are shown here. All optional parameters are initially set to ‘omitted,’ meaning they will not be included with the API call on this step.
To make this step do something a bit more useful, find the ‘Name’ parameter in the list of optional fields. Change its drop-down from ‘omitted’ to ‘default value.’ This means this parameter will be a constant, defined in the text box which appears to the right. Place the text ‘TLR’ in the box. This configures the API call to pull all the information about the resource named ‘TLR,’ which is the root of the ProVision resource hierarchy.
Step 7: While the previous step has fetched the data we need, we need to configure the Output step to return it to us. Click the blue ‘GET RESOURCES’ header to collapse the first step.
Then click the black ‘OUTPUT’ header to expand the output section. Currently, nothing is configured, and when the workflow is run it will return nothing.
Click ‘Add Parameter’ to add a new field to the output of this Workflow. Change the name from ‘output-param-1’ to ‘id’, and then select ‘Workflow Link’ from the adjacent drop-down. The form expands.
In ‘Workflow Link’ mode the third box contains all the steps of the workflow. You can select parameters from any call to return in the output, either in whole or in part. Select ‘Get Resources → (object).’ Clicking on the fourth and last box will bring up a listing of all the parameters returned by the Get Resources call.
Choose ‘id.’ This will return a single field, which is the id of the resource named ‘TLR.’
Step 8: Hit the ‘Save’ button in the upper-right.
Step 9: Hit the ‘Execute’ button next to ‘Save.’ After the processing timer finishes, a Results section appears with the response object: { "id": "1" }. We have queried the API for a resource named ‘TLR’ and have found that its resource id# is 1.
Step 10: For a more detailed look at what is going on, click on the ‘Preferences’ button between the ‘More Options’ and ‘Connectors’ links at the top of the screen. Turn ‘Debug Mode’ on. Save the Workflow and re-execute it.
This time the Results section expands into detailed reporting of what parameters were sent at each step, what data came back, and what routing path was taken. This will also show you what steps fail. Click on ‘Raw Output’ for the ‘Get resources’ step to see the raw response to our query. This is very helpful for finding errors.