Skip to main content

Config Exchange — Screening Provider Configuration & Related Party Scoping Rules

Two new configuration types are now available for import via Configuration Exchange, extending the platform's ability to promote consistent configuration across tenant environments.

Screening Provider Configuration (Screening Domain)​

Screening Provider Configuration is now available as a selectable item within the Screening domain of Configuration Exchange. Configurators can import Secondary Identifiers and Configuration Sets for the following providers:

  • World-Check One (WCO)
  • Grid
  • LexisNexis

Previously, these configurations had to be manually re-entered in each tenant environment, introducing the risk of inconsistency between Dev, UAT, Pre-Prod, and Production. With this release, provider configurations can be promoted through the standard Configuration Exchange workflow alongside other screening setup.

Key behaviours:

  • Secondary Identifiers (screening attribute mappings) and Configuration Sets (provider operational parameters) appear as two selectable sub-types under Screening Provider Configuration within the Screening domain.
  • Provider configurations are not versioned — they are always imported as the latest active setup from the source tenant.
  • Credentials (API keys, usernames, passwords) are automatically excluded from exports and will never be transferred across environments.
  • Required dependencies — including Country Reference Data Lists (ISO Alpha-2/Alpha-3), Linked Lookups (Screening Resolution Status/Reason), and provider-specific lookup values — are automatically detected and imported before the provider configuration, without manual pre-setup.
  • If a provider is not yet enabled in the target tenant, the configuration is imported in a Disabled state and a warning is recorded in the Import Log.
  • The Import Log displays provider name, configuration type (Secondary Identifier / Configuration Set), and import status (Imported / No Change / Failed) for each item.

Permissions required (no new permissions introduced):

  • Configuration Exchange Access — to view the Screening Provider Configuration tab
  • Configuration Exchange Edit — to perform imports
  • Screening Configuration Access — to view provider configurations in the source tenant
  • Screening Configuration Edit — to apply imported configurations in the target tenant

Related Party Scoping Rules (RPSRs) are now available as a selectable configuration type within the Journey domain of Configuration Exchange. Configurators can import RPSR definitions across tenant environments without manually recreating rule logic, eliminating configuration drift between environments.

Key behaviours:

  • RPSRs appear in the Bulk Selection modal under the Journey domain with type "Related Party Scoping Rule".
  • This is an import-only capability — RPSRs cannot be exported individually.
  • Imported rules are always imported in a Published state and are immediately available for selection in Journey Builder. The "Import in a Published State" toggle has no effect on RPSRs.
  • A new version is created in the target tenant on each import, incremented from the latest existing version. A traceable Version Note is generated automatically: "Imported from [Source Tenant Name] (Version [x]) via Configuration Exchange Record: [Import Record Name]."
  • Draft versions of an RPSR in the target tenant are not overwritten — these will log as "No Change."
  • Required dependencies (Relationship types, Entity Types, Association Types, Requirement Categories) are automatically detected and imported before the RPSR itself.
  • When a Journey Schema and its referenced RPSRs are included in the same import record, task references within the Journey Schema are automatically remapped to the newly imported RPSR IDs — no manual reassignment required.
  • Availability is controlled by the environment feature toggle "Enable RPSR Import". When this toggle is OFF, RPSRs will not appear in the Bulk Selection modal.
  • Related Party Scoping Rules are also now supported in Configuration Release Hub (CRH) under the Journey domain, enabling CRH-based environment promotion workflows.

Permissions required (no new permissions introduced):

  • Configuration Exchange Access — to view the Imports menu
  • Configuration Exchange Edit — to select and add RPSRs to an import record
  • Configuration Exchange Publish — required to execute the import (RPSRs always import in published state)
  • Journey Access / Edit / Approve — required in source and target tenants per the standard import flow

User Guide References: