.png?height=120&name=dark=on%20(1).png)
Once a request is submitted, it is automatically matched to the appropriate approval workflow based on the conditions defined during workflow creation.
Mapping to Workflow:
- Requests are automatically mapped to the workflow that was selected during submission.
- Conditions like request type, price, and department can be used to further customize how requests are routed through the approval process
- Workflow can have not only linear approvers but conditions that sets additional parameters to route request
- Example: I want a request after assigning to flow go to John for approval who's our IT Admin, then to Sara who's our Legal but I'd love the request gets an additional approval from Jeremy our CEO if the price is higher than $5k. For this purpose a requester provides answer in the request form which are considered for similar case of routing request within a workflow
Processing Request:
- The request will follow the steps defined in the approval flow. Each step is assigned to a specific approver(s), and the request will not move forward until all required approves are received.
- multiple approvers might exist on one step
- in such a case 'step requires approval from all of them' works here. Meaning a request won't move forward until all approvers confirm it
- if request meets a condition on its way - Spendbase makes matching check:
- if a request matches it will require an additional approval from the approver specified on the condition
- else - request will simply skip condition and go to the next step in the workflow