IMPORTANT Actions and Considerations

PRE-UPGRADE CONSIDERATIONS

Modifications to Known Functionality

Before upgrading to Oracle CPQ 25C, we recommend you review the modifications to known functionality and plan accordingly.

Oracle CPQ Feature Description
Cross-Origin Resource Sharing (CORS)

In Oracle CPQ 25C, all new sites will require logging a Service Request (SR) on My Oracle Support to enable and set values for CORS Headers.  This modification does not impact existing sites. Existing sites will retain current CORS Headers settings upon upgrade to Oracle CPQ 25C.

Oracle CPQ 25C also adds support for Access-Control-Exposed-Headers for non-preflight CORS requests.

Refer to CORS Access Control for REST APIs for more information.
DataCube Export Integration and Data Table Export Scheduler Integration Ciphers

We are announcing a security enhancement that will impact outbound integrations to customer managed SFTP servers. Beginning in Oracle CPQ 26A, we will only support the following ciphers:

  • chacha20-poly1305@openssh.com (Recommended)
  • aes256-ctr
  • aes192-ctr
  • aes128-ct
If your SFTP server does not support one of these ciphers, upon upgrade to Oracle CPQ 26A your Data Cube Export and Data Table Export Scheduler integrations will no longer work. We recommend you ensure that your infrastructure supports one of the supported ciphers.
JET 17.1.0 Oracle CPQ 25C supports JET 17.1.0. Refer below to Custom JavaScript and CSS for details.
jQuery Upgrade jQuery is a fast and concise JavaScript Library that simplifies HTML document traversing, event handling, animating, and Ajax interactions for rapid web development. Oracle CPQ 25C supports jQuery 3.6.4. Customers with an older version of jQuery and with JavaScript customizations will need to thoroughly test the customizations.
Pricing Lookups

Beginning in Oracle CPQ 25C, Pricing Lookups are moved to the CPQ platform level and are simply referred to as Lookups. We recommend you review the modifications to known functionality and plan accordingly:

  • Upon upgrade to Oracle CPQ 25C, user groups with access to "Pricing Portal" will automatically be provisioned with access to "Lookups". Afterwards, administrator user access to "Lookups" needs to be explicitly granted.
  • Pricing Portal bulk download no longer includes Lookups. Lookups are now imported and exported from the Lookups administration page.
  • Pricing Lookups contained in migration packages prior to Oracle CPQ 25C will be ignored when they are migrated to a Oracle CPQ 25C site.
See Lookups Available Across Application in this document for more details.
Administrator Access Permissions

As previously announced, the deprecation of the legacy Access Permissions feature occurs in Oracle CPQ 25C. Access Permissions, sometimes referred to as Admin Segmentation, have been replaced by Administrator Groups. Administrator Groups have been an opt-in feature, but enabling this feature is now mandatory to disable legacy Access Permissions. If you have not yet enabled Administrator Groups, you must transition to Administrator Groups.
Basic Authentication We recommend transitioning away from Basic Authentication and to OAuth as part of your overall plan for secure communication connection. OAuth 2.0 is the industry-standard protocol for authorization. Access Tokens are more secure than basic authentication.
Broadcast Email As previously announced, the deprecation of Oracle CPQ Broadcast Emails occurs in Oracle CPQ 25C. Broadcast Emails could pose a security risk therefore we recommend transitioning away from broadcast emails.  
Firefox Browser iFrame with IDCS

Oracle CPQ customers, when embedding a third-party application in an iFrame, are likely to receive an error message preventing the third-party application from rendering. Specifically this may occur when using Oracle Identity Cloud Service (IDCS) as the Identity provider and if the Oracle CPQ domain and the third-party application domain are different. This is particularly an issue when using a Mozilla Firefox browser, as the default settings for Firefox are set to prevent cross-domain content. Google Chrome and other browsers have the default set to allow cross-domain content.

Updating your Firefox browser setting may resolve the issue:

  1. Go to the Firefox browser Settings page.
  2. Disable Enhanced Tracing Protection for the specific web portal you are using in the Firefox browser.
Please note that care must be taken when iFrames are implemented due to the risk of compromising Oracle sites. Customers can log a Service Request (SR) on My Oracle Support if further assistance is required.
Legacy Quoting Rich Text Editor

As part of our ongoing efforts to enhance our product in Oracle CPQ 25B and later, we have replaced the legacy Rich Text Editor (RTE) in the Legacy Quoting UI with a new editor, consistent with the one used in the JET Quoting UI. This upgrade introduces a more robust and user-friendly text editing experience while maintaining compatibility with the existing Legacy UI. The new editor offers enhanced functionality such as improved formatting options, better performance, and cross-platform compatibility. All existing content and formatting will remain intact, ensuring a seamless transition for users.

Impact on Behavior:

  • Existing text and formatting will remain intact; no migration effort is required.
  • Users will notice differences in the editor's layout and tool availability.
  • Enhanced accessibility features make editing more inclusive for all users.
Oracle CPQ and Oracle Fusion Integrations In Oracle CPQ 25B and later, new Partner Organizations set up in Oracle CPQ and Oracle Fusion Integrations will not include the Partner Organization SuperUser account. The newly elevated Partner Organization User Administration Permission account will replace the SuperUser. 
Partner Company Layout Enhancements

In Oracle CPQ 25B, we made subtle layout improvements to the following Partner Companies, formerly Company Administration List page:

  • Displays External License Metrics at the top of the page
  • Added an Assigned Users column with link to Users page displaying all users for that company
SOAP Groups API with Web Services In Oracle CPQ 25B and later when the Host Company Application Administrator creates a group with no users for a Partner Organization via SOAP Groups API, a SuperUser will no longer be added as a default member to the group.
User Management Layout Enhancements

In Oracle CPQ 25B, we made subtle layout improvements to the following User Management pages.

  • Users formerly User Administration List page:
    • Adds a Company drop-down for host company filtering of the user list (read-only field for Partner Organizations)
    • Displays License Metrics at the top of the page
    • Adds a View drop-down
    • Reorders and adds Status to the User List columns
  • User Detail formerly User Administration page:
    • Reorganizes and renames sections
    • Adds the Group Association section
    • Supports a Reset Password action button

Planned Changes to Supported Features

To continually improve our application, Oracle CPQ routinely evaluates product capabilities to identify older features that should be replaced with improved functionality. Supporting outdated features adversely impacts the value that we bring to our customers. This announcement provides information to CPQ administrators and IT professionals to prepare for future updates, including the uptake of provided alternative functionalities. The table below includes planned feature deprecations and their removal release schedule.

What does this mean?

"Deprecated" means the feature is planned for removal in a future Oracle CPQ Update (see End of Life column in the table below). The feature will continue to function for existing users until that time but will not be further enhanced or documented. After removal, the feature will no longer be supported or function.

Oracle CPQ Feature Deprecation Announced End of Life and Removal Description
Direct Login 25A Under Review

We have announced the deprecation of the Direct Login feature for Oracle CPQ. If you are currently using Direct Login, we recommend administrators plan the transition to Single Sign-On (SSO). The end of life and removal of this functionality is currently under review.

Note: Direct Login is an infrequently used integration feature. This feature is enabled/disabled from the General Site Options page. This change in behavior will not affect users' ability to log into Oracle CPQ from the Oracle CPQ Login page.
SOAP v1
Web Services
 25A Under Review We have announced the deprecation of the SOAP v1 Web Services for Oracle CPQ. This may include Remote Web Services Single Sign-On which use SOAP v1 Login API endpoints. If you are currently using SOAP v1, we recommend administrators plan the transition to REST Web Services. The end of life and removal of this functionality is currently under review.

Custom JavaScript and CSS

While Oracle CPQ does not endorse or guarantee the use of JavaScript customizations, we recognize that some customers have extended Oracle CPQ. Customizations may conflict with new Oracle CPQ platform features, data may be corrupted or lost, maintenance and support may be difficult, cross-browser support must be verified, performance may be impaired, and testing is required for each upgrade. Customers should carefully consider the relative benefits of JavaScript customizations in light of the associated risks.

Customers are recommended to utilize the CPQJS APIs instead of manipulating the Document Object Model (DOM) structure or specific elements, classes or IDs.

If customers have added custom JavaScript that leverages the Document Object Model (DOM) structure or specific elements, classes or IDs, this customization should be thoroughly tested and may require refactoring.

Oracle CPQ 25C and later supports JET v17.1.0. Please note the following:

  • The Combobox Arrow (<oj-combobox-arrow>) and Search Select Arrow (<oj-searchselect-arrow>) tags are changed from <a> to <span>.  The following are impacted by this change: Favorites List and Detail pages, Commerce Analytics graph, and Single Select Menu (SSM).
  • The JET Table component(<oj-table>) column header custom styling behavior is changed. The Table's default column header DOM structure has been updated. As a result, alignment-related CSS applied directly to the Table's header elements via the 'headerStyle' or 'headerClassName' properties of the Column API will no longer function as expected. For example, specifying the CSS 'text-align:end' will have no effect on the alignment of a header's text. Instead, the corresponding 'oj-helper-' styling class should be specified via the 'headerClassName' property - 'oj-helper-text-align-end' in this example. This change does not affect the Alta theme.
  • The JET Selector component (<oj-selector>)  requires aria-label. Applications must specify aria-label on <oj-selector> in order for it to be accessible.
  • The Section Expand/Collapse component(<oj-collapsible>) has an updated DOM hierarchy. Hyperlink to Expand/Collapse is moved as a sibling to label node. For example:
    • JET v17.1.0 syntax:

JET 17.1.0 Syntax

  • JET v12.1.0 syntax: 

JET 12.1.0 Syntax

Note: JET widget CSS applies to elements with class that starts with '.oj'. Oracle JET reserves this as a namespace. As such all customized elements that include '.oj' should be reviewed, tested, and refactored. Going forward no customized elements should include '.oj' in order to prevent future issues.

Oracle CPQ 22C upgraded jQuery to 3.6.4. Customers using earlier versions of jQuery need to upgrade and test their JavaScript customizations.

Refer to the following resources for more information:

Migration

When using Import From Source or Connect To Destination to migrate content, both sites must use the same major update. The migration of content can only occur across minor updates within the same major update.

  • "Major update" = Update 25C
  • "Minor update" = Update 25C Patch 1

When using Migration Packages, content from 19A and forward can be uploaded to the latest site version.

Resolved Known Issues

For information on bugs fixed in Update 25C, refer to the Oracle CPQ 25C Resolved Known Issues document available at Oracle CPQ Cloud Release Documentation and from the Oracle CPQ Administration Online Help.

Translation

For some system-defined messages and components, strings were removed and others added in Oracle CPQ 25C. If you have created your own implementation-specific translations of system-defined strings, some of these strings may no longer appear. Other strings may appear in English. The strings appearing in English are new and require translation.

Most of these messages and components are on the Administration side of Oracle CPQ, but you should review both your end user and administration pages before deploying your updated installation to confirm that all strings appear in the desired language.

Translation Status

Oracle CPQ supports the consumption of both single and multi-byte character sets. Submit a service request on My Oracle Support to enable your site for a new language.

Oracle CPQ provides translations in the platform and reference application for the following languages:

  • Chinese (Simplified) [China]
  • Chinese (Traditional) [Taiwan]
  • Czech [Czech Republic]
  • Danish [Denmark]
  • Dutch [Netherlands]
  • English
  • Finnish [Finland]
  • French
  • French [Canada]
  • German
  • Hungarian [Hungary]
  • Italian
  • Japanese [Japan]
  • Korean [South Korea]
  • Norwegian (Bokmål) [Norway]
  • Polish [Poland]
  • Portuguese [Brazil]
  • Romanian [Romania]
  • Russian [Russia]
  • Spanish (Worldwide)
  • Swedish [Sweden]
  • Turkish [Turkey]

POST-UPGRADE CONSIDERATIONS

Upgrade and test all test instances on Oracle CPQ 25C before upgrading to production.

Customer Upgrade Testing

Customers should actively test new versions applied to non-production environments before a scheduled production upgrade. At minimum, customers should test the lifecycle of a transaction, with the typical actions that sales users perform. These may include but are not limited to: start transaction, new configuration, reconfigure existing configuration, parts search, discounting, printing, revisions, and approvals. Integration points should also be tested. Reviewing the What's New is highly recommended as this practice may indicate additional focus areas for testing.

Customers should also test any customizations made on the environment, especially JavaScript and unsupported integrations. Note that custom JavaScript is the most frequent cause of post-upgrade issues. Custom JavaScript and unsupported integrations are not supported by Oracle Support or Development. In particular, note that an upgrade may introduce changes to the DOM, which could impact use of customer JavaScript and CSS.

While Oracle CPQ does not endorse or guarantee the use of JavaScript customizations, we recognize that some customers have extended Oracle CPQ to support critical use cases. JavaScript API ("CPQJS") includes methods for accessing attributes, actions, and other elements on the JET Configuration and JET Transaction UIs. Customers should consider carefully the relative benefits of JavaScript customizations in light of the associated risks. Customizations may conflict with new Oracle CPQ platform features, data may be corrupted or lost, maintenance and support may be difficult, cross-browser support must be verified, performance may be impaired, and testing is required for each upgrade.

Oracle CPQ does extensive testing as part of the release cycle. Therefore your testing plan efforts should focus on testing customer-specific use cases rather than general tasks such as adding a configuration attribute.

Update Early Testing and Cohort Schedule

Customers are encouraged to take advantage of the Early Test periods in their 25C Update Cohort. This provides time for you to update one or more pre-Production environments to test customizations and use cases and make any necessary adjustments. The following table summarizes the Oracle CPQ Update 25C schedule. If you are uncertain which Update Cohort you are in, please submit a Service Request (SR) on My Oracle Support.

Cohort

Early Test Updates

Pre-Production Updates

Production Updates

A

 July 4 and 5

August 1 and 2

 August 15 and 16

B

July 4 and 5

August 1 and 2

September 5 and 6

September 19 and 20 

C

August 1 and 2 

September 5 and 6 

October 3 and 4

October 17 and 18

Oracle CPQ follows the Oracle SaaS Cohort Update Policy and Schedule. Quarterly Updates cannot be skipped. You need to integrate your Update schedule into your business and project plans. Customers must opt-in to Early Test by submitting a SR on My Oracle Support. You may elect to permanently opt-in to Early Test but must keep the same Early Test sites and cadence to do so.

Customers may request to have a few Pre-Production environments upgraded along with the Production environment on the standard Production schedule by submitting a SR on My Oracle Support. You may request to have the same sites upgraded along with your Production environment permanently to avoid having to submit SRs every quarter.

Issues after Upgrade

If a customer experiences issues after the upgrade, there are two different processes depending on if the upgrade is a non-production or production upgrade.

Issues after Non-Production Upgrade

  • Log a Service Request (SR) through My Oracle Support.
  • The Service Request will be picked up by Customer Support, and assigned to the Point of Contact (POC).
  • The Service Request is worked as a standard Customer Support Service Request.

Note: In some instances the customer administrator may resolve issues without opening a Customer Support Service Request.

Issues after Production Upgrade

  • In most cases, production upgrades go smoothly and the Upgrade Service Request is closed once the upgrade completes.
  • The customer is instructed to open a "Severity 1" Service Request in the event that there is a critical issue after the production upgrade that was not identified after the non-production upgrade. Critical issues after upgrade would be considered production site down, 100% of users cannot quote, or other revenue impacting business critical issues.
  • Once the "Severity 1" Service Request is created, the on-call team is notified.
  • On-call team member(s) will work the Service Request towards resolution.
  • On-call team member will then reach out to Oracle Upgrade Specialist who performed the post upgrade validation if needed.

Browser Support

Oracle CPQ supports all browser versions that meet the criteria of the Oracle Software Web Browser Support Policy.

If you experience issues using a supported browser version, open a ticket on My Oracle Support to resolve the issue. If an issue arises when using a supported browser, use a certified browser version until a fix is delivered. Certified browsers are selected based on current market share and are thoroughly tested to work with the current version’s standard functionality.

Certified Browsers

Windows

  • Google Chrome 136.x
  • Mozilla Firefox 138.x
  • Microsoft Edge 136.x

Mobile Devices

  • Apple iPad iOS 18.x, Safari browser
  • Apple iPhone iOS 18.x, Safari browser

Note: Compatibility issues with the selected browsers may exist when sites are created with additional JavaScript, alternate CSS, or other custom functionality. Customizations may require add-on work. Contact My Oracle Support to determine the availability of workarounds and minor fixes.

Additional Information

Please refer to the release documentation for all versions between your current version and the version to which you are upgrading to see all new functionality, resolved known issues, and functional known issues.

Refer to Oracle CPQ Administration Online Help to become familiar with the new features introduced in Oracle CPQ 25C. For additional help, see My Oracle Support.

Verify any information not explicitly mentioned in this document as supported by the software against the product help for Oracle CPQ 25C.

Disclaimer

The details in this document are provided for high-level informational purposes only and are not intended to function as a specification or to replace the Online Help. Upgrading to a subsequent release may require the re-deployment of Commerce Processes, Configuration, or global function settings. Modifications to integration XSL files or APIs may also be required.