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.35.
These release notes document new improvements available in ProcessMaker version 4.2.35. Improvements to Enterprise packages are documented below.
ProcessMaker version 4.2.31 and later 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.31 and later from previous ProcessMaker 4 versions:
See the following sections of ProcessMaker version 4.2.29 Release Notes:
Create custom Web Entry URLs based on Request variable values in the JSON data model.
Please be aware of known issues in ProcessMaker version 4.2.35.
These release notes document a known issue in ProcessMaker version 4.2.35.
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.
Clicking the Reset button from a customized user interface configured in the Custom UI feature does not reset to the default logo and icons.
After uploading a file via a File Upload control that is a required control in that Task, the following message displays momentarily after the Task is submitted: Field is required
. This message displays incorrectly because the uploaded file is now properly in that Request's data. The message may be ignored.
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.
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
Review product versions available in the open-source for ProcessMaker 4.2 for build 4.2.35.
The following are the product versions available in the open source for ProcessMaker 4.2.35's release:
Nayra BPMN 2.0 engine: Version 1.9.4
ProcessMaker BPMN Moddle: Version 6.0.2
ProcessMaker Query Language (PMQL): Version 1.6.1
Process Modeler: Version 1.23.0
Screen Builder: Version 2.50.0
Script Executor for Lua: Version 1.0.0
Script Executor for Node: 1.0.0
Script Executor for PHP: Version 1.0.1
Vue Screen Builder Form Elements: Version 0.29.1
ProcessMaker version 4.2.35 Release Notes.
Release Date: September 28, 2022.
ProcessMaker is proud to announce the immediate availability of ProcessMaker version 4.2.35. 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.31 and later 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.32 and later 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.35:
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.31 and later allows a set of non-alphanumeric characters in ProcessMaker usernames compared to ProcessMaker version 4.1.27 and earlier versions. Aside from alphanumeric characters, ProcessMaker 4.2.31 and later allows the following characters in usernames:
commercial at (@
)
hyphen (-
)
period (.
)
plus (+
)
underscore (_
)
ProcessMaker will enforce this set of special characters in a future version of the platform.
See the following topics in ProcessMaker documentation:
ProcessMaker version 4.2.30 and later 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.35.
These release notes document bug fixes addressed in ProcessMaker version 4.2.35.
ProcessMaker version 4.2.31 and later 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.31 and later from previous ProcessMaker 4 versions:
See the following sections of ProcessMaker version 4.2.29 Release Notes:
Calculated Properties in Screen Builder may reference JSON object values that include <
characters within valid JSON strings.
Calculated Properties properly multiply when a control has a default value of 0
.
When entering data in a Line Input control in a Screen, entered data to another Line Input control in the same Screen properly display.
PMQL from a Select List control properly filters data acquired from a different Select List control on that Screen.
The email response from an Actions by Email recipient properly routes to the appropriate Task and records the response.
The Actions by Email package does no longer sends error emails to mailer daemon in IMAP email servers that create an endless loop which require running the following as the work-around: php artisan package-actions-by-email:check-handler-process
.
Refreshing the web browser window displaying a dashboard properly refreshes that dashboard.
Custom favicons display properly for users that start Requests via Web Entry.
List Chart types display a horizontal scroll bar.
Email notifications configured for any email server send for Form Task elements.
Items in a translation may use the literal strings {{
, }}
, with text between these brackets that normally indicate mustache syntax referencing a Request variable (for example, {{ variable }}
).
A validation error does not occur when starting a Request via Web Entry, and the subsequent node is a Task with only a required Upload File control.
Files that have been uploaded from a Request started via Web Entry may properly be downloaded from a subsequent Task.
Create custom Web Entry URLs based on Request variable values in the JSON data model.
Review Enterprise package versions for ProcessMaker 4.2.35.
The following are the Enterprise package versions in conjunction with ProcessMaker 4.2.35's release:
Actions By Email: package-actions-by-email 1.5.0
Advanced Forms: DEPRECATED in March 2021; no longer supported
Advanced User Manager: package-advanced-user-manager 1.0.1
Auth: package-auth-auth0 1.5.2
Collections: package-collections 2.5.22
Comments: package-comments 1.3.1
Conversation Forms: package-conversational-forms 1.2.1
Data Connectors: package-data-sources 1.10.3
DocuSign Connector: connector-docusign 1.0.1
Dynamic UI: package-dynamic-ui 1.4.3
File Manager: package-files 1.4.3
Google Places: package-googleplaces 1.2.1
PDF Generator Connector: connector-pdf-print 1.8.1
Process Documenter: package-process-documenter 1.1.1
Process Optimization: package-process-optimization 1.2.1
Saved Searches: package-savedsearch 1.18.2 (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.1
Script Executor for PHP: docker-executor-php 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.11.0
Sentry: package-sentry 1.2.1
Signature: package-signature 1.3.2
Slack Notification Connector: connector-slack 1.2.1
Translations: package-translations 2.2.1
Versioning: package-versions 1.2.1
Vocabularies: package-vocabularies 2.6.2
Web Entry: package-webentry 2.5.1