Entity Hero Release Notes 1.6

Summary

We are excited to announce the release of the October 2025 update for Entity Hero. This release brings major enhancements to the CRR Risk Framework, introduces an Onboarding History page for improved visibility, and adds feature improvements to Project Cards and Update functionalities for better configurability and control.

New Features

1. Onboarding History Page

A new Onboarding History page provides a consolidated view of all entities and their onboarding statuses.

Key Highlights:

  • Accessible under the Onboarding menu.
  • Displays entities with columns: Entity ID, Customer ID, Name, Entity Type, Date Created, Status, Actions.
  • Users can download RBA reports and view entity profiles for onboarded entities.
  • Rejected entities are also listed with attached assessment reports for audit traceability.

Enhancements

1. Customer Risk Rating Framework Enhancement

A standardized Risk Framework has been introduced to improve automation, traceability, and scoring accuracy across risk assessment systems.

Key Highlights:

  • Introduced Trigger and Trigger Value fields for Category, Condition, and Sub-Condition levels.
    (Trigger defines the data field to be evaluated, while Trigger Value defines the specific value or event that activates the risk.)
  • Framework now includes Rule ID and List UID for integration with name-screening systems.
  • Automated weighted scoring based on matched triggers.
  • Dynamic score adjustment for true/false positive outcomes.
2. Project Cards

Improved Project Card UI for better visibility and control.

Key Highlights:

  • Each card now displays Logo, Project Name, Project ID, User Role, and number of Entity, Cases, Checks, Alerts, Hits.
  • Options added under the 3-dot menu: Edit, View Details, Hide (user-specific visibility).
  • Projects can be sorted by ID or Name and filtered by creation date.
3. Update Functionality

Enhanced update functionality of entities through multiple channels with consistent validation and audit logging.

Key Highlights:

  • Updates supported via UI, API, Excel Batch Upload, and SFTP.
  • Partial Update Logic: Only provided fields are updated; blanks retain existing data; explicit nulls clear fields.
  • All updates include field-level validation and audit logging.
  • Bulk updates via Excel/SFTP with row-level error reporting.
  • Consistent behaviour across all channels ensuring data integrity and compliance.