The April 2025 release includes the following new features and enhancements.
Watch the What's New video to learn about the new features and enhancements in the April 2025 release.
Accessibility Conformance
Reference 360 has enhanced accessibility for all users in compliance with Web Content Accessibility Guidelines (WCAG) 2.2 Level A and AA standards. Our Accessibility Conformance Report (ACR) based on Voluntary Product Accessibility Template (VPAT) outlines the accessibility conformance in detail.
When you create a reference data asset in Reference 360 , you can now specify a unique internal ID for the asset. Use internal ID to ensure effective integration between source and target systems.
When you create or update a reference data asset, you can also specify an alias, which is an alternative label for the asset. Use an alias to rename or manage assets more effectively.
The Reference 360 REST API includes the following enhanced resources:
codelists version 1
Use the codelists version 1 REST API to enable auto-generation of Code field values for an existing code list if the Code field is configured with a rule association. You can also retrieve the status of the code list if it's enabled with auto-generation of Code field values.
For more information about the codelists version 1 REST API, see codelists version 1.
codelists version 2
Use the codelists version 2 REST API to manage a code list based on its internal ID or alias.
Following table lists the version 2 of the REST API and the URI format:
For more information about the codelists version 2 REST API, see codelists version 2.
alias generation
Use the alias generation REST API to configure aliases for existing predefined and custom assets that don't have internal IDs. The alias generation REST API runs an alias generation job and you can retrieve the job status.
For more information about the alias generation REST API, see alias generation.