C Appendix: Upgrade Considerations

This appendix provides information about the steps you need to complete when you upgrade from one release of Customer Experience for Utilities to a newer release.

Task	Documentation Link
Register Applications Register your upgraded Oracle Utilities environment and Fusion applications to ensure that all new components and applications are functional in your upgraded release.	See Register Your Oracle Utilities Environment and Fusion Applications
Review Upgrade Policy Review the Upgrade Policy to verify that systems are upgraded to the appropriate release and maintenance levels to support all features and functionality.	See My Oracle Support Document ID 2876281.
Complete Content Merge of Utility Configurations Before you upgrade your solution to a new release, complete the following steps: Before you provision the instance, take a backup of the configurations you entered in the UtilityConfigurations REST API by invoking: GET: <FA API GW>/admin/utilityConfigurations After the instance is upgraded, invoke the UtilityConfigurations REST API using: GET: <FA API GW >/admin/utilityConfigurations Compare the pre-upgrade configuration content to the post-upgrade content, merge any utility configurations from the pre-upgrade content to the post-upgarde content, and publish the merged content by invoking: PUT: <FA API GW>/admin/utilityConfigurations	See Integration Configuration Tasks
Upgrade Extensions to Use Fragments If you have extended user actions in Agent Service or Sales, you might need to redo the configuration of those extensions to use containers. The task steps associated with the extension uses cases have been updated to reflect the use of containers.	See the updated task steps for these extension use cases: Adding an Action to the Person and Premise Search Adding an Action to the Customer Dashboard Adding an Action to Premise Customer History
Changes to Single Sign On and User Synchronization Processes Be aware that the Oracle Fusion Applications team will be contacting Oracle customers to assist them in upgrading their single sign on (SSO) and user synchronization processes.	See the updated task steps in this guide when it is time for you to upgrade to the new processes: Configure Single Sign On Configure User Synchronization
Custom Phone Purpose Any extended phone purpose from a prior release should be included in the fallback mapping configuration using the CommunicationType and Phone Purpose mapping admin entities. This ensures upgrade safety by preserving compatibility with existing data.	See person-data-sync-configs.html#GUID-4EE8B90C-6F89-4787-8073-BC4106E33AD4 for additional details.