This streaming tool ensures that the substream is started within the designed stream.
SubFlow view within Flow tools
How it looks on white canvas
Features
Text: The name of Subflow is changed from this field.
Module: As a sub-flow, it is selected in which project the flow will start.
Sub Flow Mapping: Within the selected project, there is a flow and a selection of documents to which this flow is connected. In the form fields in this document, the information on the main flow should be selected.
In order for these selections to come, for each flow - for the flow to work under normal conditions - the relevant form must be selected from the Document flow element.
After the project is selected, the fields on the connected form will appear in the Sub Flow Mapping field. These fields are located in the Field section. In the Value field, the values in the main flow will appear.
After the selection is made, red notches should appear in the Value boxes. Otherwise, the selection will not be saved.
Example Usage:
There are two separate form pages and two separate flow processes in two different modules.
Main Form:
The form page named Product Request is the main form page. After the user fills in the information here, he is asked to start the flow by pressing the Save, Send for Approval button.
A new module and form page is created. The form page and fields are as follows.
The flow processes within the two modules are different from each other. At this point, after the flow in the Main Form has started and the desired flow steps have been carried out, the flow process on this form page should be activated.
The flow process on this form page is as follows.
After making the necessary arrangements regarding this flow, the flow is shaped by returning to the main module.
After the document is saved on the form page through this flow, the 1st Supervisor goes for approval. If the 1st Supervisor approves the incoming document during the approval process, the flow in Sub Flow becomes active. The 2nd Supervisor can reject or approve according to the response given to the flow on Sub Flow. After confirmation, the DB Query runs and the flow ends. If the 2nd Chief rejects the flow, the flow ends directly.
SubFlow result varies according to the termination parameters in the downstream. In other words, the options on the arrows will change according to how many termination states there are in the substream.
After all operations are performed, the stream is saved.
The client screen is displayed. And a record is thrown for the main form made.
After the registration is discarded, the first approval process is completed (the user approves the document). And then the flow continues with the next step. The next step is to switch to the Sub Flow element. If desired, the flow chart can be viewed by clicking on SubFlow on this screen.
The view of the subflow chart that opens in a new window when the SubFlow element is clicked
This window is closed with the x button at the top and the previous window is returned.
After the whole flow process is completed, the Work Flow chart will look like the one below.
The Flow Movements on the side tab will appear as follows.
