ProcessMaker 4.0.6 Release Notes
ProcessMaker version 4.0.6 Release Notes


Release Date: June 25, 2020
ProcessMaker is proud to announce the immediate availability of ProcessMaker version 4.0.6. 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 ProcessMaker version 4.0.6 core-product functionality that is part of the ProcessMaker open-source edition, and does not describe Release Notes for non-core packages. Release notes are cumulative, and document new features, improvements, bug fixes, and/or known issues associated with this release unless otherwise noted.
ProcessMaker version 4.0.6 core product uses the following versions:
    ProcessMaker Query Language (PMQL): Version 1.1.2
    Process Modeler: Version 0.24.1
    Screen Builder: Version 0.23.22

Links to System Requirements and Special Instructions


This section documents improvements for ProcessMaker version 4.0.6.

Screen Builder

    #755: The Loop control now functions in Display-type ProcessMaker Screens.

Bug Fixes

This section documents bug fixes for ProcessMaker version 4.0.6.


    #2974: Script Editor now functions correctly when ProcessMaker runs on Apple Safari browser.
    #3008: A ProcessMaker Screen that uses a Calculated Property that uses JavaScript to determine a date now properly does so.
    #3076: After a Script Executor is created with a specific Docker programming language, the Select a language setting only displays the supported language for selection for that Docker container. For example, the PHP Script Executor that runs PHP ProcessMaker Scripts only shows the PHP language from the Select a language setting in its configuration.
    #3082: Children Requests may now start from a parent Request even if that Request started anonymously.
    #3130: When creating or configuring a ProcessMaker Script, selecting a different Script Executor allowed to run that Script no longer displays an error below the Script Executor setting.
    #3155: When creating a new user with an email address belonging to an active ProcessMaker user, the appropriate message displays that this email address is already taken by another user instead of displaying that the email address belongs to a deleted user.
    #3159: The Auth Clients page now contains the following:
      the Search setting page navigation to filter which authentication clients display on the page
      page navigation to navigate multiple pages
    #3161: Searching for notifications from the All Notifications page now properly find notifications that contain at least one apostrophe (').
    #3162: Requests now properly complete for Processes that contain multiple parallel workflows and all Script Tasks in multiple parallel workflows complete.
    #3174: An ID now associates with each ProcessMaker user and ProcessMaker group.
    #3177: When installing ProcessMaker, an installation error no longer displays.
    #3187: The Send Email connector now properly uses ProcessMaker Screens to send the contents of an email. The Send Email connector is part of the Send Email package. The Send Email package is not available in the ProcessMaker open-source edition.
    #3189: The Google Places control now properly calls the Google API to properly load the specified location's data object for a ProcessMaker Screen. The Google Places control is part of the Google Places package. The Google Places package is not available in the ProcessMaker open-source edition.
    #3223: The history for a Request now properly displays at the bottom of that Request's summary.

Screen Builder

    #724: The Required If validation rule properly evaluates if a control that requires a value contains a value prior to the submitting the ProcessMaker Screen.
    #752: The file uploaded to a File Upload control in a Record List is available for download in a subsequent Task, regardless of whether the File Upload control or the Record List control have visibility rules.
Last modified 1yr ago