Get started →
CIB · v0.1.0 · draft

The Implementation Benchmark for Creatio

Whether what was built does what it looks like it does — and reads as if somebody meant it. Processes racing each other on the same record, triggers that fire on every save, automation everybody believes is running that has not run in months, and fields still carrying the name Creatio gave them.

Controls
11
High
4
Moderate
7
Verified against
Creatio 8.x

Risk says what happens when a control is absent — not how hard it is to fix.

RACE Racing automation

Two processes doing the same work on the same record.

  1. CIB-RACE-001 Two live processes must not start on the identical trigger High
  2. CIB-RACE-002 A copied process must not run alongside the original High

TRIG Triggers

What starts a process, and whether it starts more often than it should.

  1. CIB-TRIG-001 An update trigger must name the columns it depends on Moderate
  2. CIB-TRIG-002 A process started on record creation must be conditioned Moderate
  3. CIB-TRIG-003 A trigger must not wait on a column or object that no longer exists High

FLOW Flow

Whether every path through a process actually finishes.

  1. CIB-FLOW-001 Every branch of a process must reach an end event Moderate
  2. CIB-FLOW-002 A process started in the background must not wait for a user High

LIFE Lifecycle

Automation that is switched on and no longer runs.

  1. CIB-LIFE-001 An enabled trigger that never fires must be retired or repaired Moderate

NAME Naming

Whether the model reads as anything but code names.

  1. CIB-NAME-001 A field must not keep the placeholder name Creatio gave it Moderate
  2. CIB-NAME-002 A reference to another record must be stored as a lookup Moderate
  3. CIB-NAME-003 A field must have a caption Moderate

Published by ctx10. Not affiliated with, endorsed by, or sponsored by Creatio.