A process started in the background must not wait for a user

Control Statement: A process started by a signal, a timer or another background process must not contain an element that waits for a user.

Description: Pages, pre-configured pages, user dialogs and decision-by-user elements require somebody to answer them. Where the process was started in the background there is no user session to show them to, so the element waits indefinitely. This control applies through the call graph: a sub-process with an ordinary start is in scope when a background process calls it.

Rationale: The process stops, silently, holding the record. Because it is waiting rather than failing it does not appear in any error list, and the instance accumulates stalled executions that each look like work in progress. The version started by a person works perfectly, which is why this survives testing.

Audit Procedure:

1. Enumerate the processes started by a signal, a timer, or a call from another process.
2. Follow the call graph from each, including into sub-processes.
3. Record every path that reaches an element requiring a user response.
4. Check for process instances currently stalled at those elements.

Remediation:

1. Remove the user-facing element from the background path.
2. Where a decision is genuinely needed, make it a task assigned to somebody rather than a page waiting for nobody.
3. Where one sub-process serves both a user-started and a background caller, split the two.
4. Complete or cancel the instances already stalled.

Default Value: Creatio allows a user-facing element on any path regardless of how the process is started, and reports nothing when one is unreachable.