Configuring OGS: Screening Resolution & Client Selection
This guide is for Journey Builder administrators and compliance configuration teams. It covers everything needed to configure the OGS: Screening Resolution & Client Selection task and the downstream ODS journey it triggers.
Looking for analyst workflow guidance? For the Stage 1 and Stage 2 analyst experience, see Using OGS: Screening Resolution & Client Selection.
Configuring the downstream ODS task? The ODS task triggered by OGS uses the same task type as any other ODS task. For its configuration, see Configuring ODS: Screening Resolution & Materiality.
What this guide covers
- How the OGS task relates to the downstream ODS journey
- Prerequisites
- Adding the OGS task to a journey in Journey Builder
- The two-stage task structure (Stage 1 and Stage 2)
- The launchpad task
- Configuring the downstream ODS journey
- Permissions
- Key validations
How OGS and ODS relate
The OGS workflow spans two separate journeys connected by an automated launchpad.
OGS Journey
└── OGS: Screening Resolution & Client Selection
├── Stage 1: Screening Resolution (entity level)
└── Stage 2: Client Selection (select affected clients)
│
▼ [Launchpad triggers automatically]
│
Downstream ODS Journey (one per selected client)
└── ODS: Screening Resolution & Materiality
The OGS task and the ODS task are different task types configured in different journeys. They must be set up independently.
Separation of concerns: The OGS task determines whether a hit is real at the entity level. The downstream ODS task determines what it means for each affected client — classification data, materiality assessment, and escalation. Both must be configured in their respective journeys.
Prerequisites
| Prerequisite | Detail |
|---|---|
| Task type activation | The OGS: Screening Resolution & Client Selection task type must be activated in your environment before it appears in Journey Builder. Confirm with your Fenergo implementation team that this has been done |
| Journey Builder access | Administrator-level Journey Builder access is required to add and configure both the OGS task and the downstream ODS task |
| OGS journey identified | Identify the journey where the OGS task will be added. This is typically your ongoing screening journey |
| Downstream ODS journey configured | The ODS journey that will be triggered by the launchpad must exist and have the ODS: Screening Resolution & Materiality task configured before the OGS flow is tested end-to-end. See Configuring ODS: Screening Resolution & Materiality |
| On-demand screening configured | The OGS workflow assumes an on-demand screening process is already configured in the environment |
Recommended journey structure
The following task sequence is the recommended configuration for an OGS journey. It ensures hit decisions are returned to the provider, a confirmation check is applied, and the Launchpad only fires when confirmed matches exist.
OGS Journey
└── Process: Ongoing Screening
└── Stage: Ongoing Screening
├── Screening Resolution & Client Selection ← OGS task (Stage 1 + Stage 2)
├── Return Results to Provider ← Sends resolved decisions back to provider
└── Confirmed Match Verification ← Decision gateway
└── Yes → Launchpad ← Triggers downstream ODS journeys
| Component | Purpose |
|---|---|
| Screening Resolution & Client Selection | The OGS task. Stage 1: analyst resolves hits at entity level. Stage 2: analyst selects which clients receive a downstream ODS journey |
| Return Results to Provider | Sends the resolved hit decisions back to the screening provider after Stage 1 is complete |
| Confirmed Match Verification | A decision gateway that checks whether confirmed matches exist. Routes to the Launchpad only on the Yes branch |
| Launchpad | Fires automatically on the Yes branch — triggers one ODS journey per client selected in Stage 2 |
The Launchpad is on the Yes branch of Confirmed Match Verification only. When no confirmed matches exist (No branch), no downstream ODS journeys are triggered and the flow ends.
Adding the OGS task to a journey
- Open the OGS journey in Journey Builder
- Add a new task and select
OGS: Screening Resolution & Client Selectionfrom the task type list - The task contains both Stage 1 and Stage 2 — they are not separate task instances in Journey Builder; they are stages within a single task
Details tab — task configuration
After adding the task, open the Details tab in Journey Builder.
| Setting | Behaviour |
|---|---|
| Hit Document Enabled | When enabled, analysts can optionally upload supporting documents for confirmed matches in Stage 1. Documents are stored at the hit level. A Document Type dropdown becomes visible (populated from the Document Type Reference Data lookup list). Upload is optional and does not block task completion |
Target Entity and Policy Category are not required for the OGS task — this is different from the ODS task configuration.
Assignment Conditions, Scoping Conditions, and SLA Configuration tabs behave the same as other task types.
Once the OGS task reaches Completed status, it cannot be reopened. Ensure all hit decisions and client selections are finalised before completing the task.
The OGS task is configured independently from any ODS tasks. Do not substitute or replace the OGS task with an ODS task — they serve different purposes and the stage structure is unique to the OGS task type.
The two-stage task structure
The OGS: Screening Resolution & Client Selection task contains two built-in stages. Both stages are part of the same task instance — you configure them through the single task's settings.
| Stage | Name | What happens |
|---|---|---|
| Stage 1 | Screening Resolution | The analyst reviews and resolves hits from the OGS batch run at the entity level. All providers are covered in a single hit list |
| Stage 2 | Client Selection | The analyst reviews the client relationships sharing the screened entity and selects which clients should receive a downstream ODS journey |
Stage 2 only becomes available after Stage 1 is complete (all hits resolved). The transition between stages is handled automatically by the task — no additional configuration is required.
The launchpad task
After the analyst completes Stage 2, a launchpad task automatically triggers an ODS journey for each client selected in Stage 2. This is automatic — no manual step or additional Journey Builder configuration is needed to trigger the downstream journeys.
| Behaviour | Detail |
|---|---|
| Trigger | Fires automatically when Stage 2 is completed |
| Scope | One ODS journey triggered per client selected in Stage 2 |
| Task type triggered | ODS: Screening Resolution & Materiality in the configured downstream ODS journey |
| Manual intervention | Not required |
Clients that were not selected in Stage 2 do not receive a downstream ODS journey from this OGS run. If a client was excluded in error, the downstream journey will need to be started manually.
Configuring the downstream ODS journey
The downstream ODS journey must be configured separately. The ODS task in that journey uses the standard ODS: Screening Resolution & Materiality task type — configure it following the same steps as any other ODS task.
When an ODS task is triggered by OGS, one additional behaviour applies automatically: hits from the OGS batch run are highlighted in the ODS screening results table. This is automatic when the OGS-to-ODS integration is in place — no toggle or additional configuration is required.
See Configuring ODS: Screening Resolution & Materiality for the full downstream ODS configuration guide, including task toggles, Classification Data setup, escalation pattern, and permissions.
OGS-triggered hit highlighting
When the launchpad triggers an ODS task, hits that originated from the OGS batch run are automatically highlighted in the ODS screening results table. This visual indicator tells the ODS analyst that the hits arrived via an OGS run rather than through onboarding or on-demand screening.
| Behaviour | Detail |
|---|---|
| Trigger | Automatic when ODS task is launched via the OGS launchpad |
| Configuration required | None — this is applied automatically |
| Purpose | Allows the ODS analyst to identify which hits came from the OGS run |
| Scope | Highlighting appears only on hits that originated from the OGS batch; other hits in the task (if any) are not highlighted |
Permissions
The OGS task uses the standard screening permissions. No new permission types are introduced.
| Permission | What it allows |
|---|---|
| Screening Access | Read-only access to the OGS hit list and Stage 2 client list. Users see the eye (view) icon only |
| Screening Edit | Edit access while the task is In Progress. Resolve hits, make client selections, upload documents |
| Read-only after completion | Once the task reaches Completed status, all users have read-only access |
Journey Builder permissions: Standard Journey Builder configuration permissions apply. No additional permissions are needed beyond those already required for Journey Builder administration.
Key validations and system behaviours
| Area | Validation or rule |
|---|---|
| Stage transition | Stage 2 only becomes available after all hits in Stage 1 have been resolved. The transition is automatic |
| Launchpad trigger | The launchpad fires automatically after Stage 2 completion. No manual action is required |
| Client exclusion | Clients excluded in Stage 2 do not receive a downstream ODS journey from this OGS run. This cannot be undone via the OGS task — a manual journey start would be required |
| Hit highlighting | Hits from the OGS batch are automatically highlighted in downstream ODS tasks. No additional configuration required |
| Audit trail | Match decisions, client selections, and document uploads in the OGS task are captured in Audit. Impacted Clients Updated rows appear when client selections are confirmed in Stage 2 — expand to see Legal Entity ID, selected Yes/No, and the reason for any deselected client. Document events produce distinct labelled rows (Document Added, Removed, Status Updated, Archived, Unarchived) expandable with file and type details |
| Downstream ODS task | The downstream ODS task triggered by OGS is a standard ODS: Screening Resolution & Materiality task. All ODS validations and rules apply — see the ODS configuration guide for details |
Glossary
| Term | Definition |
|---|---|
| OGS | Ongoing Screening. A periodic workflow that screens entities against watchlists on a scheduled basis |
| ODS | On-Demand Screening. The downstream task type (ODS: Screening Resolution & Materiality) triggered per client relationship after OGS Stage 2 |
| Entity level | The OGS task resolves hits at the entity level — one hit list covers all clients that share the entity — rather than per client relationship |
| Stage 1 — Screening Resolution | The first stage of the OGS task, where the analyst resolves hits from the OGS batch run at entity level |
| Stage 2 — Client Selection | The second stage of the OGS task, where the analyst selects which client relationships should receive a downstream ODS journey |
| Launchpad | An automated mechanism triggered after Stage 2 that starts ODS journeys for each selected client |
| OGS-triggered hit highlighting | Visual highlighting applied to OGS hits in the downstream ODS task so the ODS analyst can identify their origin |