# Step 3: Create Process flow
### The flow of our process as per our requirements
### Step-by-step guide for implementing the above flow
Using the[ **workflow builder tool**](https://docs.senpiper.com/workflow-builder/introduction) we’ll be able to **mimic the hierarchy** followed in the organization regarding the **business processes**.
#### 1. Initiate a workflow
Go to workflow builder and click "**Add a new workflow**" S**elect the group** and **the form** for which you want to **create the workflow**. Name your workflow "YourName\_ Reimbursement Workflow"
Once you’ve filled in the requisite details, it’ll show you the interface for the workflow builder.
Now proceed by clicking the settings button beside the submit button to add a comment. “**The reimbursement form has been submitted**.” Learn more about the **comments in workflow.**
{% hint style="info" %}
Comments are mandatory in every button of the workflow you create. It acts as a changelog when any workflow action button is clicked.
{% endhint %}
#### 2. **Apply a condition**
> Use case: As we discussed, if the reimbursement amount is **more than 10,000** it’ll be assigned to the **Department Head,** and amounts less than that will be handled by the **Manager**.
* Click the green plus icon and select the yes option for ‘**Do you want to apply any condition**’. Learn more on **how to apply a condition at a step**
* Now to set another condition go back to the ‘**+**’ icon in front of submit button and add the rule "Total Amount" <= 10,000
* The above two conditions **create 2 separate paths** for the workflow based on the "**total amount**" of the reimbursement, the workflow would now look like this.
Now that we have created the 2 paths for different conditions of the workflow. we will proceed with each path
#### 3. Create action buttons in the workflow
* Click on "+" button below the condition box where "Total amount > 10000" to ‘**add a step**’. Each workflow step has the following properties
* Target status
* Action buttons
* Other Actions
* Select the target status for each node as "**submitted**". Learn more about the **target status in a workflow step**
* Click on "**Define future actions**" and add a new action button "**Approve**". Learn more about the **actions buttons**
* And while we do that, we’ll assign the button to the **Department Head**, by selecting **company defined roles** and then **Department Head**.
{% hint style="info" %}
Ensure that the "**department head"** role should be present in the system beforehand and allocated to the right users. Learn more about **custom roles**
{% endhint %}
* Under the section "**form edit settings**". Click on "**manage individual fields**".
* Click on manage fields and select the "**Approval remarks**" fields. Set the following properties
* Visibility settings: **Show to user**
* Edit settings: **make editable**
* Optionality settings: **Make field mandatory**
> Learn more about **managing fields at a workflow step**
Fields state management at a workflow step
* Provide comments on this button under the section "**Comment log settings**".
* Click on "**add a new button"** and add a "**Reject**" button with the same settings.
#### Adding steps for the "manager" role
* Now click on the other conditional node with "**total amount**" <= 10000 and repeat the above steps to add the "**Approve**" and "**Reject**" buttons.
* While creating the buttons on these nodes" choose the company-defined roles as "**Manager**"
{% hint style="info" %}
Ensure that the **Manager** role should be present in the system beforehand and allocated to the right users. Learn more about **custom roles**
{% endhint %}
* Once the workflow action buttons are created for both conditions, click on the "+" icon of each button and select "**no**" to apply any condition.
> We selected no as we don't require further conditional logic in the stated requirements
Individual action button conditions
* Once you click on continue a new step is created. Set the target status for the step accordingly. Following should be the statuses
| Button clicked | Workflow should move to following status |
| -------------- | ---------------------------------------- |
| Approve | Approved |
| Reject | Rejected |
* Repeat this process for other sets of buttons
#### 4. End the workflow
* Now we are at the end of the requirement of process flow requirements, let's close the workflow.
* Click on the define future actions and click on "**End workflow**"
End a workflow
Workflow ended
* Here’s how the finished workflow would look like
To wrap everything up, click apply changes and the workflow configuration is completed.
### Testing the workflow
* Go to the created group
* Add a new submission to the reimbursement form with an amount less than 10000
* Assign the roles of "**manager**" and "**department head**" to two different users. Learn how to [**add roles to users**](/user-management/roles-and-users-for-the-reimbursement-use-case.md)**.**
* Add those users to the group. Learn how to [**add users to a group**](/user-management/managing-users/how-to-add-users-to-a-user-list.md)
* Login with the credentials of the that user
* Once a submission is made the user to whom the manager role is assigned will see two buttons "Approve" and "Reject"
* Click on any button and finish the workflow
* Check the status of the form
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.senpiper.com/digitize-a-sample-process/step-3-create-process-flow.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.