Bug Fixes
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.
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:

Platform Fixes

ProcessMaker Support ticket numbers are in bold text preceding the bug fix description.

Core

  1. 1.
    Tasks may now be properly opened.
  2. 2.
    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.
  3. 3.
    27668: The number of in-progress and completed Requests is appropriate for each Process in a ProcessMaker environment.
  4. 4.
    The Requests page does not display by default when logging on after the previous session has timed out.
  5. 5.
    The Tasks tab in completed Requests no longer displays because there are no other Tasks to be done.
  6. 6.
    PDFs generated by a ProcessMaker Script properly display in preview.
  7. 7.
    HTML files generated by a ProcessMaker Script may properly be downloaded from the File Manager tab in a Request summary.
  8. 8.
    Validation rules properly evaluate JSON object data in a variety of levels.
  9. 9.
    Row content correctly obtains data in the Notifications table.
  10. 10.
    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.
  11. 11.
    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.

Process Modeler

  1. 1.
    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.
  2. 2.
    26190: After a Process is imported, Script Task elements properly retain with which user each Script is configured to run.
  3. 3.
    Imported Processes that use a Script Task element properly start.
  4. 4.
    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.
  5. 5.
    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.
  6. 6.
    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.
  7. 7.
    26852: Processes correctly start Requests that properly validate.
  8. 8.
    26895: An existing Process may be opened, redesigned, and then saved without causing an invalid error.
  9. 9.
    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.

Screen Builder

  1. 1.
    Validation rules properly function in different JSON object levels and with visibility rules during a Request.
  2. 2.
    The _parent internal variable properly allows the file preview of an uploaded file when that File Upload control is within a Loop control.
  3. 3.
    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.
  4. 4.
    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.
  5. 5.
    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.
  6. 6.
    The File Upload control's progress bar properly fits within the Add screen when uploading a file.

Enterprise Fixes

Auth Package

  1. 1.
    Synchronizing with LDAP users that contain metadata import correctly.
  2. 2.
    A user that logs on to ProcessMaker via SAML properly times out for proper security.

Collections Package

  1. 1.
    28030: Searching for records in a Collection using PMQL based on dates properly returns record results.

Dynamic UI Package

  1. 1.
    Dashboards properly display for the appropriate users and/or groups after their ProcessMaker environment updates to ProcessMaker version 4.2.30.

File Manager Package

  1. 1.
    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.
  2. 2.
    The +Upload Public File screen properly displays to upload a public file.
  3. 3.
    The following message properly displays when an invalid file ID instead of an error message: No files available for download.
  4. 4.
    Large files uploaded to a Task properly show the progress bar that indicates how much of that file has uploaded.
  5. 5.
    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.

Web Entry Package

  1. 1.
    A timed-out anonymous Web Entry no longer redirects to the ProcessMaker login page.
  2. 2.
    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.