KYRA:Docs now supports extraction of entity fields and data group fields that have trigger conditions. Administrators can turn on the new Include Trigger-Conditioned Fields switch on the Document Data Extraction V2 task, and reviewers see each trigger-conditioned field only when its trigger condition is currently met.

To use this capability, turn on Include Trigger-Conditioned Fields for the task in Journey Builder. The switch is off by default, so existing behaviour does not change until it is turned on.

You can now delete scheduled reports and reset suspended schedules, and see why a schedule failed.

Scheduled reports can now be delivered as a download link instead of an email attachment.

Journey administrators can now enable validation of existing reference data values within a journey, so that values selected under an earlier version of a Lookup or Lookup Link — or brought in through migration or data ingest — are checked against the current configuration and must be updated before a user can proceed. This keeps captured data current and helps ensure that only valid, current values are passed to downstream systems.

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.

Screening V2 now supports virtual documents as supporting evidence, at entity level and at hit level.

This feature is currently in Beta and is available on request for client lower level tenants.

A Hierarchy Filter can now be applied to the Hierarchy Capture task and Related Parties task, allowing a configurable rule to narrow the related parties displayed to users based on factors such as relationship type, entity ownership threshold or the risk rating of the entity in journey. Rather than presenting the full hierarchy, only those entities that meet the configured rule conditions — along with their necessary ancestor entities — are shown within the task.

User Guide Reference: Related Party Management Related Party Adapted Experience

Verified Import now supports an optional ValidationProfile parameter on import requests. The forceSave profile stores field values exactly as received from the source system, bypassing mandatory, read-only, calculated, and conditional field rules while retaining format, limit, and lookup validation.

KYRA:Screen now supports automated materiality assessment of confirmed screening hits on the Screening Resolution & Materiality task. Administrators configure Materiality Instructions to define how hits are assessed as Material or Immaterial for each screening category, and KYRA:Screen applies them automatically.

To use this capability, create and activate Materiality Instructions and enable the Complete materiality assessment toggle on the KYRA:Screen agent instance.

Reviewers working in a Review & Approvals V2 task can now reopen a specific prior task in the journey directly from within the decision UI when selecting a Reject or Revise outcome — without navigating away from the task or using the journey instance UI.