Configurators can now include product types in a Shared Data Template. When a Group Onboarding journey runs, verified products of those types on the Group entity are automatically shared to each in-scope child entity — removing the need to create products separately for every member of a joint account or entity group.

Two new Policy Engine sources are now available: Investment Account Fund and Investment Account Fund Share Class. Configurators can use these sources to trigger data and document requirements and conditional values directly on the investment account based on the linked fund and linked share class.

Users with the Unassign Journey or Task Owner permission can now clear a Journey Owner or Task Owner assignment without needing to immediately assign a replacement, returning the owner field to an unassigned state while preserving the team assignment.

Fenergo now allows for the capture of three system-calculated, read-only date fields in the Product domain — recording when each product was onboarded, last updated, and offboarded. These dates are tracked individually per product, ensuring accuracy across all lifecycle events. Each field would need to be added to a product policy to be visible and will need a specific datakey. See user guide for more information on configuration steps.

Users can query product drafts (productdraftdata) and entity drafts (entitydraftdata) in Advanced Reporting. This will expose in-flight products and entities captured during journeys before verification occurs as well as historic drafts. Draft data for associations (relatedpartiesdraft) can now also be queried.

Users reviewing a journey can now see Investment Account and Bank Account changes directly on a new Accounts tab in the Proposed Changes task. The Accounts tab shows a field-level comparison between the verified baseline and the current journey draft for each account, covering Investment Account data, Bank Account data, related parties and linked bank accounts on Investment Accounts. Current journey data or previously verified data can be accepted individually or in bulk.

Tags and References can now be added to Product Requirement Set requirements, bringing the Product domain in line with the capability already available in Policy. Tags are a flexible way to group requirements — labels you define to suit however you want to group them, applied across requirement types and jurisdictions so that every requirement matching one or more tags can be retrieved and reviewed together. References let you record the external legislation or internal documentation behind a requirement.

Custom Dashboards lets users build their own configurable, interactive dashboards from their reporting data. Any saved query, including one generated with KYRA:Report, can be added as a data source for a widget arranged on a flexible grid. Depending on the widget used, different actions and formats are supported.

KYRA:Report is a new digital agent that lets users build and run reports using natural language. Rather than writing SQL, users describe the data they need in plain language and KYRA:Report generates the query, runs it, and returns the results ready to preview, refine, save, schedule or analyse. The agent is schema-aware, resolving the correct fields and parameters for your tenant, and retains conversation history so users can resume a session or reuse a query later.

ETL Screening is now available on all production tenants. Clients migrating from a legacy KYC system can use ETL to load historic screening data — including screening entities, match records, and adjudicated decisions — directly into the Fenergo Screening domain, enabling resolution reuse and NoMatch suppression from day one without requiring a full re-screen.