Known SugarBPM Issues Due to Non-Standard Configuration Changes

Dear SugarCRM Customers,

Last week, we announced changes to SugarBPM that introduced workflow issues for our SugarCloud customers with non-standard configuration changes. This has been fixed in SugarCloud, but will also impact on-site customers who upgrade to the recently announced 14.0.3 or 25.1.2 versions of Sugar Enterprise.

What actions do I need to take?

Add the following to your config_override.php file after upgrading to ensure BPM processes will work as expected:

$sugar_config['bpm_denylisted_fields'] = [
    'Users' => ['is_admin', 'user_name', 'user_hash']
];

What if I’m still having SugarBPM issues?

If you notice any further issues with your SugarBPM processes, or if you have any further questions, please:

1. Have a Sugar support-authorized contact create a case or email support@sugarcrm.com.
2. Reference this communication so our team can assist with 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.