ACR Rules

⌘K
  2. Home
  4. Docs
  6. ACR Rules
  8. Project hygiene (32)
  10. Sub-Microflows that are used in Nanoflows should be prefixed properly

Sub-Microflows that are used in Nanoflows should be prefixed properly

Introduced in version 2.1 (Released November 3rd)

Since the release of Mendix 8.2, it is possible to call a microflow from a nanoflow. It is a requirement to give these microflows permission. If these are called with the prefix SUB_ you may encounter violations in the rule Microflow should only have permissions if used from a page. To prevent this violation, we advise sub-microflows that are called from a nanoflow to be named with the prefix NSub_

Non-compliant example:

The microflow CalledFromNanoflow_NotOK & SUB_Microflow_NotOK has the wrong naming convention because they are called from a nanoflow

Compliant example:

The microflow NSub_Microflow_OK is correctly named because it’s called from a nanoflow

Sub-Microflows that are used in Nanoflows should be prefixed NSub_

If you want to use a sub-microflow from a microflow AND a nanoflow, you need to be aware of its permissions. In this case, we advise using a special Nsub_ wrapper (with permissions) in the nanoflow that calls the SUB_microflow (with no permission) that is also used as a regular sub-microflow.