This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Workflow Newbie needs help!

Former Member
Former Member
I'm pretty new to M-Files and have never implemented a workflow before. I need some advice.

I understand that workflow is just a set of states with some rules about which states can move to which other states, and a set of actions that are to be performed upon a state transition (e.g. email notifications etc).

I have the situation where a document may be entered into the M-Files vault by a sales guy. It will go in as "not approved" or some such status. Then the document will need to be approved by 3 other people (e.g. from the Finance, Commercial and Operations departments). These representatives need to be selected on a case-by-case basis, but will be other M-files users, most likely on concurrent licenses. Finally, the document will be approved and ready to be accepted finally into the repository by me (or one of my admin colleagues).

Can anyone give me the basic pointers to the best way to resolve the issue about selecting the three "approvers"? They are not always fixed and will need to be entered manually according to some big list of approvers I have on my desk (the list, not the approvers :)).

I imagine the sales guy dropping in the new doc, at which point pops up a custom dialog saying "enter Finance approver" etc and when he presses "ok", it enters the "awaiting finance approval" state and sends a notification to finance etc.

is something like this possible?

cheers
Dom
Parents
  • Former Member
    Former Member
    You can specify in properties of each class defines who can see, edit or create this class.
    So if you create a group "approvers" you can simply add permission to create and edit to the class you wants, and defines on others class they can not edit or create.

Reply
  • Former Member
    Former Member
    You can specify in properties of each class defines who can see, edit or create this class.
    So if you create a group "approvers" you can simply add permission to create and edit to the class you wants, and defines on others class they can not edit or create.

Children
No Data