Table 21 details the general features supported by the
connector.
Category | Feature | Support | Notes |
---|---|---|---|
Business object attributes | Foreign key | Full | Clarify CRM makes full use of Foreign Key. |
Foreign Key attribute property | Partial | The connector for Clarify CRM uses a complicated set of rules when dealing with the foreign Key property, please see the Section Business Object Attribute Properties, sub section Foreign Key Property, in the connector documentation. | |
Key | Full | The first attribute must be marked Key in Clarify CRM. | |
| Max Length | No | Clarify CRM ignores this field. However, if the size of a field passed into the connector is larger than the field in Clarify CRM, the data is automatically truncated. |
Meta-data-driven design | Full |
| |
Required | Full | Clarify CRM uses the Required field with the Foreign Key field. | |
Connection lost | Connection lost on poll | Full |
|
Connection lost on request processing | Full |
| |
Connection lost while idle | No |
| |
Connector properties | ApplicationPassword | Full |
|
ApplicationUserName | Full |
| |
UseDefaults | Full |
| |
Message tracing | General messaging | Partial | Tracing is supported; however, compliance with this standard needs to be reviewed. |
generateMsg() | No | Clarify CRM uses generateMsg() for all tracing. | |
Trace level 0 | Full |
| |
Trace level 1 | Full |
| |
Trace level 2 | Partial |
| |
Trace level 3 | Partial |
| |
Trace level 4 | Partial |
| |
Trace level 5 | Partial |
| |
Misc. | CDK method LogMsg | Full |
|
Java Package Names | N/A |
| |
Logging messages | Full |
| |
NT service compliance | Full |
| |
Transaction support | Full |
| |
Special value | CxBlank processing | Full |
|
CxIgnore processing | Full |
|