Communication Type
You must provide the mapping of lookup values for COMMUNICATION_TYPE. This list of values is fixed in Fusion applications and configurable in Oracle Utilities systems, where it is referred to as a routing type. If the values in Oracle Utilities are different than the fixed values in Fusion, you can map the corresponding values. If there is no entry, the values will be passed through unchanged.
The table below provides additional details on the tasks you need to complete.
| Task | Configuration | Comments |
|---|---|---|
| Add all needed communication types |
POST /api/CXIPlatformService/v1/CXIReferenceEntity/communicationType Example: POST https://<hostname>/api/CXIPlatformService/v1/CXIReferenceEntity/communicationType |
Oracle recommends using the same value for 'id' and 'faValue' in the request. Multiple communication type records can be added together by adding them to the "items" list in the request. |
| Edit a communication type record |
POST /api/CXIPlatformService/v1/CXIReferenceEntity/communicationType Example: POST https://<hostname>/api/CXIPlatformService/v1/CXIReferenceEntity/communicationType |
Multiple communication type records can be edited at the same time by adding them to the "items" list in the request. |
| Delete a communication type |
POST /api/CXIPlatformService/v1/CXIReferenceEntity/communicationType Example: POST https://<hostname>/api/CXIPlatformService/v1/CXIReferenceEntity/communicationType |
Multiple communication type records can be deleted at the same time by adding them to the "items" list in the request. |
| Fetch all communication types |
GET /utilitiesAdmin/v1/communicationType Example: GET https://<hostname>/api/utilitiesAdmin/v1/communicationType A specific country record can be fetched using: GET /utilitiesAdmin/v1/communicationType/{id} Example: GET https://<hostname>/api/utilitiesAdmin/v1/communicationType/PHONE |
Parent topic: View, Edit and Add Reference Types