ProcessMaker 4 version 4.0.3

# Overview

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 for Business Process Modeling to become full applications with our “low code/no code” approach using our BPMN 2.0-compliant suite of services.

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 known issues associated with this release unless otherwise noted.

ProcessMaker version 4.0.3 uses the following versions of Screen Builder and Process Modeler:

• Screen Builder: Version 0.22.2

• Process Modeler: Version 0.18.4

Links to System Requirements and Special Instructions

1. On-Premises Server Requirements

2. ProcessMaker 4.0 must be installed to upgrade to ProcessMaker 4.0.3

Improvements

This section documents improvements for ProcessMaker version 4.0.3.

Core

1. #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.

Screen Builder

1. #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.

2. #614 : Loop control settings are improved from the ones introduced in ProcessMaker version 4.0.1.

3. #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.

Bug Fixes

This section documents bug fixes for ProcessMaker version 4.0.3.

Core

1. #2843 : Process models that fail validation properly note the validation errors and highlight those elements and settings that do not meet validation.

2. #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.

3. #2875 : ProcessMaker Environment Variables now allow long names at least 88.9 KB large.

4. #2882 : Requests that use Intermediate Timer Event elements now have workflow routing data in which to continue workflow routing.

5. #2908 : ProcessMaker Environment Variables can now have hyphens (-) in their names.

6. #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)

Screen Builder

1. #539 : The following Screen Builder validation issues are addressed when configuring multiple validation rules for multiple controls in one 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.

2. #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.

3. #550 : Validation now properly applies to controls on a 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.

4. #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.

5. #558 : The Options props in SortableJS , a library used in Screen Builder, has properly been deprecated from Screen Builder to use Vue.draggable instead.

6. #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.

7. #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.

8. #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.

9. #562 : Request data entered from a previous ProcessMaker Screen in that Request now passes to a nested Screen when it displays.

10. #563 : Magic Variables in a Request now pass to a nested Screen when it displays.

11. #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.

12. #566 : A ProcessMaker Screen that has already been displayed within another ProcessMaker Screen via a Nested Screen control cannot be displayed again. This prevents an infinite loop whereby two ProcessMaker Screens using Nested Screen controls cannot reference each other.

13. #567 : The message is more clear that warns that a Form-type ProcessMaker Screen without a Submit Button control cannot be submitted.

14. #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.

15. #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.

16. #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.

17. #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.

18. #572 : The Multicolumn/Table control now properly displays custom CSS applied to it.

19. #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.

20. #576 : An editable record list from a Record List control can how be submitted when one of the controls to submit a record is a required control.

21. #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

22. #594 : Labels now consistently read “Calculated Properties” instead of “Computed Properties” regarding the Calculated Properties function.

23. #602 : Record lists with more than 50 records properly display.

24. [#605](https://gi...

Version 4.0.2

Bug Fix Release

This release is to fix a regression with a missing route error message when using a timer event.

ProcessMaker 4 Version 4.0.1

New Features

This section documents new features for ProcessMaker 4.0.1.

Core

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.
2. 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.

Screen Builder

1. 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.

2. 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.

3. Default values: Set the default values for ProcessMaker Screen controls, thereby requiring Screen users less effort to enter information into your Screens.

4. 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.

Improvements

This section documents improvements for ProcessMaker 4.0.1.

Screen Builder

1. Variable default naming: Variables automatically are named as you add them into a ProcessMaker Screen.

2. Validated UI redesign: Validation rules can now be quickly added using the new rules user interface (UI).

3. 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.

Process Modeler

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.

2. Editable labels for Connectors: The default labels in ProcessMaker connectors can be customized from their default values.

3. Closer element support: Elements in a Process model can be positioned closer together before the Sequence Flow elements loop around the connecting elements.

Bug Fixes

This section documents bug fixes for ProcessMaker 4.0.1.

Core

#2857: The ProcessMaker payload size is now optimized to increase performance.

#2853 : ProcessMaker records when a Process is created or edited.

#2854 : Requests now properly record Request data when Start Event elements trigger, such as when a Start Event element triggers.

#2851 : ID column values throughout ProcessMaker, such as for Requests and Tasks, are now HTML hyperlinks instead of JavaScript.

#2821 : 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.

#2817 : Apostrophe characters (‘) are allowed in the names for the following:

* Processes and Process Categories
* ProcessMaker Scripts and Script Categories
* ProcessMaker Screens and Screen Categories

#2811 : The Custom UI feature properly refreshes the ProcessMaker interface when user interface (UI) changes are made.

#2814 : ProcessMaker user name accounts now support UTF-8 characters for the First Name and Last Name settings.

#2786 : ProcessMaker Scripts may now be properly copied by using the Copy icon.

#2788 : 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.

#2857 : The ProcessMaker payload size is now optimized to increase performance.

Screen Builder

#531 : 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.

#533 : 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.

#526 : 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.

Process Modeler

#2854 : Requests now properly record Request data when Start Event elements trigger, such as when a Start Event element triggers.

#2825 : Intermediate Timer Event elements in an in-progress Request no longer causes ProcessMaker to stop responding.

#2787 : Invalid third-party XML-structured Process models can no longer be imported into Process Modeler.

#2785 : 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.

#2783 : 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.

#526 : 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.

ProcessMaker 4 GA

The ProcessMaker 4 team is pleased to announce the immediate availability of ProcessMaker 4.

Overview

ProcessMaker is an open source, workflow management software suite, which includes tools to automate your workflow, design forms, create documents, assign roles and users, create routing rules, and map an individual process quickly and easily. It's relatively lightweight and doesn't require any kind of installation on the client computer. This file describes the requirements and installation steps for the server.

Use the file "processmaker4-prod.tar.gz" for production servers