Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
ProcessMaker 4.0.x Release Notes
ProcessMaker Open Source Edition is licensed under the GNU Affero General Public License version 3.0. ProcessMaker Enterprise Edition is licensed under a separate enterprise agreement.
ProcessMaker user documentation and Release Notes may change without notice.
Current production version: ProcessMaker 4.4.1, released March 20, 2023. See Release Notes.
See ProcessMaker 4.1.x Release Notes, 4.2.x Release Notes, 4.3.x Release Notes, and 4.4.x Release Notes.
© Copyright 2000-2024 ProcessMaker Inc. All rights reserved.
ProcessMaker version 4.0.14 Release Notes
Release Date: October 22, 2020
ProcessMaker is proud to announce the immediate availability of ProcessMaker version 4.0.14. 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.14 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.
ProcessMaker version 4.0.14 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.11
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
This section documents bug fixes in conjunction with ProcessMaker version 4.0.14.
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
FOUR-2138: ProcessMaker Data Connectors now properly return an API response when that returned data is not in JSON format.
FOUR-1989: The Date Picker control now functions correctly when the ProcessMaker instance is in a time zone at UTC+0 or later.
ProcessMaker version 4.0.15 Release Notes
Release Date: November 5, 2020
ProcessMaker is proud to announce the immediate availability of ProcessMaker version 4.0.15. 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.15 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.
ProcessMaker version 4.0.15 core product uses the following versions:
ProcessMaker Query Language (PMQL): Version 1.1.3
Process Modeler: Version 1.1.2
Screen Builder: Version 1.1.12
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.2
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.3
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
This section documents bug fixes in conjunction with ProcessMaker version 4.0.15.
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
FOUR-2035: A parent Request may now start a child Request when the calling Sub Process element's outgoing Sequence Flow element connects to an Event-Based Gateway element.
FOUR-2077: ProcessMaker Screens that are too large to fit on one screen without scrolling now properly may be printed in their entirety to show all controls in that Screen.
FOUR-2080: Signal Start Event elements and Message Start Event elements now properly start child Requests when called from a parent Request.
FOUR-2146: When a self-service Task and an assigned Task fork after an Inclusive Gateway element, and the self-service Task completes first, the _user
ProcessMaker Magic Variable now retains its value for the Form Task element's assigned Task.
FOUR-2149: Laravel Horizon's PHP configuration file that sets Horizon's workload scaling and resource allocation is now more flexible to better handle when queue jobs quickly increase.
FOUR-1927: The File Upload control now functions as expected when setting or changing naming with folder formatting.
FOUR-2046: ProcessMaker users that log on via authenticated Web Entry are not properly redirected to the configured URL to view the Task.
ProcessMaker version 4.0.17 Release Notes
Release Date: January 8, 2021
ProcessMaker is proud to announce the immediate availability of ProcessMaker version 4.0.17. This update addresses one bug fix.
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.17 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.
ProcessMaker version 4.0.17 core product uses the following versions:
Nayra BPMN 2.0 engine: 1.1.2
ProcessMaker BPMN Moddle: 0.7.0
ProcessMaker Query Language (PMQL): Version 1.1.3
Process Modeler: Version 1.1.2
Screen Builder: Version 1.1.13
Script Executor for JavaScript: 1.0.1
Script Executor for Lua: 1.0.0
Script Executor for PHP: 1.0.0
Vue Screen Builder Form Elements: 0.15.8
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.3
Collections: package-collections 1.6.4
Comments: package-comments 1.0.3
Data Connectors: package-data-sources 1.0.20
Dynamic UI: package-dynamic-ui 1.0.1
File Manager: package-files 1.1.5
Google Places: package-googleplaces 1.1.3
PDF Generator Connector: connector-pdf-print 1.4.0
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.5
Script Executor for C#: docker-executor-csharp 1.0.1
Script Executor for Java: docker-executor-java 1.0.1
Script Executor for Python: docker-executor-python 1.0.0
Script Executor for R: docker-executor-r 1.0.0
Send Email Connector: connector-send-email 1.2.4
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.5
This section documents one bug fix in conjunction with ProcessMaker version 4.0.17.
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
FOUR-2550: Controls that are required within nested multi-page ProcessMaker Screens properly validate.
ProcessMaker version 4.0.16 Release Notes
Release Date: January 4, 2021
ProcessMaker is proud to announce the immediate availability of ProcessMaker version 4.0.16. This update addresses an improvement and 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.16 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.
ProcessMaker version 4.0.16 core product uses the following versions:
Nayra BPMN 2.0 engine: 1.1.2
ProcessMaker BPMN Moddle: 0.7.0
ProcessMaker Query Language (PMQL): Version 1.1.3
Process Modeler: Version 1.1.2
Screen Builder: Version 1.1.13
Script Executor for JavaScript: 1.0.1
Script Executor for Lua: 1.0.0
Script Executor for PHP: 1.0.0
Vue Screen Builder Form Elements: 0.15.8
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.3.0
Collections: package-collections 1.6.4
Comments: package-comments 1.0.3
Data Connectors: package-data-sources 1.0.20
Dynamic UI: package-dynamic-ui 1.0.1
File Manager: package-files 1.1.5
Google Places: package-googleplaces 1.1.3
PDF Generator Connector: connector-pdf-print 1.4.0
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.5
Script Executor for C#: docker-executor-csharp 1.0.1
Script Executor for Java: docker-executor-java 1.0.1
Script Executor for Python: docker-executor-python 1.0.0
Script Executor for R: docker-executor-r 1.0.0
Send Email Connector: connector-send-email 1.2.4
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.5
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.16.
FOUR-2449: Save search results only display columns affected by that Saved Search to decrease the amount of time to display the results and the data payload.
This section documents bug fixes in conjunction with ProcessMaker version 4.0.16.
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
FOUR-2417: ProcessMaker Screens function as expected in the following scenario:
A multi-page ProcessMaker Screen uses a Nested Screen control not on the first page to embed a second ProcessMaker Screen.
The second ProcessMaker Screen uses a Record List control on the first page. As required, that ProcessMaker Screen has a secondary page from which the Record List control references data entered into each record.
Both in Preview mode and during Requests, while viewing the secondary page on the first ProcessMaker Screen, the record list in the nested ProcessMaker Screen properly references its secondary page from which to enter data for each record.
FOUR-2455: Multi-page ProcessMaker Screens properly print correctly.
FOUR-2522: Request forms properly print after loading.
FOUR-2523: A Loop control with incorrectly formatted content properly retains entered content as new loops are added.
FOUR-2384: ProcessMaker group members that are configured to log on via SAML and see a custom experience configured via the Dynamic UI package properly see the customized top menu options and dashboard when they log on.
FOUR-2520: Files that have the same file name but uploaded using different Request variables are both available in the Request summary.
FOUR-2524: The File Manager tab in Request summaries shows the File Upload control label associated with each uploaded file to that Request, making it easier to understand which uploaded file corresponds with which control.
FOUR-2436: ProcessMaker Screens function as expected in the following scenario:
A multi-page ProcessMaker Screen uses a Nested Screen control not on the first page to embed a second ProcessMaker Screen.
The second ProcessMaker Screen uses a Record List control on the first page. As required, that ProcessMaker Screen has a secondary page from which the Record List control references data entered into each record.
Both in Preview mode and during Requests, while viewing the secondary page on the first ProcessMaker Screen, the record list in the nested ProcessMaker Screen properly references its secondary page from which to enter data for each record.
FOUR-2521: Text that has been previously entered into a Rich Text control loads more quickly so that the Request participant may add more text to the existing content.
FOUR-1837: HTML syntax properly renders in Rich Text controls when used in Email-type ProcessMaker Screens.
FOUR-2319: Task email notifications properly send emails when Request conditions are met as configured in the Expression setting for that Form Task element.
FOUR-2531: Special characters are no longer escaped in the email subject.
FOUR-2525: Files uploaded to each child Request initiated from a parent Request are available to download.
ProcessMaker version 4.0.12 Release Notes
Release Date: September 21, 2020
ProcessMaker is proud to announce the immediate availability of ProcessMaker version 4.0.12. 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:
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.
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
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.0
Collections: package-collections 1.6.1
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.1
Google Places: package-googleplaces 1.1.3
PDF Generator Connector: connector-pdf-print 1.3.1
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.2
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.3
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:
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
ProcessMaker version 4.0.13 Release Notes
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:
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.
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
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
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.
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.
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
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.
ProcessMaker version 4.0.11 Release Notes
Release Date: September 11, 2020
ProcessMaker is proud to announce the immediate availability of ProcessMaker version 4.0.11. 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:
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.
ProcessMaker version 4.0.11 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.4
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.0
Collections: package-collections 1.6.1
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.1
Google Places: package-googleplaces 1.1.3
PDF Generator Connector: connector-pdf-print 1.2.20
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.1
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.4
Vocabularies: package-vocabularies 2.2.0
Web Entry: package-webentry 1.2.2
This section documents improvements in conjunction with ProcessMaker version 4.0.11.
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 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:
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
Core product: ProcessMaker version 4.0.12 core-product functionality that is the .
: ProcessMaker now appropriately displays No data available for a PMQL search for a requester when the PMQL search query contains an invalid ProcessMaker user.
and : 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.
: 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).
: The PDF File Name setting used to specify the generated PDF's file name now only allows characters that Windows operating systems support in both plain-text and via a Request variable in mustache syntax.
: After customizing the columns for a Saved Search and then clicking the Reset to Default button, columns now properly return to the default columns without displaying a Web browser console error.
: The File Upload control now consistently stores the file ID of an uploaded file in Request data.
: 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.
: The Select List control now properly returns either single value or a JSON object regardless of whether the Allow Multiple Selections option is used.
: An editable Record List control that contains a second Record List control, of which has a configured column, may now save without errors.
: A Line Input control that validates for a date no longer freezes Screen Builder in Preview mode.
: 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.
: 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.
: The Display-type ProcessMaker Screen that the Web Entry package installs named "Web Entry Generic Thank You" may now use the _request.id
ProcessMaker Magic Variable in mustache syntax that represents the Request ID.
Core product: ProcessMaker version 4.0.13 core-product functionality that is the .
: 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.
: If a ProcessMaker Collection is deleted, all Saved Searches for that Collection now are automatically deleted.
: A Select List control in which its data source is a ProcessMaker Collection may filter from all the records in that Collection.
: 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.
: The Auth Clients page now contains pagination functionality.
: When using Mozilla Firefox browser, an error message no longer displays that the Request is aborted or 401
error (Unauthorized) after completing a Task.
: 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.
and : 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.
: Viewing a Task summary no longer displays a 500
error (Internal Server Error).
: 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.
: The Script Executors page now contains pagination functionality.
: The Auth Clients page search now supports upper-case characters in a search.
: 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.
: The _user
Magic Variable now properly stores the ProcessMaker user that self-assigned a self-service Task.
: 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.
: A validated Process model that contains a Sub Process element may now import correctly without displaying an error.
: A Select List control in which its data source is a ProcessMaker Collection may filter from all the records in that Collection.
: After a PDF Generator connector generates a PDF, Request data now stores the output PDF's ID instead of its file name.
: Start Event elements and End Event elements may now be properly copied without producing a console error.
: 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.
: Requests no longer error when the Process of such Requests route workflow in the following circumstances:
: Double-clicking on a Process model node no longer causes a console error.
: 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.
: 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.
: When clicking the Advanced panel for a selected Process model node, the Configuration panel no longer expands as well.
: 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.
: If a ProcessMaker Collection is deleted, all Saved Searches for that Collection now are automatically deleted.
: 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.
: 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.
: The Date Picker control now properly shows the control's date instead of datetime when configured to use Date
data type.
: File Download controls may now download files uploaded in a previous Task via a File Upload control that are 100 MB or larger.
: 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.
: 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.
: 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.
: 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.
: 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.
: 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.
: Web Entries authenticated via SSO now redirect properly to the initial URL.
Core product: ProcessMaker version 4.0.11 core-product functionality that is the .
: The performance is improved to search the results of a Saved Search.
: The Web browser no longer produces an Uncaught TypeError error in the Developer console when developing a properly-composed Advanced-type ProcessMaker Screen that otherwise contains no errors.
: A ProcessMaker user that is not assigned a Task during a Request but is tagged in a Task comment now automatically becomes a Request participant and can view that Task's summary to interact with that comment.
: 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.
: ProcessMaker group members assigned Request permissions can now view files uploaded to Requests in which they participate.
: 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
.
: The template that sends errors no longer has its own error.
: Data connectors designed with older versions of the ProcessMaker Data Connector package that use POST endpoints now no longer produce 500
errors (POST) in the browser console when used on the most recent Data Connector package version.
: The Select List control can now get its options properly by using a ProcessMaker Data Connector as its data source.
: Counters for Saved Search results using default PMQL search query settings, such as for Request or Task status, now match with the total number of applicable Requests/Tasks for that status type. For example, the number of completed Requests for a Process matches that for the Saved Search result of completed Requests.
: ProcessMaker users and/or all members of a ProcessMaker group that have been shared a Saved Search have access to view its results, but now cannot access the Request summaries from those Saved Search results. This redesign allows stakeholders that have been shared Saved Search results to be have an overview of Request data without accessing sensitive information that may be in Request summaries.
: Saved Search Chart controls used in Screen Builder may now be configured by ProcessMaker users that do not have the Make this user a Super Admin setting.
: When editing a Saved Search chart from one chart type to another, the new chart type now renders correctly without a horizontal visual distortion that cosmetically should not be in the chart data.
, , , and : Validation rules are now observed for controls that are contained within a Loop control.
: The Rich Text control now properly renders HTML from a Request variable in Email-type ProcessMaker Screens.
: When referencing a Request variable that uses the date
data type, the Line Input control no longer displays the datetime for that Request variable.
: A Start Event or Task element configured with Web Entry that requires authentication now properly provides ProcessMaker users or groups for which authentication is required.
ProcessMaker version 4.0.7 Release Notes
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 core product uses the following versions:
ProcessMaker Query Language (PMQL): Version 1.1.2
Process Modeler: Version 0.24.1
Screen Builder: Version 0.24.3
This section documents improvements for ProcessMaker version 4.0.7.
#3167: To enhance ProcessMaker security, unnecessary process data returned from a ProcessMaker Script is not saved to the ProcessMaker log.
#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.
#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.
This section documents bug fixes for ProcessMaker version 4.0.7.
#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.
#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.
#3215: The default ProcessMaker Script Executor for PHP now rebuilds correctly.
#3216: Requests now start properly in a Process that use both an Intermediate Signal Throw element and Intermediate Signal Catch element in that Process.
#3217: Action by Email and Send Email connectors may now be renamed from their default Process Modeler labels.
#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
#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.
#3220: ProcessMaker Screens in Tasks now properly display ampersand (&
) and apostrophe ('
) characters.
#3222: The ProcessMaker Script Executor for NodeJS's Docker container uses the LTS version to run ProcessMaker Scripts written in JavaScript.
#3282: The Artisan command can now retry failed ProcessMaker Scripts.
#3425: The ProcessMaker API now uses pagination to mitigate timeouts for Request lists.
#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.
#765: Validating a percentage between two values now works as expected.
#780: Required controls within a Loop control that contain required data no longer prevent Form-type ProcessMaker Screens from submitting.
ProcessMaker version 4.0.10 Release Notes
Release Date: August 28, 2020
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.
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.
ProcessMaker version 4.0.10 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.3
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.3
Auth: package-auth-auth0 1.0.1
Auth SAML: package-auth-saml 1.1.0
Collections: package-collections 1.6.0
Comments: package-comments 1.0.2
Data Connectors: package-data-sources 1.0.20
Dynamic UI: package-dynamic-ui 1.0.0
File Manager: package-files 1.1.0
Google Places: package-googleplaces 1.1.3
PDF Generator Connector: connector-pdf-print 1.2.20
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.0
Send Email Connector: connector-send-email 1.2.1
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.4
Vocabularies: package-vocabularies 2.2.0
Web Entry: package-webentry 1.2.0
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:
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
FOUR-1721: 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.
FOUR-1820: Files associated with a parent Request via a Sub Process are now available to all child Requests and vice versa.
FOUR-1658: The PDF Generator connector now has a new setting labeled PDF File Name. Use mustache syntax to reference a Request variable from which to name the generated PDF file instead of the ProcessMaker Screen name that the PDF Generator connector references.
FOUR-1688: The SAML Auth package now allows a ProcessMaker user to log on to ProcessMaker via Single Sign On (SSO) or ProcessMaker user name and password.
FOUR-1865: A new ProcessMaker permission in a new Saved Search category called Toggle Notifications allows a ProcessMaker user or members of a ProcessMaker group to toggle Saved Search notifications. If a ProcessMaker user is not granted this new permission, then that user does not receive notifications from the Notifications icon regarding Saved Searches. This permission is disabled by default.
This section documents bug fixes in conjunction with ProcessMaker version 4.0.10.
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
FOUR-1821: If a Process includes a Task that uses a ProcessMaker Screen of the Advanced Screen type with customized settings from the default template, the custom code now properly imports when the Process imports.
The Advanced Screen type is a highly technical solution only for advanced HTML and JavaScript designers intended only for specific solutions. ProcessMaker Support cannot support nor troubleshoot advanced forms.
As a best practice when developing Advanced-type ProcessMaker Screens, design your Screen outside of ProcessMaker to test its functionality, and then copy-and-paste your code into Screen Builder to test your Screen in Requests, Tasks or ProcessMaker Collections. The Advanced Screen type cannot be previewed in Screen Builder.
Please use at your own risk.
FOUR-1783: 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.
FOUR-1831: 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.
FOUR-1836: 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.
FOUR-1872: 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.
FOUR-1881: 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 version 4.0.8 Release Notes
Release Date: August 11, 2020
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 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.2
Process Modeler: Version 0.24.2
Screen Builder: Version 1.0.3
The following are the non-core package versions at the time of this release:
Actions By Email: package-actions-by-email 1.1.0
Advanced Forms: package-advancedforms 1.1.2
Auth: package-auth-auth0 1.0.1
Auth SAML: package-auth-saml 1.0.0
Collections: package-collections 1.5.0
Comments: package-comments 1.0.2
Data Connectors: package-data-sources 1.0.20
Dynamic UI: package-dynamic-ui 1.0.0
File Manager: package-files 1.0.3
Google Places: package-googleplaces 1.1.3
PDF Generator Connector: connector-pdf-print 1.1.2
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.7.0
Send Email Connector: connector-send-email 1.2.1
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.4
Vocabularies: package-vocabularies 2.2.0
Web Entry: package-webentry 1.2.0
This section documents bug fixes for ProcessMaker version 4.0.8.
The ProcessMaker API documentation for the GET
users
endpoint now accurately documents the body response.
The ProcessMaker API documentation for the POST
request files
endpoint now accurately documents the body response.
ProcessMaker now displays the appropriate error message when attempting to import an invalid ProcessMaker Screen into Screen Builder.
The ProcessMaker API documentation for the GET
processes
endpoint now accurately documents the body response.
The ProcessMaker API now requires a password for a new ProcessMaker user when creating that user via the POST
user
endpoint.
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.
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.
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.
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.
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.
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.
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.
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.
Searching on the Screens page to find a particular ProcessMaker Screen now functions more accurately.
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.
Screen Builder now properly validates the data type for a control placed within a Record List control.
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.
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.
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.
A ProcessMaker user that does not have any ProcessMaker permissions may now properly view a Screen embedded into a Nested Screen control.
The Submit Button control now functions correctly when the ProcessMaker Screen also contains a Select List control.
ProcessMaker version 4.0.9 Release Notes
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.
ProcessMaker version 4.0.9 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.2
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.3
Auth: package-auth-auth0 1.0.1
Auth SAML: package-auth-saml 1.0.0
Collections: package-collections 1.6.0
Comments: package-comments 1.0.2
Data Connectors: package-data-sources 1.0.20
Dynamic UI: package-dynamic-ui 1.0.0
File Manager: package-files 1.1.0
Google Places: package-googleplaces 1.1.3
PDF Generator Connector: connector-pdf-print 1.1.2
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.8.1
Send Email Connector: connector-send-email 1.2.1
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.4
Vocabularies: package-vocabularies 2.2.0
Web Entry: package-webentry 1.2.0
This section documents improvements in conjunction with ProcessMaker version 4.0.9.
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
#3276: 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.
#3307: 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.
#3323: A ProcessMaker Administrator may now prioritize queue workers.
package-files #25: The File Manager package has the following improvements:
Create folders in the Public folder.
Upload files to created folders in the Public folder.
The name of a file by default is how to reference that file in Variable Name setting in a ProcessMaker Screen.
Rename files from any folder within the Public directory.
The File Manager package is not available in the ProcessMaker open-source edition.
Collections #200: A Saved Search Chart control can now use an additional PQML query to visualize a Saved Search for a ProcessMaker Collection by referencing the Collection's ID in the additional PMQL query. The Saved Search package and the Collections package are not available in the ProcessMaker open-source edition.
This section documents bug fixes in conjunction with ProcessMaker version 4.0.9.
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
#3324: If the database becomes unresponsive, a Task still receives a valid token so that Task assignee may continue work on that Task.
FOUR-1430: 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.
FOUR-1539: A Task may be properly reassigned to another ProcessMaker user even when the original Task assignee is not the requester.
FOUR-1657: 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.
FOUR-1760: 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.
FOUR-1832: 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.
FOUR-1725: Searching for a Saved Search using the Search returns results more quickly.
FOUR-1733: Emails now properly distribute when sending a Saved Search report.
FOUR-1778: The PMQL comparative operator <=
now works in the Saved Search Chart control's Query setting to add an additional PMQL query to filter a chart's data.
FOUR-1852: Opening a Saved Search that does not have any columns set no longer causes an error.
#790: 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.
FOUR-1742 and FOUR-1846: 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.
FOUR-1789: 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.
FOUR-1819: 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.
FOUR-1855: 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.
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.
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
This section documents improvements for ProcessMaker version 4.0.6.
This section documents bug fixes for ProcessMaker version 4.0.6.
the Search setting page navigation to filter which authentication clients display on the page
page navigation to navigate multiple pages
ProcessMaker version 4.0.5 Release Notes
Release Date: May 26, 2020
ProcessMaker is proud to announce the immediate availability of ProcessMaker version 4.0.5. This update addresses multiple improvements, bug fixes, and known issues.
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.
ProcessMaker version 4.0.5 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.20
This section documents improvements for ProcessMaker version 4.0.5.
Anonymous: Start the Request anonymously. This is the default setting.
Previous Assigned User: The ProcessMaker user assigned the previous Task from the parent Process Request may start the child Request.
Requester: The Requester of the parent Request may start the child Request.
Users / Groups: A selected ProcessMaker user or members of a ProcessMaker group may start the child Request.
By User ID: The ProcessMaker user based on a Variable Name value as entered into a ProcessMaker Screen during a previous Task in the parent Request. For example, if a Line Input control in a ProcessMaker Screen has the Variable Name value of Name
, to contain a user's name, then the ProcessMaker user associated with that user ID may start the child Request.
Sequence Flow elements support counter functionality by adding 1
to an existing Request variable value.
Example: {{ VariableName }} + 1
, where VariableName
is the name of the Request variable to reference its value in the Request data, then add 1
.
This section documents bug fixes for ProcessMaker version 4.0.5.
The parent ProcessMaker Screen properly exports and imports. The parent ProcessMaker Screen contains the Nested Screen control(s).
The child ProcessMaker Screen properly exports and imports. The child ProcessMaker Screen is referenced from the parent Screen containing the Nested Screen control(s).
After placing a control into a Loop control, and then moving that placed control out of and above the Loop control properly moves that control out of the Loop control.
After placing a control above a Loop control, and then placing that control into the Loop control properly moves that control into the Loop control.
If the content in a control does not meet validation set for that control.
When the ProcessMaker Screen is submitted, the following validation occurs:
All controls in that ProcessMaker Screen undergo native Screen Builder validation.
If that ProcessMaker Screen contains custom CSS in the Custom CSS screen, custom CSS rules are validated.
After Date
After or Equal to Date
Before Date
Before or Equal to Date
Between Min & Max
In
Max Length
Min Length
Not In
Regex
Required Unless
Same
This section documents known issues for ProcessMaker version 4.0.5.
Watchers do not properly trigger when monitoring the initial selection of a Select List control. For example, when a Watcher monitors when a country is selected from one Select List control, the states and/or provinces in another Select List control do not load that country's states/provinces as options upon the initial selection from the first Select List control. A Request participant must make that selection again from the Select List control that the Watcher monitors for its selection.
This document contains Release Notes for ProcessMaker version 4.0.6 core-product functionality that is part of the , 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.
: The Loop control now functions in Display-type ProcessMaker Screens.
: Script Editor now functions correctly when ProcessMaker runs on Apple Safari browser.
: A ProcessMaker Screen that uses a Calculated Property that uses JavaScript to determine a date now properly does so.
: 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.
: Children Requests may now start from a parent Request even if that Request started anonymously.
: 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.
: 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.
: The Auth Clients page now contains the following:
: Searching for notifications from the All Notifications page now properly find notifications that contain at least one apostrophe ('
).
: Requests now properly complete for Processes that contain multiple parallel workflows and all Script Tasks in multiple parallel workflows complete.
: An ID now associates with each ProcessMaker user and ProcessMaker group.
: When installing ProcessMaker, an installation error no longer displays.
: 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.
: 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.
: The history for a Request now properly displays at the bottom of that Request's summary.
: The Required If validation rule properly evaluates if a control that requires a value contains a value prior to the submitting the ProcessMaker Screen.
: 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.
This document contains Release Notes for ProcessMaker version 4.0.5 core-product functionality that is part of the , 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.
: The Sub Process element now has an additional setting in Process Modeler that configures how a Request for that child Process starts. The child Process is the Process that the Sub Process element references from the parent Process containing that Sub Process element. The new setting is labeled Start Process As with the following options:
: Sequence Flow elements in a Process model now have the following improvements:
Sequence Flow elements support to reference Request variable values.
: The Validation Rule setting for controls that provide input validation for that control now displays an Update button and Cancel button to set or change parameters for a validation rule.
: The revised record list control message (documented in and ) updates the translation for that revised message. These bug fixes do not affect the ProcessMaker user interface.
: Screen Builder properly imports ProcessMaker Screens not assigned a Screen Category.
: When assigning a Task in Process Modeler by using a rule expression, it no longer displays an error in the Request summary and cause that Request's status be Error.
: If two Script Task elements run their respective ProcessMaker Scripts simultaneously in parallel, one Script cannot overwrite a Request Variable value that the other Script stores but does not change.
: ProcessMaker Screens with Nested Screen controls now properly export and import. If a Process contains one or more ProcessMaker Screen using the Nested Screen control, the following ProcessMaker assets properly export and import:
: If a Display-Type ProcessMaker Screen's Submit Button control is configured to set a value to another Screen control to trigger a Watcher () then that Screen may now properly import.
: The About page now properly displays instead of showing a server error.
: When configuring a new Script Executor from which to build a Dockerfile that runs ProcessMaker Scripts based on that supported programming language, a server error does not occur and a programming language may be selected.
: Using a Loop control in the following ways function as expected:
: The Web browser console no longer displays console errors when clicking the Add button in Preview mode to add a record in an editable Record List control.
and : The message that indicates when a Record List control contains no records now reads the following for greater clarity: This record list is empty or contains no data.
.
: Screen Builder now does not show validation errors until the following events occur:
, , and : Records from a Record List control properly display from within a column of a Multicolumn / Table control.
#: The Line Input control now properly displays Universal Time Coordinated (UTC) dates in Preview mode when its data type is set to date
or datetime
.
: Large single-page ProcessMaker Screens no longer freeze when opened.
: The following validation rules now properly function with the Date Picker control:
: When a Checkbox control is configured to be selected by default, that default selection now properly enter that Request's data when that ProcessMaker Screen is submitted.
ProcessMaker version 4.0.3 Release Notes
Release Date: March 13, 2020
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 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.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/or known issues associated with this release unless otherwise noted.
ProcessMaker version 4.0.3 core product uses the following versions:
ProcessMaker Query Language (PMQL): Version 1.1.2
Process Modeler: Version 0.18.5
Screen Builder: Version 0.22.0
This section documents improvements for ProcessMaker version 4.0.3.
#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.
#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.
#614: Loop control settings are improved from the ones introduced in ProcessMaker version 4.0.1.
#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.
#631: A Screen Builder variable called _parent
now contains Request data for Loop and Record List controls. The _parent
variable cannot be accessed or read from other ProcessMaker assets other than Screen Builder.
This section documents bug fixes for ProcessMaker version 4.0.3.
#2843: Process models that fail validation properly note the validation errors and highlight those elements and settings that do not meet validation.
#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.
#2875: ProcessMaker Environment Variables now allow long names at least 88.9 KB large.
#2882: Requests that use Intermediate Timer Event elements now have workflow routing data in which to continue workflow routing.
#2908: ProcessMaker Environment Variables can now have hyphens (-
) in their names.
#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)
#539: The following Screen Builder validation issues are addressed when configuring multiple validation rules for multiple controls in one ProcessMaker Screen 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.
#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.
#550: Validation now properly applies to controls on a ProcessMaker Screen 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.
#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.
#558: The Options
props in SortableJS, a library used in Screen Builder, has properly been deprecated from Screen Builder to use Vue.draggable
instead.
#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.
#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.
#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.
#562: Request data entered from a previous ProcessMaker Screen in that Request now passes to a nested Screen when it displays.
#563: Magic Variables in a Request now pass to a nested Screen when it displays.
#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.
#566: A ProcessMaker Screen that has already displayed within another ProcessMaker Screen via a Nested Screen control cannot display again in the same Request. This prevents an infinite loop whereby two ProcessMaker Screens using Nested Screen controls reference each other indefinitely.
#567: The message is more clear that warns that a Form-type ProcessMaker Screen without a Submit Button control cannot be submitted.
#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.
#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.
#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.
#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.
#572: The Multicolumn/Table control now properly displays custom CSS applied to it.
#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.
#576: An editable record list from a Record List control can now be submitted when one of the controls to submit a record is a required control.
#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
#594: Labels now consistently read "Calculated Properties" instead of "Computed Properties" regarding the Calculated Properties function.
#602: Record lists with more than 50 records properly display.
#605: Nested ProcessMaker Screens are properly validated before the Screen using the Nested Screen control submits.
#611: ProcessMaker Screens used in the ProcessMaker Web Entry package can now be nested in a Nested Screen control.
ProcessMaker version 4.0.4 Release Notes
Release Date: April 29, 2020
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.
This document contains Release Notes for ProcessMaker version 4.0.4 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.4 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.3
This section documents new features for ProcessMaker version 4.0.4.
#2887: ProcessMaker administrators may now add custom third-party packages to properly run ProcessMaker Scripts that require them. For example, to run a ProcessMaker Script that calls a Google API endpoint that requires a Google package to run successfully, add that package to your ProcessMaker instance so that any ProcessMaker Script that requires it can access it when that Script runs.
#1167: Process Modeler now supports the Terminate End Event element. When a Terminate End Event element triggers during a Request, all workflow associated with that Request, including parallel workflow and child Requests started from a Sub Process element, terminate immediately to end all Request workflow. That Request completes.
#2990, #3007 and #3058: Process Modeler now supports the following BPMN 2.0 elements related to Signal events:
Signal Start Event element: Start a new Request when this element receives a selected signal from an Intermediate Signal Throw Event or Signal End Event element from any other Request in that ProcessMaker instance.
Intermediate Signal Throw Event element: After this element triggers, broadcast a selected signal. Any of the following elements configured to monitor for that signal trigger:
Signal Start Event element
Intermediate Signal Catch Event element
Boundary Signal Event element
Intermediate Signal Catch Event element: Resume workflow for a Request when this element receives a selected signal from an Intermediate Signal Throw Event or Signal End Event element from any other Request in that ProcessMaker instance.
Boundary Signal Event element: If this element receives a selected signal from an Intermediate Signal Throw Event or Signal End Event from any other Request in that ProcessMaker instance, alternate workflow routes through that element instead of its associating element. A Boundary Signal Event element can associate with any of the following element types:
Task element (now called Form Task element, #1138)
Manual Task element
Script Task element
Signal End Event element: After this element triggers, broadcast a selected signal, and then complete that Request. Any of the following elements configured to monitor for that signal trigger:
Signal Start Event element
Intermediate Signal Catch Event element
Boundary Signal Event element
This section documents improvements for ProcessMaker version 4.0.4.
#2896: Links to the Software Development Kit (SDK) and ProcessMaker Application Program Interface (API) documentation are now included when a new ProcessMaker Script is created.
#2982: The shared memory in Docker containers that securely run ProcessMaker Scripts has been increased to 256 MB.
#3036: Web Entry portals using ProcessMaker now have the following improvements:
Use the embed code for a ProcessMaker Screen to embed that Screen into your web portal. See an example of this improvement at c19report.com.
When clicking the Page Navigation control in a multi-page ProcessMaker Screen for a Task, the page automatically scrolls to the top when it displays.
#3037: The latest Vue Form Elements and Screen Builder packages are now part of core that provide improvements to Screen Builder controls.
#3040: When ProcessMaker runs a Script securely in a Docker container, ProcessMaker ensures resources are allocated for any custom images. This improvement does not affect the ProcessMaker user interface.
#1098: Process designers may now align and/or distribute multiple BPMN elements and/or connectors (objects) placed in a Process model for greater legibility. Multiple objects must be selected (#1100). Boundary-type elements associated with any selected elements are not affected: they remain with their respective elements. Sequence Flow elements, Message Flow elements, and/or Association elements are not affected: they maintain their connections with their respective objects. Lane elements are not affected.
Process Modeler now has the following icons from left to right in the same bar as the Process name:
Align Left: Left-justifies two or more selected objects based on the left-most element/connector selected.
Center Horizontally: Horizontally centers two or more selected objects based on the horizontal center location of all the selected elements/connectors.
Align Right: Right-justifies two or more selected objects based on the right-most element/connector selected.
Align Bottom: Bottom-justifies two or more selected objects based on the bottom-most element/connector selected.
Center Vertically: Vertically centers two or more selected objects based on the vertical center location of all the selected elements/connectors.
Align Top: Top-justifies two or more selected objects based on the top-most element/connector selected.
Distribute Horizontally: Horizontally distributes three or more selected objects based on the placement of the left-most and right-most selected elements/connectors. If a Pool element is among the selections, elements and/or connectors in that Pool element are not affected.
Distribute Vertically: Vertically distributes three or more selected objects based on the placement of the top-most and bottom-most selected elements/connectors. If a Pool element is among the selection objects, objects in that Pool element are not affected. Selected objects that are in different Lane elements may cause one or more objects to move to a different Lane element.
#1099: Process designers may now copy a selected BPMN element or connector that is placed in a Process model. In doing so, the copied element/connector has the same settings as its source. Select the element or connector to copy, and then select the Copy Element icon.
#1100: Process designers may now selected multiple BPMN elements and/or connectors (objects) placed in a Process model to either move them together or or align/distribute them (#1098). If the multiple objects are inside a Pool element, then only the first object is affected: multiple objects cannot be selected. To select multiple objects, select one object, hold the Shift key, and then select other non-Pool element objects.
#1138: The following labeling changes clarify that Request participants use forms when working on Tasks:
In the Elements and Connectors palette that is to the left of the Process Modeler canvas, the Task element label has been changed to Form Task.
After placing a Form Task element in the Process model, the option to place a Task a Request participant performs has been changed to Form Task.
#1139: If the Process Modeler palettes are hidden when a Process model element or control is selected, the Settings palette now automatically displays to show the selected element/control settings. When the element/control is no longer selected, such as by clicking the Process Modeler canvas, the Settings palette automatically hides.
#1147: Process designers may now change the color of a selected BPMN element or connector that is placed into a Process model. Select from pre-set colors or your own custom color. The color of the text label also changes. Changing the color does not affect workflow routing. Select the element or connector in which to change its color, and then select the Open Color Palette icon.
#1184: Sequence Flow elements can now be set as the default outgoing Sequence Flow element from an Exclusive Gateway or an Inclusive Gateway element. If none of the conditions specified in any of the outgoing Sequence Flow elements meet the Request conditions to trigger, the default outgoing Sequence Flow triggers, thereby preventing the Request from pausing indefinitely. If a Sequence Flow element is set as the default, then its evaluation is ignored and it triggers by default. Only one outgoing Sequence Flow element from an outgoing Exclusive Gateway or Inclusive Gateway element may be set as the default.
#15: The Rich Text control now supports images and page breaks.
#619: When a Select List control uses a JSON array of objects as its options, settings are redesigned such that any of the following may become the Variable Name setting value for the Select List control:
the name of one selected JSON object
the value for one selected JSON object
a selected JSON object that contains all its object properties
Example:
Suppose that a Select List control uses the the following nested JSON array of objects to include as options:
company = {
"name": "Company",
"CEO": "Bob",
"employees": [
{ "name": "Diane", "more": ["email": "diane@company.com", "title": "CTO"] },
{ "name": "Harry", "more": ["email": "harry@company.com", "title": "CFO"] },
{ "name": "Beatty", "more": ["email": "beatty@company.com", "title": "COO"] },
]
}
If the Request data from the JSON array employees
are options for the Select List control, and the options are shown from the object property more.title
, then CTO
, CFO
, and COO
would display as options. When one or more options are selected, either the object property more.title
or the value(s) CTO
, CFO
, and/or COO
become the Variable Name setting value for the Select List control.
#620: When typing in a multi-select Select List control to filter its options during a Request, the option(s) that match entered text automatically filter. This makes it easier and faster to locate the specific option(s) to select.
#654: Screen Builder now has the following validation rule types for controls that support validation:
After a date: Validate that the date entered into the control is after a specified date. Applies to Date Picker and Line Input controls.
After or equal to a date: Validate that the date entered into the control is after or the same as a specified date. Applies to the Date Picker and Line Input controls.
Before a date: Validate that the date entered into the control is before a specified date. Applies to the Date Picker and Line Input controls.
Before or equal to a date: Validate that the date entered into the control is before or the same as a specified date. Applies to the Date Picker and Line Input controls.
Regex pattern: Validate that the value entered into the control contains a specified text by matching a specific search pattern for that text. For example, use a Regex pattern validation rule to search for a date within a paragraph entered into a Textarea control.
#646: If a Screen Builder control has a defined default value, that default value is already entered or selected in that control to indicate that default value.
#661: Any additional Loops added while doing a Task may now be removed if necessary.
#665: The toolbar for the Rich Text control now docks at the top of the Rich Text control editor space.
This section documents bug fixes for ProcessMaker version 4.0.4.
#2096: All ProcessMaker assets associated with an exported ProcessMaker Screen are intact when that Screen is imported, including nested Screens, Scripts, and connectors.
#2897: All usernames and passwords are hidden in ProcessMaker Environment Variables.
#2932: Request histories now display the label how a Gateway-type element evaluated in a Request. This bug fix applies to all Gateway-type BPMN elements ProcessMaker supports.
#2975: The Remember me function from the ProcessMaker log on page that remembers the last valid log on credentials now properly functions.
#2977: Packages and their versions that are not part of the core-product functionality properly display in the About page.
#2978: Pending Tasks now properly indicate that they are completed even if such a Task is not accessed through the notification displayed from the Notification icon.
#2979: Columns in the To Do Tasks page now display in a non-English language when the ProcessMaker user changes the language to display ProcessMaker labels and messages. Note that English-language is the default language and the only natural language provided for the ProcessMaker open-source edition. However, if the Translations package is installed to your ProcessMaker instance, you may display the ProcessMaker user interface labels and messages to German-, Spanish-, or French-language.
#2997: The page navigation buttons on the Users page that list all ProcessMaker users in that ProcessMaker instance now function correctly.
#3019: The Composer.lock
file now is properly in-sync. This issue did not affect product functionality prior to it being addressed.
#3028: ProcessMaker now properly associates with existing Docker images when running a Script.
#13: The PMQL operator !=
properly functions as the "not equal to" operator.
#1148: The Process Modeler validation console does not display a validation error when any connector is added to an opened Process model.
#173: The Rich Text control properly opens hyperlinks that have been placed into its content.
#635: The Loop control can read the value of the _parent
variable (introduced in ProcessMaker 4.0.3), but cannot change its value. This prevents the Loop control from possibly changing the _parent
variable value to the Variable Name setting value of a control that the Loop control includes in the set of controls that it duplicates, thereby causing an infinite loop whereby the Loop control indefinitely calls itself.
#637: When a Currency data type value that does not use a currency symbol (such as EUR) is entered into a Line Input control, the currency amount no longer displays as a null value in Preview mode.
#638: When a Loop control that contains other controls is placed into a Multicolumn / Table control, that Loop control as well as the control it contains now display properly in the Multicolumn / Table control.
#639: The tooltip for the function to copy a ProcessMaker Screen control and its settings now displays Copy Control to match usability language throughout ProcessMaker.
ProcessMaker version 4.0.1 Release Notes
Release Date: February 10, 2020
ProcessMaker is proud to announce the immediate availability of ProcessMaker version 4.0.1. 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.
ProcessMaker version 4.0.1 core product uses the following versions:
ProcessMaker Query Language (PMQL): Version 1.1.2
Process Modeler: Version 0.18.4
Screen Builder: Version 0.2.6
This section documents new features for ProcessMaker version 4.0.1.
Command-line installation flags: Install ProcessMaker using command-line flags instead of running the step-by-step installer. Run php artisan
from the command line for commands.
Start Event Interstitial: Configure an interstitial to run as soon as a Request starts. The page refreshes automatically until the Task assignment or the Request is completed.
Loop control: Use a Loop control in ProcessMaker Screens to design a set of ProcessMaker Screen controls into a container to loop a set number of times. During the Request, the Request participant enters information for all controls in the container the set number of times. As an example, design a container of controls into which the Task assignee enters the prescription name, dosage, and prescribing doctor for each prescription.
Nested Screens: Embed one or more ProcessMaker Screens into another Screen, thereby referencing the embedded Screens. If a nested ProcessMaker Screen is changed, it is automatically updated in any Screen it is nested.
Default values: Set the default values for ProcessMaker Screen controls, thereby requiring Screen users less effort to enter information into your Screens.
Watcher Import/Export: Import and export Watchers from one ProcessMaker Screen to another. In doing so, the ProcessMaker Data Connector/ProcessMaker Script configuration settings are also imported/exporting, making it easier to share and start using Watchers in other ProcessMaker Screens.
This section documents improvements for ProcessMaker version 4.0.1.
Expression labels now show Label Copy: Outgoing Sequence Flow elements from Gateway-type elements now display the label set by the Process designer instead of the expression.
Editable labels for Connectors: The default labels in ProcessMaker connectors can be customized from their default values.
Closer element support: Elements in a Process model can be positioned closer together before the Sequence Flow elements loop around the connecting elements.
Variable default naming: Variables automatically are named as you add them into a ProcessMaker Screen.
Validated UI redesign: Validation rules can now be quickly added using the new rules user interface (UI).
Settings are presented in a different order: Control settings are presented in a different order for greater usability.
Improved Watcher UI: The Watcher user interface (UI) has been updated to make it easier to use, including a more clearly labeled user interface and messages, as well as how Watchers are organized.
This section documents bug fixes for ProcessMaker version 4.0.1.
Processes and Process Categories
ProcessMaker Scripts and Script Categories
ProcessMaker Screens and Screen Categories
ProcessMaker version 4.0.2 Release Notes
Release Date: February 21, 2020
ProcessMaker is proud to announce the immediate availability of ProcessMaker version 4.0.2. 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.
ProcessMaker version 4.0.2 core product uses the following versions:
ProcessMaker Query Language (PMQL): Version 1.1.2
Process Modeler: Version 0.18.4
Screen Builder: Version 0.2.6
This section documents bug fixes for ProcessMaker version 4.0.2.
This document contains Release Notes for ProcessMaker version 4.0.1 core-product functionality that is part of the , 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 Scripts may now be properly copied by using the Copy icon.
: Requests that are in Error status may continue if the expression for at least one outgoing Sequence Flow from an Exclusive Gateway element is changed to allow conditions in that Request to continue. Furthermore, a more descriptive error displays when a Request errors in this situation.
: The Custom UI feature properly refreshes the ProcessMaker interface when user interface (UI) changes are made.
: ProcessMaker user name accounts now support UTF-8 characters for the First Name and Last Name settings.
: Apostrophe characters ('
) are allowed in the names for the following:
: ProcessMaker group members who are not assigned Category permissions for Processes, ProcessMaker Scripts, or ProcessMaker Screens no longer see the following error message: this action is unauthorized.
: ID column values throughout ProcessMaker, such as for Requests and Tasks, are now HTML hyperlinks instead of JavaScript.
: ProcessMaker records when a Process is created or edited.
: Requests now properly record Request data when Start Event elements trigger, such as when a Start Event element triggers.
: The ProcessMaker payload size is now optimized to increase performance.
: While previewing a ProcessMaker Screen that uses a Page Navigation control, the Data Preview panel now displays the JSON data model while previewing the Page Navigation control.
: When configuring a Task element that uses the Display Next Assigned Task To Task Assignee setting, the Screen Interstitial setting is now required. This prevents Requests from causing an error because the ProcessMaker Screen to display has not been configured in the Process model.
: In-progress Requests that use a Sub Process element, which in turn uses its own Sub Process element, properly continue when both the grandchild and child Requests complete.
: Invalid third-party XML-structured Process models can no longer be imported into Process Modeler.
: Intermediate Timer Event elements in an in-progress Request no longer causes ProcessMaker to stop responding.
: Requests now properly record Request data when Start Event elements trigger, such as when a Start Event element triggers.
: While previewing a ProcessMaker Screen that uses a Page Navigation control, the Data Preview panel now displays the JSON data model while previewing the Page Navigation control.
: If JSON data from the Data Input panel in Preview mode is changed to invalidate the JSON structure, the ProcessMaker Screen still validates if the ProcessMaker Screen is valid in Design mode.
: As part of the improved Watcher user interface, the Watcher user interface (UI) has been updated to make it easier to use, including a more clearly labeled user interface and messages, as well as how Watchers are organized.
This document contains Release Notes for ProcessMaker version 4.0.2 core-product functionality that is part of the , 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.
: Intermediate Timer Event elements properly display a routing error message.