Microflow

3 minutes to read Download PDF Edit

Common Properties

Name

The internal name of the microflow.

Folder

The folder in which the microflow is located in the project.

Concurrent Execution Properties

Disallow

With this property you can specify whether it is allowed for the microflow to be executed more than once concurrently. This applies to all users at the same time.

OptionDescription
FalseIt is possible to execute the microflow more than once concurrently.
TrueIt is not possible to execute the microflow more than once concurrently; the user receives a message or another microflow is executed instead.

Disallowing concurrent execution of a microflow is useful if a microflow would interfere with another running instance. For example, if it accesses a global resource.

Error message

Error message defines the message the user gets when concurrent execution is not allowed and the user tries to start the microflow while it is already being executed.

Error Microflow

Error microflow defines which microflow is executed when concurrent execution is not allowed and the user tries to start the microflow while it is already being executed. When set, there will be no further message shown to the user.

Output Properties

Return type

The return type defines what information the microflow returns. The caller of the microflow will get a result of this type.

Security Properties

Allowed roles

Allowed roles defines to which module role the user must have to be able to execute the microflow.

See also Module Security.

Apply entity access

This property indicates whether entity access based on the current user is applied when performing operations on objects. Applying entity access limits the objects that are retrieved by the retrieve action to only those that the current user is allowed to see. Similarly, to reading and writing attributes and associations the entity access of the current user is applied. If entity access is not applied on the other hand, all operations are allowed and all objects are retrieved.

OptionDescription
YesEntity access is applied to retrieving and manipulating objects. The rights of current user are taken into account.
NoEntity access is not applied.

Default value: No

Usage Properties

Mark as used

You can search for unused items (Ctrl+Shift+F, Search for = Unused items) in the Modeler. Microflows that are only called from Java code will be listed as unused because the Modeler cannot look inside Java source code.

By setting the propery ‘Mark as used’ to ‘Yes’ you specify that the document is used implicitly and the Modeler will no longer list it when searching for unused items.

Default value: No