Fusion Data Synchronization

In the ongoing data synchronization process, updating data from the Customer Experience for Utilities solutions is an asynchronous update that is completed using Oracle Signals. This process requires you to:

  • Enable Signals in your profile options

  • Provision a user role to fetch signals from Oracle Fusion applications

  • Update existing signal definitions (optional)

  • Understand the naming conventions for signals

  • Create a user in your Oracle Utilities customer information system to persist data

The remaining steps in this topic are written for Oracle Utilities Customer Cloud Service. If you are using another Oracle Utilities customer information system, refer to the documentation for your identity management system to determine how to complete these steps for your implementation. Contact your implementation team for additional assistance.

Additionally, extended attributes are currently not supported. Signal definitions are seeded and cannot be modified. Seeded signal definition cannot be configured to have an extended attribute. Create, update, and delete of extended attributes is not supported.

Task Details
Enable Signals

To implement near real-time synchronization for contact and account records, you must enable the Signals functionality by setting the profile option, Common CRM Signals Active (ORA_ZCA_ENABLE_SIGNALS), to Yes. By default, Signals functionality is disabled.

For information about setting profile options, see Set Profile Option Values in the Oracle Fusion Implementing Applications Guide.

Provision User Role to Fetch Signals

Add the Sales Administrator role (ORA_ZBS_SALES_ADMINISTRATOR_JOB) to the provisioned FABRIC_CX4U_SYSTEM_USER user.

For additional information, see Manage Roles and Users.

Update Existing Signal Definitions (Optional)

  1. Fetch all active seeded definitions using the following URL: https://<HOST>:<PORT>/crmRestApi/resources/11.13.18.05/signalDefinitions?q=OwnerGroup='CX4U';ActiveFlag=true

  2. Fetch the configuration using the following URL: https://<HOST>:<PORT>/crmRestApi/resources/11.13.18.05/signalDefinitions/<SignalDefinitionId>/enclosure/Configuration

  3. Encode the modified configuration into Base64 format.

  4. Submit the request:

    URL: https://<HOST>:<PORT>/crmRestApi/resources/11.13.18.05/signalDefinitions/<SignalDefinitionId>

Request: PATCH

Sample Payload:

 

{

"eyJPYmplY3RQYXlsb2FkQXR0cmlidXRlcyI6WyJQYXJ0eU51bWJlciIsIlNvdXJjZVN5c3RlbSIsIlNvdXJjZVN5c3RlbVJlZmVyZW5jZVZhbHVlIl0sIlJlbGF0ZWRPYmplY3RQYXlsb2FkQXR0cmlidXRlcyI6WyJDb250YWN0UG9pbnRJZCIsIkNvbnRhY3RQb2ludFR5cGUiLCJFbWFpbEFkZHJlc3MiLCJFbWFpbFB1cnBvc2UiLCJMYXN0VXBkYXRlZEJ5IiwiUGhvbmVBcmVhQ29kZSIsIlBob25lRXh0ZW5zaW9uIiwiUGhvbmVOdW1iZXIiLCJQaG9uZVB1cnBvc2UiLCJQcmltYXJ5RmxhZyIsIlNvdXJjZVN5c3RlbSIsIlNvdXJjZVN5c3RlbVJlZmVyZW5jZVZhbHVlIiwiU3RhdHVzIiwiVVJMIiwiV2ViUHVycG9zZSJdLCJQZXJzaXN0ZWRGbGFnIjp0cnVlLCJTdHJlYW1lZEZsYWciOmZhbHNlLCJDb25kaXRpb24iOiIkU291cmNlU3lzdGVtID09ICdDSVMnICYmICRMYXN0VXBkYXRlZEJ5ICE9ICdGQUJSSUNfQ1g0VV9TWVNURU1fVVNFUicifQ=="

}

  5. Also, when making any configuration changes, modify only the following configurations:

    • ObjectPayloadAttributes

    • RelatedObjectPayloadAttributes

    • ChangeAttributes
Understand the Naming Conventions for Signals

When cloning a signal definition, the signal should be modified to use the <Signal Name>/<Version> format. For example:

  • Create Account ContactPoint for CX4U/v1

  • Create Account ContactPoint for CX4U/v2

If there are multiple active versions with the same signal name, only the higher version is considered for the polling. In the above example, only Create Account ContactPoint for CX4U/v2 would be considered for signal polling, and Create Account ContactPoint for CX4U/v1 would be ignored.
Create an Oracle Utilities User to Persist Data

To create the utilities user that enables data synchronization, complete these steps:

  1. Log into your Oracle Utilities customer information system and your related Oracle Identity Cloud Service (IDCS) as an administrator.

  2. In IDCS, select Oracle Cloud Services.

  3. Locate the record with the description "CX4U Integration (Signals)" and click the hyperlink in the Name column.

  4. Scroll down to the OAuth Configuration section, and locate the Client ID field.

  5. Copy the value displayed in the Client ID field.

  6. Go to your Oracle Utilities customer information system, and add a user that has the following values:

    • User: Enter a name that represents an integration user. For example, CX4UINTG.

    • Login ID: Enter the Client ID you copied from IDCS.

    • First Name: Enter a name that will enable you to easily understand the purpose of this user. For example, CX4U.

    • Last Name: Enter a name that will enable you to easily understand the purpose of this user. For example, OAuth Client.

  7. User Enable: Select Enable.

  8. Specify a user group that is given to users who are using the Customer Experience for Utilities experiences.

  9. On the To Do Roles tab, specify a role that enables integration of all necessary data between your customer information system and Customer Experience for Utilities. For example, ensure that the role includes customer, person, and account data.

  10. On the Access Security tab, specify a data access role that enables this user to access all data required by the integration, and pass it between systems. For example, person, customer and account data.

  11. Complete the steps for creating a user. See Security and User Options in the Framework Administrative User Guide for your Oracle Utilities customer information system, available in the Oracle Energy and Water help center.

Parent topic: Ongoing Data Synchronization