Defining How Your Controls Interact.
The Action Builder is where you define how your Airkit applications respond to input from users.
The Action Builder is unlike other Builders in that is it is not represented in the Builder Bar and instead exists as a subcomponent of the Activity Builder. You can find it in the Inspector, under the Actions tab, but only if you are are inspecting an element associated with an Event capable of triggering actions.
Not every component you can inspect in the Activity Builder will have an Event associated with it. The way users interact with a Label Web Control, for instance, is by reading the contents of Label in their own time; there is no trackable Event. On the the other hand, the way users interact with a Button Web Control is by clicking the Button; clicking is a trackable Event capable of triggering actions. This is why it is possible to access the Action Builder while inspecting a Button Web Control but not a Label Web Control. The Action Builder is accessible only when relevant.
In this document, we will discuss the broad functionality of each component of the Action Builder and provide links to additional resources that provide a more detailed discussion of specific tools provided by it.
Clicking on the'+' button the right of an Event in the Inspector will present you with the Action Menu. The left side of the Action Menu are the categories of available actions. Select different categories to see the different available Actions associated; these will appear on the right side of the Action Menu. Select an Action from the right side of the Action Menu to add it to the bottom of your Action Tree.
For a complete list of the actions you can work with in the Action Builder, check out Available Actions.
The Action Tree is where you can see all the actions that will be performed when a particular Event is triggered. These actions will be performed in the order they are listed. For instance, in the following example, upon clicking the relevant button, the user will navigate to another Web Page, and then a Chat Bot will start:
The Action Tree can contain any number of actions. Actions can be deleted by clicking the trash can icon to the right of the action. Actions can be re-ordered by clicking and dragging the handle at the left side of the action.
The Action Tree also makes it easy to work with actions that are only taken conditionally. Actions nested under conditionals in the Action Tree will be taken only when the condition above them is met, and actions can be dragged into and out of the umbrella of certain conditions as easily as they can be reordered.
The following example show how a simple conditional might appear in the Action Tree. In this example, a Chat Bot starts only if the variable session.timeZone is a certain value; otherwise a Voice Bot starts instead. Regardless of whether a Voice Bot or a Chat Bot starts, the user will navigate to another Web Page. Note how the actions are nested to indicate under what conditions they'll be done:
For more on working with conditionals within the Action Builder, check out The Condition Action.
Clicking on an action in the Action Tree will open the Action Editor. This is where you'll be able to edit the configurations of the selected action.
The editable configurations, and thus the layout of the Action Editor, will vary from action to action. For a more detailed dive into how each action type can be edited, check out the links provided in Available Actions.
Here is a complete list of all the actions that can be added, ordered, and edited within the Action Builder:
- Voice and Chat