A process started on record creation must be conditioned

Control Statement: A process started by a record-added signal must carry a condition narrowing which new records start it.

Description: Where a process starts on record creation with no condition, it runs for every record of that type created by any means — a user, an import, an integration, a data migration. This control requires a condition that expresses which new records the process is actually for.

Rationale: The failure mode is bulk. A process that is correct for the handful of records a person creates each day behaves very differently when a migration inserts fifty thousand, and the first time anybody discovers this is usually during the migration. Conditioning the start is also the cheapest protection there is against an integration replaying its backlog.

Audit Procedure:

1. Enumerate the processes started by a record-added signal.
2. For each, inspect the start condition.
3. Record every signal with no condition.
4. Establish, for each, whether a bulk source (import, integration, migration) creates that record type.

Remediation:

1. Express which new records the process is for as a start condition.
2. Where the process must run for every new record, record that as a deliberate decision.
3. Test with a bulk insert, not a single record — that is the case the condition exists for.

Default Value: Creatio applies no condition to a record-added signal by default; the process starts on every new record of that type.