Hierarchy management in the new workflows
The terms used in the article below correspond to iSYBUY. To find iBAT equivalents, click on this link.
Defining an approval circuit allows you to better control and segment your purchasing process. You can define one or more order approvers per project, per company, per order type, per cost line, per amount, per line manager... and so on. With this workflow management system, the possibilities are endless (or almost!).
New : You can now define line managers for workflows!
Note :
Workflow management can only be accessed and modified by users with privileges over the Group scope.
In this article :
Managerial hierarchy
e.g. John is the manager of Michael, who is in turn the manager of Frederique.
This information is defined in each user's file. The manager can be selected from all the users in the Group.
Structural hierarchy
e.g. The person in charge of the project, department or company
This information is defined in the project, department or company file. The manager can be selected from all the users in the Group.
Note :
If you deactivate a user set up as a line manager (for a user or a structure), a pop-up will appear before deactivation, prompting you to replace the user with another user before deactivating him or her.
Examples :
- iBAT Time - Absences: IF absence requested by an employee from the Depot department THEN Approver: Eric; Except if employee = Eric, then approver = Jean-Louis
- IF order value > €20,000 THEN Approver : project manager
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 :
Workflows - approval path - circuit - purchase - time - consult