Skip to main content

Configuration Release Hub (Beta)

Note: this beta release available to customers by request

Managing configuration across multiple tenants can be challenging when relying on manual, ad-hoc imports. Configuration Release Hub introduces a modern, centralised mechanism for creating, versioning and deploying configuration, enabling clients to maintain configuration in a single source tenant (typically Dev) and promote versioned snapshots to higher environments through controlled, repeatable processes.

Using Configuration Bundles, customers can group related configuration changes into publishable versions that are safely stored and imported via API. This ensures consistent deployment across UAT, Pre-Prod and Prod, supports stronger governance, and aligns configuration management with standard SDLC and CI/CD practices.
This enables predictable, auditable configuration promotion and reduces risk by eliminating uncontrolled tenant-to-tenant changes.

New Address Type: LexisNexis

A new address type: “Business” is now supported for Individual entities during LexisNexis screening, allowing clients to screen Sole Traders using either their Residential or Business addresses.

Document Deferral

This feature introduces the ability to gather deferred documents on journey completion for the entity in journey, and associated related parties, into an entity specific document review to automate the triggering of a journey for subsequent collection. Document Deferral utilises the Review Manager and Review Journey Scheduling enhancement released earlier this month.

Journey Launch Controls Per Team

This enhancement introduces the ability to configure journey launch permissions at a team level, extending the existing Journey Launch Controls functionality. Configurators can now restrict which teams are permitted to initiate specific journey types.

Investment Account Related Parties

The capture and management of Related Parties (RPs) within the Investment Account task has been enhanced to align with the existing Related Party capture task.
This optimisation provides a consistent user experience across Fenergo tasks, ensuring that related party information can be captured, searched, and maintained in the same intuitive way used elsewhere in the platform.

Review Manager Dashboard

The reviews domain has been enhanced with the inclusion of a Review Dashboard that allows users view and manage both scheduled and in progress reviews. The dashboard leverages the previously released ‘Review Journey Scheduling’ feature (Release Notes) and this allows us to surface scheduled reviews for visibility and management.

warning

Clients currently using the ‘Journey Schedules’ feature should wait for an upcoming migration tool before adopting this.

Risk Factor Group Threshold & Custom Threshold Colours

Adds configuration on the Risk Model screen to set numeric thresholds at Risk Factor Group level and assign a colour to each threshold band across Overall, Group and Factor. Group thresholds drive band mapping for that Group; if not configured, the Overall model applies.

If colours not configured, system default applies.

New Secondary Identifiers for LexisNexis

New secondary identifiers are now available for LexisNexis:

  • Individuals: SSN, Driver’s License
  • Companies: EIN

These must be enabled in the LexisNexis Secondary Identifier Configuration in order to use them. For LexisNexis Ongoing Screening (OGS), the Batch Formats configured in Bridger must be updated to include these secondary identifiers for it to be sent and used in OGS. The updated Batch Format files can be downloaded from the User Guide.

Related Party Risk

A user interface has been added to the Related Party Risk Review task. This enhancement allows users to view the full breakdown of input values used to calculate each risk factor for a given related party. The UI includes aggregate and per-party scores, relationship details, and a drill-down into the contributing risk data.

This enhancement is available without configuration changes, but it does not apply retroactively to tasks completed before this date. To access the updated view, the task must be re-run.