Skip to main content

36 posts tagged with "Screening"

View All Tags

OAuth 2.0 authentication for LexisNexis

LexisNexis is withdrawing Basic Authentication from its Bridger Insight XG screening APIs by 31 December 2026. Fenergo SaaS now supports OAuth 2.0 client credentials, and each client moves its own connection across from the LexisNexis Credentials tab.

Twice-Daily Ongoing Screening for LexisNexis

LexisNexis Ongoing Screening can now run twice a day instead of once, so entities are screened against new sanctions-list updates sooner. Fenergo enables this on request for clients that need more frequent screening. It applies to LexisNexis only — World-Check One and Grid Ongoing Screening are unchanged.

Screening V2: Auto-Complete Task When No Actions Remain

The ODS: Screening Resolution & Materiality task can now auto-complete once every hit has been resolved and no required action remains — not just when a screening returns no hits at all. This removes the need for a separate "complete task" call for clients who disposition hits on an external system and push results to Fenergo via API.

Verify Screening Period

Journeys can now be configured to require re-screening when screening results have aged past a set validity period. The new Verify Screening Period task checks every screening process it governs against the validity period configured on the relevant Configuration Set(s), and blocks the journey with a checkpoint if any result has expired.

At the checkpoint, users can go back and refresh any governed screening stage — not only the one that expired — or continue without rescreening. Going back is recorded to the audit trail like any other reopen; continuing without rescreening is reflected in the task's completion record instead. Verify Screening Period is available for both Screening V1 tasks and the ODS: Screening Resolution & Materiality (v2) task.

World-Check One: Ongoing Screening by Configuration Set

Ongoing Screening alerts from World-Check One can now be routed by Configuration Set. Each Configuration Set can be individually enabled for Ongoing Screening and mapped to its own Journey Schema for Individual, Company, and Other entities, so alerts from different screening groups launch the correct review journey.

Where an entity is screened On Demand under more than one Configuration Set, Ongoing Screening results are now processed and routed separately for each set, rather than a single Journey Schema handling every alert.