Get Account Communications (Oracle Utilities Customer Cloud Service Initiated)

Call center agents and other users should be able to view recent Opower communications in Customer Cloud Service.

Customer Cloud Service sends a synchronous request to retrieve the latest customer communications for a specific utility and account. Opower returns both email and mobile app push customer communications in the response.

The request may include the date and time of the account’s last communications synchronization. If provided, the response should include only communications after that timestamp. If no timestamp is provided, Oracle Integration Cloud (OIC) uses the values configured in the lookups for each channel.

The following diagram shows a graphical representation of the Get Account Communication integration process.

A CCS account request triggers OIC queries for email and push communications. OIC combines the results and returns a response or fault to CCS.

Get account communications

Processing Details

The integration process deployed on Oracle Integration Cloud is exposed as a REST API and performs the following activities:

  1. The process is triggered when it receives a request from Oracle Utilities Customer Cloud Service to get the latest communications for an account.
  2. Get the latest email communications by querying the OU Opower BillingAccountOutboundCommunications API given an account id and a date time interval.
  1. Check the response from the query:

    • If no nodes are returned, proceed to the PUSH query.
    • If error nodes are returned, throw a fault or error back to Customer Cloud Service and end the process.
    • Otherwise, filter records so only RELAYED events are processed.
  2. Next, get the latest mobile app push communications by querying the Opower BillingAccountOutboundCommunications API given an account id and a date time interval.

  1. Check the response from the query:

    • If no nodes are returned, proceed to the next step.
    • If error nodes are returned, throw a fault or error back to Customer Cloud Service and end the process.
  2. Collect the returned communications for both queries and map them to the Customer Cloud Service response format.

  3. Return the communication information to Customer Cloud Service for customer contact creation and display.

  4. Any errors encountered are reported back to Customer Cloud Service as a fault/error.

Each channel query requests communications for one billing account and returns up to 100 communications. The integration does not support account-level pagination and must not update the scheduled flows’ start and end timestamps. If no communications are returned, no new customer contacts are created

Technical Details

The following table describes the integration processes and the respective Oracle Utilities Customer Cloud Service and Oracle Utilities Opower artifacts used in this integration process.

ArtifactValue
Integration Process NameOU CCS OPOWER Account Communications Get
Integration Process IdentifierOUTL-BA-CCS_OPWR_ACCTCOMMS_GET
Integration Project NameOU CCS OPOWER
Source Connection (Oracle Utilities Adapter)

OU REST CCS for CCS-OPOWER
triggerOutbound Message Type: C1ACCCOMMUOM (Account Communications)
Target Connection (REST Adapter)OU REST OPOWER for CCS-OPOWER
invokeService: Opower GraphQL API
Query: BillingAccountOutboundCommunications
Method: POST
URI: https://<host_name>/graphql/
LookupsOUTL-BRT-CCS_OPWR_BusinessConfigProps
OUTL-BRT-CCS_OPWR_CommunicationStatus
OUTL-BRT-CCS_OPWR_DeliveryChannel
OUTL-BRT-CCS_OPWR_TechnicalConfigProps