eADM
eADM
Breadcrumbs

The Synchronization Cycle

The Synchronization Cycle is a fundamental process in eADM runs multiple times a day. This automated cycle is responsible for importing data from source systems, maintaining user accounts, and exporting the updated information to various target systems.

The entire cycle consists of individual synchronization steps, which are specific tasks performed in a predefined order.


Synchronization Steps

Synchronization steps are the building blocks of the cycle, each performing a distinct function. The table below describes common steps.


Note: This list is not an exhaustive list of all possible synchronization steps.


Step Name

Description

Import Hierarchy

Import the organizational data structure.

Import HR

Import account, group, and department information from the primary source system (e.g., HR system).

ImportHrFuture

Import data for accounts scheduled to be created in the future (e.g., from Visma).

Import samAccountName

Import all existing samAccountName usernames from the organization's Active Directory.

Synchronization

Compares the newly imported source data with the previous data to generate a list of required changes.

Export AD

Exports new or updated objects to the organization's Active Directory.

Import AD Results

Imports the results from the Active Directory export to verify that the changes were successful.

Export HR

Exports data back to the source HR system.


The Synchronization Cycle Flow

The cycle follows a logical sequence, beginning with data import, followed by change analysis, and ending with data export to target systems.

Here is a detailed, step-by-step description of the process:

  1. Starting eADM triggers the synchronization cycle. This typically occurs at a scheduled time each day, often in the morning.


  1. eADM data from the primary source system, which is typically an XML file from a payroll or HR system. It may also import supplementary data, such as the AD organizational structure and any manually maintained data files. All this information is consolidated into a single source data file, which is stored in eADM later comparison.


  1. Analyze Change Requirements eADM the new source data file with the one from the previous cycle. The differences between these two files generate a list of change requirements, which specifies which accounts, groups, and departments need to be created, modified, or deleted.


  1. Apply Import Filter If an import filter is active, eADM the number of new, modified, and deleted objects against pre-configured thresholds. If the number of changes exceeds any of these thresholds, the synchronization cycle is automatically aborted to prevent unintended mass changes.


  2. Export to Active Directory (AD) If AD is a configured target system, eADM the required changes to AD. Afterward, it imports the results from AD to verify that the export was successful. If the results do not match the intended changes, the process is aborted and an error is reported.


  3. Export to Other Target Systems eADM exports changes to all other configured target systems, such as Azure AD, Google Workspace, or Public 360°. For each system, eADM the data, imports the result, and validates the outcome.


Warning: If any export fails or the validation detects a mismatch, the synchronization cycle will stop at that specific step and report an error. The cycle will not continue until the error has been resolved.


  1. The synchronization cycle completes successfully once all steps have been completed without errors.