Bug: Workflow conditions and actions fail if dependent on a field that a 'trim' of a WorkFlow field removes 7.14.6: and 7.15

DJuser · 11 January 2026 14:17

in 7.14.6 in data/SugarBean.php a ‘trim’ was added that means that EVERY module’s fields are now trimmed: this breaks thing in Workflows if any of your workflow fields depend on a character that would be stripped by ‘trim’.

Eg if your Workflow Condition is checking that there are no spaces in a field: then the space character you enter as the condition, is deleted when you save the Woirkflow.

See the Github issue 10750 I raised for that, , with the workround to remove the ‘trim’ from SugarBean.php

QUESTION for PHP developers: how could SugarBean.php be set to exclude the various WorkFlow modules from this trim? That would be a better solution.

pgr · 12 January 2026 11:59

I just commented on this on the PR that (I think) introduced the problem:

github.com/SuiteCRM/SuiteCRM

Fix #10339 - Inconsistent application of trim function on name & varchar fields

hotfix ← SinergiaTIC:fix_10339

opened 03:47PM - 26 Jan 24 UTC

SinergiaCRM

+5 -0

- Closes #10339 ## Description This Pull Request addresses issue [#10339](h…ttps://github.com/salesagility/SuiteCRM/issues) by implementing improvements in the `cleanBean()` function in `data/SugarBean.php`. It now executes `trim` on all "name" and "varchar" type fields during save operations. A check has been added to avoid using `trim` when the field value is `null` to prevent errors in PHP. ## Motivation and Context This change is necessary to improve data consistency and cleanliness in text fields where unnecessary spaces can impact data quality and search efficiency. ## How To Test This 1. Create or edit a record in SuiteCRM with additional spaces in "name" or "varchar" type fields in various modules, including modules created using the Module Builder and through Web forms. 2. Save these records and verify that the additional spaces have been automatically removed. 3. Ensure that this functionality works consistently across standard modules, custom modules created via Module Builder, and records entered through web forms to ensure comprehensive testing. ## Types of changes - [x] Bug fix (non-disruptive change that solves an issue) - [ ] New feature (non-disruptive change that adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to change) ### Final Checklist - [x] My code follows the coding style of this project found [here](https://docs.suitecrm.com/community/contributing-code/coding-standards/). - [ ] My change requires a change in the documentation. - [x] I have read the [**How to Contribute**](https://docs.suitecrm.com/community/contributing-code/) guidelines.