For the Simplified Chinese translation, click 中文译文.
Actions provide the actual microflow actions of the app service. Once an app service version is set to Consumable, its parameters and return type are no longer editable, as they are part of the app service contract.
In the General tab, you can set the microflow that corresponds to the action. When the microflow is set, the Parameters tab will be filled automatically.
An action page has the tabs below.
This is the name of the action the consumer will see in their toolbox.
This is the icon that belongs to the action. An icon can be selected from any image documents in the app. A new icon can be added to an image document if it is not available yet.
This defines which microflow will be executed when this action is called.
This describes the action. The consumer will see this description in their overview.
3.1 Microflow Parameter
This defines the name of the parameter in the microflow.
This defines the type of the parameter.
3.3 Can Be Empty
This defines whether a value can be empty as an input parameter.
3.4 Action Parameter
This defines the name of the parameter in the app service action call. This is initially copied from the microflow parameter name, but it can be modified. There are three reserved parameter names that are not allowed to be used:
- appservicelocation (case insensitive)
3.5 Exposed Attributes & Associations
A button is available for complex types (for example, an entity from your domain model) in order to define whether to include the attribute in an entity as well as to define whether an attribute can be empty as an input.
4 Return Type
This defines what kind of object will be returned by the action. This can be a simple type (like an integer or string), or a complex type (for example, an entity from your entity model).
4.1 Can Be Empty
This defines whether the return value can be empty.
For example, an empty ReturnObject is disallowed here: