The Document Management Archive permission has been split into two independent permissions. Document Management – Archive and Document Management – Unarchive . This enables administrators to assign them separately to different user groups. The original combined permission has been retained with an updated suffix of Legacy, and will be evaluated at a later stage for removal.
This release introduces the Policy Agent, a new Fenergo Digital Agent that automates the analysis of policy documents. Analysts can upload a PDF policy document, review AI-extracted requirements classified by entity type, field type, and confidence level, and compare them against existing Fenergo Policy configuration — all within a single, auditable workflow. Results from the Extracted Policy Requirements and Policy Comparison screens can be exported to Excel for offline review or internal sign-off.
Note: The Policy Agent can only be enabled on one tenant at a time. Contact your Fenergo representative to have it enabled on your tenant.
User Guide Reference: Policy Agent User Guide
A new configuration toggle — Default To Existing Value — has been added to the Document Data Extraction task in Journey Builder. When enabled, the current system value is pre-selected in the analyst review panel instead of the extracted value from the uploaded document. This gives configurators control over the analyst's starting position when reviewing extracted data, helping to prevent existing entity data from being unintentionally overwritten. If a field has no current system value, the extracted value is pre-selected as a fallback. The toggle is disabled by default and is configured at the task level in Journey Builder.
This enhancement increases the global metadata extraction page limit for Intelligent Document Processing (IDP) from 5 pages to 10 pages, allowing metadata values such as signatures, certification dates, and expiry dates that appear beyond page 5 to be correctly extracted. The document classification page limit remains unchanged at 5 pages, with both limits now configured independently of each other.
User Guide Reference: Using the Document Agent — Additional Considerations
KYC Analysts will now see a warning message when the combined first-level ownership of Related Parties to a main client exceeds 100% in the hierarchy. The warning appears inline as a brief toast message when adding new related parties and as a banner at the top of the task. This applies to both the Related Parties and Hierarchy Capture task types. The warning is informational only and does not block data entry.
Two new configuration types are now available for import via Configuration Exchange, extending the platform's ability to promote consistent configuration across tenant environments.
This release introduces Hierarchy Comparison Insights within the Related Party step of the External Data – Entity Enrichment task. This summary highlights missing entities, missing associations and other differences and supports the user in making informed decisions on whether to retain, update or remove associations.
The Screening Agent's hit adjudication logic has been updated to improve consistency and accuracy across entity types.
Journey administrators can now configure a setting in Journey Builder that makes the 'Reason for Cancellation' dropdown mandatory when cancelling a journey. When enabled, users must select a reason for cancellation before a journey can be cancelled.
Journey administrators can now configure a setting in Journey Builder that restricts task reopening to users who belong to the team assigned to that task. When enabled, users outside the assigned team cannot reopen a task, ensuring the responsible team retains control over their assigned work.