A field must not keep the placeholder name Creatio gave it

Control Statement: A field added by the organisation must not retain a default placeholder name such as Column1 or UsrColumn2.

Description: Creatio names a newly added column with a sequential placeholder until somebody changes it. This control requires that every field the organisation added carry a name that says what it holds.

Rationale: The placeholder is not a cosmetic problem, because the code name is not confined to the designer: it follows the field into every list, report, export and integration payload. A column called UsrColumn7 in a spreadsheet on a finance director’s desk is unreadable, and the only way to find out what it means is to open the object in Creatio — which is exactly the dependency handing an instance over is meant to remove.

Audit Procedure:

1. Enumerate the fields on objects the organisation added or extended.
2. Record every field whose name matches a placeholder pattern (Column, Field or Attribute followed by a number).
3. For each, establish what the field actually holds.

Remediation:

1. Rename each field to describe its contents, keeping the instance prefix.
2. Update anything referencing the old name — processes, business rules, reports, integrations.
3. Rename early: the cost rises with every reference added.

Default Value: Creatio assigns a sequential placeholder name to each new column and never requires it to be changed.