Known Issues

Please be aware of known issues in ProcessMaker Platform Spring 2023.2.

These release notes document known issues in ProcessMaker Platform Spring 2023.2. Platform section documents known issues affecting the ProcessMaker Platform Spring 2023.2 open-source edition.

Platform

Core

1. Request filters run during every parameter adjustment, not when the Apply button is selected: Request filtering occurs each instance a filter parameter changes instead of only when the Apply button is clicked.

Process Modeler

1. Boundary-type event objects connected with a Sequence Flow to a subsequent object can be moved to another Pool element: When a Boundary-type event object is connected to another object in the same Pool element, the Boundary-type event and its attached object can be moved from one Pool element to another Pool element. Process model objects that are connected to other objects in the same Pool element are not allowed to be moved to another Pool element.

2. Sequence Flow elements behave unexpectedly when moved outside of their Pool element: After pasting Process model objects that are connected with Sequence Flow elements, and then moving those copied Process model objects outside of their Pool element, the Sequence Flow elements move unexpectedly.

3. Boundary-type event objects connected with a Sequence Flow to a subsequent object can be copied, pasted, and moved outside of their Pool element: When a Boundary-type event object connects to a subsequent object using a Sequence Flow element, those copied objects can be moved outside of their Pool element.

4. Process model object labels overlap the border of the Pool element: When Process model objects are placed near the edge of a Pool element, such as the bottom, the Pool element does not readjust in size to properly include the labels.

5. The Process corrupts after copying elements inside one Pool element to another, then deleting both Pool elements: After doing the following, the Process cannot validate BPMN:

   1. Copy the contents of a Pool element.

   2. Move the pasted elements to a second empty Pool element.

   3. Select both Pool elements and then delete them.

   4. Add, and then connect, new BPMN elements to the Process model. When attempting the validate the BPMN, Process Modeler invalidates it.

6. Removing a Pool element containing elements, and then creating a second Pool element with its own elements, deleting the first Pool element removes the Sequence Flow elements from the elements within the second Pool element: Doing the following manifests the known issue:

   1. Place a Start Event element, Form Task element, and an End Event element into the Process model.

   2. Place a Pool element onto the existing elements, and then save the Process.

   3. Place a second Pool element, and then place a Start Event element, two consecutive Form Task elements, and an End Event element.

   4. Connect the elements in the second Pool element.

   5. Delete the first Pool element.

   The known issue manifests whereby the Sequence Flow elements are removed from the elements within the second Pool element.

Screen Builder

1. Controls set as required on secondary pages of nested Screens can be submitted without values: An intermittent issue occurs related to required controls on secondary pages of nested Screens. In some instances, when these controls are left blank, the parent Screen can be submitted without prompting for the necessary information. The usual alerts and visual cues indicating that a required field has not been filled may not consistently appear. Rest assured, we are working diligently to enhance the uniformity of these alerts across all Screen configurations to deliver a more intuitive user experience.

2. Helper text for validation rules Required and Required Unless do not work for Date Picker controls: When a Date Picker control has validation rules for Required or Required Unless, the helper text that indicates when the Date Picker control's validation is not met do not display.