Some condition, activity, and approval nodes may be restricted to Premium or Pro plans. Your company must have one of these plans to incorporate them in your workflow.
Expense approval nodes complement activity nodes in the workflow to perform specific business logic.
The workflow designer includes these approval nodes:
Note: Before an approval node, you need an activity node. After an approval node, you need Need revision, Draft, Rejected, and In review status nodes.
Final approval
Use this node to set up several types of approval flow, depending on what you need.
Technically, what this node does is when multiple or one approver is assigned to a document, when that user approves the document, it clears the list of approvers from the document and moves forward to the next step in the flow. In other words, it lets any approver end the approval flow and move the document to the next step in the workflow.
Use this node with these activity nodes:
- Assign approvers with property: it skips the approvers list, resulting in “any” of the approvers able to end the approval flow.
- Assign custom cost object approvers: it skips the approvers list, resulting in “any” of the approvers able to end the approval flow.
- Assign all custom field approvers: creates an “any” all custom field approvers approval flow, meaning that anyone of the assigned approvers on the custom field values can end the approval flow.
- Assign static approver: it skips the all the approvers on the list, resulting in “any” of the approvers able to end the approval flow.
Cost object approval
Configure a cost object approval flow. Technically, what it does is it takes the approver/list of approvers created by the activity node and sends the document for approval to that user until all users on the list have given their approval.
It is used in combination with Assign all cost object approvers or Assign custom cost object approvers activity nodes.
This node can perform escalation to the parent cost object. This occurs in standard Perk workflows in these cases:
- If the submitter is the cost object owner, the expense is sent to the owner of parent cost object for approval.
- If the approval threshold on the cost object is exceeded, the expense is sent to the parent cost object owner.
| Option | Accepted values | Description |
|---|---|---|
| Check for independence | Boolean (true/false) | Escalates to the parent cost object if the submitter is equal to the approver on approval. This means that when a user approves, Perk checks if it was the submitter. If so, it escalates approval to the parent cost object. |
| Escalate to parent cost object | Boolean (true/false) | Perk checks the approval limit on the cost object. If the approval limit is breached, it escalates the document to the parent cost object. |
If the expense is escalated automatically using this node, this information is recorded in the expense history:
Line manager approval or escalate
Configure a special approval flow in combination with Assign line manager.
Caution: This node must be used before the line manager assigner; otherwise, it does NOT work.
This specific node has one option that must be set up:
| Option | Accepted values | Description |
|---|---|---|
| Amount reference |
expense / trip
|
|
All approvers must approve
Set up an approval flow in which all approvers must approve before the document can be moved to the next status. Technically, what this node does is the following:
- Once an approver approves, it removes the approver ID from the list of current approver IDs.
- Assigns the document to other approvers assigned to the document who still need to approve.
Once all approvers have approved the document, it moves the document to the next step in the flow.