ورژن جديد Processmaker

Release Date: February 11th, 2019
This document contains release notes for ProcessMaker 3.3.4. Release notes are cumulative, so these
release notes document improvements and bug fixes associated with this release unless otherwise
noted. A list of older ProcessMaker release notes is included at the end of this document.
Links to System Requirements and Special Instructions for This
Release

1. Supported Stacks
2. Supported Web Browsers
3. ProcessMaker 3.3.0 or later must be installed to upgrade to ProcessMaker 3.3.4
Improvements
This section documents improvements for ProcessMaker 3.3.4:
1. REST API Endpoint - Sub-process cases: The new “Sub-process cases” endpoint improves the
ProcessMaker REST API by retrieving the list of sub-process cases. The endpoint response is an
array of all sub-process cases of which the parent case is the one provided in the {app_uid}
parameter. Each item in the array shows the case information of each sub-process case.
○ Business Value: Use this endpoint to fully integrate with cases created by sub-processes. This
functionality expands options for your implementations. For example, use this REST API call for
greater traceability and accountability for cases created from sub-processes.
2. Custom Summary Form in Unassigned Cases: As a Process Architect with the proper
permissions now you can configure your processes to show a Dynaform in the case summary for
unassigned cases. As an operator with the proper permissions, you can open a case in the
unassigned list and see the Dynaform summary. This Dynaform summary shows all the Dynaform
information in view mode with the Claim and Cancel buttons.
○ Business Value: This improvement helps Self-Service users make better decisions when
claiming cases, thereby avoiding errors that will cost time and money to fix later.

ProcessMaker - Version 3.3.4 Release Notes February 11, 2019
Bug Fixes
This section documents bug fixes for ProcessMaker 3.3.4:
1. Consecutive clicks on the pause button no longer affect a case ruing in parallel threads:
The parallel threads now are converging after the thread is unpaused. Validations were added to
prevent pausing a case multiple times. The solution in this bug also applies when the
PMFPauseCase function runs multiple times.
○ Scope: This bug affects ProcessMaker 3.2.1 to 3.3.3.
2. When creating a case via the REST API, the “New Case Impersonate” endpoint now correctly
sets process system variables in the ProcessMaker database: The system variables now
populate correctly the “New case Impersonate” REST API endpoint as soon as the case is created.
After using the “New Case Impersonate” endpoint, the APPLICATION, PROCESS, TASK, INDEX,
USER_LOGGED, and USR_USERNAME fields are correctly saved in the APP_DATA column of the
APPLICATION table. No longer causing issues in triggers that relies on these system variables when
a case is created or triggers executed by other REST endpoints.
3. Custom Case List now properly updates new fields in report tables: When a report table
related to the Custom Case List feature is updated, new fields properly update on load without
selecting the report table again. If a field is removed or renamed from the report table, then the
column is also removed from the referenced cases lists. Custom Case List now is updating new
fields as well as editing and deleting fields in the Inbox, Draft, Participated, Unassigned and Paused
lists.
4. Control labels now display with the correct spacing in the HTML class property: The HTML
class property in control labels now display properly the spacing between col-sm-2 and col-md-2.
Control labels now display with the correct spacing in the following controls types: text field, text
area, check group, checkbox, radio, dropdown, suggest, and label.
○ Scope: This bug affects ProcessMaker 3.2.0 to 3.3.3.
5. Server files no longer download without authentication: A security hole was fixed by sanitizing
the arguments received by ProcessMaker. Furthermore, actions in classic processes now have
access controls.
6. Cases run correctly in script tasks that use the “cancel case” function: Cases no longer stuck
in the script task if a trigger uses the PMFCancelCase function to cancel the case.
○ Scope: This bug affects ProcessMaker 3.3.0 to 3.3.3.
7. Variables now are updated properly when the case has more than one trigger placed after
and before routing: The variables now are updated correctly when the steps have more than one
trigger even if they are using functions like PMFDerivateCase or PMFSendMessage.
ProcessMaker - Version 3.3.4 Release Notes February 11, 2019
Previous Release Notes
Refer to the previous release notes from ProcessMaker versions 3.2 through 3.3.4:
● 3.3.3
● 3.3.2
● 3.3.1
● 3.3.0
● 3.2.3
● 3.2.2
● 3.2.1
● 3.2