ProcessMaker 4.0.13 Release Notes

ProcessMaker version 4.0.13 Release Notes

Overview

Release Date: October 9, 2020

ProcessMaker is proud to announce the immediate availability of ProcessMaker version 4.0.13. This update addresses multiple improvements and bug fixes.

The ProcessMaker 4 platform makes it easy to create business processes that have the power of applications with our low-code approach using our BPMN 2.0-compliant suite of services so that you can design and deploy automated workflows that deliver true digital agility to your organization.

This document contains Release Notes for the following:

  • Core product: ProcessMaker version 4.0.13 core-product functionality that is the ProcessMaker open-source edition.

  • Non-core packages: ProcessMaker version 4 packages that extend core-product functionality. Packages are not available in the ProcessMaker open-source edition, but are available to customers that purchase or subscribe to ProcessMaker version 4. Release Notes that affect package functionality are documented with the core product section that the feature, improvement, bug fix, or known issue affects.

Release notes are cumulative, and document new features, improvements, bug fixes, and/or known issues associated with this release unless otherwise noted.

Core Product Versions

ProcessMaker version 4.0.13 core product uses the following versions:

  • ProcessMaker Query Language (PMQL): Version 1.1.3

  • Process Modeler: Version 1.1.1

  • Screen Builder: Version 1.1.9

Non-Core Package Versions

The following are the non-core package versions at the time of this release:

  • Actions By Email: package-actions-by-email 1.2.0

  • Advanced Forms: package-advancedforms 1.1.4

  • Auth: package-auth-auth0 1.0.1

  • Auth SAML: package-auth-saml 1.1.1

  • Collections: package-collections 1.6.2

  • Comments: package-comments 1.0.3

  • Data Connectors: package-data-sources 1.0.20

  • Dynamic UI: package-dynamic-ui 1.0.0

  • File Manager: package-files 1.1.2

  • Google Places: package-googleplaces 1.1.3

  • PDF Generator Connector: connector-pdf-print 1.4

  • Process Documenter: package-process-documenter 1.0.3

  • Process Optimization: package-process-optimization 1.0.3

  • Salesforce Connector: connector-salesforce 1.1.1

  • Saved Searches: package-savedsearch 1.9.4

  • Send Email Connector: connector-send-email 1.2.2

  • Sentry: package-sentry 1.0.2

  • Signature: package-signature 1.0.0

  • Slack Notification Connector: connector-slack 1.0.5

  • Translations: package-translations 2.0.5

  • Versioning: package-versions 1.0.5

  • Vocabularies: package-vocabularies 2.3.0

  • Web Entry: package-webentry 1.2.4

Links to System Requirements and Special Instructions

Improvements

This section documents improvements to the following, of which the issue(s) referenced are not publicly available:

  • Non-core ProcessMaker packages GitHub repositories

  • References that are only available to individuals who have permission settings to view FOUR project Jira tickets at ProcessMaker

This section documents improvements in conjunction with ProcessMaker version 4.0.13.

  1. FOUR-2040: ProcessMaker users with the Make this user a Super Admin option may now directly view the Tasks as displayed in the Task column of Request summaries by clicking a link to that Task.

  2. The following BPMN 2.0 elements for conditional events are now available in Process Modeler:

    • Conditional Boundary Event element: Use a Conditional Boundary Event element to route workflow through its outgoing Sequence Flow element(s) when specified Request conditions for that element are met. If the element is interrupting, workflow routes immediately through its outgoing Sequence Flow element regardless of whether its associating element is complete; otherwise, the element is non-interrupting and workflow routes through its outgoing Sequence Flow element after its associating element completes. A Conditional Boundary Event element may be used with any of the following elements or connectors:

      • Form Task element

      • Manual Task element

      • Script Task element

      • Sub Process element

      • Actions By Email connector (requires the Actions By Email package)

      • Data Connector connector (requires the Data Connector package)

      • PDF Generator connector (requires the PDF Generator package)

      • Send Email connector (requires the Send Email package)

    • Conditional Start Event element: Use a Conditional Start Event element to trigger a Request when Request conditions from a parent Request are met, thereby starting a child Request. If the conditions in the parent Request are not met, the Conditional Start Event element ignores the call to start a Request.

    • Intermediate Conditional Catch Event element: Use an Intermediate Conditional Catch Event element to pause workflow for a Request until specified Request conditions are met, thereby resuming workflow through whichever outgoing Sequence Flow element's conditions meet those Request condition.

Conditional event elements associated with Sub Process elements are still under development. Please use at your own risk.

Bug Fixes

This section documents bug fixes in conjunction with ProcessMaker version 4.0.13.

This section documents bug fixes to the following, of which the issue(s) referenced are not publicly available:

  • Non-core ProcessMaker packages GitHub repositories

  • References that are only available to individuals who have permission settings to view FOUR project Jira tickets at ProcessMaker

Collections Package

  1. FOUR-1663: If a ProcessMaker Collection is deleted, all Saved Searches for that Collection now are automatically deleted.

  2. FOUR-2041: A Select List control in which its data source is a ProcessMaker Collection may filter from all the records in that Collection.

Comments Package

  1. FOUR-1960: When a ProcessMaker user that has Comment permissions is tagged in a Task summary comment in which that user is not already a Request participant no longer causes the error This action is unauthorized. when that user views the commented Task.

Core

  1. FOUR-137: The Auth Clients page now contains pagination functionality.

  2. FOUR-1117: When using Mozilla Firefox browser, an error message no longer displays that the Request is aborted or 401 error (Unauthorized) after completing a Task.

  3. FOUR-1524: ProcessMaker users that do not have the "View Users" permission will no longer be able to share a Saved Search with other users or view other users in the Requester setting of a PMQL search. Likewise, ProcessMaker users that do not have the "View Groups" permission will no longer be able to share a Saved Search with groups.

  4. FOUR-1705 and FOUR-1981: When two Parallel Gateway elements are used in a Process model, the first diverging and the second converging, the converging Parallel Gateway element now no longer causes an inappropriate BPMN validation error.

  5. FOUR-1841: Viewing a Task summary no longer displays a 500 error (Internal Server Error).

  6. FOUR-1843: A File Preview control that previews a file uploaded in a previous Task in that Request now displays that file's preview for a Task configured for anonymous Web entry.

  7. FOUR-1968: The Script Executors page now contains pagination functionality.

  8. FOUR-1971: The Auth Clients page search now supports upper-case characters in a search.

  9. FOUR-1991: Requests may now start without an error for Processes that initially contained one Parallel Gateway element, but then is replaced with an Event-Based Gateway element.

  10. FOUR-1994: The _user Magic Variable now properly stores the ProcessMaker user that self-assigned a self-service Task.

  11. FOUR-2011: Request summaries may now display the Request details for any Task from the Forms tab without locking the Web browser tab that is displaying ProcessMaker.

  12. FOUR-2059: A validated Process model that contains a Sub Process element may now import correctly without displaying an error.

Data Connector Package

  1. FOUR-2041: A Select List control in which its data source is a ProcessMaker Collection may filter from all the records in that Collection.

PDF Generator Package

  1. FOUR-2049: After a PDF Generator connector generates a PDF, Request data now stores the output PDF's ID instead of its file name.

Process Modeler

  1. FOUR-1533: Start Event elements and End Event elements may now be properly copied without producing a console error.

  2. FOUR-2042: When a validated Process model contains an Exclusive Gateway element, then is changed to a Parallel Gateway element, Process Modeler no longer inappropriately invalidates the Process. The Process can be saved successfully.

  3. FOUR-2035: Requests no longer error when the Process of such Requests route workflow in the following circumstances:

    • In a Request, an Intermediate Signal Throw Event element triggers, thereby sending its signal.

    • In that Request, workflow immediately routes to an Event-Based Gateway element.

    Intermediate Signal Catch Event elements in that Request or Signal Start Event elements in a child Request now properly receive the signal from the Intermediate Signal Throw Event element.

  4. FOUR-2038: Double-clicking on a Process model node no longer causes a console error.

  5. FOUR-2044: When workflow routes through a Conditional Boundary Event element, the existing Request data is no longer inappropriately overwritten by data from the Conditional Boundary Event element.

  6. FOUR-2047: A Boundary Timer Event element, Boundary Error Event element, Boundary Signal Event element, or Boundary Conditional Event element may be added to any Form Task element even after previously deleting one of these boundary event type elements from a Form Task element.

  7. FOUR-2048: When clicking the Advanced panel for a selected Process model node, the Configuration panel no longer expands as well.

Saved Searches Package

  1. FOUR-1524: ProcessMaker users that do not have the "View Users" permission will no longer be able to share a Saved Search with other users or view other users in the Requester setting of a PMQL search. Likewise, ProcessMaker users that do not have the "View Groups" permission will no longer be able to share a Saved Search with groups.

  2. FOUR-1663: If a ProcessMaker Collection is deleted, all Saved Searches for that Collection now are automatically deleted.

Screen Builder

  1. FOUR-1522: Designed CSS settings in Custom CSS mode no longer revert to default CSS settings after a ProcessMaker version 4.0.12 instance is upgraded to ProcessMaker version 4.0.13 or later.

  2. FOUR-1804: Editing or copying a Select List control that uses a ProcessMaker Data Connector as its data source no longer inappropriately loads the My Requests page.

  3. FOUR-1883: The Date Picker control now properly shows the control's date instead of datetime when configured to use Date data type.

  4. FOUR-1898: File Download controls may now download files uploaded in a previous Task via a File Upload control that are 100 MB or larger.

  5. FOUR-1954: A Record List control placed inside a Loop control now properly shows the modal screen that contains the Record List control's referenced controls to enter a record.

  6. FOUR-1966: File Manager in a Request summary now shows unique files uploaded via a File Upload control when that control is contained in a Record List control instead of only the last file uploaded.

  7. FOUR-2055: When a Select List control that get its options from a ProcessMaker Collection as JSON objects via a Data Connector, those JSON objects no longer contain mustache syntax curly brackets ({{ and }}) around those objects.

Vocabulary Package

  1. FOUR-2024: A ProcessMaker Vocabulary that uses a text attribute type and then implemented in a Form Task element no longer causes an error message during a Request when the Task assignee complies with the Vocabulary's JSON schema.

Web Entry Package

  1. FOUR-1843: A File Preview control that previews a file uploaded in a previous Task in that Request now displays that file's preview for a Task configured for anonymous Web entry.

  2. FOUR-1927: Files uploaded to a Request from a Task completed via Web Entry now properly display in the File Manager package within the File Manager tab of that Request's summary by referencing the file's ID instead of its file name.

  3. FOUR-2046: Web Entries authenticated via SSO now redirect properly to the initial URL.