| Chapter 2 • Synchronizing at a Glance | |
|
|
|
Check Name | Check Description |
|
|
|
|
Fields mapping | Checks that a field mapping is defined between the |
|
defined | endpoints and that it can be obtained by the |
|
| Synchronizer. |
|
|
|
|
Consistency of | Checks that if a field mapping is defined from the |
|
mapping and | endpoint, the link is set to handle record creation or |
|
endpoint events | updates in the other endpoint. Also checks that if the link |
|
| is set to handle record creation or updates in the |
|
| endpoint, a field mapping is defined to the endpoint. |
|
|
|
|
Checks Performed on Link Field Mappings
An integrity check performs the following checks on the field mappings you define for the link. The Synchronizer also performs these checks when you check the field mappings when you create or configure a link. Depending on the type of field mapped, not all of these checks are performed for every identity mapping.
Check Name | Check Description |
|
|
Required fields | Checks that required fields in the destination endpoint |
check | are mapped to a field in the source endpoint, or are |
| assigned a constant value. If this is not the case, the check |
| fails. |
| In addition, checks that recommended fields in the |
| destination endpoint are mapped to a field in the source |
| endpoint, or are assigned a constant value. If this is not |
| the case, the check passes with a warning. |
|
|
Field existence | Checks that the field exists in the endpoint. |
check |
|
|
|
Field types match | Checks that if a mapping exists between fields of different |
check | types, the values can be converted between the types. |
|
|
Fields length match | For string type fields (String, Multi value list, Single value |
check | list, User list), checks that the maximum length for values |
| for each of the fields in a mapping is the same. If the |
| maximum length is different, the check passes with a |
| warning that some values may be truncated. |
|
|
39