ProcessMaker 4 version 4.0.12

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

• ProcessMaker Query Language (PMQL): Version 1.1.2
• Process Modeler: Version 0.24.4
• Screen Builder: Version 1.1.6

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

Bug Fixes

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

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

Core

1. ProcessMaker now appropriately displays No data available for a PMQL search for a requester when the PMQL search query contains an invalid ProcessMaker user.
2. A ProcessMaker user that does not have the Make this user a Super Admin setting but has all Processes category permissions may now properly save a Process without receiving a 403 error (Forbidden).
3. 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.

Screen Builder

1. The File Upload control now consistently stores the file ID of an uploaded file in Request data.
2. A Select List control within a Record List control's container that uses Request data as its data source now properly shows its options both in Preview mode and during Requests.
3. The Select List control now properly returns either single value or a JSON object regardless of whether the Allow Multiple Selections option is used.
4. An editable Record List control that contains a second Record List control, of which has a configured column, may now save without errors.
5. A Line Input control that validates for a date no longer freezes Screen Builder in Preview mode.
6. 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.

Please download and use the GZip file from below.

ProcessMaker 4 version 4.0.11

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.

ProcessMaker 4 version 4.0.10

# Overview

ProcessMaker is proud to announce the immediate availability of ProcessMaker version 4.0.10. 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.10 core-product functionality that is the ProcessMaker open-source edition .

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.10 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.3

Improvements

This section documents improvements in conjunction with ProcessMaker version 4.0.10.

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

Improvements

Core

1. A new ProcessMaker permission in the Users category called View Other Users Profiles allows a ProcessMaker user or members of a ProcessMaker group to view another ProcessMaker user’s profile when granted this permission. This improvement allows only particular ProcessMaker users or all members of a ProcessMaker group to view sensitive profile information such as an email address, thereby improving ProcessMaker security. If a ProcessMaker is not granted this new permission, then that user receives an Error 404 (not found) page when clicking on another user’s avatar or manually adjusting the URL to view another user’s profile page. This permission is disabled by default.
2. Files associated with a parent Request via a Sub Process are now available to all child Requests and vice versa.

Bug Fixes

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

Core

1. The API documentation for the GET requests{request_id}files{file_id} endpoint that returns the a file associated with Requested based on the IDs of the request and sought file is updated to accurate describe what the endpoint returns.
2. If creating a new ProcessMaker user via the API using the POST /users endpoint that does not submit all required parameters in the API call, such as the new user’s password, the Error 422 response now properly indicates which required parameters were not in the API call.

Screen Builder

1. The ProcessMaker Screen page using a Record List control now properly shows that page during a Request instead of the page that the Record List control references for its records.
2. A ProcessMaker Screen that uses a Loop control containing a Select List control now submits correctly when a value is selected from the Select List control.
3. Submitting a ProcessMaker Screen during a Request that uses a File Preview control no longer displays the error Cannot read property ‘mime_type’ of undefined.

ProcessMaker 4 version 4.0.9

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.

ProcessMaker 4 version 4.0.8

ProcessMaker is proud to announce the immediate availability of ProcessMaker version 4.0.8. This update addresses multiple 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.8 core-product functionality that is the ProcessMaker open-source edition .

Non-core product 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.
ProcessMaker version 4.0.8 core product uses the following versions:

• ProcessMaker Query Language (PMQL): Version 1.1.3
• Process Modeler: Version 0.24.0
• Screen Builder: Version 1.0.2

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

Bug Fixes

This section documents bug fixes for ProcessMaker version 4.0.8.

Core

1. The ProcessMaker API documentation for the GET users endpoint now accurately documents the body response.
2. The ProcessMaker API documentation for the POST request files endpoint now accurately documents the body response.
3. ProcessMaker now displays the appropriate error message when attempting to import an invalid ProcessMaker Screen into Screen Builder.
4. The ProcessMaker API documentation for the GET processes endpoint now accurately documents the body response.
5. The ProcessMaker API now requires a password for a new ProcessMaker user when creating that user via the POST user endpoint.
6. An Intermediate Message Catch Event element in a parent Request now properly receives a message from a Message End Event element in one of its child Requests to properly start a new parent Request.
7. A ProcessMaker user who does not have Super Admin status whereby ProcessMaker permission evaluation does not occur can now properly be granted Super Admin status.
8. Boundary Timer Event elements in a Request now properly trigger to route that Request when its associated Task is not complete within its configured time from when the Task triggered.
9. An inappropriate error no longer displays when viewing the Public folder in the File Manager. The File Manager package is not available in the ProcessMaker open-source edition.
10. A Saved Search showing Request data no longer causes ProcessMaker to prevent assigned Tasks from being opened. The Saved Searches package is not available in the ProcessMaker open-source edition.
11. A Task using authenticated Web entry now functions correctly when the redirecting URL to do that Task is a custom homepage configured from a Dynamic UI setting. Neither the Web Entry package nor the Dynamic UI package are available in the ProcessMaker open-source edition.

Process Modeler

1. When configuring a Task to use anonymous Web entry whereby any person may do that Task, the Password Protect setting in the Web Entry package that a person must enter to start that Task is now optional. The Web Entry package is not available in the ProcessMaker open-source edition.

Screen Builder

1. ProcessMaker user documentation now indicates that a visibility rule on a ProcessMaker Screen control overrides custom CSS designed for that Screen. For example, if custom CSS is designed to hide a ProcessMaker Screen control by default when that control’s visibility rule dictates that it be visible, the visibility rule overrides the custom CSS to display that control. As a best practice, use visibility rules instead of custom CSS to hide a control by default.
2. Searching on the Screens page to find a particular ProcessMaker Screen now functions more accurately.
3. When a ProcessMaker Collection record references a ProcessMaker Screen that contains a Watcher, the Watcher now properly runs. The ProcessMaker Collection package is not available in the ProcessMaker open-source edition.
4. Screen Builder now properly validates the data type for a control placed within a Record List control
5. A ProcessMaker user or ProcessMaker group member that does not have any ProcessMaker permissions may now view one of the following when assigned a Task:
   • The ProcessMaker Screen uses a Nest Screen control that contains an embedded Screen.
   • The ProcessMaker Screen uses additional pages accessible via a Page Navigation control.
6. The saved signature entered into a Signature control can no longer overwrite the signature already saved in another Signature control when both Signature controls are on separate ProcessMaker Screen pages. The Signature package that allows signatures be saved into ProcessMaker Screens is not available in the ProcessMaker open-source edition.
7. When using a File Preview control in a ProcessMaker Screen that is not configured with a file from which to preview when that Screen display, a message shows that the file is missing. The File Manager package that allows files be previewed within ProcessMaker Screens is not available in the ProcessMaker open-source edition.
8. A ProcessMaker user that does not have any ProcessMaker permissions may now properly view a Screen embedded into a Nested Screen control.
9. The Submit Button control now functions correctly when the ProcessMaker Screen also contains a Select List control.

ProcessMaker 4 version 4.0.7

Release Date: July 22, 2020

ProcessMaker is proud to announce the immediate availability of ProcessMaker version 4.0.7. 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.7 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.7 uses the following versions of Screen Builder and Process Modeler:

• ProcessMaker Query Language (PMQL): Version 1.1.3
• Process Modeler: Version 0.24.1
• Screen Builder: Version 0.24.3

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

Improvements

This section documents improvements for ProcessMaker version 4.0.7.

Core

1. #3167 : To enhance ProcessMaker security, unnecessary process data returned from a ProcessMaker Script is not saved to the ProcessMaker log.
2. #3218 : In Process Modeler, filtering a ProcessMaker asset name is improved when typing the asset name to select a ProcessMaker Script for a Script Task element or a ProcessMaker Screen for a Form Task or Manual Task element.
3. #3231 (in conjunction with Screen Builder # 763 ): The File Upload control in Screen Builder now has a Required setting to make uploading a file to that ProcessMaker Screen before that Task can be submitted.
4. #3233 : The URL to start a Request for a Process is now accessible as an HTML link from the Start button for that Request by right-clicking its Start button and then selecting your Web browser’s “copy link” function.

Screen Builder

1. #763 (in conjunction with Core #3231 ): The File Upload control in Screen Builder now has a Required setting to make uploading a file to that ProcessMaker Screen before that Task can be submitted.

Bug Fixes

This section documents bug fixes for ProcessMaker version 4.0.7.

Core

1. #3213 : The pagination buttons on the last page of the Requests page now properly display when that last page has fewer Requests to display than the set number per page.
2. #3214 : When using PMQL to perform an advanced Request search for an invalid user that does not exist in that ProcessMaker instance, ProcessMaker properly displays the message “No data available” instead of an error.
3. #3215 : The default ProcessMaker Script Executor for PHP now rebuilds correctly.
4. #3216 : Requests now start properly in a Process that use both an Intermediate Signal Throw element and Intermediate Signal Catch element in that Process.
5. #3217 : Action by Email and Send Email connectors may now be renamed from their default Process Modeler labels.
6. #3218 : When selecting a ProcessMaker Script for a Script Task element or a ProcessMaker Screen for a Form Task or Manual Task element, the items that dis
7. #3219 : In Process Modeler, you may now use the Backspace key to delete a ProcessMaker Screen from the Screen for Input setting as the Screen to use for a Form Task or Manual Task element.
8. #3220 : ProcessMaker Screens in Tasks now properly display ampersand (&) and apostrophe (‘) characters.
9. #3222 : The ProcessMaker Script Executor for NodeJS’s Docker container uses the LTS version to run ProcessMaker Scripts written in JavaScript.
10. #3282 : The Artisan command can now retry failed ProcessMaker Scripts.
11. #3286 and #3287 : Requests that a ProcessMaker user may start now properly display in the New Request screen.
12. #3425 : The ProcessMaker API now uses pagination to mitigate timeouts for Request lists.

Screen Builder

1. #746 / #754 : The Required If validation rule now properly validates a control’s value when it is not inside a Loop control’s container.
2. #764 : An editable Record List control that references two File Upload controls and a Checkbox control in its referencing Screen page functions correctly in the following circumstances:
   • One of the File Upload controls has a Visibility Rule setting to display only when the Checkbox control is selected.
   • During a Request that uses this ProcessMaker Screen, add a new record, select the Checkbox control to display the File Upload control with a Visibility Rule setting in the new record, and then upload a file to each File Upload control.
   • Each File Upload control has its uploaded file at the completion of that Request.
3. #765 : Validating a percentage between two values now works as expected.
4. #780 : Required controls within a Loop control that contain required data no longer prevent Form-type ProcessMaker Screens from submitting.

ProcessMaker 4 version 4.0.6

ProcessMaker is proud to announce the immediate availability of ProcessMaker version 4.0.6. This update brings multiple new features, 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.

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 uses the following versions of Screen Builder and Process Modeler:

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

For a complete list of features, improvements and fixes visit the documentation at:

https://processmaker.gitbook.io/processmaker-release-notes/processmaker-4.0.x/processmaker-4.0.6-release-notes

Download the processmaker4.0.6.tar.gz for the production build.

ProcessMaker 4 Version 4.0.5

ProcessMaker is proud to announce the immediate availability of ProcessMaker version 4.0.5. This update brings multiple new features, 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.

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.5 uses the following versions of Screen Builder and Process Modeler:

Process Modeler: Version 0.24.2
Screen Builder: Version 0.23.20

For a complete list of features, improvements and fixes visit the

ProcessMaker 4.0.5 Release Notes - ProcessMaker Release Notes

ProcessMaker 4 version 4.0.4

# Overview

ProcessMaker is proud to announce the immediate availability of ProcessMaker version 4.0.4. This update brings multiple new features, 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.

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.4 uses the following versions of Screen Builder and Process Modeler:

• ProcessMaker Query Language (PMQL): Version 1.1.3
• Process Modeler: Version 0.24.1
• Screen Builder: Version 0.23.3

For a complete list of features, improvements and fixes visit the ProcessMaker 4.0.4 Release Notes - ProcessMaker Release Notes

ProcessMaker 4 version 4.0.3

# Overview

ProcessMaker is proud to announce the immediate availability of ProcessMaker version 4.0.3. This update brings multiple new features, improvements, and bug fixes.

The ProcessMaker 4 platform makes it easy for Business Process Modeling to become full applications with our “low code/no code” approach using our BPMN 2.0-compliant suite of services.

This document contains Release Notes for ProcessMaker version 4.0.3 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 known issues associated with this release unless otherwise noted.

ProcessMaker version 4.0.3 uses the following versions of Screen Builder and Process Modeler:

• Screen Builder: Version 0.22.2

• Process Modeler: Version 0.18.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.3

Improvements

This section documents improvements for ProcessMaker version 4.0.3.

Core

1. #2865 : The Users page now displays a Deleted Users tab from which ProcessMaker users that have been deleted can now be restored. Restored users display in the Users page.

Screen Builder

1. #544 : The Submit Button control now has the following improvements:

   • Default functionality: The Submit Button control submits the Form-type ProcessMaker Screen.
   • Script functionality: Script functionality sets a value to another Screen control to trigger a Watcher.

2. #614 : Loop control settings are improved from the ones introduced in ProcessMaker version 4.0.1.

3. #621 : Configure a control based on the settings of an existing control in a ProcessMaker Screen by copying the existing control, thereby duplicating the control and its settings.

Bug Fixes

This section documents bug fixes for ProcessMaker version 4.0.3.

Core

1. #2843 : Process models that fail validation properly note the validation errors and highlight those elements and settings that do not meet validation.

2. #2874 : When a Request that uses a ProcessMaker Screen with a Nested Screen control, the data from a nested ProcessMaker Screen properly displays in the Request summary.

3. #2875 : ProcessMaker Environment Variables now allow long names at least 88.9 KB large.

4. #2882 : Requests that use Intermediate Timer Event elements now have workflow routing data in which to continue workflow routing.

5. #2908 : ProcessMaker Environment Variables can now have hyphens (-) in their names.

6. #2921 : ProcessMaker now properly allows any ProcessMaker Screen in that ProcessMaker instance be selected from packages not available in the ProcessMaker open-source edition, including the following:

   • Actions By Email package (which installs the Actions By Email connector in Process Modeler)
   • Send Email package (which installs the Send Email connector in Process Modeler)
   • Web Entry package (where a Screen can be selected from Start Event and Task elements)

Screen Builder

1. #539 : The following Screen Builder validation issues are addressed when configuring multiple validation rules for multiple controls in one page:

   • Validation rule setting labels and helper text is fixed (related to #568 ).
   • Input value(s) to one validation rule do not automatically display in another validation rule for the same or another control.
   • The ProcessMaker Screen cannot be submitted unless all validation rules are met.

2. #545 : When a Request that uses a ProcessMaker Screen with a Nested Screen control, the data from a nested ProcessMaker Screen properly displays in the Request summary.

3. #550 : Validation now properly applies to controls on a page that a Record List control references to enter records. For example, if a control is required on the page that a Record List control references for its records, that control must contain data for a record to be submitted to the Record List control.

4. #552 : After adding a record in a Record List during a Request, the controls are properly empty when a another record is added to that Record List.

5. #558 : The Options props in SortableJS , a library used in Screen Builder, has properly been deprecated from Screen Builder to use Vue.draggable instead.

6. #559 : When a Form-type ProcessMaker Screen is nested, its Submit Button control hides so that the ProcessMaker Screen using the Nested Screen control is used to submit that Screen.

7. #560 : From the Screens page where all ProcessMaker Screens are listed, successfully search for a Screen that has been nested into another Screen when your ProcessMaker instance has at least 11 Screens.

8. #561 : Request information entered into a nested ProcessMaker Screen from one page of a multi-page Screen properly displays in other pages of that Screen.

9. #562 : Request data entered from a previous ProcessMaker Screen in that Request now passes to a nested Screen when it displays.

10. #563 : Magic Variables in a Request now pass to a nested Screen when it displays.

11. #565 : ProcessMaker Screens that are nested inside a Nested Screen control properly display Custom Cascading Style (CSS) from the Screen using the Nested Screen control unless the nested Screen has its own CSS designed in the Custom CSS screen.

12. #566 : A ProcessMaker Screen that has already been displayed within another ProcessMaker Screen via a Nested Screen control cannot be displayed again. This prevents an infinite loop whereby two ProcessMaker Screens using Nested Screen controls cannot reference each other.

13. #567 : The message is more clear that warns that a Form-type ProcessMaker Screen without a Submit Button control cannot be submitted.

14. #568 : The setting label and the helper text for the Min Length validation rule now correctly describe that this validation rule checks for a specified minimum length of entered data entered into a control.

15. #569 : A typographical error is addressed in the message that a Record List control cannot reference its own page for controls to submit records to that control.

16. #570 : When configuring a Multicolumn/Table control, a message now displays in the following circumstances as guidance for proper configuration:
    * The total column width of all columns in the control does not equal 12.
    * If you attempt to enter a negative number as the column width for a column.

17. #571 : After clicking a Page Navigation control to navigate between pages in a multi-page ProcessMaker Screen, the top of the page displays instead of the bottom.

18. #572 : The Multicolumn/Table control now properly displays custom CSS applied to it.

19. #573 : The Record List control now properly references the variable names for controls that it references. The variable name is the value entered into the Variable Name setting value for a control.

20. #576 : An editable record list from a Record List control can how be submitted when one of the controls to submit a record is a required control.

21. #592 : The following buttons now work properly within a Loop control:
    * Page Navigation controls
    * Submit Button controls
    * The Add Record button to add a record in a Record List control

22. #594 : Labels now consistently read “Calculated Properties” instead of “Computed Properties” regarding the Calculated Properties function.

23. #602 : Record lists with more than 50 records properly display.

24. [#605](https://gi...