Summary table of how Approval Paths work
The terms used in the article below correspond to iSYBUY. To find iBAT equivalents, click on this link.
On iSYBUY you have several possible options for approval paths. You'll find the description here so that you can adapt them to your needs later.
Once you're on the approval paths, you'll find all the possible implementation options in the second "Options" tab.
| No option |
Approval starts at the level where one of the approvers has sufficient commitment, then the approvers at this level with sufficient commitment are added. Subsequent levels and the company level are added to the route. The levels are run through 1 by 1. Only one approver per level is needed to validate the level. |
|
Option :
Start at first level
|
Runs through all levels, from first to last, including company. The applicant's commitment has no influence. The levels are run through 1 by 1. Only one approver per level is needed to validate the level. |
|
Option:
Start at the highest commitment level
|
The route starts at the level whose approvers have a commitment higher than the applicant's commitment. The amount of the order is not taken into account in this case. All approvers with a higher commitment will therefore be approached, grouped by level. |
|
Option :
Stop at sufficient level
|
Approval starts at the level where one of the approvers has sufficient commitment, then the approvers at that level with sufficient commitment are added. The process is limited to this level; approvers at other levels are not involved. |
|
Option :
Forced circuit
|
Launched regardless of the applicant's commitment. Works in the same way as without the option, except for the company, where approvers are approached in turn. |
|
Option :
Inform the last level
|
The course proceeds normally depending on the options chosen. If the approver(s) at the last level (before the company level) did not take part in the validation, they will be informed by email that the order has been validated. |
|
Option :
Threshold
|
The threshold amount determines the minimum amount below which no approval is required. The applicant's commitment amount is not taken into account; it can be less than the order amount without triggering the route. Above this threshold, the process is triggered normally, and varies according to the options selected. |
Do you have any other questions we haven't thought of? Send us your request at this address. We look forward to hearing from you!
Related keywords :
Workflow - validation circuit - approval path - path - approver - options - configuration - customisation - threshold - priority - level - commitment - purchase
Workflow - validation circuit - approval path - path - approver - options - configuration - customisation - threshold - priority - level - commitment - purchase