Action Steps in the Action Editor
Action Steps define the flow of an Action. Using Action Steps, you can add functionality to your application, such as:
- Conditions (e.g. if a task is changed to a particular status, send an alert)
- User Alerts (e.g. send email notifications, or display on-screen messages)
- Searches (e.g. find all task records that are associated with a specific project record)
- Set Values (e.g. create a new task directly from a project so they are linked)
- Actions across multiple applications (e.g. retrieve data record from the Order Management application and update record in the Inventory application)
- Scripting (e.g. extending business logic by adding your own XML coded action steps into the process flow)
The table below describes the different Action Steps that an Author can use to define custom Actions.
Action Step |
Description |
Usage |
 |
Allows alternative paths to be taken in the action process based on a specified condition. If condition A is true, perform B, else perform C |
If City = San Francisco, then calculate the Sales Tax using 8.50%. If Project Status changes to "High Priority" trigger an e-mail alert to Project Manager |
 |
Allows a series of steps to be executed repeatedly while some condition remains true. While condition A is true, perform B |
Perform a calculation to update the inventory available on an item included in an order until all the line items in the order have been accounted for. |
 |
Allows a series of steps to be performed on each record returned in a set of search results. |
Update the Status of each Task record that is associated with a selected Project record. |
 |
Allows an exit from a loop or entire Action flow with a message to the user. |
Prompt a message to the user that a mass update of records has been completed. Ask the user to complete certain fields before the Action can be performed. |
 |
Allows a separate action (potentially on a different collection or different application) to be executed. |
After changing the status of tasks associated with the selected project record, save the changes. |
 |
Allows the searching of a collection for one or many records based on some criteria. |
Find all records created by the current user. Find all Lead records that are associated with a specific Account record. |
 |
Allows interaction with users via a notification or a work item request. |
In a Project Management application, if a new task is created, send an email to the person assigned to complete it. |
 |
Allows the manipulation of data within the action scope, e.g. transferring information from one record like a Sales Order to a different record such as an invoice. |
In an Order Management Application, an Action can be defined to create a Sales Order from the Items Collection. To achieve this, information about the Items (i.e., name, description, unit cost) can be populated into the Sales Order record. |
 |
Allows the addition of XML coding to extend the business logic of an application. |
Use XML to execute complex application logic. |
Adding and Removing Action Steps to the Action Process
- Click and drag an Action Step from the Action Steps palette and drop it on the Action Canvas. The location you drop the action step will determine where it will appear in your action process. Every action must start with the green Input arrow and end with the red Output arrow.
- To remove an action step from the action canvas, place your mouse over the action step so that it is highlighted. You will see a red X icon at the top right of the action step's icon. Click on the X to remove the action step.
To get information on how to define and use a specific type of Action Step, select a topic below.