We've enhanced the Reverse Geocoding feature to return multiple address results for a given set of geographic coordinates. You can now define a search radius and maximum number of results — giving you the flexibility to apply custom logic to select the most relevant one. This improvement helps you handle ambiguous or overlapping locations with greater precision. For more information, see topic Get addresses with geographic coordinates.

Contact your Account Executive or Customer Success Manager to discuss the best offering for your business.

We are enhancing security by transitioning from AWS access key and secret authentication to IAM role-based authentication using AssumeRole to access Reltio-owned AWS resources. This change aligns with AWS best practices, reducing credential exposure and improving access management. If you currently use AWS access keys to access Reltio-owned AWS resources, we recommend transitioning to IAM roles as soon as possible.

For more details, see AWS access key and secret in favor of IAM roles for Reltio-owned resources.

We've introduced a new generationLogic parameter, named generateUidWhenAllOvMissing, to improve surrogate crosswalk key generation. Previously, when all attributes for an entity lacked operational values (OVs), the system generated an MD5 hash using null values, leading to potential duplicates. Now, with this new parameter, a UUID is generated instead, ensuring unique keys even when all OV values are missing.

This update helps prevent unintended entity merges and improves data consistency. It's available in Surrogate Crosswalks configuration for all tenants.

For more details, see Configuring surrogate keys.

We've simplified how you load interactions into your tenants. Previously, to load interactions, you needed to define a schema. Now, you're able to load interactions with no defined schema. This means that you aren't required to map attributes, allowing you for a quicker setup before the job starts.

This enhancement is available in the Console > Data Loader application and in the Data Loader.

For more details, see Load interactions without defining a data model.

Customer password policies now inherit the following properties from the default policy if not explicitly defined:

• numberOfFailedLoginAttempts
• numberOfFailedMFALoginAttempts
• inactivePeriodInDays

This simplifies configuration by allowing you to focus on the specific settings you want to customize, while maintaining consistency with the default security standards. For more details, see Set a customer password policy.

The User Management API operations now return a single, standardized error response and HTTP status code for both valid and invalid usernames, ensuring a consistent experience in case of errors. For details on the API operations, see User Management API.