Known Issues

Please be aware of known issues in ProcessMaker Platform Summer 2023.

These release notes document known issues in ProcessMaker Platform Summer 2023.

Core

1. Cannot remain in the current session when the session is near expiration: When the Session Warning screen displays to indicate that the current session is about to expire, the Stay Connected button does not function to remain in the session. The session expires when time timer expires.

   • Workaround: Continue working in ProcessMaker Platform Summer 2023 frequently enough to prevent the Session Warning screen from displaying.

Customize UI

1. Icons and the favicon do not change properly when changing them from the defaults in Customize UI: Revised icons for the Custom Login Logo, Custom Logo, Custom Icon, and Custom Favicon settings do not change from their default values in Customize UI.

Request Tracking

1. Borders configured for Process model objects when tracking a Request do not match as configured in the Process model: When viewing tracking for a Request from the Overview tab of that Request, the border colors shown for Process model objects do not match that as configured in the Process model in Process Modeler.

PM Blocks

1. The PM Block name as the author named it in configuration is lost in the Process model: After creating a PM Block from a Process and then configuring it, when that PM Block is placed into a Process's model, closing the Process, and then reopening that Process, the name of the PM Block as its author configured it is missing.

   • Workaround: The Process Designer using that PM Block must manually enter a name to display for that PM Block in the Process model. The Process Designer's name remains after the automatic saving occurs.

2. When editing a Block Environment Variable that contains an existing value, clicking the Cancel button removes the values for that Block Environment Variable: When editing a Block Environment Variable that contains an existing value, clicking the Cancel button removes both the Field Label setting and Helper Text setting values.

   • Workaround: When editing a Block Environment Variable, click the Update button even when no changes are made. The Block Environment Variable retains its settings.

3. Importing a Process using a PM Block does not import properly: When importing a Process that contains a PM Block, the PM Block does not import. Furthermore, the Sequence Flow element(s) incoming to that PM Block do not follow the original Process design as exported.

   • Workaround: The PM Block must be placed into the imported Process and connect the Sequence Flow element(s) as originally intended. Any custom configuration(s) to the PM Block from the exported Process must also be done within the imported Process.

4. Refreshing the Web browser window in a Process using a PM Block causes the original Process model to no longer represent intended design: After saving and/or publishing a Processing using a PM Block, and then refreshing the Web browser window displaying that Process, the PM Blocks and incoming/outgoing Sequence Flow elements move in unintended ways.

   • Workaround: Do not refresh the Web browser window displaying the Process until closing that Process.

Process Creation Using Natural Language

1. Creating a Process using natural language takes an inappropriate amount of time to create: When creating a Process using natural language, Process creation may take an unexpectedly and inappropriately long period of time to generate.

   • Workaround: This is a deployment issue, not an engineering issue. Therefore, this issue will become resolved after ProcessMaker Cloud Operations addresses it.

Process Templates

1. Processes saved as Templates, and then revised, do not import: When a Process is saved as a Template, and then that Template is revised and exported, that Template cannot import successfully. A server error occurs.

   • Workaround: Instead of revising the Process Template prior to exporting, revise the Template after it is imported as a new Template.

Process Modeler

1. Boundary Timer Event elements configured to interrupt workflow to send a message do not function correctly: When a Boundary Timer Event element is set to trigger and interrupt workflow for a Task, the Boundary Timer Event element does not interrupt workflow. Instead, workflow resumes uninterrupted when the associating Task completes.

Script Executor

1. Scripts do not run properly on their Script Executors because they do not rebuild: Script Executors are not rebuilding. Furthermore, Scripts that are configured to run on those Script Executors do not run.

User Activity Logging

1. Updating Decision Table Categories does not show all Categories in user activity logging: When assigning an existing Decision Table with new Decision Table Categories, user activity logging for that user making configuration revisions does not show the previously assigned Decision Tables Categories in the DecisionTableUpdated event.