Flows How To's
How to's for the Flows guide.
Creating a New Flow
To create a new flow:
- Go to Solution Explorer.
- Right-click on the Flows folder.
- Select New Item.
- Choose Flow from the dialog.
- Enter a name such as
MyExpenseFlowand click Create.
This action creates a new .flow file and opens it in the Flow Designer.
Setting Group Approval with One User Only
- Add a Position Group object to your flow.
- Open its Events tab and find the Approve event.
- Click Condition and select
Number. - Set the Condition Value to
1.
This allows the flow to proceed when a single group member approves, rather than waiting for all.
Sending an Info Message to Flow Starter
- Drag and drop an Information object onto the flow canvas.
- From the Group Content property, add Flow Starter.
- Connect this node after a Reject or End event.
This ensures the flow starter receives a notification when the process is completed, rejected, or revised.
Configure Conditional Routing with Comparison Object
- Drag a Comparison object from the Toolbox to the canvas.
- Set the Source Object to a numeric variable (e.g.,
TotalExpenseAmount). - In the Results popup, click Add and define:
- Comparison Type:
LessThanOrEqual - Constant Value:
2000
- Comparison Type:
- Connect the true path to one position (e.g., HR Group).
- Connect the false path to another (e.g., Department Manager).
This structure enables flows to diverge based on expense total value.
Adding a Revision Event to a Position
- Select the Position object in your flow.
- Open the Events tab from the Property Inspector.
- Click Add Event and select Revision.
- Enable the Reason checkbox to make a reason mandatory.
- Fill in Reason Title (e.g., "Revision Reason").
This allows approvers to send the document back for correction with a stated reason.
Adding an Approval Position to a Flow
- Open the flow file in the Flow Designer.
- From the Toolbox, drag the Position object onto the canvas.
- Configure the
Target ObjectasPosition1. - Set Source Type to
Flow Starter's Manager. - Link this position to the previous node with a connector.
This setup routes the document to the user’s manager for approval.