Nanoflow Properties
Introduction
This page describes the properties of nanoflows. For details on using nanoflows and nanoflow elements, see Nanoflows.
Properties
Nanoflow properties consist of the following sections:
General Section
Return Type
The return type defines what information the nanoflow returns. The caller of the nanoflow gets a result of this type. For information on possible return types, see Data Types.
List Parameters
This property determines how list parameters are passed to the nanoflow.
The following options are available:
- Shared - adding or removing items in the called nanoflow is reflected in the caller. This aligns nanoflow behavior with that of microflows.
- Isolated (legacy) - the called nanoflow works with a separate list. So adding or removing items is not reflected in the caller. This option is deprecated and will be removed in Mendix 12.
Default: Shared
Common Section
Name
Name is the internal name of the nanoflow. You use this name to refer to the nanoflow in the app. It must be unique within the module, but you can have two nanoflows with the same name in different modules. When referring to the nanoflow, you normally prepend the name of the module to ensure uniqueness and allow you to use nanoflows in other modules.
Documentation
Documentation allows you to describe your nanoflow to make it easier for people to use and modify it.
Usage Section
Mark as Used
You can search for unused items (Ctrl + Shift + F, then select Unused items in the Search for drop-down menu) in Studio Pro. Nanoflows that are only called from JavaScript code will be listed as unused, because Studio Pro cannot look inside the source code.
By enabling the property Mark as used, you explicitly specify that the nanoflow is used and Studio Pro will no longer list it when searching for unused items.
Default: disabled
Security Section
Allowed Roles
These are the module roles the user must have to be able to execute the nanoflow.
For more information, see Module Security.