VisualWorkflows

for M-Files by Neurones Technologies SA

Technical Guide
Compatibility
VisualWorkflow operates on a minimum version of M-Files 2015.3.

Install
1. Open M-Files Admin
2. Right-click the vault's name, choose "Applications"
3. C lick the "Install" button in the bottom left corner
4. Select the VisualWorkflow.mfappx file downloaded
5. Install license : select the "VisualWorkflow" application and click the "License" button

Note : you may be asked to restart your vault and close active user sessions.

You should now see 2 new installed applications, one embedded in the other (if not click the +
icon on the left of "VisualWorkflow"). The "parent" is the vault application, the "child" is the UI.

C ongratulations, you have successfully installed VisualWorkflow !

License and trial period

On application's first install, a trial period of 30 days is started on the server. After this period, you
may reach out to an M-Files C hannel Account Manager to buy a regular license.

P ricing information is available in M-Files price list.

Note : because the trial license is installed on the server, any vault installed on the server falls
under this 30 days countdown.

Concepts
Here are the main concepts of the VisualWorkflow application.

Object types

The Visual Workflows are stored in M-Files, along with the rest of your data. Being objects, they
inherit M-Files objects' advantages :

you may use the powerful M-Files permissions system on your VisualWorkflow objects
you may access the history of those objects as they are checked in/out
 You don't want to edit or create the objects yourself as this can result in a broken
installation. You can let the application handle that.

Permissions

You may prevent the visual workflows from being updated by unathorized users by using the M-
Files permissions system.

A ccess restrictions can be configured in the Permissions tab of the V isual Workflow
object type.

A user with Create objects of this type permission on the Visual Workflow object type will be
able to create and edit visual workflows.

All users that can access the object can see the visual workflow associated, assuming it exists.

If there is no visual workflow related to the object's workflow, only users with the
Create objects of this type permission will see the Workflow tab.

M-Files applications

VisualWorkflow contains 2 M-Files applications.

1. One is the UI and is installed on the client's side. M-Files handle the installation and provides
M-Files client with the VisualWorkflow UI application as soon as a new user logs in to the
vault. This application renders the visual workflow in the "Workflow" tab when an object is
selected.

2. The second application is installed on the vault itself (VisualWorkflow). It ensures that the
necessary object types exist and provides the UI application with extension methods to
access an object's visual workflow information.

These 2 applications rely on each other to provide what you expect from M-Files VisualWorkflow.

The visual workflows won't be displayed if you uninstall either of them.