Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
devel:documentation:systems:dev:system-mapping [2019/07/02 09:11]
svandav [MERGE (Merge)]
devel:documentation:systems:dev:system-mapping [2019/07/02 09:15]
svandav [AUTHORITATIVE_MERGE (Authoritative merge)]
Line 152: Line 152:
  
 ==== AUTHORITATIVE_MERGE (Authoritative merge) ==== ==== AUTHORITATIVE_MERGE (Authoritative merge) ====
 +{{tag>authoritative merge}}
  
 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 167:
  
 ==== MERGE (Merge) ==== ==== MERGE (Merge) ====
 +{{tag>merge}}
  
 <note warning>Since version **9.3.0** was provisioning merge completely reimplemented!</note> <note warning>Since version **9.3.0** was provisioning merge completely reimplemented!</note>
Line 218: Line 220:
  
 ==== Skip merged value if contract is excluded ==== ==== Skip merged value if contract is excluded ====
 +
 +{{tag>merge skip exclude contract}}
  
 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. 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.
Line 230: Line 234:
 <note important>**If all roles which defines the account will have skipped values, then account will not be deleted!**</note> <note important>**If all roles which defines the account will have skipped values, then account will not be deleted!**</note>
  
-{{ :devel:documentation:systems:dev:skip.png |}}+{{ :devel:documentation:systems:dev:skip_m.png |}}
  
 ==== Additional characteristics of strategies ==== ==== Additional characteristics of strategies ====
  • by svandav