Custom configuration elements must carry the instance naming prefix

Control Statement: Configuration elements created by the organisation must carry the naming prefix configured for the instance.

Description: Creatio holds a naming prefix for the instance in the SchemaNamePrefix system setting. This control requires that objects, processes and other configuration elements created by the organisation or its implementation partner carry that prefix.

The prefix is free text and can be changed, so the requirement is consistency with the value the instance currently carries, not any particular string.

Rationale: The prefix is what separates the organisation’s own work from the platform’s. Without it, nobody inheriting the instance can answer the first question they will ask — what did we build here? — except by inspection, and anything they miss is work that goes unreviewed, unmaintained and unaccounted for at upgrade time.

Audit Procedure:

1. Open System Designer → System settings and record the value of SchemaNamePrefix.
2. Enumerate the configuration elements not maintained by the platform vendor.
3. Record every element whose name does not begin with the configured prefix.
4. Confirm the prefix in use matches the one recorded for the instance — a changed prefix will make correctly named older elements appear non-compliant.

Remediation:

1. For each, determine whether it is genuinely the organisation’s own work.
2. Rename it to carry the prefix, addressing references from other elements at the same time.
3. Prefer renaming early: the cost rises with each element, process and integration that refers to the existing name.
4. Where an element cannot be renamed, record the exception so later reviews include it.

Default Value: Creatio ships a default prefix of Usr, which an organisation may change. It does not enforce the prefix when a configuration element is created, and does not report elements that omit it.