Skip to main content

Screening V2: Classification Data Trigger Conditions

Screening v2 Classification Data fields could previously only be configured against the Client, and once configured they always rendered regardless of the case's policy attributes. This release adds trigger conditions, so a Classification Data field can be shown or hidden based on Policy field values on the main entity of the journey or the entity of the match, and a Target Entity setting so a field can be configured specifically for the Client or a Related Party.

This release enables you to:

  • Configure one or more trigger conditions on a Classification Data field, referencing a Policy field on the main entity of the journey or on the entity of the match
  • Show or hide a Classification Data field automatically based on those conditions, using the combination logic already defined in your policy configuration — no new configuration screen or rules engine required
  • Rely on hidden fields being excluded from mandatory-field validation, so analysts are never blocked by a field that doesn't apply to their case
  • Set a Classification Data field's Target Entity to Client or Related Party, so classification data can be captured specifically about a Related Party in addition to the Client (configured as two independent field definitions, one per Target Entity)

User Guide Reference: Configuring ODS: Screening Resolution & Materiality — Classification Data setup