Difference between revisions of "ProxyUpdateType"
(Created page with "== Basics == There are three different interface scenarios that can be configured for every single Proxy Prop-erty * Master * Client * Bi-directional This Interface direction...") |
|||
| Line 18: | Line 18: | ||
* Solve the conflict according the Timestamp information: the newest change wins agains the older one. | * Solve the conflict according the Timestamp information: the newest change wins agains the older one. | ||
* Manual solve: mark the object and let the user solve the “problem” | * Manual solve: mark the object and let the user solve the “problem” | ||
| + | |||
| + | ==See also== | ||
| + | * [[Proxy]] | ||
| + | * [[MetaProxy]] | ||
| + | * [[ProxyMetaProperty]] | ||
Revision as of 13:48, 16 January 2014
Contents
Basics
There are three different interface scenarios that can be configured for every single Proxy Prop-erty
- Master
- Client
- Bi-directional
This Interface direction as well as the conflict solving mechanism must be configureable on the Relation between MetaProxy and ProxyMetaProperty.
Master
As the Proxy Property is defined as a Master, the value is always exported from UBIK. The value will never be imported. Changes from the external system will always be discarded.
Client
As the Proxy Property is defined as a Client, the value is always be updated during an import from the 3rd party system. The value will never be exported. Changes in UBIK will always be dis-carded.
Bi-Directional
As the Proxy Property is defined as export/import “Bi-Directional” the Proxy supports both, exporting and importing the Property value. During the processing conflicts must be recog-nized. A conflict is as the property was changed in UBIK AND in the external system. There are two different Conflict scenarios:
- Solve the conflict according the Timestamp information: the newest change wins agains the older one.
- Manual solve: mark the object and let the user solve the “problem”
