meta data for this page

Workflow Map Preview

Since Workflow Maps are process maps like any other process map, they are shown in the preview tab just alike. So the general functionality of the preview tab applies. However, there is an important difference: The workflow map interacts with an associated object in the listview. So you typically see the listview with objects (which should be on a workflow path) and then a corresponding workflow map in the right tab. The open workflow map tab listens to the currently selected object or document and then hands this over for interpretation to the workflow map.

  • Workflow maps highlight dynamically the current state (red). They automatically zoom to that state (if configured)
  • Workflow maps show the next potential workflow states (lite red) and provide a grey command icon to invoke a state change.

  • The yellow rectangle with the number is an optional display. It shows the number of workflow state visits based on the history of the object. Calculation of this number is an asynchronous process and may take a while. We recommend to switch this off if it does not provide value to the users.

Also, it is important to note that, if for a specific M-Files workflow there are multiple workflow process maps, then these workflow maps are offered for selection in a dropdown in the toolbar. This provides the ability to look at a workflow from different points of view or provide information on different levels of depth.

Since Workflow maps can contain symbols from all notations (BPMN, Flowchart, EPC, Portfolio) and since they can contain smart nodes that are dynamically filled with the data of the associated object, they can provide additional information and also allow to jump to other maps, create documents, etc.

  • The smart node on the right is filled with the data of the selected employee.
  • The image of the employee is shown.
  • Commands with template documents are available when they are needed
  • Additional information is offered, when you hover over the smart node
This website uses cookies: We only use cookies here as standard user session identifier, for authentication after login and for remembering helpful user preferences, like the size of the text editor. More information