Entity Hero Release Notes 1.14

Summary

The July 2026 release introduces enhancements across onboarding, name screening, project configuration, navigation, and PreScreening.io integration. Key highlights include automatic onboarding date population, support for Internal Watchlists in Customer Risk Rating (CRR), configuration-based module visibility, the introduction of an On Hold status for onboarding, and enhanced identifier validations for PreScreening.io. These updates improve platform usability, configuration flexibility, and streamline the onboarding and screening experience.

Enhancements

1. Automatic Onboarding Date Population

The onboarding process has been enhanced to automatically populate the Onboarding Date when an entity transitions from Entity Hero Onboarding (EHO) to Entity Hero Core (EHC), ensuring consistent onboarding records while preserving existing data.

  • The Onboarding Date is automatically populated with the date on which an entity moves from EHO to EHC.
  • The Onboarding Date remains non-editable for EHC entities across all ingestion methods, including UI, Batch Upload, and APIs.
  • Existing EHC entities with a manually populated Onboarding Date retain their existing value without any overwrite.
2. Internal Watchlists Support for Name Screening

Entity Hero now supports Internal Watchlists as an additional name screening risk category, enabling organizations to include internal watchlist matches in Customer Risk Rating (CRR) calculations alongside existing screening categories.

  • Internal Watchlists has been introduced as the fifth supported name screening risk category.
  • Multiple List UIDs can be mapped to a single Internal Watchlists category.
  • Internal Watchlists is available as a configurable category within the CRR Risk Framework.
  • Framework configuration supports configurable weightage, trigger score, override, prohibited, and null fallback settings.
  • Internal Watchlist matches received during both initial screening and ongoing monitoring are automatically considered during CRR calculation.
3. Configuration-Based Navigation Visibility

Navigation has been enhanced to display modules based on project configuration, ensuring users only see features applicable to their project.

  • The Onboarding module is displayed only when an onboarding framework is configured for the project.
  • The Settings module is displayed only when ignoreCrrFramework = False and is hidden when ignoreCrrFramework = True.
  • Module visibility is automatically managed based on project configuration without requiring manual intervention.
  • This enhancement improves the user experience by reducing navigation clutter and displaying only relevant functionality.
4. Introduction of On Hold Status for Onboarding

A new On Hold status has been introduced to allow users to temporarily pause onboarding decisions until additional information or approvals become available.

  • Users can place entities in the On Hold state from the Entity Profile, Entity Manager.
  • The On Hold status is displayed consistently across entity listings and the Entity Profile.
  • Entities placed On Hold can later be revisited and either onboarded or rejected.
  • Existing onboarding and rejection workflows continue to function without any changes.
  • This enhancement enables users to manage incomplete onboarding cases directly within Entity Hero.
5. Enhanced Identifier Validations for PreScreening.io Integration

Identifier validation has been strengthened to improve the integration between Entity Hero and PreScreening.io, ensuring cleaner data submission and a more reliable screening process.

  • Identifier-specific validation rules have been introduced before entities are submitted for name screening.
  • Validation logic is applied according to the selected identifier type.
  • Different identifier types now support their respective validation criteria.
  • Improved validations reduce screening failures caused by invalid identifier formats.
  • These enhancements provide a more seamless and reliable screening experience with PreScreening.io.