Action
The action editor within the class designer allows the user to customize their actions. This section introduces the process to create an action, and provides in-depth information about its properties.
Last updated
The action editor within the class designer allows the user to customize their actions. This section introduces the process to create an action, and provides in-depth information about its properties.
Last updated
An action defines what kind of activity a user can execute on a class or an instance of a class.
Starting in the Class Designer, click on the down arrow on the left side of the class you wish to work on. Next, expand the Actions for the class. Go to Add new action and enter the name of your action. Press Enter to open the action editor.
Clicking on an existing action opens it in the action editor to allow changing its configurations.
The Common section contains general properties of an action. In this section, you can specify how the action is presented in your application by setting the name, description and other information.
The internal key is a unique identifier for your action and defines the name for your action in the database.
The Internal Key field is compulsory when creating a class.
The action name is a user-friendly name to help users easily identify an action.
The Name field is compulsory when creating a class.
The action description provides additional information that can be used as help text.
An action can be defined as valid in two scenarios only.
Class: The action can be executed outside an instance of the class (e.g. Filter operation) Instance: The action can only be executed within a concrete instance (e.g. Save operation)
This setting defines whether the action is visible in your application or not.
Similar to classes and fields, action configurations and data are stored in the database. The Mapping section defines how actions are identified and used on a database level by the platform and your application.
The mapping key defines the exact name under which your action is saved in the database.
The Key field is compulsory when creating a class.
The result data type defines the type of the return value. It mainly describes the value of an action that the source adapter can perform.
For instance, a Download action would have the File result data type.
Furthermore, the action can return a list of values by setting the Result Is List checkbox to true.
This feature is used especially in the context of source adapters. For more information on Result Data Types, see our Source Adapter documentation.
Parameters can be used to request information for direct storage in the corresponding class fields when the NEW action is executed.
It is important that the parameters have the same key as the respective field.
In the advanced section of an action, you can further customize the flow of an action by defining what happens before and/or after the action is executed.
This property allows you to specify a confirmation question that will be displayed to the user before the action is executed. The user has to confirm the dialog for the action to proceed.
For instance, on a Delete operation, it would make sense to set the Before Execute Question to a confirmation message like: Are you sure you want to delete this object?
In some cases, an action flow may require it to be followed by other actions after execution. This can be specified in the Post Action property.
For instance, Open an instance automatically after the Create action has executed.
In this section, you can define an additional business logic that must be executed before or after the execution of an action. This is done by creating new scripts.
Create and Open Pre-Execute Script: Allows the creation of a script that runs before the action. Create and Open Post-Execute Script: Allows the creation of a script that runs after the action.
Scripts can be written using the script designer by clicking on the create script button.
This section deals with specific action read and write permissions for single users or user groups.
More information about permissions can be found in the Rights Designer
