May 2025
To receive updates about new posts and release notes, subscribe to our RSS feed: https://documentation.omadaidentity.com/horizons-release-notes/rss.xml
Changes 
Processing terminated identities
The introduction of Horizons improved performance, scalability and brought additional functionalities, for example identity merge, without drastically changing how data is manipulated during the import process. However, terminated identities were filtered out from the processing stage which made managing updates and attributes for terminated and re-hires identities challenging.
To address the challenge with the processing of terminated identities that have accounts still existing in the system, the FilterTerminatedIdentities setting has been configured to the false value by default.
With the following mappings it allows to have an overview of the account ownership for terminated identities that were not deleted from Omada Identity.
| Destination | Operator | Source |
|---|---|---|
| Status | Expression | IDENTITYSTATUS_Value == "Terminated" ? "PostValidity" : IDENTITYSTATUS_Value |
| ManagedByOIS | Expression | IDENTITYCATEGORY_Value == "Contractor" || IDENTITYTYPE_Value == "Machine" || IDENTITYSTATUS_Value == "Terminated" |
For newly deployed and migrated systems that are operating with the Horizons solution, the FilterTerminatedIdentities setting is by default configured to false.
For systems that are already utilizing Horizons, Omada recommends changing the FilterTerminatedIdentities value to false for non-production environments.If testing of the terminated identities management is satisfactory, contact Omada Support to change the default value of the setting in the production environment.
For more information, go to the Recommendations section of Horizons documentation.