2.2.4 Configuration of the flow
Navigation Platform allows you to create a flow that has a maximum of three branch destinations for a branch. When you use Branch Nodes in a flow, pay attention to the following points:
- The results of input and selection performed when the flow is displayed for the first time are held
-
The Guide Parts associated with a Process Node hold the values that are input or selected first for the Guide Parts. In a flow including a Merge node, when a previously displayed Process Node is displayed again (by way of a different route), the Guide Parts associated with the Process Node display the values they displayed previously.
To vary the value displayed by a Guide Part according to a condition, you need an I/O Plugin. Request the developer to create an I/O Plugin that varies the value to be displayed according to the condition.
- Precaution for the flow configuration that can form a loop
-
If you create an Operational Flow that can form a loop by using Branch Nodes, the problems described below might result. We recommend that you create a flow that does not form a loop.
-
When a user tries to transition to a Process Node that the user has previously transitioned to by clicking in the Operational Content Execution Window, the user cannot find the previous route of transition (executed processes).
-
If a flow that can form an infinite loop is operated, Navigation Platform operation slows down.
-
- Setting to print a flow in order of processes
-
A flow is printed in ascending order of Process Node IDs. To print a flow in the appropriate order, Process Nodes must be placed in the flow in ascending order of their IDs.
For this reason, create a flow with prior consideration to Process Node IDs, or review Process Node IDs after determining the configuration of the flow.