An action can be in one of four different status:
- End of Life.
When creating an action, it is possible to save it as Draft (1) or to publish it (2) as seen in Figure 12. As the name depicts, saving it as Draft saves the action with the Draft status. Publishing the action sets it to Active.
A Draft Action can be tested, but cannot be used outside the configuration page. However, it can, contrary to other states, be fully edited. With this, the most common flow would be:
1 - Save as Draft.
2 - Test action.
3 - Edit action to correct what was incorrect.
4 - Test action.
5 - Publish action.
Once an action is published, its status is set to Active, and it can no longer be set as Draft. Once it is Active, it can no longer be edited, but it can be used in Studio.
An action can be published straight away when configuring the action (Figure 7).
The action can also be published afterwards, when visualizing the action (Figure 8).
When the action is not supposed to be used, as it will eventually stop working, its status must be changed to Deprecated.
An End of Life status indicates the action may no longer be working correctly.
Regardless, Active, Deprecated and End of Life actions can be configured in Studio and executed from there.
After saving, the action will be listed under the Actions tab (1 from Figure 14) of the custom connection page.
By clicking Action (2 from Figure 14 - Action is just an example), you can access the View Action page (Figure 15). You can edit the action settings by clicking the Edit button, in the top right corner. You can also test the action and publish it (if it's a draft), as shown below.
Updated 3 days ago