Update to Known SugarBPM Issues Due to Non-Standard Configuration Changes

Dear SugarCRM Customers,

We recently announced changes to SugarBPM that introduced workflow issues for customers with non-standard configuration changes. We are glad to announce that on Friday, 26 September 2025, a fix was added to SugarCloud to repair the impacted functionality.

Do I need to take action?

No immediate action is required.

What Happened?

During routine security patching in SugarCloud, a fix introduced unintended consequences that impacted some SugarBPM processes. While the underlying vulnerabilities were not exploited, the BPM changes caused certain processes to fail.

This issue affects only customers who made non-standard configuration changes to SugarBPM process definitions, such as:

• Creating process definitions manually or programmatically by editing a package definition’s code
• Performing code-level overrides to alter read-only or calculated fields
• Modifying a field’s vardefs to change the “process = false” definition
• A field was added to a definition and later marked as read-only

Customers who have only created or modified processes through the standard Process Manager front-end were not impacted.

What if I need additional help or am still experiencing issues?

1. Have a Sugar support-authorized contact create a case or email support@sugarcrm.com
2. Reference this communication so our team can apply the appropriate fixes to your instance

For additional guidance, please see our Working With Sugar Support article.

We appreciate your understanding and want to assure you that our Customer Support team is fully equipped to resolve any issues quickly and effectively.