Introduced in version: 1.3 (29 Jan 2020)
Microflows that are used as sub-microflows and microflows that are used for unit tests are examples of microflows that do not need and should not have permissions.
Non-compliant example:
Assuming that the microflow is only used as a sub-microflow:
Compliant example:
Assuming that the microflow is only used as a sub-microflow:
How to solve this violation?
When you are working on solving this violation, but you get a message in Studio Pro that states that the specific microflow does need permission, make sure that you have applied the correct naming convention:
– If the microflow is used directly from a page, the microflow should not start with SUB. Read through our documentation to select the correct naming convention for the function of your microflow. If you use the microflow both from a page and as a sub-microflow somewhere else in the project, we advise creating a microflow that calls the sub-microflow, and that you handle the permission there.
– If a sub-microflow is also called from a nanoflow, we recommend 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. Read more about this naming convention here.
– If the specific microflow is used from the project navigation, we recommend changing the prefix to Nav_. Read more about this naming convention here.