Skip to content

Commit 556561a

Browse files
committed
Adjust the Outcomes section for call microflow
1 parent d1ec1ed commit 556561a

1 file changed

Lines changed: 5 additions & 1 deletion

File tree

  • content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements

content/en/docs/refguide/modeling/application-logic/workflows/workflow-elements/call-microflow.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,11 @@ Parameters of the selected microflow. Depending on the selected microflow, you w
3636

3737
### Outcomes Section {#outcomes}
3838

39-
**Outcomes** depends on the return type and values of the microflow. For example, when there is not return type, you have a single outcome; for the Boolean, you have **true** and **false** outcomes; and for the enumeration – an outcome per each enumeration value and an empty one when the value is unassigned.
39+
The outcomes depend on the return type of the selected microflow:
40+
41+
* **No return type**: The activity has a single outcome and the workflow proceeds to the next step.
42+
* **Boolean**: The activity has two outcomes: `true` and `false`. The workflow proceeds to the next step based on the returned value.
43+
* **Enumeration**: The activity has one outcome for each enumeration value, plus an `empty` outcome for when the value is unassigned. The workflow proceeds to the next step based on the returned value.
4044

4145
### Boundary Events Section {#boundary-events}
4246

0 commit comments

Comments
 (0)