A copied process must not run alongside the original

Control Statement: Where a business process has been copied, the copy and the original must not both be enabled on the same trigger.

Description: Creatio names a copied process after its source with a suffix. Where both the original and the copy remain enabled on the same signal, every qualifying record is handled twice — usually by two slightly different versions of the same logic, which is worse than being handled twice by one.

Rationale: Copying a process is how a change gets tested without touching the live one, which makes it a good practice with a bad ending: the copy goes live and nobody disables the original, because disabling it was never part of the task. The two then drift. Months later the instance is running two versions of one rule, and which version applied to a given record depends on the order they happened to execute in.

Audit Procedure:

1. Identify business processes whose names indicate they are copies of another.
2. For each, confirm the source process still exists.
3. Record every pair where both the copy and the source are enabled and can be triggered.
4. Compare the two definitions and note where they have diverged.

Remediation:

1. Decide which of the two is authoritative.
2. Port any divergence worth keeping into it.
3. Disable the other, and delete it once the change has been observed in production.
4. Rename the survivor if its name still says it is a copy.

Default Value: Creatio creates the copy enabled and leaves the original enabled. Nothing indicates that two processes are versions of the same thing beyond the name.