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/05/06 10:10]
svandav 		devel:documentation:systems:dev:system-mapping [2019/07/02 09:13]
svandav [Skip merged value if contract is excluded]
Line 18: Line 18:
  
 The last advantage is the ability to use **multiple connections** to one target system, which is especially advantageous during parallel processing. The last advantage is the ability to use **multiple connections** to one target system, which is especially advantageous during parallel processing.
 +
 +=== Pool configurations: ===
 +  * **Pooling supported** - Enable / disable entire pool
 +  * **Max idle objects**
 +  * **Minimum number of idle objects**
 +  * **Max objects** - Max number of objects in the pool.
 +  * **Max time to wait** - Max time to wait for free object in the pool.
 +  * **Minimum time to wait before evicting** - Minimum time to wait befor evicting idle object.
 +
 +<note important>By default is pool **disabled**!</note>
 +
 +<note tip>Pool configuration is persisted in EAV attributes and use form definition with code "pooling-connector-configuration".</note>
  
  
Line 204: Line 216:
  
 <note important>Final values merge from roles is set, **all duplicates will be removed**. For example: if you have two roles with merge mapping for same attribute and value for this attribute is same, to end system will be send only one.</note> <note important>Final values merge from roles is set, **all duplicates will be removed**. For example: if you have two roles with merge mapping for same attribute and value for this attribute is same, to end system will be send only one.</note>
 +
 +==== 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.
 +
 +For enable this feature you need to check the option **'Skip value when contract is excluded'**.
 +
 +**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/s**. If identity has assigned more same roles on different contracts, then for skipping of the value must be **all** connected contracts excluded.
 +
 +<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_m.png |}}
  
 ==== Additional characteristics of strategies ==== ==== Additional characteristics of strategies ====
  • by svandav