Selecting this option will add a fallback step at the end of the workflow, where you must define at least two people who
will receive the task only if the document is approved by only one person. That one person will be excluded from
this list. Only one of the remaining approvers needs to give their approval before the document is considered approved.
1. Define the steps. See **How to edit steps** below for more information.
1. Click **Save**.
1. Test the set up using the workflow simulator.
1. Describe your changes in the comment section. See **How to use the simulator** below for more information.
## How to edit steps
The procedure below assumes that you are in the **Edit workflow** window. See **How to configure or edit a workflow**
above for information on how to access this window.
A workflow may consist of several steps which can have one or more approvers. You can skip a step under specific
circumstances. For example, documents with a high amount may require approval by team leader, department manager
and CEO, whereas documents with a small amount only require approval by team leader.
If you have registered branches in Visma.net ERP, you can also assign specific approvers for a branch.
1. Go to the step you want to edit or click **Add new step**.
1. Optional: Change the **Step name**.
1. Define if the step is conditional. This means if the step can be skipped based on the amount of the document. To activate:
1. Select **Step condition**.
1. Select one of the following options:
- Below the limit
- Above the limit
- Between the limits
1. Select the limit from the drop-down if it already exists. If not:
1. Click **Change the limits**.
1. Click  in the upper part of the pop-up window.
1. Enter a name for the limit and click **Save**.
1. Select the limit name.
1. Click  in the lower part of the pop-up window.
1. Select a currency.
1. Enter an amount.
1. Click **Save**.
1. Click **OK** to close the pop-up window.
1. Choose how the approvers are selected under **Approve Invoices by**.
You can create multiple rules by clicking
. This way, in the same step, you can find approvers in
different ways based on for example amount limits.
This list of approvers
Manual approval
Enter the name(s) of the approver(s) to determine the correct approver(s) for this step. If you enter multiple names,
all the approvers will receive the task, only one needs to approve to complete the step.
Automatic approval
You can choose to automatically approve the document. Automatic approval is always done on behalf of one user with the
correct approver role. However, this user will not receive an email notification, and does not need to handle a task.
Exceptions
Under Exceptions you can add an employee at the left side that should have different approver(s) than those specified
under the general rule. At the right side, add the approver(s) for that employee.
Any approver with this cost unit role
Uses the set up of the Cost units to determine the approver(s).
First make sure that you have set up the Cost units with valid combinations of cost units in the approval
hierarchy, and with the specific roles used to determine the right approver in each step of the workflow.
Then select the approval role from the drop-down to select the correct approver(s) for this step.
The nearest manager
Uses the manager defined on the employee in an integrating service such as Visma Lønn. You can see this setup in
the Managers window in Approval, but the set up must be done in the
integrating service.
The department manager
Uses the approvers assigned to the department in the Departments window.
First make sure that you have entered the departments in the service you are sending documents from.
Then assign approvers to the departments in the Departments window.
The project manager
Uses the project manager assigned to a project within Visma.net ERP. No additional set up within Visma.net Approval
is required to select approvers using the project manager.
Any approver with this project unit role
Uses the set up of the projects to determine the approver(s).
First make sure that you have set up the projects with valid combinations of project units in the
Projects window,
and with the specific roles used to determine the correct approver in each step of the workflow. Then select the
approval role from the drop-down list to select the correct approver(s) for this step.
Any approver with this role
Uses the approver as defined with the roles in an integrating service such as Agda PS.
Any approver with this organisation unit role
Uses the Organisation chart that you create in an integrating service such as Enterprise HRM to determine the
approver based on the organisation unit and the role.
1. Select if **This rule depends on amount limit** if you want to skip this rule based on certain amounts.
See the instructions under step 2 in this list for information on how to do this.
1. If available: choose whether you want to **Approve the lines**. If selected, documents with multiple lines can be
approved by different approvers, based on the cost units entered on the lines. If not selected, approvers are
assigned at document level.
1. Choose if you want to **Block the document when no approvers are found**.
If selected, the document will become blocked if no approvers are found. If not selected, the step is skipped if
no approvers are found. Please note that a document will always become blocked if there is no approver for any of the steps.
1. If available: choose if you want to **Allow editing and re-approve changes**. If selected, the approver can edit
basic information of the document without having to reject the document. You need to decide whether or not changes
must be re-approved by earlier approvers in the workflow. You can also choose to let the approver
decide whether or not the changes should be re-approved.
### Other actions on steps
- Click the **Delete** icon on a step to delete the step. The last step of a workflow configuration cannot be deleted.
- Click the **Delete** icon on a rule (next to approve document type by) to delete only that rule. The last rule in a
step cannot be deleted.
- You can use the arrows on the right hand side to move steps vertically and change their order (drag and drop).
- You can use the arrow on the left to expand/collapse the step. Collapsing steps make it easier to move them.
## How to use the simulator
The procedure below assumes that you are in the **Edit workflow** window. See **How to configure or edit a workflow** for
information on how to access this window.
The simulator is used to test different scenarios before activating a new/changed workflow or to troubleshoot if
documents arrive in a **blocked** state. All steps below are optional.
You can choose which fields you want to use to test your scenarios. The following fields are available:
- **Submitter/Requester**: Add the name of the user that submits the document.
- If available, **Exclude the requester from the approvers**: When approving for example expense claims, the approver
may not be the same as the person sending in the expense claim.
- **Amount**: Enter the amount of the document. This is important if you skip steps or choose specific approvers based
on the amount of the document.
- If available, **Initial approvers**: Add one or more initial approvers that should approve the document before the
actual workflow starts.
- If available, **Branch**: Select a branch to verify that the correct approvers will receive the documents for that branch.
- If available, **Cost units**: Enter different cost unit combinations to verify that the correct approvers receive
the document for approval.
- If available, **Departments**: Enter the department to verify that the correct department manager is set up.
- If available, **Projects**: Enter different projects to verify that the correct approvers receive the document for approval.
Click **Simulate workflow** to run the simulator and check the output. Click **Reset simulator** to empty all fields
and start a new simulation.
## How to use the Workflow history
You can access the **Workflow history** table the **Workflows** window, either by clicking the **Workflow History** button
(for the history of all workflow configurations), or by clicking the three dots next to a workflow (to see the
history of just that workflow configuration).
The Workflow history is used to store all the changes done to the available workflow configurations, grouped per
document type.
You can choose to view all document types or choose between the available document types.
Close the table when you want to go back to the **Workflows** window.