A start up configuration contains all the required properties and options for a tangible synchronizationThe processSequence of process steps for mappingList of object matching rules and property mapping rules which map the schema properties of two connected systems to one another. an operational workflow. The process steps are connected to one another by predecessor/successor relationships. This functionality allows flexibility when linking up actions and sequences on object events. of comparing data between One Identity Manager and a target system. Objects and their properties are compared by fixed rules. Synchronization results in the identical data situation in the target system and One Identity Manager database.. This specifies which synchronization configuration components (workflows, mappings, variable sets) should be used for synchronization. Synchronization is started with a scheduleTask to run on a cyclical basis. Schedules control regular running of processes, calculation tasks, and other scheduled tasks. You define the start and interval times for the scheduled tasks. The activation time can be given in local time or Universal Time Code. A schedule can be in control of several tasks.. Different start up configurations can be set up for different synchronization targets.

If the synchronization projectA collection of all data required for synchronizing and provisioning a target system. Connection data, schema classes and properties, mappings, and synchronization workflows all belongs to this. was creating using a default project templateTemplateRule for mapping object properties. Templates can be applied to an object and also have a cross-object effect. used by the project wizard to create a preconfigured synchronization project., a start up configuration is added. You can edit this start up configuration and create new start up configurations. If the synchronization project was created without a project template, start up configuration is set up.