Entity Hero Release Notes 1.5

Summary

We are excited to announce the release of the September 2025 update for Entity Hero. This release introduces a customer onboarding page for along with project configurability for batch file. This release introduces a structured onboarding flow, enabling entities to start with either Screening or Risk Assessment and generate Risk-Based Assessment reports. It also delivers project-level configurability with unique Data IDs, giving clients isolated, flexible, and consistent project setups.

New Features

1. Onboarding Flow

A new Onboarding Flow has been introduced, providing a configurable and auditable process for bringing entities onto the platform.

Users can begin the journey either with Screening or Risk Assessment.

Both flows capture basic entity details and calculate a risk assessment score.

At completion, users can download a Risk-Based Assessment PDF Report and choose to either onboard the entity or reject it.

This enhancement ensures a streamlined, flexible, and transparent onboarding experience.

2. Project Configurability

Project-Level Configurability has been introduced to allow clients to run projects with independent configurations and data field structures.

Key highlights:

Client-Specific Data Fields: Each client/project defines which fields are required, visible only to them.

Custom Integrations: Excel templates and API payloads are unique to each client/project and operate independently.

Configurable & Extensible Model: New fields can be added anytime based on client requirements. Each field is registered in the Datafield Master with a unique ID. Client-specific fields are isolated and not visible to other clients.

Independent Operations: Batch files and APIs are all driven by the Project Datafield setup, ensuring changes for one client do not affect others.

Data IDs – Ensuring Structure & Traceability: Every field created in Entity Hero is assigned a unique Data ID, which serves as the backbone of Project-Level Configurability.

Consistency: The same field always carries the same ID across UI, Excel, and APIs.

Isolation: Fields created for a client/project have unique IDs and are not accessible by others.

Traceability: Each Data ID is stored in the Datafield Master, recording metadata such as field name, type, client/project ownership, and status.

Flexibility: New fields automatically receive unique IDs and can be used immediately across templates and APIs.

Change Management: Data IDs remain stable even if field names are changed, ensuring integrations do not break.

Consistency & Backward Compatibility: Entity Hero now behaves consistently across API and Excel, ensuring the same experience in both scenarios.

Backward compatibility has been maintained. Existing clients will continue to operate as before, with no impact from the new release.