Initial imports for Horizons

This page describes the recommended sequencing for initial imports when enabling Horizons in Omada Identity Cloud Private, covering identities, contexts, and how to control import timing with the Defer processing parameter.

Prerequisite

Omada Identity Governance is a prerequisite for enabling Horizons. It is responsible for provisioning users to the ES (Enterprise Server), based on identities imported from the HR source. Once enabled, the Provisioning section appears with a pre-configured data model and task mappings, but under Advanced settings it is set to Review mode.

Identities

To export managers and owners to ES, every corresponding identity must have a user created in ES (depending on the authentication type configured for the customer). Creating a user in ES requires a valid email, so confirm that every identity object has an email in the HR source before proceeding.

Recommended steps:

1. Remove Review mode on the Omada Identity system.
2. In Export queries and mappings, disable the Identity Owner mapping.
3. Run an import from the HR source with a small sample (for example, 10 identity records) and verify users were created in ES.
4. Run an import with all identities and verify users were created for all of them.
5. Enable the Identity Owner mapping and run a resync on the Omada Identity system.

Contexts

Contexts can be imported together with identities.

Recommended steps:

1. In Export queries and mappings, disable the Context Owner mapping before the first import.
2. Run an import from the HR source.
3. Enable the Context Owner mapping and run the import again.

Defer processing

All export queries run in parallel, and adapting starts as soon as an import begins. The Defer processing parameter postpones adapting a query until other queries have completed.

note

Defer processing is enabled by default on context hierarchy queries, to ensure all contexts exist before the parent-child relationships are set.