Known Issues

The following limitations and known issues apply to this integration release. Resolution of these issues is planned for a future release:

Missing Purpose for New Contact Points in Oracle Fusion CX Service

The Person Contact Type field missing error can occur in the OU CX CCS Contact Account Sync integration process when a contact point is synchronized from Oracle Fusion CX Service without a Purpose. Although Purpose is optional in Oracle Fusion CX Service, the integration requires it to determine the corresponding Oracle Utilities Customer Cloud Service Person Contact Type.

Specify a Purpose when creating phone, email, or web contact points in Oracle Fusion CX Service.

Contact Point Status Differences Between Applications

The OU CCS CX Person Sync integration process synchronizes Active or Inactive contact details from Oracle Utilities Customer Cloud Service only when their Contact Status is Approved. Additional statuses, such as Pending and Rejected, are not included in synchronization.

A previously synchronized contact point may therefore remain active in Oracle Fusion CX Service after its Contact Status changes to a transitional state in Oracle Utilities Customer Cloud Service.

Additional Integration Instances for Update and Delete CX Events

An update or delete event in Oracle Fusion CX Service may trigger up to five integration instances in Oracle Integration Cloud due to additional synchronization messages generated by Oracle Utilities Customer Cloud Service. These messages carry the same data, and existing controls prevent synchronization loops.

Lookup Value Matching and Duplicate Entries

Lookup values in OUTL-BRT-CCS_CX_CharacteristicValue and OUTL-BRT-CCS_CX_CommunicationType must match the expected values for each application exactly, including capitalization. In CommunicationType, enter CX contact point types as PHONE, EMAIL, or WEB.

Duplicate or conflicting mapping rows may cause lookup matching issues during synchronization. Remove duplicate rows so each lookup key resolves to a single mapping, and verify exact value matching before synchronizing.