Skip to main content
Version: Cloud

Horizons Release Notes

Here you can learn about newest additions and improvements to Horizons platform. You can find the newest entries on the top of the page, with changes from previous months grouped under an appropriate section.

For more details, go to Horizons page.

note

Each entry contains a badge indicating the type of change that has been made:

DescriptionBadge
New version of a component is introduced.New version
A new component is added.New component
A change to a component was introduced that can change it's behavior.Component changed
A issue or a bug is resolvedResolved issues

May 2025​

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.

DestinationOperatorSource
StatusExpressionIDENTITYSTATUS_Value == "Terminated" ? "PostValidity" : IDENTITYSTATUS_Value
ManagedByOISExpressionIDENTITYCATEGORY_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.

April 2025​

Resolved bugs and issues ​

Account joined to multiple identities​

There was an issue with a single account joined to multiple identities. The issue has been resolved and no longer occurs.

INC-288773

Account matching to two identities​

There was an issue with an account matching to two identities, with one of them having the terminated status. The issue has been resolved.

INC-289439

Frozen import​

There was an issue with imports being suspended and not progressing. The issue has been resolved.

INC-290154

New hire calculations fail​

There was an issue with the way accounts were fetched resulting in calculations failing. This issue has been resolved and identities are processed correctly.

INC-289592

Import not starting​

There was an issue with the Worker Service losing connection with SignalR. If the reconnection attempt failed in a short timeframe, the Worker Service was not receiving notifications from SignalR, thus disrupting the import process. The issue has been resolved.

INC-289305

March 2025​

Resolved bugs and issues ​

Missing Account join scope​

There was an issue with the missing Account join scope in ownership rules. It has been resolved, and complete configuration is provided to the Account join component, ensuring it works correctly.

INC-289350

Account classification issue​

We have resolved a classification issue where, during the migration process, accounts were assigned incorrect type.

INC-288861

February 2025​

Resolved bugs and issues ​

Identities joining on empty fields​

There was an issue with identities joining with the join field value empty or set to null. The issue has been resolved preventing this behavior.

Errors during staging phase of the import​

There was an issue with inconsistent date formats in records, which caused errors during the staging phase of the import. Changing the expression to parse the incorrect date format has resolved the issue.

INC-286652

System import issue​

An issue with starting the system import, caused by incorrectly set id, has been resolved.

INC-286535

RoPE calculation issue​

An issue with a suspended RoPE calculation has been resolved.

INC-286501

Account join doesn't assign account type​

An issue where classification rule, that can only have the Scope attribute setting configured with the Identity join reason or Identity join properties value, was not working correctly because those values are also used by the ownership rule. The issue has been resolved.

INC-286323

Old data not removed after updating​

An issue with old records not being removed after data is updated has been resolved and now only entries with correct data are visible.

INC-286406

January 2025​

Highlight

With the January 2025 CU release, the Horizons platform achieves full feature parity with our previous data ingestion platform.

The following components have been updated ​

  • Account join
  • API
  • Delete detection
  • History tracking
  • Identity join
  • Identity merge
  • Import service
  • Import worker
  • Lookup service
  • Operational data store
  • Reproject component
  • Rope adapter

December 2024​

The following components have been updated ​

  • Account join
  • API
  • Delete detection
  • Identity join
  • Identity merge
  • Import service
  • Lookup service
  • Reproject component
  • RoPE adapter
  • RoPE calculator
  • Worker service