Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Learn about improvements to previously released features that are now available in ProcessMaker version 4.2 for ProcessMaker build 4.2.30.
These release notes document new improvements available in ProcessMaker version 4.2.30. Platform section documents new improvements also available in the ProcessMaker open-source edition. Improvements to Enterprise packages are documented in alphabetical order below the Platform section.
ProcessMaker version 4.2.30 is compatible to upgrade from any ProcessMaker version 4.x. ProcessMaker version 4.2 introduces many new features and improvements that were introduced in ProcessMaker version 4.2.29.
See the following important sections that describe changes to ProcessMaker version 4.2.30 from previous ProcessMaker 4 versions:
See the following sections of ProcessMaker version 4.2.29 Release Notes:
As necessary, a ProcessMaker CloudOps engineer may add a custom email footer that displays at the bottom of all emails distributed by your ProcessMaker instance.
As necessary, a ProcessMaker CloudOps engineer may add HTML to the head tag of your ProcessMaker instance so that custom HTML displays. This may include custom CSS or script injections for analytics platforms.
The Customize UI settings now supports custom favicons.
ProcessMaker version 4.2.30 Release Notes.
Release Date: May 25, 2022. This release is not allowed for distribution. Instead, see ProcessMaker version 4.2.31 Release Notes.
ProcessMaker is proud to announce the immediate availability of ProcessMaker version 4.2.30. This update includes multiple improvements, bug fixes, and a known issue.
Create BPMN 2.0-compliant business processes using the ProcessMaker 4 platform's low-code approach. Design and deploy automated workflows that deliver true digital agility to your organization.
ProcessMaker version 4.2.30 is compatible to upgrade from any ProcessMaker version 4.x. ProcessMaker version 4.2 introduces many new features and improvements that were introduced in ProcessMaker version 4.2.29.
See the following important sections that describe changes to ProcessMaker version 4.2.30 from previous ProcessMaker 4 versions:
See the following sections of ProcessMaker version 4.2.29 Release Notes:
See the following sections for core product and non-core package versions for ProcessMaker version 4.2.30:
Core product: ProcessMaker version 4.x core-product functionality is the ProcessMaker open-source edition.
Non-core packages: ProcessMaker version 4.x packages 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.x. Release Notes that affect package functionality are documented in separate sections.
Release notes are cumulative with all previous ProcessMaker 4.x releases, and document new features, improvements, bug fixes, and/or known issues associated with this release unless otherwise noted.
ProcessMaker version 4.2.30 allows a more restricted set of non-alphanumeric characters in ProcessMaker usernames than ProcessMaker version 4.1.27 and earlier versions. Aside from alphanumeric characters, ProcessMaker 4.2.30 allows only the underscore (_
) and the hyphen character (-
) in usernames.
Ask your ProcessMaker Customer Success agent to coordinate reviewing all usernames in your ProcessMaker instance before your instance is upgraded to ProcessMaker version 4.2.30.
See the following topics in ProcessMaker documentation:
ProcessMaker version 4.2.30 now disables by default the number of items that correspond to each Saved Search when viewing the names of Saved Searches from the left sidebar. Prior to ProcessMaker 4.2.30, the number of applicable Requests, Tasks, or Collections displayed beside the name of that Saved Search. To increase performance, this number is disabled by default.
If you need the number of items that correspond to each Saved Search enabled, please submit a Support ticket.
Learn about bug fixes in ProcessMaker version 4.2 for ProcessMaker build 4.2.30.
These release notes document bug fixes addressed in ProcessMaker version 4.2.30.
See the following important sections that describe changes to ProcessMaker version 4.2.30 from previous ProcessMaker 4 versions:
See the following sections of ProcessMaker version 4.2.29 Release Notes:
ProcessMaker Support ticket numbers are in bold text preceding the bug fix description.
Tasks may now be properly opened.
26190: The appropriate Script Executor properly runs a Script using the appropriate user's authentication during a Request after that Process has been imported to that ProcessMaker environment.
27668: The number of in-progress and completed Requests is appropriate for each Process in a ProcessMaker environment.
The Requests page does not display by default when logging on after the previous session has timed out.
The Tasks tab in completed Requests no longer displays because there are no other Tasks to be done.
PDFs generated by a ProcessMaker Script properly display in preview.
HTML files generated by a ProcessMaker Script may properly be downloaded from the File Manager tab in a Request summary.
Validation rules properly evaluate JSON object data in a variety of levels.
Row content correctly obtains data in the Notifications table.
Start Event elements configured with Web Entry and an Interstitial Screen route route a Request correctly when that Start Event element is immediately followed by a Script Task element. Processes that are designed as follows route Requests and use Interstitial Screens properly:
A parent Process is configured with a Start Event element and Form Task element to each use an Interstitial Screen.
The parent Process uses a Sub-Process element that calls a child Request.
The child Process uses a Start Event element, Script Task element, and End Event element.
Toggle keys/check boxes can no longer be modified when viewing a Screen for a completed Task from the Forms tab of a Request summary.
25596: A Task which is interrupted by a boundary-type event properly does not display in that Request's history because that Task never completed.
26190: After a Process is imported, Script Task elements properly retain with which user each Script is configured to run.
Imported Processes that use a Script Task element properly start.
An interstitial Screen properly displays only once when immediately following that Task's element is a Sub Process element in which a Script Task is within the child Process.
26659: Users with the Make this user a Super Admin option enabled can no longer accept Self-Service Tasks that are not potential Tasks assignees in that Request.
26665: Processes properly start Requests when the first Task in that Request is a Form Task element that uses a Screen containing a File Upload control in a Loop control.
26852: Processes correctly start Requests that properly validate.
26895: An existing Process may be opened, redesigned, and then saved without causing an invalid error.
A Request properly displays its summary from an End Event element when that element is preceded by a Form Task element using an Interstitial Screen and a Script Task, in that order.
Validation rules properly function in different JSON object levels and with visibility rules during a Request.
The _parent
internal variable properly allows the file preview of an uploaded file when that File Upload control is within a Loop control.
26955: When a File Upload control is included as part of a Record List, which itself is in a Loop control, the file uploaded to each looped record in the Record List remains available.
When both a File Upload control and a Loop control are part of a Record List, files uploaded via the File Upload control in multiple loops of a record remain available in subsequent Tasks of that Request.
A Screen may use more than one Submit button as long as only one of them is configured to submit (as opposed to save) without causing a validation error.
The File Upload control's progress bar properly fits within the Add screen when uploading a file.
Synchronizing with LDAP users that contain metadata import correctly.
A user that logs on to ProcessMaker via SAML properly times out for proper security.
28030: Searching for records in a Collection using PMQL based on dates properly returns record results.
Dashboards properly display for the appropriate users and/or groups after their ProcessMaker environment updates to ProcessMaker version 4.2.30.
During a Request, if a file is uploaded to an initial Task, followed by a Sub Process, that file is available to download from a subsequent Task.
The +Upload Public File screen properly displays to upload a public file.
The following message properly displays when an invalid file ID instead of an error message: No files available for download.
Large files uploaded to a Task properly show the progress bar that indicates how much of that file has uploaded.
A file uploaded via a File Upload control within a Loop control of one Task properly previews and may be downloaded from a second Task that references the JSON array from the first Task.
A timed-out anonymous Web Entry no longer redirects to the ProcessMaker login page.
27527: Start Event elements configured with Web Entry and an Interstitial Screen route route a Request correctly when that Start Event element is immediately followed by a Script Task element.
ProcessMaker version 4.2.30 is compatible to upgrade from any ProcessMaker version 4.x. ProcessMaker version 4.2 introduces many new features and improvements that were introduced in .
.
.
View links to system requirements and special instructions to install the on-premises ProcessMaker open-source edition.
See these on-premises server requirements prior to installing the ProcessMaker open-source edition on-premises.
ProcessMaker requires the following newer system requirements than those from ProcessMaker 4.0.x:
PHP 7.3 or later
Please be aware of known issues in ProcessMaker version 4.2.30.
These release notes document a known issue in ProcessMaker version 4.2.30.
When previewing a Screen that has more than one page, only images on the first page preview in the Form tab. Images on subsequent pages do not preview. Instead, the following message displays: Something went wrong and the file cannot be previewed. Click the download button to continue. No files available for download.
When previewing a Record List control that contains no records, the following error message displays: There is a validation error in your form.. This message does not impact preview functionality or in-progress Requests.
Workaround: Close the message.
Conversation-type Screens do not function correctly in the following situations:
Controls in a Conversation Screen do not display when that Screen is used for Web Entry.
After configuring two or more Select List controls in a Conversation Screen, only the first Select List control functions correctly in preview.
The Conversation package is being redesigned for a future release.
When email server settings are updated, the old settings remain cached in memory. The old email server settings display in the Email Report screen for that Saved Search. The email server uses these old settings to email the Saved Search report.
Review product versions available in the open-source for ProcessMaker 4.2 for build 4.2.30.
The following are the product versions available in the open source for ProcessMaker 4.2.30's release:
Nayra BPMN 2.0 engine: Version 1.9.3
ProcessMaker BPMN Moddle: Version 6.0.2
ProcessMaker Query Language (PMQL): Version 1.5.1
Process Modeler: Version 1.22.0
Screen Builder: Version 2.28.1
Script Executor for Lua: Version 1.0.0
Script Executor for Node: 1.0.2
Script Executor for PHP: Version 1.0.0
Vue Screen Builder Form Elements: Version 0.29.0
Review Enterprise package versions for ProcessMaker 4.2.30.
The following are the Enterprise package versions in conjunction with ProcessMaker 4.2.30's release:
Actions By Email: package-actions-by-email 1.3.16
Advanced Forms: DEPRECATED in March 2021; no longer supported
Advanced User Manager: 0.1.2
Auth: package-auth-auth0 1.4.14
Auth SAML: package-auth-saml 1.3.2
Collections: package-collections 2.5.17
Comments: package-comments 1.2.1-RC3
Conversation Forms: package-conversational-forms 1.1.7
Data Connectors: package-data-sources 1.9.15
DocuSign Connector: connector-docusign 0.1.9
Dynamic UI: package-dynamic-ui 1.3.7
File Manager: package-files 1.3.12
Google Places: package-googleplaces 1.1.7
PDF Generator Connector: connector-pdf-print 1.7.7
Process Documenter: package-process-documenter 1.0.3-RC1
Process Optimization: package-process-optimization 1.1.1-RC1
Salesforce Connector: connector-salesforce 1.1.1
Saved Searches: package-savedsearch 1.16.12 (See section Number of Items for Each Saved Search Disabled by Default)
Script Executor for C#: docker-executor-csharp 1.0.1
Script Executor for Java: docker-executor-java 1.0.1
Script Executor for Node: docker-executor-node-ssr 1.0.0
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.9.15
Sentry: package-sentry 1.1.2
Signature: package-signature 1.2.3
Slack Notification Connector: connector-slack 1.1.3
Translations: package-translations 2.1.3
Versioning: package-versions 1.1.4-RC
Vocabularies: package-vocabularies 2.5.6-RC
Web Entry: package-webentry 2.3.10