Overview
Often times, integration actions that have different purposes are connected to transition/transactions within a workflow. There is no difference to how integration actions work when configured on a transition vs. transaction.
Understanding an Example
Suppose there is a simple form with the following workflow:
The designer of this form wants to send an email to someone when the form is complete. This will require an integration action to be tied to the Complete transition, such that, when this transition is run by the form user, the integration action will run.
For this example, there is already an integration action to send an email that has already been created. This integration action is called "Email Completion (HOUND DEMO)".
The process for attaching the integration action to the transition is as follows:
1) Select the transition that the integration action will be tied to.
2) On the right side of the screen, navigate to and select the 'Integration Actions' tab towards the bottom of the screen.
3) Click on the "+" within the 'Integration Actions' tab.
4) Select the appropriate integration action - in this case, it will be the "Email Completion (HOUND DEMO)"
5) Set values for input parameters (if necessary). Sometimes an integration action may not require any input parameters to run, however, for this email action, there is a parameter for the recipient and the subject. For this example, there will be a constant value mapped for the Recipient and Subject parameters, however, often times this is mapped to either a field in the dialog box within the transition, or mapped to a field on the form which is done using a calculation.
Example for constant value for Recipient parameter
Example for constant value for Subject parameter
In addition, sometimes the user may want to directly use a field from the form instead of using a calculation. In this scenario, the user would click the "Source Field Browser" button from the integration action configuration screen, which will open up the fields from the form. Make sure to switch the context from the transition to the form.
6) Once the input parameters have been mapped (if necessary), click "OK" on the bottom right hand corner of the integration action screen.
7) After the integration action is complete, the 'Integration Actions' tab will be updated with the number of integration actions that are associated with the transition (or transaction). The user will also be able to see the list view of the integration actions.