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.11 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.11 core product uses the following versions:

• ProcessMaker Query Language (PMQL): Version 1.1.3
• Process Modeler: Version 0.24.4
• Screen Builder: Version 1.1.4

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.11

Bug Fixes

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

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

Core

1. A ProcessMaker user that does not have an appropriate API token to access the ProcessMaker RESTful API no longer receives a 500 error (Internal Server), but appropriately receives a 403 error (Forbidden) since that user does not have an appropriate API token.
2. ProcessMaker group members assigned Request permissions can now view files uploaded to Requests in which they participate.
3. From the ProcessMaker RESTful API documentation in Swagger, testing the POST requests{request_id}/files endpoint that uploads a file to a specified Request by its ID no longer shows a 422 error (Undocumented) in the response that data_name is required.
4. The template that sends errors no longer has its own error.

Screen Builder

1. Validation rules are now observed for controls that are contained within a Loop control.
2. The Rich Text control now properly renders HTML from a Request variable in Email-type ProcessMaker Screens.
3. When referencing a Request variable that uses the date data type, the Line Input control no longer displays the datetime for that Request variable.