| PARTNER_WITH_ACTIVE_RISK_PROFILE |
Main local-dev partner: BR, PEP, sanction, name-screening hit and adverse-media hit — populates every section of the partner page. |
|
| PARTNER_WITH_PENDING_COMPLIANCE_REVIEW |
BR whose compliance review is REQUESTED and awaiting CRM response |
|
| PARTNER_WITH_NAME_SCREENING_HIT |
Partner with an open WorldCheck name-screening alert (two evidences: one NEW, one MATCH) |
|
| PARTNER_WITH_ADVERSE_MEDIA_HIT |
Partner with an open adverse-media alert (one LexisNexis article evidence) |
|
| BR_WITH_EVENT_BASED_REVIEW |
BR with a CRR profile and an event-based review in ONGOING state |
|
| PARTNER_RISK_SUBSYSTEM_ERROR |
Partner whose risk-profile subsystem calls fail with HTTP 500 (error-path testing) |
|
| PARTNER_PAS_SUBSYSTEM_ERROR |
Partner whose PAS subsystem calls fail with HTTP 500 (error-path testing) |
|
| PARTNER_DATA_SUBSYSTEM_ERROR |
Partner whose partner-data-mgmt subsystem calls fail with HTTP 500 (error-path testing) |
|
| BR_RISK_SUBSYSTEM_ERROR |
BR whose only partner has a failing risk-profile subsystem, for br-mgmt/orchestrator error-path testing |
|
| PEP_PARTNER_WITH_ACTIVE_RISK_PROFILE |
Individual PEP partner — exercises PepAttributes DB seeding under the local profile |
|
| PARTNER_WITH_SANCTION |
Individual partner flagged with a sanction — exercises SANCTION DB seeding under the local profile |
|
| BLANK_PARTNER |
Partner with no risk element populated — a clean slate for save-flow testing |
|
| PARTNER_WITH_SINGLE_NAME_SCREENING_HIT |
Partner with one NEW, unassessed name-screening evidence — the starting point of the approval workflow |
|