Overview

Documentation

Description

This module is an extension on the workflow feature as available in mendix 9 (not working on mendix 9.6 and up).

Typical usage scenario

The standard workflow feature has some limitations which are reduced by applying this module. By adding this module more features are available. Instead of using System.WorkflowContext use WorkflowExtensions.WorkflowExtension as generalization on workflow level. To add the functionality on activity level it is required to link the taskextension via the task on create option.
 

Features and limitations

Extension on workflow level

Usage of the workflowextension adds several functionality to the workflow:

• Phases with a phasetype enables a higher level of activity reporting (for example combine multiple user tasks into one phase)
• Management reporting based on these phases which enables reporting of STP processes versus non-STP processes
• Additional logging 
• Most import the possibility to start another workflow from a workflow and wait on completion of this workflow
• Extended tasklist shows both the user and system tasks applied in a workflow
• Additional processing options based on status changes of a task
• Additional messaging options based on status changes of a task 

Extension on workflow activity level

Additional activities are added:

• Wait steps, enable to possibility to wait a given period since the start of the activity. This can be usefull when waiting on completion in another system
• Additional warning to user when activity gets close to the due date (early warning). 
• Task execution via a queue. Queueing provides the option to have a more flexible work assignment capability. It is possible to assign new users to a queue which can directly execute the tasks in the queue. 
• Indication of picked up tasks and avoiding that tasks are executed twice
• Checking and option to execute a microflow when a task is overdue

Additional options available in the workflow toolbox

• MI Start (NOTLIST), option to add at the start of a workflow to collect MI information
• MI End (NOTLIST), option to end the MI information and perform some calculations
• Phase Start (NOTLIST), option to start a new phase
• Phase End (NOTLIST), option to end a phase and eventually end the MI information
• Phase Start and End (NOT LIST), combines the ending and the starting of a phase, not possible to end MI information
• Coinflip, option that gives a true or false back based on parameter (probability). This can be used for example to do a manual check of the workflow in only x% of the workflows
• Set due date (NOTLIST). Provides the option to set the due date based on the workflow initiation date (as available in the workflowextension enity).

*NOTLIST prevents the activity to be shown in the extended task list

Dependencies

- Requires Mendix 9.1 or higher (but not 9.6)
- Community Commons (version 8.4.0)
- Mendix SSO Atlas Core (version 2.3.1) (including Atlas Core version 3.0.2)
- Workflow Commons (version 1.1.0)
- Nanoflow Commons (version 2.0.1)
- Email module with templates (version 11.0.0)
- Encryption module (version 2.1.3)
- MX Model Reflections (version 6.2.0)
- MIcroflow Timer

Installation

- An after startup microflow is included in thet workflowextension module. This needs to be called from the application after startup module
- In de application after startup module the deeplink should be started (see documentation on deep link module)
- In the workflow extension module the module roles are mapped to the application roles. This is taken care of in the ASU. The application roles need to be in line with application security. Best practice is to include these three createmapping calls in teh application asu and NOT call the Workflow Extension after startup.
- the supplied email templates should be manually checked and the placeholders should be added

Configuration

Users need to be assigned to queues, no further configuration needed

In the Phone template (WE_AtlasPhone) a reference to the Responsive profile is used. This needs to be adjusted in the project so it references to a Phone profile

Deeplink and Email configuration needs to be done, read relevant documentation from these modules

Bugs

No known bugs