> ## Documentation Index
> Fetch the complete documentation index at: https://docs.go.gbgplc.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to configure module outcomes in GO

> Learn how to configure and customise default module outcomes in GBG GO.

By default, each module in GBG GO comes with default outcomes that determine the result of the module based on specific **rules** set in the "Configure outcomes" window. For example, the **Document Classification** module has the following default outcomes:

* *Document Classified*
* *Document Classification Mismatch*
* *Document NOT Classified*
* Document Partially Classified
* ERROR

<Tip>
  You can rename, configure, and customise these default outcomes and rules to match your business use cases.
</Tip>

This guide walks you through the process of configuring module outcomes in GO.

<Info>
  Outcomes refer to module results. Decisions refer to evaluation results.
</Info>

Configuring module outcomes involves:

* Adding more outcomes to a module
* Renaming an outcome
* Adding outcome rules
* Adding subgroups to an outcome

## Add an outcome

In a module, you can add as many outcomes as needed to ensure a strong verification process based on your use case.

Follow the steps below to add a new outcome.

1. Select a module.
2. Click **Configure outcomes**.
3. Click **Add outcome**. A new outcome appears at the bottom of the window. You can now build outcome rules in the provided query builder.

<Note>
  If none of the decisions are met during a verification process, the default outcome is *No warning signals*. You can't select a different default outcome.
</Note>

## Change outcome name

Renaming outcomes helps you identify and manage them more easily, especially when you are working with multiple modules or complex journeys.

Follow the steps below to change a module outcome name.

1. Select a module.
2. Click **Configure outcomes**.
3. Click the **Rename outcome** button next to the outcome you want to rename. For example, in a **Document Classification** module, you can rename the default outcome *Document Classified* to *Valid Document*.
4. Type the outcome name of your choice into the text input field.
5. Click **Done**.

## Add outcome rules

Outcome rules define what happens in a module when specific conditions are met during customer verification. Think of them as *if-then* statements, for example, in a **Document Classification** module, you could configure an outcome that works like this: If Document Classification result is "Document Classified", then the module outcome is *Document Classified*.

Follow the steps below to add additional module rules.

1. Click the **Add rule** button next to the <Tooltip tip="A combinator is a type of logical operator that determines how multiple rules within an outcome are evaluated together." cta="To learn more, check out the glossary page" href="/docs/go-v1/get-started/glossary">combinator</Tooltip>.
2. Select a <Tooltip tip="A specific data point or verification check available within a module or variant that can be evaluated when configuring outcome rules. Each module or variant provides different capabilities based on its functionality, which can be used to create conditional logic for determining customer journey outcomes.">capability</Tooltip> from the <Tooltip tip="Fields are predefined data points or verification checks that you can use to build conditional rules within your journey outcomes. " cta="To learn more, check out the glossary page" href="/docs/go-v1/get-started/glossary">Fields</Tooltip> list.

<Note>
  The available fields vary depending on the module and variant outcome you are configuring.
</Note>

<Info>
  You can add multiple rules to a single outcome to create more precise verification logic. Click **Add rule (+)** to add additional conditions. Choose between **All Match** (every rule must pass) or **Any Match** (at least one rule must pass) to define how the rules work together.

  For example, an "Alert" outcome might include multiple rules:

  * User's age is under 18
  * GBG score is less than 80
  * Number of matching sources is less than 2

  With "Any Match" selected, the Alert outcome triggers if any of these conditions are true.
</Info>

## Add subgroup to outcome

A subgroup allows you to build nested conditional logic within your outcome rules. They let you group conditions together and apply different logic operators to each group.

Subgroups allow you to build logic to create better outcome conditions to fit your use case.

Follow the steps below to add a subgroup to an outcome.

1. Click **Add sub group**. A subgroup appears at the bottom of the outcome.
2. Configure module subgroup outcomes.

## Preview existing outcomes

As a user, you can preview existing outcomes that were previously configured. This allows you to view default and pre-configured module outcomes before adding the modules to the customer journey.

Follow the steps below to preview existing outcomes:

1. In the journey builder, click **Processing**.
2. Select a module.
3. Click **Preview outcomes**.

You can then preview the existing outcomes.

## Edit existing outcomes and subgroups

As a user, you can make edits and configurations to existing outcomes. Follow the steps below to edit existing modules.

1. Select a module.
2. Click Configure outcomes.
3. Edit the outcome and subgroup parameters as needed. For example, in a **Name Match** module, you can change the match type from All Match to Any Match using the list. Then, you can modify the rule from Does name match to Match score. You can then set a match score to be equal to 80.

<Info>
  These configurations determine the outcome result. In the example above, the settings would trigger a successful **IsNameMatch** outcome when the conditions are met.
</Info>

## Delete outcomes

Click the delete icon to remove an outcome or rule from a module.

## Example: Configuring an outcome in a Document Extraction module

In a module, you can select variants and modify default outcomes to trigger specific results based on your use case.

In this example, you will configure an outcome in a **Document Extraction** module to trigger an *Alert: Extraction Unsuccessful* outcome when a document expires.

1. Select the **Document Extraction** module in the journey builder.
2. Click **Configure outcomes**.
3. Rename the *Extraction Unsuccessful* outcome to *Alert: Extraction Unsuccessful*.
4. Click the **Add rule** button next to the *All Match* combinator.
5. Select the **Document Expiry Status** capability from the Fields list.
6. Select the operator **is**.
7. Select the value **Expired**.
8. Click **Close**.

The outcome is now configured. When a document expires during verification, the module triggers the *Alert: Extraction Unsuccessful* outcome.

<Note>
  Different modules have different variants, and default outcomes may vary between these variants.
</Note>