After reading this article you will know:
- What an action is.
- What the visual action editor is.
- Which two types of actions can exist in your app.
- What action events and triggers are.
Actions are your app logic, defined in literal actions.
Actions can do just about anything you want in your app. You can create an entire action by adding action events to your action. You can choose between 25 different action events to add to your action, going from a create or update event to http requests (web services) or Pdf generates.
There are two places where you can create actions. The action button in the builder bar brings you to the back-end actions overview. Here you can create all your actions, but you can also create an action in a web page (endpoint). These actions are only visible/editable on the endpoint itself, they will not show in the actions overview. The actions you define in an endpoint are always manually triggered actions, which execute when the endpoint is called upon.
The action in web pages (endpoints) can be considered as manually-triggered actions.
The Visual Action Editor
An action is executed on one object of a model. So you start by choosing the action’s model.
A trigger defines the moment your action initiates. If you want to have a button which a user has to click in order to execute the action, you’ll have to set the trigger to Manual, but if you want an action to execute whenever a new record is created you can set the trigger to after_create. Below we have created an overview of all triggers:
To learn you everything about actions, we’ve made 2 references. The action reference will learn you all about the different settings en possibilities of an action.
The action event reference will tell you all about the different action events: what they are, what they do and how to use them. Please check them out!