> For the complete documentation index, see [llms.txt](https://docs.complycube.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.complycube.com/documentation/product-guides/compliance-studio/workflows/outcome-rules-and-actions.md).

# Outcome rules and actions

Configure automated KYC decisions and follow-up actions in the workflow editor. Evaluate verification results and client attributes, update client stages, and assign review cases.

### How outcome rules and actions work <a href="#toc_2" id="toc_2"></a>

The area below **Complete flow** controls the session's **outcome** and the **actions** taken for that result.

<table><thead><tr><th width="182.921875">Control</th><th>Purpose</th></tr></thead><tbody><tr><td><strong>Outcome rules</strong></td><td>Evaluate conditions to set the session to Clear, Attention, or Rejected.</td></tr><tr><td><strong>Result lanes</strong></td><td>Set client stages or open cases for each session outcome.</td></tr><tr><td><strong>Alert cases</strong></td><td>Open cases for selected check findings, regardless of the overall session outcome.</td></tr></tbody></table>

These controls are part of Workflows. Configure them in either the **Flow** canvas or **Lifecycle** view.

### Configuring outcome rules <a href="#toc_3" id="toc_3"></a>

Select the **Outcome rules** diamond directly below **Complete flow**. When it displays **Default**, the workflow uses ComplyCube's standard session result.

Add a rule, give it a descriptive name, configure its conditions, and select an outcome: **Clear**, **Attention**, or **Rejected**. Arrange rules in the order you want them evaluated.

<figure><img src="https://1615271746-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKyFKMqftsmT6qln9zo5y%2Fuploads%2Fiv26HgBCKdPc4PSvvaEo%2Fworkflows_outcome_rules_multi.png?alt=media&amp;token=ab789ff3-1aa0-446d-b7ee-42946871b23b" alt=""><figcaption><p>Workflow Outcome Rules - Review rule order and the fallback used when no rule matches.</p></figcaption></figure>

#### Conditions and groups <a href="#toc_4" id="toc_4"></a>

Rules can evaluate:

* **A check in the workflow**: Its overall result, a part of its analysis, or an individual finding. For example, evaluate Document Check's forensic analysis or a tampering finding. Available condition values include **Clear**, **Attention**, and **Not processed**.
* **Client attributes**: Client type, country, risk level, and client stage.

Combine conditions using **All (AND)** or **Any (OR)**. Add a **group** to nest conditions one level deep, such as `A AND (B OR C)`.

<figure><img src="https://1615271746-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKyFKMqftsmT6qln9zo5y%2Fuploads%2Ff5OuvEXnsh0yXeys1gvz%2Fworkflows_outcome_rules_modal.png?alt=media&amp;token=317072be-5239-4372-aa1c-7271b0b84ff9" alt=""><figcaption><p>Workflow Outcome Rules - Combine verification findings and client attributes in a session outcome rule.</p></figcaption></figure>

You can **rename**, **reorder**, **duplicate**, and **delete** rules. The editor warns when an earlier rule always matches first and prevents a later rule from being reached.

#### Evaluation order <a href="#toc_5" id="toc_5"></a>

1. **Outcome rules run after the last check**, from top to bottom. The **first matching rule** sets the rule-based session outcome; later rules are not evaluated.
2. If no rule matches, or rules are disabled, ComplyCube uses the [default session result](/documentation/product-guides/compliance-studio/workflows/workflow-sessions-and-results.md#toc_8). See Session results.
3. **Compliance policies** are evaluated after outcome rules and can still raise **Attention**.
4. A **direct session outcome override** by a team member takes precedence over automated outcomes.

If a reviewer changes an individual check's result, the rules are **evaluated again**. A direct manual session override is not overwritten by that reevaluation.

{% hint style="info" %}
Outcome rules set the **session outcome**. They do not change individual **check results**. If a rule sets the session to Clear, the checks it relied on are not flagged as requiring attention on the [home page](https://portal.complycube.com/), but their underlying results remain available for review.
{% endhint %}

The session page displays **Set by outcome rule** and the rule's name when a rule determines its outcome.

### Result lanes <a href="#toc_6" id="toc_6"></a>

Below **Outcome rules**, three lanes represent **Clear**, **Attention**, and **Rejected**. Each lane lists the actions configured for that result.

Select **+ Add action** on a lane to add:

* **Set client stage**: Move the client to a built-in or custom lifecycle stage, such as **Onboarded** after a Clear result. Use **Manage stages** to manage stage options.
* **Open a case**: Create a review case from a case template.

`[SCREENSHOT: The three lanes with "Stage → Onboarded" on Clear and "Opens a case" on Attention and Rejected]`

<figure><img src="https://1615271746-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKyFKMqftsmT6qln9zo5y%2Fuploads%2FYWbOOFRkkqACxadIh5Ld%2Fworkflows_bottom_lane.png?alt=media&amp;token=2c40a9b5-734b-4bd1-82df-60fb550aca81" alt=""><figcaption><p>Workflow Outcome Rules - Configure client stage updates and case creation for each session outcome.</p></figcaption></figure>

<table><thead><tr><th width="144.69140625">Result</th><th>When its actions run</th></tr></thead><tbody><tr><td><strong>Clear</strong></td><td>When the session's final result is Clear, including after review.</td></tr><tr><td><strong>Attention</strong></td><td>As soon as the session requires attention.</td></tr><tr><td><strong>Rejected</strong></td><td>When the session's final result is Rejected, including after review.</td></tr></tbody></table>

Each configured action runs **once per session**. Hover over an action to remove it.

Client stages are attributes of the **client record**, separate from workflow session states. They can also be updated manually, through the API, or through Lifecycle Triggers.

### Configuring cases <a href="#toc_7" id="toc_7"></a>

Select a case action on a result lane to open its settings.

<table><thead><tr><th width="219.984375">Setting</th><th>What to configure</th></tr></thead><tbody><tr><td><strong>Case template</strong></td><td>The template used to create the case.</td></tr><tr><td><strong>Assign to</strong></td><td>The team member or user group responsible for the case.</td></tr><tr><td><strong>Priority</strong></td><td>The priority assigned to the case.</td></tr><tr><td><strong>Due date</strong></td><td>The number of days before the case is due.</td></tr></tbody></table>

<figure><img src="https://1615271746-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKyFKMqftsmT6qln9zo5y%2Fuploads%2Flcb6mLUz42u91d4Wzj15%2Fworkflows_case_template_options.png?alt=media&amp;token=cc537e6a-1738-4480-a6f7-09324bb9ec22" alt=""><figcaption><p>Workflow Outcome Rules - Assign ownership, priority, and a deadline to an automatically created case.</p></figcaption></figure>

Under **More options**, configure:

* **Evaluation order**: The order in which case configurations are checked.
* **Don't open later cases**: Whether to stop later case configurations from opening cases.
* **Existing open cases**: Whether to skip case creation or open another case when the client already has an open case from this workflow.
* **Close the case automatically**: Whether to close the case when the session's checks or result are clear.
* **Case name**: An optional name for the case.

Review the panel's summary to check the full behavior.

{% hint style="info" %}
Case actions require **case management** in your plan. See [Advanced Case Management](/documentation/product-guides/compliance-studio/advanced-case-management.md) for case operations and team controls.&#x20;
{% endhint %}

### Alert cases <a href="#toc_8" id="toc_8"></a>

Use **alert cases** when a particular check finding requires review regardless of the overall session outcome.

Select the **Alert cases** indicator below the result lanes. Choose the check and result that should open a case, then configure the case settings.

For example, create an alert case when **AML Screening returns Attention**, even if the session's overall outcome is **Clear**. This routes the finding to a reviewer independently of the result lane.

### Testing decisions and actions <a href="#toc_9" id="toc_9"></a>

Before activating a new workflow version, test the conditions you expect it to encounter:

* **Matching rules**: Confirm each rule produces the intended session outcome.
* **Rule order**: Check situations where several rules could match.
* **Fallback behavior**: Verify what happens when no rule matches or a check is Not processed.
* **Policy evaluation**: Confirm that policy results are reflected alongside the rule-based outcome.
* **Case routing**: Check case ownership, deadlines, existing-case behavior, and alert conditions.
* **Reviewer changes**: Verify the behavior after an individual check result is reviewed or the session outcome is overridden directly.

Use the session's **Flow setup** tab to inspect the configuration version used for the test, and review its **results** and **activity timeline** to confirm the behavior.

### Frequently asked questions <a href="#toc_10" id="toc_10"></a>

<details>

<summary>Do outcome rules change individual verification results?</summary>

No.

A rule sets the **session outcome**. The original check results remain available so reviewers can inspect the underlying findings.

</details>

<details>

<summary>Can a compliance policy still require review after a rule matches?</summary>

Yes.

Compliance policies run after outcome rules and can still raise Attention. Review policy results in the session's Policy Assurance section.

</details>

<details>

<summary>Can a case open when a session is Clear?</summary>

Yes.

Add a case action to the **Clear** result lane, or configure an **alert case** for a specific check result that needs review independently of the session outcome.

</details>

<details>

<summary>What happens if no outcome rule matches?</summary>

ComplyCube uses its **default session result**. The rules panel shows this fallback so you can review it when configuring decisions

</details>

<details>

<summary>Will automated rules override a manual session decision?</summary>

No.

A team member's **direct session outcome override** takes precedence. Reviewing an individual check can cause rules to be reevaluated, but it does not overwrite a direct manual session override.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.complycube.com/documentation/product-guides/compliance-studio/workflows/outcome-rules-and-actions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
