Update 21C

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date	Product	Feature	Notes
07 OCT 2021	Commerce	Indicator for Unconfigured Models in Line Item Grid	Updated document. Delivered feature in Updated 21C.
30 JUN 2021			Created initial document.

Overview

Oracle Configure, Price, and Quote (CPQ) enables companies to streamline the entire opportunity-to- quote-to-order process, including product selection, configuration, pricing, quoting, ordering, and approval workflows. Oracle CPQ provides a flexible, scalable, enterprise-ready solution ideal for companies of all sizes that sell products and services across direct, indirect, and e-commerce sales channels.

This guide outlines the information you need to know about new or improved functionality in Oracle CPQ 21C and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

Key Resources

Refer to Oracle CPQ Administration Online Help for detailed descriptions and instructions.

Security & New Features

If your system has modified security structures, you may need to advise your security administrator of new features you would like to implement.

Give Us Feedback

We welcome your comments and suggestions to improve the content. Please send us your feedback at cpqcloud_documentation_us_grp@oracle.com.

Feature Summary

CPQ-Pre 21D

Commerce

The following Commerce features are available in Oracle CPQ 21C.

Concurrent Commerce Rule Processing Enhancement

Oracle CPQ 21C enables the internal parallel processing of Commerce rules to improve end user response time.

Concurrent rule processing enhancements improve performance in Commerce transactions for end users.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

If you want to disable parallel processing of Commerce rules, submit a Service Request (SR) on My Oracle Support.

Formula Management Enhancements

Oracle CPQ 21C exposes system variables and version attributes for use in formula inputs. Administrators can now select system variables and version attributes from the Attributes panel in the Formula Management UI.

This feature improves the administrator experience by removing the need to write BML to use system variables and version attributes in Commerce.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

System variables and version attributes are not available in output Attribute Name columns. User cannot set values to these variables.

Indicator for Unconfigured Models in Line Item Grid

As part of integrations, models can be added to a transaction that may require further configuration changes via reconfiguration to complete the configuration and get the transaction pricing and etc, these models are called unconfigured models. The Unconfigured Model indicator visually communicates to the user model line items that are not configured.

The Unconfigured Model indicator is displayed in the same LIG column that displays the Lock icon. 

NOTE: When an unconfigured model is also locked, the Locked icon will take priority.

For example, in the following image shows a Line Item Grid with four unconfigured models.

Beginning in Oracle CPQ 21C, the Transaction UI Line Item Grid displays an indicator for all the unconfigured models added to the transaction.

Steps to Enable

You don't need to do anything to enable this feature.

New System Revenue Items for Commerce Main and Sub-documents

Oracle CPQ 21C introduces the Revenue Category system attribute for Commerce main documents and the platform-level Revenue Attributes set for Commerce sub-documents.

The main document Revenue Category attribute identifies the category of revenue for this sales transaction (e.g. renewal versus new business) and is created using the new Revenue Category attribute type. When an administrator adds a new Revenue Category type attribute, the Revenue Category (_revenueCategory_t) is generated. This attribute a Single Select Menu with 'New', 'Renew', and 'Expansion' menu options.

The sub-document Revenue Attributes set contains the following revenue attributes that store aggregate revenue values and other information used for financial analysis and forecasts.

• The Revenue Category attribute (_revenueCategory_l) identifies the category of revenue for this line (e.g. renewal versus new business). This attribute is a Single Select Menu with 'New', 'Renew', and 'Expansion' menu options.

• The Revenue ID attribute (_revenueId_l) is a Text type attribute that lists the ID of the Revenue Line Item in the associated opportunity.

This feature allows CPQ to capture Oracle Sales revenue items for CPQ quotes. This allows Oracle Sales to retain versus re-enter their information associated with revenue lines once the quote is created.

Steps to Enable

Add a Commerce Main Document Revenue Category Attribute

Complete the following steps to add a Revenue Category attribute to the Commerce main document.

1. Log in to Oracle CPQ and open the Admin Home page.

2. Click Process Definition in the Commerce and Documents section.

3. Select Documents for the applicable Commerce process, and then click List.

4. Select Attributes for the main document, and then click List.

5. Click Add.

6. Select Revenue Category from the Attribute Type drop-down menu.

7. Click Add.

The Revenue Category (_revenueCategory_t) Single Select Menu is created with 'New', 'Renew', and 'Expansion' menu options.  

Add a Commerce Sub-Document Revenue Attributes Set

Complete the following steps to add a Revenue Attribute set to the Commerce sub-document.

1. Log in to Oracle CPQ and open the Admin Home page.

2. Click Process Definition in the Commerce and Documents section.

3. Select Documents for the applicable Commerce process, and then click List.

4. Select Attributes for the sub-document, and then click List.

5. Click Add.

6. Select Revenue Category Set from the Attribute Type drop-down menu.

7. Click Add.

The Revenue Attributes set is created with Revenue Category (_revenueCategory_l) and Revenue ID (_revenueId_l) attributes.

Tips And Considerations

• Only one Revenue Category attribute can be added to a Commerce main document and only one Revenue Attributes set can be added to a Commerce sub-document.

• The Variable names for Revenue Category and Revenue ID attributes are not editable.

• Menu Items for the Revenue Category attribute are not editable.

Oracle CPQ Administration

The following Oracle CPQ Administration feature was initially released in Oracle CPQ 21B Patch 3 and is available in Oracle CPQ 21C.

Support for Pagination of User Login History

Administrators can set a pagination option for the Login History. With the Login History pagination feature, a subset of user history will be loaded on the page when the page is accessed. This decreases the initial load time of the page and allows the user to page through the login history to access the information. Administrators can set the number of user login history rows to view per page. The setting permits a range of 50 to 500 rows per page in 50 row increments. The default setting is 100 rows per page.

To view the Login History page, perform the following steps:

1. Navigate to the Options - General page.  Admin > General > General Site Options
2. Click View Login History in Options - Login.

The following example shows the Login History page with pagination links.following example shows the Login History page with pagination links.

Steps to Enable

The Login History pagination feature is automatically available on Oracle CPQ 21C sites with 100 rows per page set as the default value.

To modify the number of rows to view per page for the user login history, perform the following steps:

1. Navigate to the Options – General page.  Admin > General > General Site Options
2. Click Row Count Per Page in the Feature Settings.

3. Select the desired number of rows to display per page from the User Login History List Page drop-down.

4. Click Update.

Oracle CPQ Licensing Metrics

The following Oracle CPQ licensing metrics feature is available in Oracle 21C.

Support for Improved eCommerce Interaction Licensing

Oracle CPQ 21C supports a new “user” property in the access token that can be passed from any eCommerce application to Oracle CPQ. For a quick registration user, the "user" property and the access token created using the private key are validated against the uploaded public secure certificate to authenticate the user for CPQ access. Once authenticated, a quick registration user is seamlessly allowed access into the Oracle CPQ application and a CPQ interact license is assigned for their use during that login session.

This feature enhances the quick registration user login procedure and better defines CPQ interact license consumption for quick registration users and guest users.

Steps to Enable

You don't need to do anything to enable this feature.

Pricing Engine

The following Pricing Engine feature is available in Oracle 21C.

Simple Conditions for Pricing Profiles

Oracle CPQ 21C introduces Simple Conditions for Percent, Amount, and Absolute Price type Pricing Profiles. Simple Conditions can be easily set up without the need for coding. Administrators can simply select the necessary condition attributes, select the appropriate comparison operator, and specify the values of the attributes for which the Pricing Profile is invoked.

Add a Simple Condition to a Pricing Profile

Complete the following steps to add a Simple Condition to a Pricing Profile in the Pricing Engine.

1. Log in to Oracle CPQ and open the Admin Home page.

2. Click Pricing Engine in the Products section.

3. Select the Profiles tab.

4. Select an existing Pricing Profile or click Add Profile to create a new profile.

For more information on adding a new Pricing Profile, refer to the CPQ Administrator Online Help – Product Pricing Administration topic.

5. Select the Simple Condition option.

6. Create a simple condition:

   1. Select an Attribute Name from the drop-down list of the Pricing Attributes defined for this site.

   2. Select an Operator.

   3. Enter the desired Attribute Value.

7.  Click the "Add" icon (+) to add the condition to the Pricing Profile.

8. (Optional) Repeat Steps 6 and 7 to add additional conditions.

9. Enter Row Grouping.

10. Click Save.

Pricing Engine enhancements allow administrators to easily create Simple Conditions for Percent, Amount, and Absolute Price type pricing profiles instead of creating BML scripts in Advanced type pricing profiles.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

• Beginning in Oracle CPQ 21C, Advanced profiles can be set to "Always True".

• All new pricing profiles, including Advanced pricing profiles, will default to "Always True". Existing pricing profiles will not be changed.

• Simple Conditions are not supported in bulk uploads or bulk downloads.

Web Services

The following Web Service feature is available in Oracle CPQ 21C.

Usage Metrics REST API

Beginning in Oracle CPQ 21C, a new v12 REST API expands Web Service support to provide administrators with easier access to licensing information as follows:

• Total number of API licenses available and the number of API licenses consumed within a specified date/time range.
• Total number of eCommerce interactions available and the number of eCommerce interactions consumed within a specified date/time range.
• Total number of internal licenses purchased and the number of enabled internal licenses.
• Total number of channel licenses purchased and the number of enabled channel licenses.

Get Usage Metrics

This endpoint returns specified types or all licensing usage information.

• Endpoint:  /rest/v12/companies/usage
• Method:  GET

The REST API endpoint with the type, timestamp, and company query parameters can be used to return licensing information for a specific type of license for a specific date/time range. The following example endpoint returns information for all license types during a one month time range for ABC Company.

This REST call provides accurate and real-time licenses information to help administrators in decision making, usage tracking, and troubleshooting. Refer to the Usage Metrics REST API topic in Oracle CPQ Administration Online Help or REST API Services for Oracle CPQ in the Oracle Help Center for additional information and examples.

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Tips And Considerations

The Get Usage Metrics REST API supports MongoDB operators for the query parameter with the following restrictions:

• {"type", "timestamp", and "company"} can only be grouped together by $and
• "type" supports the $in operator only
• "company" can only be a single company name
• "timestamp" supports $gt, $gte, $lt, and $lte to specify a date/time range

IMPORTANT Actions and Considerations

PRE-UPGRADE CONSIDERATIONS

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
Configuration Page Templates	21A	21D	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 will no longer be able to create and edit the configuration page templates. To learn more about Configuration Flows, refer to the Configuration Flows topic in the Oracle CPQ Administration Online Help.
Document Engine	21A	21D	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. We recommend that you do not create new documents using Document Engine and transition to Document Designer as soon as possible. To learn more about Document Designer, refer to the Document Designer Overview topic in the Oracle CPQ Administration Online Help.
Oracle CPQ Shopping Cart	21A	22A	The Oracle CPQ shopping cart feature is being deprecated from Legacy Configuration UI. We are working on developing a similar experience 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 22A, 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 22A (safe harbor), your implementation will be automatically upgraded to use the new shopping care alternative.
ExtJS Library Helper	21C	22A	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. 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, we strongly recommend you remove those references from your script. With the Oracle CPQ 22C release, we will be removing this framework from the Oracle CPQ product. 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.
Legacy Global Functions	21C	22B	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). With Oracle CPQ 22B, we will be removing this functionality from the product. To verify if you have Legacy Global Functions enabled in your environment, follow the steps below: Navigate to the Admin Home Page. Under Developer Tools section, if you see the Global Functions option available this indicates that Legacy Global Functions are enabled for your CPQ environment.
Legacy Commerce UI	21C	22C	In Oracle CPQ 21C, we are announcing the deprecation of Legacy Commerce Transaction UI. The end of life and removal of this functionality will occur in Oracle CPQ 22C. We introduced JET Responsive UI for Commerce in Oracle CPQ 18C, and after years of evolution and production experience, our customers are experiencing the benefits of the new JET Responsive UI for both Commerce and Configuration. The majority of Oracle CPQ customers have successfully made the complete transition to the JET UI. Moving forward, we are focusing our development efforts on enhancing the JET Responsive UI to improve the overall user experience. We’re announcing these changes to give our customers early visibility and the opportunity to prepare for this update. If your Oracle CPQ implementation still uses Legacy Commerce UI, we encourage you to start preparing for the transition to the JET UI. For more information on enabling JET Commerce UI, visit the Oracle CPQ Administration Online Help JET Transaction UI topic or watch the CPQ JET UI: Best Practices and Customization Video.
Legacy Configuration UI	21C	22C	In Oracle CPQ 21C, we are announcing the deprecation of Legacy Configuration UI. The end of life and removal of this functionality will occur in Oracle CPQ 22C. We introduced JET Responsive UI for Configuration in Oracle CPQ 19B, and after years of evolution and production experience, our customers are experiencing the benefits of the new JET Responsive UI for both Commerce and Configuration. The majority of Oracle CPQ customers have successfully made the complete transition to the JET UI. Moving forward, we are focusing our development efforts on enhancing the JET Responsive UI to improve the overall user experience. We’re announcing these changes to give our customers early visibility and the opportunity to prepare for this update. If your Oracle CPQ implementation still uses Legacy Configuration UI, we encourage you to start preparing for the transition to the JET UI. For more information on enabling JET Configuration UI, visit the Oracle CPQ Administration Online Help JET Configuration UI topic or watch the CPQ JET UI: Best Practices and Customization Video.
Legacy Commerce and Configuration Mobile Layouts	21C	22C	In Oracle CPQ 21C, we are announcing the deprecation of Legacy Commerce and Configuration Mobile Layouts. The end of life and removal of this functionality will occur in Oracle CPQ 22C. Legacy Mobile Layouts were built to provide an adaptive experience for quoting and configuring on mobile devices. The JET Responsive UI provides a clean, streamlined user experience that is fully responsive across desktop, tablet, and phone devices, eliminating the need for the administration of separate UI Layouts for desktop and mobile users. If your Oracle CPQ implementation has legacy mobile layouts enabled, we advise you to make a transition to JET Responsive UI to provide an optimal experience for your end users. For more information on enabling the JET UI responsive experience, visit the online help for JET Responsive UI.
Legacy Rich Text Editor	21C	22C	In Oracle CPQ 21C, we are announcing the deprecation of the Legacy Rich Text Editor. The end of life and removal of this functionality will occur in Oracle CPQ 22C. Oracle CPQ occasionally disables old areas of the product that have been replaced by newer and improved versions. As previously announced in CPQ 20C, we introduced a new inline editor for rich-text editable attributes (RTE). The new JET editor includes more text formatting options than the legacy editor. Features include undo/redo, images, links, table tools, and functions with the browser's native spell-check. We are also working on adding user-specific template support to the new editor before retiring the legacy editor from the product.
GXT Customer Images and CSS References	21C	22C	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. With the Oracle CPQ 22C release, we will be removing this framework from the Oracle CPQ product. GXT Images/Icons References The images used by this framework can be 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 can be 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.

Custom JavaScript

While Oracle CPQ does not endorse or guarantee the use of JavaScript customizations, we recognize that some customers have extended the 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 consider carefully the relative benefits of JavaScript customizations in light of the associated risks.

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.

Update 21C, which supports JET v8.3.0, includes changes to the following DOM structures that will very likely impact existing JavaScript Customizations:

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

Refer to the following resources for more information:

• Oracle CPQ Administration Online Help > Style & Templates > JavaScript Customizations for JET UIs
• Oracle CPQ JET Configuration and Transaction UI: Refactoring Existing JavaScript Customizations (Doc ID 2490016.1)
• JavaScript Extension Toolkit and JET v8.3.0 Release Notes

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 21C
• "Minor update" = Update 21C 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 21C, refer to the Oracle CPQ 21C Resolved Known Issues document available on My Oracle Support and the Oracle CPQ Administration Online Help.

Translation

For some system-defined messages and components, strings were removed and others added in Oracle CPQ 21C. 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.

For the following languages, a translation of the Oracle CPQ user interface is available for both the platform and the reference application:

• 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 21C 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.

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.

IMPORTANT: 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

CPQ Cloud 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 the delivery of a fix. Certified browsers are selected based on current market share and thoroughly tested to work with the current version's standard functionality.

Certified Browsers

Windows

• Google Chrome 90x
• Mozilla Firefox 88.x
• Microsoft Edge 90.x

Mobile Devices

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

IMPORTANT:

• Internet Explorer browser certification and support was discontinued in Oracle CPQ 21A.
• Compatibility issues with the selected browsers may exist when sites contain 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.

Salesforce Integration Support

Oracle officially supports version 8.1, 8.2, and 8.3 of the Oracle CPQ Connector for Salesforce. We also continue to support version 7.2 of the legacy Oracle CPQ Commerce Integration.

Training

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 the Oracle CPQ Administration Online Help to become familiar with the new features introduced in Oracle CPQ 21C. 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 21C.

Additional Information

For more information on Oracle CPQ, visit the Oracle CPQ Documentation site.

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.

Customer Requested Enhancements

The CPQ Cloud Release 18D release introduces the following customer requested enhancements:

• BML Support for GZIP File Format Enhancement
• File Download and Email Delivery Processing Enhancements
• Overcrowded Mode Enhancements
• User Administration List Pagination Enhancement