Overview

Release Date: August 21, 2020
ProcessMaker is proud to announce the immediate availability of ProcessMaker version 4.0.9. 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.9 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.9 core product uses the following versions:

• ProcessMaker Query Language (PMQL): Version 1.1.3
• Process Modeler: Version 0.24.2
• Screen Builder: Version 1.1.1

Links to System Requirements and Special Instructions

1. On-Premises Server Requirements
2. ProcessMaker 4.0 must be installed to upgrade to ProcessMaker 4.0.9

Improvements

This section documents improvements in conjunction with ProcessMaker version 4.0.9.

Core

1. Outgoing Sequence Flow elements from Exclusive Gateway elements and Inclusive Gateway elements may now more easily create a new Request variable and its value if Request workflow routes through that Sequence Flow element.
2. A ProcessMaker Administrator may now delete the Request data from the database, including the Task data related with those Requests. All Request data is deleted from the database and cannot be undone, though a message confirms the deletion of the Request data. This improvement is useful to reset a ProcessMaker instance as if it was a new deployment.
3. A ProcessMaker Administrator may now prioritize queue workers.

Bug Fixes

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

Core

1. If the database becomes unresponsive, a Task still receives a valid token so that Task assignee may continue work on that Task.
2. An imported Process model that contains an Actions By Email connector may now assign a user to that connector. The Actions By Email connector is part of the Actions By Email package, which is not available in the ProcessMaker open-source edition.
3. A Task may be properly reassigned to another ProcessMaker user even when the original Task assignee is not the requester.
4. In a Process model that contains two Pool elements, the second of which uses a Message End Event element to message an Intermediate Message Catch Event element in the first Pool element when its Request completes, the Intermediate Message Catch Event element now properly receives the message from the Message End Event element to resume its Request.
5. A legitimate but corrupt cookie in a ProcessMaker instance, placed in the ProcessMaker instance when a ProcessMaker user selects the Remember me setting in the log on screen, no longer causes an error that displays the ProcessMaker user credentials in the ProcessMaker logs.
6. For each additional loop added to a Loop control, the Variable Name setting values for those controls within that Loop control now automatically increment by one.

Screen Builder

1. The Select List control now appropriately returns a single value as its data source when the Type of Value Returned setting is set to Single Value.

2. Two or more ProcessMaker Screens may now properly nest into one another. For example, a Nest control may contain a ProcessMaker Screen which uses a Nest control with its own nested Screen. While similar to the addressed issue that affected anonymous Request participants using a ProcessMaker Screen via the Web Entry package, this bug affected ProcessMaker users.

3. In Preview mode while entering data into controls contained within a Record List control, data entered in the page with the Record List control no longer lose data entered into them.

4. Preview mode functions properly when a ProcessMaker Screen contains the following controls:

   • Loop control: The Loop control is set to use an existing JSON array as its data source and to allow additional loops.
   • Select List control: The Loop control contains a Select List control in which it is set with a default value.
   • Check Box control: The Loop control contains a Check Box control.

5. A Select List control that uses a ProcessMaker Collection record as its data source in which that ProcessMaker user does not have permission to view that Collection now properly references that Collection record for its options. The Collection package is not available in the ProcessMaker open-source edition.

For production, please use the processmaker4.0.9.tar.gz below.