Important Update: SugarBPM Issues Linked to Custom Configuration Change

Dear SugarCRM Customers,

We have identified an issue affecting some SugarCloud customers who have made non-standard configuration changes related to SugarBPM process definitions.

If you have only created or modified SugarBPM processes through the standard front-end user interface, you are not impacted. Please read on if you may have introduced changes outside of the standard interface.

How do I know if I am impacted?

You may be affected if your SugarBPM processes were created or modified outside of the standard Process Manager front-end interface, 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

This is not an exhaustive list. If you are seeing errors in BPM definitions that previously worked, you may be impacted.

What should I do if I am impacted?

If you suspect your instance is affected:

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.
3. For more information about working with Support, 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 help you resolve any issues quickly and effectively.