Important Update: SugarBPM Issues Linked to Custom Configuration Change

RE: Important Update: SugarBPM Issues Linked to Custom Configuration Change

Alex Nassi — Mon, 29 Sep 2025 18:04:34 GMT

This past Friday (26 Sept 2025), a fix was added to SugarCloud to address this issue. Please review today's update, [mention:0678e4b51623477f878d27cb72c18bc2:f7d226abd59f475c9d224a79e3f0ec07] for details and more information.

(cc: [mention:e8c8b4658dd3465d861616af26ed392a:e9ed411860ed4f2ba0265705b8793d05] - I believe the update post should answer the questions you shared here)

RE: Important Update: SugarBPM Issues Linked to Custom Configuration Change

Chris Raffle — Tue, 23 Sep 2025 09:51:59 GMT

After some investigation, this issue has a much wider impact than the initial post indicates. Previously, you could use SugarBPM to modify a read-only field by doing the following:

Remove the read-only attribute from the field via Studio.
Configure the process definition to modify the field
Mark the field as read-only again in Studio

I confirmed that processes configured in this fashion no longer function as they did previously. Based on my review of affected customers, it looks like this change was deployed on September 18th. Is that accurate? Why was a change that significantly alters customizations and configurations introduced outside of the normal software release schedule?

RE: Important Update: SugarBPM Issues Linked to Custom Configuration Change

Chris Raffle — Mon, 22 Sep 2025 10:16:14 GMT

Where should we be looking for errors to identify if there is anything impacted? There are many ways that processes may have errors including validation of the process definition, processes resulting in an 'error' status, errors generating at the log level, etc. Also, is this affecting all customers in SugarCloud or only customers on specific versions?