This release delivers two targeted enhancements to the Conflict Resolution Task to improve reviewer efficiency and transparency.

First, categories and tabs with no field-level differences between in-flight and verified data can be optionally hidden by default through the Journey Schema, reducing information overload and helping reviewers focus only on what requires a decision. This behaviour applies to journeys triggered after deployment and can be toggled via task properties.

Second, fields whose values are controlled by conditional value rules can be optionally classified and badged as "Calculated" directly on the task and made read only so the user cannot change their value, ensuring greater transparency and trust in the review process. This behaviour applies to fields at the entity level only currently.

Administrators can now configure negative threshold boundaries in Risk Models. This enables risk models that incorporate mitigating factors — where certain inputs actively reduce the overall risk score — to be configured without restriction.

The Product Related Party Launchpad is a new task type that allows due diligence journeys to be triggered for related parties associated with products in a journey. It operates within a Product Connected Journey, mirroring the behaviour of the Related Party Journey Launchpad V2 in a product relationship context.

Administrators can now configure Ownership and Control requirements for Investment Account Related Parties. Required related parties are displayed to the user directly above the related party grid. Users are prevented from completing the Investment Account task until all required related parties have been added.

The Provider Priorities tab on the External Data Configuration screen now displays only the options relevant to each organisation's setup. Organisations using KYRA:Source continue to have full access to the Rules configuration, while those that do not will see only the default provider setting.

When data is imported via an external provider through KYRA:Source, the audit trail now records the name of that provider — for example, "Orbis" — in the Source field, replacing the previous generic label. Auditors and KYC analysts can accurately trace the origin of each imported data point to its source provider.

KYRA:Docs — Document Data Extraction V2 brings the review of extracted entity data, data groups, and related parties into a single, unified task. Reviewers can now compare extracted information against the current entity record, understand the outcome assigned by KYRA:Docs, and record an explicit resolution before any changes are applied. This release replaces the legacy extraction experience with a more controlled, transparent, and auditable review process — supporting both standard and Maker-Checker journeys.

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.