Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
devel:documentation:systems:dev:system-mapping [2019/05/06 10:28] svandav [Connector pool configuration] |
devel:documentation:systems:dev:system-mapping [2019/07/02 09:16] svandav [Attribute mapping] |
||
---|---|---|---|
Line 29: | Line 29: | ||
<note important> | <note important> | ||
- | Pool configuration is persisted in EAV attributes and use form definition with code " | + | <note tip>Pool configuration is persisted in EAV attributes and use form definition with code " |
Line 52: | Line 52: | ||
===== Attribute mapping ===== | ===== Attribute mapping ===== | ||
+ | {{tag> | ||
When the system scheme is created, we can move on to attribute mapping in the **Attribute mapping** tab. Mapping serves two basic purposes: | When the system scheme is created, we can move on to attribute mapping in the **Attribute mapping** tab. Mapping serves two basic purposes: | ||
Line 121: | Line 122: | ||
====== Mapped attribute strategy ====== | ====== Mapped attribute strategy ====== | ||
+ | {{tag> | ||
The attribute strategy defines how will the attribute and primarily its value be dealt with during provisioning and synchronization. | The attribute strategy defines how will the attribute and primarily its value be dealt with during provisioning and synchronization. | ||
Line 152: | Line 154: | ||
==== AUTHORITATIVE_MERGE (Authoritative merge) ==== | ==== AUTHORITATIVE_MERGE (Authoritative merge) ==== | ||
+ | {{tag> | ||
This strategy (identically to MERGE) alters the logic of calculating attributes and their values. With the other strategies applies the following: if there are more occurrences of the same strategy for the same attribute (more overloaded attributes in more roles), the one with the highest priority is found (according to role priorities or their names). The resulting value going into provisioning is calculated on the basis of this one attribute only. | This strategy (identically to MERGE) alters the logic of calculating attributes and their values. With the other strategies applies the following: if there are more occurrences of the same strategy for the same attribute (more overloaded attributes in more roles), the one with the highest priority is found (according to role priorities or their names). The resulting value going into provisioning is calculated on the basis of this one attribute only. | ||
Line 166: | Line 169: | ||
==== MERGE (Merge) ==== | ==== MERGE (Merge) ==== | ||
+ | {{tag> | ||
<note warning> | <note warning> | ||
Line 216: | Line 220: | ||
<note important> | <note important> | ||
+ | |||
+ | ==== Skip merged value if contract is excluded ==== | ||
+ | |||
+ | {{tag> | ||
+ | |||
+ | Since version **9.7.0** was added new feature enabling skip of value defined in merge attribute, if contract (on witch is role assigned) will be excluded. | ||
+ | |||
+ | For enable this feature you need to check the option **' | ||
+ | |||
+ | **Value will be skipped only if**: | ||
+ | - Attribute has strategy type sets to **MERGE** or **AUTHORITATIVE_MERGE** (only for this options will checkbox shows). | ||
+ | - Feature is **enabled** on the role mapping. | ||
+ | - Identity has assigned this role/s to the **excluded contract/ | ||
+ | |||
+ | <note important> | ||
+ | |||
+ | {{ : | ||
==== Additional characteristics of strategies ==== | ==== Additional characteristics of strategies ==== |