State Transition Based off of User and their Group

Is there an easy way to have an automatic state transition based off of the user and the user group they belong to for approval? For example, I create a request and because I am in the Sales user group, the next state transition will automatically send it for approval to the Sales Manager. However, if I was in the Accounting user group, then it would send it to the Accounting Manager for approval.

Parents
  • You don't necessarily need different transitions for this if your vault structure and workflow is set up in a way that you can resolve the departmental manager based on the requestor.

    A sample structure: you would have object types Employee and Department. Each Employee object would reference the Department they belong to and each Department object would contain the manager information (also a reference to an Employee object). Each Employee object also contains the M-Files user account of the person (e.g. in property "M-Files user").

    With this kind of a structure, you could define in the request workflow that the approval assignment is sent to Employee.Department.Manager.M-Files user. The assignment is sent to the manager of whoever is tagged in the Employee field. In the screenshot above, for Jonathan it would be Mike who is the manager of the Sales team. Everyone can use the same states and transitions in the workflow.

    When creating the request, you can automatically fill the Employee field based on the current user. A sample configuration for this available on the Support Portal.

Reply
  • You don't necessarily need different transitions for this if your vault structure and workflow is set up in a way that you can resolve the departmental manager based on the requestor.

    A sample structure: you would have object types Employee and Department. Each Employee object would reference the Department they belong to and each Department object would contain the manager information (also a reference to an Employee object). Each Employee object also contains the M-Files user account of the person (e.g. in property "M-Files user").

    With this kind of a structure, you could define in the request workflow that the approval assignment is sent to Employee.Department.Manager.M-Files user. The assignment is sent to the manager of whoever is tagged in the Employee field. In the screenshot above, for Jonathan it would be Mike who is the manager of the Sales team. Everyone can use the same states and transitions in the workflow.

    When creating the request, you can automatically fill the Employee field based on the current user. A sample configuration for this available on the Support Portal.

Children
No Data