Enter the following details for a property mappingList of object matching rules and property mapping rules which map the schema properties of two connected systems to one another. rule.
Detail |
Description | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Rule types |
Select the rule type for a new rule.
| ||||||||||
Rule name |
Name of the rule. The rule name must be unique within a mapping. Click to change rule names. The rule name is used as key. Changes to the rule name may cause errors. | ||||||||||
Display name |
Rule display name. | ||||||||||
Mapping directionDirection in which schema property data is transferred. The mapping direction determines the primary system for the schema property. |
Specify the permitted mapping direction for mapping selected schema properties.
| ||||||||||
Ignore mapping direction restrictions on adding |
Specifies whether the given direction of mapping is ignored when new objects are added. If this option is set, the property mapping rule can also be run if the synchronization mapping is in the opposite direction. Property mapping rules not assigned a mapping direction are also ignore when new objects are added. If this option is not set, the specify mapping direction is valid when new objects are added. Example: A telephone system is managed with One Identity Manager. The telephone system acts as the primary system when the telephone numbers are synchronized. The direction of mapping is set to One Identity Manager. The telephone number is a mandatory value in the target system. In One Identity Manager, a new employee is added. Each employee is given and initial telephone number. These employees should be added to the target system by synchronizing them. So that the telephone numbers are written to the target system during synchronization, the Ignore mapping direction restrictions on adding option must be set on the property mapping rule. | ||||||||||
Description |
Text field for additional explanation. | ||||||||||
Concurrence behavior |
Specifies whether the property mapping rule is always applied. Objects in a connected systemSystem the objects and their properties are transferred to during synchronization. The connected system is defined by the synchronization direction. Example of synchronization direction "Target system" (One Identity Manager -> Active Directory): Here Active Directory is the connected system and One Identity Manager is the primary system of synchronization. (synchronization target) that
are excluded by default to avoid data conflict. If possible, synchronization of these objects is repeated by the next synchronization run. In rare cases, it may still be necessary to synchronize some properties of these objects immediately, to transfer safety-critical changes to the connected system, for example.
For more information, see Concurrence behavior of synchronization objects. | ||||||||||
Schema propertyProperty of a schema type. Refers to exactly one column of a table or view of the database based schema or exactly one object type property of the non-database based schema. |
Select the schema properties to be mapped. | ||||||||||
Do not overwrite |
The schema property value is only changed by synchronization if the schema property does not contain a value. | ||||||||||
Mapping condition |
Condition under which the property mapping rule is used. Click Create condition to create the condition with the wizard. For more information, see Wizard for entering filters. Example: Left.CanonicalName = 'Managed Service Accounts' The property mapping rule is applied to all objects assigned to the container "Managed Service Accounts" in One Identity Manager. |
Detail |
Description |
---|---|
Force mapping against direction of synchronization |
If this option is set, the property mapping rule can also be applied if the synchronization mapping is in the opposite direction. For more information, see Mapping against the direction of synchronization. The option can only be set if:
The property mapping rule may not be run in both directions. |
Detecting rogue modifications |
Specifies whether rogue modifications are identified and logged if the direction of synchronization is opposite to the mapping direction. The option can only be set if:
If this option is set, rogue modifications are detected and logged. The log can be evaluated after synchronization. For more information, see Synchronization analysis. If the option is not set, the property mapping rule is ignored by synchronization. |
Correct rogue modifications |
Specifies whether rogue modifications are corrected if the direction of synchronization is opposite to the mapping direction. The option can only be set if:
If the option is set, the property mapping rule is run by synchronization. The object propertyValue of a schema property for a specific object. in the connected system is overwritten with the value from the primary system. Thus rogue changes are ignored. If the option is not set, rogue changes are only logged. |
Ignore case |
Specifies whether changes that only differ through case are ignored by the mapping. This option affects only schema properties with the String data type. |
Deal with the first value of the property as a single value |
If a multi-value schema property is mapped using a value compare rule, the first value from the value list is taken into account by synchronization. |
Disable merge mode support |
Specifies whether to disable merge mode for single provisioning of memberships in this property mapping rule. If the option is set, when memberships are provisioned and merge mode is enabled on the assignment tableTable in which relationships between two tables are established. Both tables' objects are assigned to each other as a many-to-many relationship. For example, assignment tables are PersonInDepartment or ADSAccountInADSGroup., the entire membership list is also transferred. |
Member filter | Description |
---|---|
Only include these | Select all members in the value list to be mapped to the schema property of the connected system. |
Exclude these | Select all members in the value list not to be mapped to the schema property of the connected system. |