IMPORTANT Actions and Considerations

PRE-UPGRADE CONSIDERATIONS

Modifications to Known Functionality

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

Oracle CPQ Feature	Description
Admin Home	Following upgrade to Oracle CPQ 26B, the Admin Home page displays in Redwood UI for all customers. Oracle CPQ no longer supports the option to switch between Classic UI and Redwood UI. The Oracle CPQ Redwood Administration supports existing functionality and provides additional usability, such as: Improved navigation for quick access to frequently used admin tasks. Comprehensive and consolidated view of all relevant information. Simplified and modernized design to enhance user satisfaction and reduce training time. Your feedback plays a key role in shaping the future of Oracle CPQ. Go to Share Your Feedback: NextGen CPQ Redwood Administration Experience to share your insights on the new Redwood Administration UX experience.
JET 19.0.1	Oracle CPQ 26B supports JET 19.0.1. 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 26B supports jQuery 3.7.1. Customers with an older version of jQuery and with JavaScript customizations will need to thoroughly test the customizations.
Near Real Time Synchronization for Oracle Sales to Oracle CPQ	We previously announced, the deprecation of Near Real Time Synchronization for products and product structures from Oracles Sales to Oracle CPQ occurs in Oracle CPQ 26B. If you are currently using Near Real Time Synchronization, you must transition to Batch Synchronization.
Redwood Quote User List	Redwood Quotes List shows actions if they are set to Active in Commerce Process Action access rights. Customers migrating to or currently using Redwood Quote User Interface (UI) may find users allowed access to Process Actions in JET UI are not allowed access in Redwood Quote UI. This occurs when the Process Action’s Profile View for users contains a blank value which is treated as Inactive To update Process Action visibility for Redwood Quote UI, an administrator must navigate to the Process Action Details (Admin Home > Processes > Standard Quote Process >Manage Process Actions >Process Actions > Process View) and update the Profile Status to Active.
Sender Policy Framework (SPF) for Customer Domains on Oracle CPQ	We strongly encourage all CPQ customers to implement Sender Policy Framework (SPF) for sending outbound email using your company’s domain from Oracle CPQ. If you have not already implemented SPF, we recommend administrators plan the transition. SPF aids in distinguishing between an email that truthfully claims to be from a particular sender and an email that is forged or otherwise falsified. Proper use of email authentication provides an increased level of security for both sender and recipient. Sender Policy Framework (SPF) and Domain Key Identified Mail (DKIM) are two common forms of authentication. With this addition to your Domain Name System (DNS) entries, you're telling recipients that you've authorized CPQ to send emails on your behalf. Refer to Requirements for Sending Outbound Mail from Customer Domains on CPQ (KM4918) for implementation instructions. IMPORTANT: When implementing SPF do not remove the current bigmachines.com domain from your SPF record. You need to simply add oraclecloud.com to ensure seamless continuity as Oracle includes additional cloud email resources to your service.
Users REST API	In Oracle CPQ 25A, we introduced new Users web service REST API calls that no longer mandate a company be specified for the endpoint. This new endpoint simplifies the management of users on the site by providing a single static endpoint which can be used to update users across all companies. For example: Users REST API: /rest/v19/users Company Users REST API: /rest/v19/companies/{companyName}/users We have continued supporting the Company Users REST API. However, we request that if you are using calls to the legacy Company Users REST API endpoints, you replace them with the new Users REST API endpoints. The legacy Company Users REST API endpoints are planned for deprecation soon. Refer to User Management REST APIs for a complete list of Users and Company Users REST API endpoints.
Oracle CPQ URL Path	All new Oracle CPQ sites running in Oracle Fusion require the following Uniform Resources Locator (URL) path for all CPQ pages, endpoints, and file paths. The new standard URL path will include /cpq/. Refer to the following example: New URL Format: `/cpq/rest/v19/parts` Old URL Format: `/rest/v19/parts` The URL path change does not impact existing sites not running in Oracle Fusion. However, we recommend all administrators apply this new format to all new URLs and suggest you consider transitioning from your existing URL path to the new URL path.
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.
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.
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: Go to the Firefox browser Settings page. 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.
User Information	Oracle CPQ recommends administrators review user records for complete information, such as first and last name, email address, and phone number. Complete user information is needed for a smooth transition in the future to multi-factor authentication.

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
Oracle CPQ Connector for Salesforce versions 7.x and older 8.x Managed Package		Customer on Notice	For customers using the Oracle CPQ Connector for Salesforce Managed Package version 7.x or older 8.x implementations, we encourage you to update to the latest Managed Package version available. While deprecated (7.x and prior) and unsupported versions have continued to function, they have been officially out of support since Oracle CPQ Update 22D. Managed Package older versions will not continue to work indefinitely. At a future date, they will no longer connect with Oracle CPQ. We recommend you upgrade to the latest dot release of Managed Package version 8. Refer to Integrate CPQ Cloud with Salesforce for the latest Managed Package download and documentation.

Oracle CPQ Feature

Deprecation Announced

End of Life and Removal

Description

Oracle CPQ Connector for Salesforce versions 7.x and older 8.x Managed Package

Customer on Notice

For customers using the Oracle CPQ Connector for Salesforce Managed Package version 7.x or older 8.x implementations, we encourage you to update to the latest Managed Package version available.

While deprecated (7.x and prior) and unsupported versions have continued to function, they have been officially out of support since Oracle CPQ Update 22D.

Managed Package older versions will not continue to work indefinitely. At a future date, they will no longer connect with Oracle CPQ. We recommend you upgrade to the latest dot release of Managed Package version 8. Refer to Integrate CPQ Cloud with Salesforce for the latest Managed Package download and documentation.

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 26B supports JET v19.0.1. Please note the following:

List View (<oj-list-view>) - Putting focus on table elements will enable actionable mode.
Button (<oj-button>) Updated dark mode outlined button border colors to match the Redwood UX specification, making dark mode outlined borders slightly more pronounced.
ojtree - The deprecated ojtree jQuery code has been removed.
Menu (<oj-menu>) Due to issues related to default browser context menu, href attribute is removed from menu items.
Status Meter Guage (<oj-status-meter-guage>) - The default value of 'auto' for metric-label.rendered no longer renders metric-label in oj-status-meter-gauge with orientation="circular".
Input Time (<oj-input-time>)
- The default value of time-picker.show-on has been changed from 'focus' to 'image' to better match the Redwood UX specification.
- The default value of autocomplete has been changed from 'on' to 'off' to better match the Redwood UX specification.
Rating Guage (<oj-rating-guage>) and Status Meter Guage (<oj-status-meter-guage>) - Removed support for displaying "No Data to Display" in gauges; the gauge now renders blank when no data is available. Applications are recommended to set the value to 0 if a visual indicator is needed.

Notes:

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 25C to 26A supported JET v17.1.0. Refer to Oracle CPQ Administration Online Help > Pre-Upgrade Considerations for Oracle CPQ 26A or earlier for notes and considerations regarding JET v17.1.0.

Oracle CPQ 26B upgraded jQuery to 3.7.1. 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 26B General Availability Weekly Bundle 0327
“Minor update” = Update 26B Weekly Bundle

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 26B, refer to the Oracle CPQ 26B 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 26B. 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.

POST-UPGRADE CONSIDERATIONS

Upgrade and test all test instances on Oracle CPQ 26B 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 26B 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 26B 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	April 3 and 4	May 8 and 9	May 22 and 23
B	April 3 and 4 May 8 and 9	June 5 and 6	June 19 and 20
C	May 8 and 9 June 5 and 6	July 3 and 4	July 17 and 18

Cohort

Early Test Updates

Pre-Production Updates

Production Updates

April 3 and 4

May 8 and 9

May 22 and 23

April 3 and 4

May 8 and 9

June 5 and 6

June 19 and 20

May 8 and 9

June 5 and 6

July 3 and 4

July 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 145.x
Mozilla Firefox 145.x
Microsoft Edge 145.x

Mobile Devices

Apple iPad iOS 26.x, Safari browser
Apple iPhone iOS 26.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 26B. 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 26B.

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.