Pre-Upgrade Considerations

Overview

Considerations are listed by release. For more information about upgrading, see the Release Documentation.

Update 25B

Oracle CPQ Feature	Description
Administrator Access Permissions	In Oracle CPQ 25A we announced the deprecation of the legacy Access Permissions feature for Oracle CPQ. Access Permissions, sometimes referred to as Admin Segmentation, have been replaced by Administrator Groups. Enabling Administrator Groups has been an opt-in feature. If you have not enabled Administrator Groups, we recommend administrators plan to transition to Administrator Groups before the end of life and removal of the legacy Administrator Access Permission in Oracle CPQ 25C. In Oracle CPQ 25B to prevent customers from deploying a soon-to-be deprecated feature, we have disabled set up of Administrator Access Permissions for the following: New customer sites Existing customer sites with Administrator Groups enabled Existing customer sites that have not enabled either Administrator Access Permission or Administrator Groups Warning: Existing customers who are not using Administrator Access Permission will have Administrator Groups forced ON. When Admin Groups are turned on, all Full Access users will lose access to administration unless they are Application Administrators. If a Full Access users cannot access Administration following upgrade, an Application Administrator will need to explicitly grant them access via Admin Groups.
Legacy Quoting Rich Text Editor	As part of our ongoing efforts to enhance our product, beginning in Oracle CPQ 25B 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	Oracle CPQ 25B 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 account will replace the SuperUser. Refer to Partner Organization User Administration Permission for more information.
Partner Company Layout Enhancements	Oracle CPQ 25B made subtle layout improvements to the Partner Companies page, 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
User Management Layout Enhancements	Oracle CPQ 25B 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
SOAP Groups API with Web Services	Beginning in Oracle CPQ 25B 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.
Application Administrator Permission	Oracle CPQ 25A and later introduced the Application Administrator permission that can be granted to host company FullAccess users. You should review the Application Administrator Permission information and plan your transition prior to upgrading your site.
Content Security Policy (CSP)	The Oracle CPQ 25A and later CSP policy intentionally blocks framing as a security measure. Customers can log a Service Request (SR) to discuss the CSP policy and determine if special circumstances for allowing framing is required. Care must be taken when framing is referenced due to the risk of compromising the Oracle CPQ site.
Content Security Policy (CSP) Imports	The Oracle CPQ 25A and later CSP policy intentionally blocks loading all external resources (i.e. images, fonts, scripts, style, etc.) as a security measure. All custom scripts and style resources must be stored in the CPQ File Manager. Customers can log a Service Request (SR) to discuss the CSP policy and determine if special circumstances for allowing external resource access to images and fonts is required. Care must be taken when any external site is referenced due to the risk of that site being compromised and in turn compromising the Oracle CPQ site.
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.

Update 25A

Oracle CPQ Feature	Description
Application Administrator Permission	Oracle CPQ 25A introduces a new Application Administrator permission that can be granted to host company FullAccess users. You should review the Application Administrator Permission information and plan your transition prior to upgrading your site. Refer to Application Administrator Permission.
Content Security Policy (CSP)	The Oracle CPQ CSP policy intentionally blocks loading all external resources (i.e. images, fonts, scripts, style, etc.) as a security measure. All custom scripts and style resources must be stored in the CPQ File Manager. Customers can log a Service Request (SR) to discuss the CSP policy and determine if special circumstances for allowing external resource access to images and fonts is required. Care must be taken when any external site is referenced due to the risk of that site being compromised and in turn compromising the Oracle CPQ site.
Legacy Quoting Rich Text Editor	As part of our ongoing efforts to enhance our product, we are replacing 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, effective in Oracle CPQ 25B. 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.
Pricing	Oracle CPQ 24D and later released version 17 of Calculate Price REST API which has important differences from version 16. The Calculate Price version 17 REST API simplifies the request and response payloads and streamlines the support for multiple charges. You should review the difference carefully before uptaking version 17. Refer to Calculate Price REST API for more information.
XML Integration (Real-Time Integration)	Beginning in Oracle CPQ 24D and later, Real-Time Integration has been renamed XML Integration. The Integration Settings link within the Integration Platform section of the Administration Home page has also been renamed XML Integration.
XML Integration	In Oracle CPQ 24D and later, XML Integration (formerly known as Real-Time Integration) tasks had always processed serially, even if they could be processed in parallel. Oracle CPQ has changed this behavior to enhance XML Integration processing.

Update 24D

Oracle CPQ Feature	Description
Pricing	Oracle CPQ 24D releases version 17 of Calculate Price REST API which has important differences from version 16. The Calculate Price version 17 REST API simplifies the request and response payloads and streamlines the support for multiple charges. You should review the difference carefully before uptaking version 17. Refer to Calculate Price REST API for more information.
XML Integration (Real-Time Integration)	Beginning in Oracle CPQ 24D, Real-Time Integration has been renamed XML Integration. The Integration Settings link within the Integration Platform section of the Administration Home page has also been renamed XML Integration.
XML Integration	XML Integration (formerly known as Real-Time Integration) tasks had always processed serially, even if they could be processed in parallel. Oracle CPQ has changed this behavior to enhance XML Integration processing.
WebMethods Connection Method	As previously announced, the deprecation of the WebMethods Connection Method for XML Integration (formerly known as Real-Time Integration) occurs in Oracle CPQ 24D. If you are currently using WebMethods Connection, you must transition to the HTTP Post Connect Method. Refer to Deprecation Announcements for more information.
Performance Logging	The following performance logging enhancements are included in Oracle CPQ Update 24C and later: The Session ID and IP Address is anonymized in the Bulk Download and REST API response. When application event logging or response logging is enabled, the Request ID is included in the response header.
Pricing	In Oracle CPQ 24C and later, collaborative quoting when a header type Pricing attribute value is modified the Pricing Engine is triggered for pricing update.

Update 24C

Oracle CPQ Feature	Description
Performance Logging	The following performance logging enhancements are included in Oracle CPQ Update 24C: The Session ID and IP Address is anonymized in the Bulk Download and REST API response. When application event logging or response logging is enabled, the Request ID is included in the response header.
Pricing	In Oracle CPQ 24C collaborative quoting when a header type Pricing attribute value is modified the Pricing Engine is triggered for pricing update.
BML	As part of Oracle CPQ 24B and later, the html() BML function is supported to provide a method for HTML escaping (output encoding) of a string as safe plain text. This applies for content that originated from user input which could be vulnerable to injection attacks such as cross-site scripting (XSS). Refer to BML String Functions for more information.
Commerce Attributes	In Oracle CPQ 24B and later, you cannot delete Commerce attributes that are referenced to any Commerce layout.
Integration	As part of Oracle CPQ 24B and later security software updates, web-based browsers may block redirects from the Oracle CPQ server to external sites. The web browser changes will impact Oracle CPQ integrations with non-Oracle software (i.e. Salesforce). Administrators can log a Service Request (SR) on My Oracle Support to add trusted domains to their allowed partner list to ensure integration connectivity.
Native Lightning UI for Salesforce Connector	As previously announced, the Salesforce Native Lightning UI, also known as the "Lightning Mode", has reached end of life and is no longer supported in the Salesforce managed package. Refer to Deprecation Announcements for more information.
Salesforce Integration – Enable CRM OAuth	When one or more Salesforce Connections are enabled in the Integration Center and the Enable CRM OAuth is set to No, users cannot be paired to a Salesforce connection. Oracle CPQ displays an error message. To resolve this issue, go to the Oracle CPQ General Site Options page and set the Enable CRM OAuth to Yes.
Salesforce Integration – PKCE Enabled	In Salesforce Winter24 the Require Proof Key for Code Exchange (PKCE) was introduced and enabled by default for all NEW connected apps. Oracle CPQ does not support PKCE and displays an error when PKCE is enabled while setting up new connection. To resolve this issue, go to the Connect App Setting > API (Enable OAuth Settings), uncheck the Require Proof Key for Code Exchange (PKCE) Extension for Supported Authorization Flows setting, and click Save.

Update 24B

Oracle CPQ Feature	Description
BML	As part of Oracle CPQ 24B, the html() BML function is supported to provide a method for HTML escaping (output encoding) of a string as safe plain text. This applies for content that originated from user input which could be vulnerable to injection attacks such as cross-site scripting (XSS). Refer to BML String Functions for more information.
Commerce Attributes	You cannot delete Commerce attributes that are referenced to any Commerce layout.
Integration	As part of security software updates, web-based browsers may block redirects from the Oracle CPQ server to external sites. The web browser changes will impact Oracle CPQ integrations with non-Oracle software (i.e. Salesforce). Administrators can log a Service Request (SR) on My Oracle Support to add trusted domains to their allowed partner list to ensure integration connectivity.
Pricing Rate Cards	As part of Oracle CPQ 24B, Rate Card Templates are administered as a template option of Pricing Matrix Templates within the Pricing Portal. Rate Cards are no longer supported in migration but continue to be supported in bulk service. This is consistent with Oracle CPQ's direction to use migration for moving schema-type data and use bulk service for moving data. As a result, if your site contains Rate Cards and is on Oracle CPQ 24A or earlier, its pricing migration package cannot be imported into a Oracle CPQ 24B site via cross-version migration.
Native Lightning UI for Salesforce Connector	As previously announced, the Salesforce Native Lightning UI, also known as the "Lightning Mode", has reached end of life and is no longer supported in the Salesforce managed package. Refer to Deprecation Announcements for more information.
Salesforce Integration – PKCE Enabled	In Salesforce Winter24 the Require Proof Key for Code Exchange (PKCE) was introduced and enabled by default for all NEW connected apps. Oracle CPQ does not support PKCE and displays an error when PKCE is enabled while setting up new connection. To resolve this issue, go to the Connect App Setting > API (Enable OAuth Settings), uncheck the Require Proof Key for Code Exchange (PKCE) Extension for Supported Authorization Flows setting, and click Save.
Supported Fonts	The following fonts are not supported in the Document Designer and Email Designer in Oracle CPQ 24A and later: Albany WT J Albany WT TC Andale Duospace WT J Beginning in Oracle CPQ 24A and later, the following fonts are supported: Google Noto Jp Google Noto Kr Google Noto Sans Mono Jp Google Noto Sc Google Noto Tc Refer to Supported Fonts for more information.

Update 24A

Oracle CPQ Feature	Description
Pricing - Automatically Add Missing Standard Charge Attributes	Oracle CPQ 23C introduced new standard charge attributes in Pricing Portal, whose names should be unique within the combined domain of charge attributes and pricing attributes. If there was an existing custom pricing attribute that already used the same variable name, the new, standard charge attribute was not created as part of the upgrade. When upgrading to Oracle CPQ 24A the missing standard charge attributes are automatically added and the naming conflict is resolved as described below. Reserved standard charge attribute variable names include: `priceType`, `pricePeriod`, `unitPrice`, `netPrice`, `discountType`, and `calculationInfo`. In order to simplify your upgrade process, the Oracle CPQ 24A upgrade first examines if there are any conflicting pricing attributes that are either not used in Pricing Portal or are used only in simple conditions in Pricing Portal. Second, these attributes are automatically renamed. For example, a pricing attribute named "`netPrice`" exists in the Pricing Portal, it will now be renamed "`netPrice_c`". If the pricing attribute is used in simple conditions in Pricing Portal, its reference in the simple conditions will also be automatically rewired to the new variable name. Third, after automatically resolving the naming conflict, the standard charge attributes are generated. In the case where a conflicting pricing attribute is used in BML in Pricing Portal, the upgrade will skip the renaming of the existing pricing attribute with a warning. After upgrade, the customer should adopt a different pricing attribute variable name and submit a service request on My Oracle Support to restore the missing charge attribute .
Salesforce Integration – Enable CRM OAuth	When one or more Salesforce Connections are enabled in the Integration Center and the Enable CRM OAuth is set to No, users cannot be paired to a Salesforce connection. Oracle CPQ displays an error message. To resolve this issue, go to the Oracle CPQ General Site Options page and set the Enable CRM OAuth to Yes.
Salesforce Integration – PKCE Enabled	In Salesforce Winter24 the Require Proof Key for Code Exchange (PKCE) was introduced and enabled by default for all NEW connected apps. Oracle CPQ does not support PKCE and displays an error when PKCE is enabled while setting up new connection. To resolve this issue, go to the Connect App Setting > API (Enable OAuth Settings), uncheck the Require Proof Key for Code Exchange (PKCE) Extension for Supported Authorization Flows setting, and click Save.
Supported Fonts	Beginning in Oracle CPQ 24A, the following fonts are not supported in the Document Designer and Email Designer: Albany WT J Albany WT TC Andale Duospace WT J Beginning in Oracle CPQ 24A, the following fonts are supported: Google Noto Jp Google Noto Kr Google Noto Sans Mono Jp Google Noto Sc Google Noto Tc Refer to Supported Fonts for more information.
Legacy Global Functions	As previously announced the Legacy Global Functions, also known as Jython scripts, has officially reached end of life and is no longer supported in Oracle CPQ 24A. Refer to Deprecation Announcements for more information..
GXT Customer Images and CSS References	As previously announced GXT Customer Images and CSS References has officially reached end of life and is no longer supported in Oracle CPQ 24A. Refer to Deprecation Announcements for more information.

Update 23D

Oracle CPQ Feature	Description
Pricing Bulk Service	With the introduction of the new Price Model Item object, the signature for bulk services on prices has changed. Bulk download files created on earlier releases can no longer be uploaded without revision. We advise generating a new bulk download of pricing data after upgrading to 23D to use as the basis for performing updates.
Price Charges-related Attributes	When using pricing charges, the standard Charge Key Attributes (Price Type, Price Period, and Charge Type) now require a non-null value. If null values exist prior to upgrade, the values will be populated with the default value on upgrade, with the Price Period populated only for recurring and usage charges. A Usage UOM value is now required for charges with a Price Type of 'Usage'. If none is specified, when you modify the charge's pricing the default Usage UOM will be applied .
Pricing REST APIs	Several REST APIs for Price Model Pricing Data have been replaced with Price Model Item APIs to support the new Price Model Item object. Refer to Pricing Administration REST APIs.
Fusion Order Management Integration	Beginning in Oracle CPQ 23C, Oracle Fusion Order Management application requires that each Charge for an item have a unique combination of Price Type and Charge Type. If you are integrating Oracle CPQ with Fusion Order Management, you will need to define a different Charge Type to distinguish Charges with the same Price Type but different Price Periods.
Site License Metric	Oracle CPQ 23C has modified the user license counting to exclude Web Services Only users in the count. In addition, once the maximum number of licenses is allocated, Web Services Only users can still be added to the site.

Update 23C

Oracle CPQ Feature	Description
Fusion Order Management Integration	Oracle Fusion Order Management application requires that each Charge for an item have a unique combination of Price Type and Charge Type. If you are integrating Oracle CPQ with Fusion Order Management, you will need to define a different Charge Type to distinguish Charges with the same Price Type but different Price Periods.
Site License Metric	Oracle CPQ 23C has modified the user license counting to exclude Web Services Only users in the count. In addition, once the maximum number of licenses is allocated, Web Services Only users can still be added to the site.
Pricing	Beginning in Oracle CPQ 23B, pricing settings are no longer set via General Site Options or Commerce Settings. Pricing settings are now consolidated in the Pricing Portal Pricing Options. Navigation links are provided from the prior settings locations to direct administrators to the Pricing Options page.

Update 23B

Oracle CPQ Feature	Description
JET 12.1.0 Support	Oracle CPQ 23A supports JET v12.1.0. Refer to Custom JavaScript and CSS for details.
Pricing	Beginning in Oracle CPQ 23B, pricing settings are no longer set via General Site Options or Commerce Settings. Pricing settings are now consolidated in the Pricing Portal Pricing Options. Navigation links are provided from the prior settings locations to direct administrators to the Pricing Options page.

Update 23A

Oracle CPQ Feature	Description
JET 12.1.0 Support	Oracle CPQ 23A supports JET v12.1.0. Refer to Custom JavaScript and CSS for details.
Oracle CPQ REST API	The following REST APIs will respond with 404 instead of 500 when an invalid number is used as the key of the resource: assets performanceLogs parts eligibilityRule configBomInstance commerceDocuments prefix - Commerce Process based end-points custom prefix - Data table endpoints JET Transaction UI will have a change in behavior when the current user doesn’t have access. For example, when a user doesn’t have access to a quote (a participant profile is not given access to a Document in Commerce Steps Admin), the user will be navigated to Access Denied page.

Update 22D

Oracle CPQ Feature	Description
Oracle CPQ REST API	The following REST APIs will respond with 404 instead of 500 when an invalid number is used as the key of the resource: assets performanceLogs parts eligibilityRule configBomInstance commerceDocuments prefix - Commerce Process based end-points custom prefix - Data table endpoints JET Transaction UI will have a change in behavior when the current user doesn’t have access. For example, when a user doesn’t have access to a quote (a participant profile is not given access to a Document in Commerce Steps Admin), the user will be navigated to Access Denied page.
Supported Fonts	In Oracle CPQ Update 22C, we changed the supported fonts available for use with Oracle CPQ. Customers need to review their existing document template font selections and determine the best course of action for their implementations. This change impacts several areas of Oracle CPQ including Document Designer, Email Designer, Document Engine, and Rich Text Editor (RTE). In effort to minimize the impact of the font changes, Oracle CPQ has determined substitute fonts which closely resemble the now unsupported font selections. The Supported Fonts topic provides the complete list of supported fonts and the options available to you to address this change. The following resources are available regarding the supported fonts: Refer to the Supported Fonts topic. Refer to the CPQ Supported Fonts (Doc ID 2875457) on My Oracle Support. Log a Service Request (SR) on My Oracle Support.
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 22C and later supports jQuery 3.6.0. Customers with an older version of jQuery and JavaScript customizations will need to thoroughly test the customizations.
Parts	Undeployed part custom field changes will be deployed when a site is upgraded to Oracle CPQ 22D.

Update 22C

Oracle CPQ Feature	Description
Supported Fonts	Beginning in Oracle CPQ Update 22C, we are changing the supported fonts available for use with Oracle CPQ. Customers may want to review their existing document template font selections and determine the best course of action for their implementations. This change impacts several areas of Oracle CPQ including Document Designer, Email Designer, Document Engine, and Rich Text Editor (RTE). In effort to minimize the impact of the font changes, Oracle CPQ has determined substitute fonts which closely resemble the now unsupported font selections. The Supported Fonts topic provides the complete list of supported fonts and the options available to you this change. The following resources are available regarding the supported fonts: Refer to the Supported Fonts topic. Refer to the CPQ Supported Fonts (Doc ID 2875457) on My Oracle Support. Log a Service Request (SR) on My Oracle Support.
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 22C supports jQuery 3.6.0. Customers with an older version of jQuery and JavaScript customizations will need to thoroughly test the customizations.
Oracle CPQ Shopping Cart for Legacy UI	The Oracle CPQ shopping cart feature has been deprecated from Legacy Configuration UI. Beginning in Oracle CPQ 22B, we released the new for the Shopping Cart for the JET Configuration UI. If your implementation uses a shopping cart with Legacy Configuration UI, we recommend you to transition to the JET Configuration UI. Upon upgrade to Oracle CPQ 22B or later, customers will no longer have access to the shopping cart feature in their Legacy Configuration UI. If you have implemented a shopping cart with JET Configuration UI, upon upgrade to Oracle CPQ 22B or later (safe harbor), your implementation will be automatically upgraded to use the new shopping cart alternative.
Parts	Undeployed part custom field changes will be deployed when a site is upgraded to Oracle CPQ 22C.

Update 22B

Oracle CPQ Feature	Description
Oracle CPQ Shopping Cart	The Oracle CPQ shopping cart feature is being deprecated from Legacy Configuration UI. Beginning in Oracle CPQ 22B, we have released the new for the Shopping Cart for the JET Configuration UI. If your implementation uses a shopping cart with Legacy Configuration UI, we recommend you to transition to the JET Configuration UI. Upon upgrade to Oracle CPQ 22B, customers will no longer have access to the shopping cart feature in their Legacy Configuration UI. If you have implemented a shopping cart with JET Configuration UI, upon upgrade to Oracle CPQ 22B (safe harbor), your implementation will be automatically upgraded to use the new shopping cart alternative.
BOM Mapping	In Oracle CPQ 22A and earlier when a BOM mapping rule with a condition setting on the rule enters Configuration, the BOM data tables are loaded into cache and the BOM mapping logics are executed even if the rule condition is false. Beginning in Oracle CPQ 22B, the BOM information is only loaded into cache if the rule condition is true.
JET 10 Support in Oracle CPQ and IE 11	Oracle CPQ 22A introduces support for Oracle JET 10. Oracle JET 10 is not certified using Internet Explorer 11 or earlier. Therefore, Oracle CPQ 22A new features may not function properly using the JET User Interface with IE 11. Previous features are expected to continue to function, however Oracle CPQ will not address new issues that arise. If you are using IE 11, you need to complete your own certification testing prior to Oracle CPQ 22A upgrade. For your reference, the following list of known issues exist related to Oracle CPQ JET 10 UI and IE11: Creating a new quote from an existing Model Configuration with a Pricing Rule results in a page loading icon and error messages in the bm.log file. A new quote is not able to be created. After loading a Model Configuration in JET 10 UI, users cannot save a SSPL text attribute value entered from the Arrays tab. After loading a Model Configuration for update in JET 10 UI, Single Select Pick List text attribute fields are disabled. We strongly encourage customers to upgrade to a certified and supported browser version.
Parts	Undeployed part custom field changes will be deployed when a site is upgraded to Oracle CPQ 22B.
ExtJS Library Helper	ExtJS is a JavaScript library for building web application pages. Oracle CPQ used this framework for its internal implementation and did not expose this library for customer use. As of Oracle CPQ 22A, we eliminated this library from our product. If you are using JavaScript for your CPQ implementation and have made any custom references to ExtJS Library functions, you must remove those references from your script. Please follow the below steps to verify the custom usage of EXTJS Library in your CPQ implementation. Step 1 To verify if you are referencing ExtJS Library in your Home XSL Template, follow the instructions below: Click Admin to go to the Admin Home Page. Click Home Page in the Style and Templates section. To see the Admin XSL Template page, click Define XSL Template. If you have defined a custom XSL Template for Production and Internal Test, perform the document search with “Ext.” to find the ExtJS references. If you find any references for "Ext." outside the below XSL tag, this indicates the customer usage of the ExtJS library. <xsl:variable name=“gSkinJsCode”> ... </xsl:variable> Step 2 Click Admin to go to the Admin Home Page. Click Home Page in the Style and Templates section. To see the Admin XSL Template page, click Define XSL Template. If you have defined a custom JavaScript File, perform the document search with “Ext.” to find the ExtJS references. If you find any references for “Ext.” in your JavaScript file, this indicates the custom usage of the ExtJS library. Step 3 Click Admin to go to the Admin Home Page. Click Header & Footer in the Style and Templates section. If you have defined a custom JavaScript here, perform the document search with “Ext.” to find the ExtJS references. If you find any references for “Ext.” in your JavaScript file, this indicates the custom usage of the ExtJS library. Step 4 If you have defined and referenced custom JavaScript from the File Manager, perform the document search with "Ext." to find the ExtJS references.

Update 22A

Oracle CPQ Feature	Description
JET 10 Support in Oracle CPQ and IE 11	Oracle CPQ 22A introduces support for Oracle JET 10. Oracle JET 10 is not certified using Internet Explorer 11 or earlier. Therefore, Oracle CPQ 22A new features may not function properly using the JET User Interface with IE 11. Previous features are expected to continue to function, however Oracle CPQ will not address new issues that arise. If you are using IE 11, you need to complete your own certification testing prior to Oracle CPQ 22A upgrade. For your reference, the following list of known issues exist related to Oracle CPQ JET 10 UI and IE11: Creating a new quote from an existing Model Configuration with a Pricing Rule results in a page loading icon and error messages in the bm.log file. A new quote is not able to be created. After loading a Model Configuration in JET 10 UI, users cannot save a SSPL text attribute value entered from the Arrays tab. After loading a Model Configuration for update in JET 10 UI, Single Select Pick List text attribute fields are disabled. We strongly encourage customers to upgrade to a certified and supported browser version.
Part	Undeployed part custom field changes will be deployed when a site is upgraded to Oracle CPQ 22A.
ExtJS Library Helper	ExtJS is a JavaScript library for building web application pages. Oracle CPQ used this framework for its internal implementation and did not expose this library for customer use. As of Oracle CPQ 22A, we are eliminating this library from our product. If you are using JavaScript for your CPQ implementation and have made any custom references to ExtJS Library functions, you must remove those references from your script. Please follow the below steps to verify the custom usage of EXTJS Library in your CPQ implementation. Step 1 To verify if you are referencing ExtJS Library in your Home XSL Template, follow the instructions below: Click Admin to go to the Admin Home Page. Click Home Page in the Style and Templates section. To see the Admin XSL Template page, click Define XSL Template. If you have defined a custom XSL Template for Production and Internal Test, perform the document search with “Ext.” to find the ExtJS references. If you find any references for "Ext." outside the below XSL tag, this indicates the customer usage of the ExtJS library. <xsl:variable name=“gSkinJsCode”> ... </xsl:variable> Step 2 Click Admin to go to the Admin Home Page. Click Home Page in the Style and Templates section. To see the Admin XSL Template page, click Define XSL Template. If you have defined a custom JavaScript File, perform the document search with “Ext.” to find the ExtJS references. If you find any references for “Ext.” in your JavaScript file, this indicates the custom usage of the ExtJS library. Step 3 Click Admin to go to the Admin Home Page. Click Header & Footer in the Style and Templates section. If you have defined a custom JavaScript here, perform the document search with “Ext.” to find the ExtJS references. If you find any references for “Ext.” in your JavaScript file, this indicates the custom usage of the ExtJS library. Step 4 If you have defined and referenced custom JavaScript from the File Manager, perform the document search with "Ext." to find the ExtJS references.
Configuration Page Templates	This administrative feature was not widely implemented. If you are among the customers that currently have configuration page templates in your environment you need to migrate to standard configuration flows. In Oracle CPQ 21D and later, customers are no longer be able to create and edit the configuration page templates. To learn more about Configuration Flows, refer to Configuration Flows.
Document Engine	Document Engine, which is used to created proposals and submissions, is being deprecated. Customers need to recreate their existing DocEngine Templates with the Document Designer. Upon upgrade to Oracle CPQ 21D or later, customers no longer have access to Document Engine administration for the editing of templates. However, customers retain edit access to the raw XSL templates that Document Engine produced. Print actions using templates created with the Document Engine continue to function for end users. To learn more about Document Designer, refer to Document Designer Overview.

Update 21D

Oracle CPQ Feature	Description
Configuration Actions	Configuration Process Invocation REST service calls establish the sequence of Configuration Actions to be presented in the order they are within the Oracle CPQ database. Administrators need to be aware of this and check the UI to ensure the order of the actions are as desired.
Single Sign-On Guest User Language and Currency Preferences	For Single Sign-On guest users, user preferences, such as language and currency, are not able to be updated. Only registered users are able to update user preferences.
Configuration Page Templates	This administrative feature was not widely implemented. If you are among the customers that currently have configuration page templates in your environment you need to migrate to standard configuration flows. Beginning in Oracle CPQ 21D, customers are no longer be able to create and edit the configuration page templates. To learn more about Configuration Flows, refer to Configuration Flows.
Document Engine	Document Engine, which is used to created proposals and submissions, is being deprecated. Customers need to recreate their existing DocEngine Templates with the Document Designer. Upon upgrade to Oracle CPQ 21D, customers will no longer have access to Document Engine administration for the editing of templates. They will, however, retain edit access to the raw XSL templates that Document Engine produced. Print actions using templates created with the Document Engine will continue to function for end users. To learn more about Document Designer, refer to Document Designer Overview.

Known Functionality

The following items describe functionality that you should be aware of before you upgrade.

Configurator Web Service Support to BOM Mapping

This release introduces the optional bomprice element to the Configuration web service (v1 and v2). The response includes the BOM price, if BOM mapping is enabled and contains a non-zero BOM price.

Note: BOM Mapping is available on all 2016 R1 sites, refer to the BOM Mapping section for additional information.

Sample Response:

<bm:price>
   <bm:bomPrice>$16.0000</bm:bomPrice>
   <bm:totalPrice>$45.0000</bm:totalPrice>
</bm:price>

The web service WSDL, when regenerated, includes the newly introduced "bomPrice" optional element:


<xsd:complexType name="ConfigurationPriceType">
  <xsd:sequence>
     ...
    <xsd:element maxOccurs="1" minOccurs="0" name="bomPrice" nillable="true" type="xsd:string"/>
     <xsd:element maxOccurs="1" minOccurs="1" name="totalPrice" nillable="false" type="xsd:string"/>
  </xsd:sequence>
</xsd:complexType>

Secure URL Addresses

Confirm that all references to your Oracle CPQ URL, such as in customizations or third-party tools, use https:// in the URL.

Translation

For some system defined messages and components, some strings have been removed and others have been added. 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.

Migration

When migrating from one site to another using the Migration Center, both sites must be on the same major release. Content may only be migrated across minor releases within the same major release. Migration across major releases cannot occur.

“Major release” = A major product release, such as 2015 R2
“Minor release” = A release update, such as 2015 R2 Update 1

Resolved Known Issues

For information on bugs fixed in 2016 R1, refer to the 2016 R1 Resolved Known Issues document available on My Oracle Support and Release Documentation.

2015 R2

2015 R1

Pre-Upgrade Considerations

Overview

Planned Changes to Known Behavior

Deprecation Announcements

Custom JavaScript and CSS

Migration

Resolved Known Issues

Translation

Planned Changes to Known Behavior

Deprecation Announcements

Custom JavaScript and CSS

Migration

Resolved Known Issues

Translation

Planned Changes to Known Behavior

Deprecation Announcements

Custom JavaScript and CSS

Migration

Resolved Known Issues

Translation

Planned Changes to Known Behavior

Deprecation Announcements

Custom JavaScript and CSS

Migration

Resolved Known Issues

Translation

Planned Changes to Known Behavior

Deprecation Announcements

Custom JavaScript and CSS

Migration

Resolved Known Issues

Translation

Planned Changes to Known Behavior

Deprecation Announcements

Custom JavaScript and CSS

Migration

Resolved Known Issues

Translation

Planned Changes to Known Behavior

Deprecation Announcements

Custom JavaScript and CSS

Migration

Resolved Known Issues

Translation

Planned Changes to Known Behavior

Deprecation Announcements

Custom JavaScript and CSS

Migration

Resolved Known Issues

Translation

Planned Changes to Known Behavior

Deprecation Announcements

Custom JavaScript and CSS

Migration

Resolved Known Issues

Translation

Planned Changes to Known Behavior

Deprecation Announcements

Custom JavaScript and CSS

Migration

Resolved Known Issues

Translation

Planned Changes to Known Behavior

Deprecation Announcements

Custom JavaScript and CSS

Migration

Resolved Known Issues

Translation

Planned Changes to Known Behavior

Deprecation Announcements

Custom JavaScript and CSS

Migration

Resolved Known Issues

Translation

Planned Changes to Known Behavior

Deprecation Announcements

Custom JavaScript and CSS

Transport Layer Security Support

Migration

Resolved Known Issues