Deprecation Announcements

The WebMethods Connection Method for XML Integrations, previously known as Real-Time Integration, is deprecated. If you are currently using WebMethods Connection, you must transition to HTTP Post Connect Method. The end of life and removal of this functionality is Oracle CPQ 24D.

In earlier versions of Oracle CPQ the Legacy Global Functions, also known as Jython scripts, allowed customers to write custom python scripts to use with BML for various types of processing. Due to poor performance, Oracle CPQ ended support for these scripts several years ago. If your Oracle CPQ implementation uses this functionality, we recommend administrators migrate to standard supported functionality (e.g., Util BML Libraries, Commerce BML Libraries, and BMQL).

To verify if you have Legacy Global Functions enabled in your environment, follow the steps below:

1. Navigate to the Admin Home Page.
2. Under Developer Tools section, if you see the Global Functions option available this indicates that Legacy Global Functions are enabled for your CPQ environment.

GXT is a Java framework for building web application pages. Oracle CPQ used this framework for its internal implementation and did not expose this for customer use. We are eliminating this framework from our product. If you are referencing images or CSS provided by this framework, we strongly recommend you to remove those references from your implementation. The end of life and removal of this functionality is Oracle CPQ 24A.

GXT Images/Icons References

The images used by this framework is likely found under the folder path: "/gwt/gxt/images/default/" Refer to the example below. If you are referencing any image from this folder, remove those references and use the File Manager to manage your customized images.

GXT CSS References

The CSS file used by this framework is likely found under this folder path: "/gwt/gxt/css/gxt-all.css". Refer to the example below. If you have customized the above CSS file or referencing any CSS classes from this file, remove those customizations and use Stylesheet Manager to manage your customized CSS.

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.

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:

1. Click Admin to go to the Admin Home Page.
2. Click Home Page in the Style and Templates section.
3. To see the Admin XSL Template page, click Define XSL Template.

4. If you have defined a custom XSL Template for Production and Internal Test, perform the document search with “Ext.” to find the ExtJS references.

   

5. 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

1. Click Admin to go to the Admin Home Page.
2. Click Home Page in the Style and Templates section.
3. To see the Admin XSL Template page, click Define XSL Template.
4. If you have defined a custom JavaScript File, perform the document search with “Ext.” to find the ExtJS references.
5. If you find any references for “Ext.” in your JavaScript file, this indicates the custom usage of the ExtJS library.

Step 3

1. Click Admin to go to the Admin Home Page.
2. Click Header & Footer in the Style and Templates section.
3. If you have defined a custom JavaScript here, perform the document search with “Ext.” to find the ExtJS references.
4. 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.

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 the Configuration Flows.