3.2.0

• We upgraded the module to Mendix 10.3.0
• You can now delete an obsolete workflow definition in the 'Workflow management' page
• We introduced a new wizard to clean-up completed and aborted workflows, you can find this option in the 'Possible actions' menu of the 'Workflow details' page
• We now use the Gallery widget in the 'My initiated workflows' page
• We removed dependency on the 'List view controls' widget
• We added support for the new multi-user task decision method (Microflow)

3.1.0

• We upgraded the module to Mendix 10.0.0
• We added support for new multi-user task decision methods (Majority, Threshold)
• We changed the way target users are displayed on the workflow admin page so that it is consistent with the list of assignees
• We changed the way the decision method is retrieved on the workflow admin page

3.0.0

• We upgraded the module to Mendix 10.0.0-beta2
• We added support for multi-user tasks
• With the introduction of multi-user tasks, assignees are now a reference set. If you used Workflow Commons in your project before and have existing data on user tasks, you will need to migrate your existing assignee data in Workflow Commons. Note: you can only upgrade data from Workflow Commons v2.4.0 or higher, if you currently use a version of WFC before this version, please upgrade to WFC v2.4.0 or higher first. To run the migration, you can either:
  • Use the migration microflow 'ACT_Assignee_Migration' (also added to the 'WorkflowAdminCenter' page), or:
  • Add the 'ASu_Assignee_Migrate' microflow to the project's after startup microflow to transfer to the new association 'UserTaskView_Assignees'.
• The 'UserTaskView_Assignee' association is deprecated, please use the 'UserTaskView_Assignees' association instead. See the note regarding multi-user tasks above.
• We added support for lock/unlock; you can now lock or unlock a workflow definition from the Workflow Management page. If a workflow definition is locked, no new instances of this workflow can be created. When you lock/unlock a workflow definition, you can choose to pause/unpause the running workflow instances.

2.3.2

• We fixed CVE-2022-46664 - for more information, see security advisory at https://cert-portal.siemens.com/productcert/pdf/ssa-210822.pdf

2.1.4

• We fixed CVE-2022-46664 - for more information, see security advisory at https://cert-portal.siemens.com/productcert/pdf/ssa-210822.pdf

2.5.0

• We upgraded the module to Mendix 9.20.0
• Starting with Mendix 9.20.0, you can disable the auto-assignment of users when opening a user task. We updated the user task page templates to include the message "You can only complete a task when you are the assigned user" that is displayed when you open a user task page and you are not the assigned user for this user task
• We optimized the 'Refresh' action that is used in the Task Inbox page. For this action we now use the 'Refresh entity' action that is available in the Nanoflow Commons module. This module is included by default when starting a new app. If your app currently does not include the Nanoflow Commons module, please make sure to import Nanoflow Commons from the marketplace when upgrading to v2.5.0 of Workflow Commons

2.4.0

• We upgraded the module to Mendix 9.19.0
• Attachments outside the scope of a comment now need to be part of your own domain model, and should be associated to the context entity of the Workflow. This is required so you can configure the applicable security settings, since the context of a specific Workflow is not known in advance in Workflow Commons
  • In Studio, attachments can be added using the ‘File’ property in the Workflow wizard
  • In Studio Pro, attachments can be added using a specialization of System.FileDocument
• As a result: Attachments in Workflow Commons are now (an optional) part of comments. A migration microflow is provided that will create a comment for every workflow instance and link all its existing attachments. If your app requires migration, this option will be shown in the Workflow Admin Center. Until the migration has been executed, existing comments and attachments will not be visible in any of the included pages and snippets. Make sure to create a backup of your data before you execute the migration
• We added support for subworkflows in the Workflow Admin page and page template: whenever a workflow was called from a parent workflow, this is shown in the page header
• We fixed CVE-2022-46664 - for more information, see security advisory at https://cert-portal.siemens.com/productcert/pdf/ssa-210822.pdf
• We updated the icons that are used in the ‘Jump to Activity’ pop-up

2.3.1

• We updated Charts module compatibility to version 3.0.1

2.1.3

• We updated the admin actions in the Workflow Admin page. Failed workflows can now be aborted.

2.3.0

• We have introduced Jump-to action. For more details on this, please visit https://docs.mendix.com/refguide/jump-to/
• We moved the Workflow Definition View page from Workflow dashboard to Workflow management
• We updated Charts module compatibility to version 3.0.0
• We updated Data Widgets module compatibility to version 2.5.4