You are here: General Administration > Pre-Upgrade Considerations

Pre-Upgrade Considerations

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

Closed2015 R2

ClosedKnown Functionality

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

ClosedEmail Template Editor

ClosedSecure URL Addresses



ClosedResolved Known Issues

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

ClosedFunctional Known Issues

There are two functional known issues for Secure Attributes. For more information on Secure Attributes in general, see Secure Attributes.

ClosedSecure Attributes Lose Value in Mobile

ClosedSecure Attribute Values only Available to First AJAX Rules Execution or Save

ClosedTranslation Status

CPQ Cloud 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 CPQ Cloud User Interface is available for both the platform and the reference application:

The following languages were added in CPQ Cloud 2015 R2:

Closed2015 R1


You can no longer create an attribute variable with the name bs_id. Existing attribute variables with this name will still function, but avoid using this name.

ClosedEmail Templates

The Commerce connection to Email Templates has changed. Instead of using the variable name of the template, the name of the template will be used.

If two or more templates have the same name, they are automatically renamed during the upgrade. The variable name is prepended to the template name. This allows admins to differentiate between the two templates. If necessary, the name is truncated to fit the size limit of the label.

The old variable name of the template is no longer displayed to the user.


The SimSun, NSimSun, and SimHei fonts are no longer supported. When printing PDFs (in both Apache FOP and Antenna House), any text using the deprecated fonts will be replaced with the font Arial Unicode MS.

Text with the font type Arial Unicode MS cannot be formatted in bold or italic in any output type. If bolding or italics are applied to Arial Unicode MS text, the text will appear bold/italic in the Document Designer/Email Templates editors, but the text will not be bold/italic in the output.

As needed, you can modify existing documents to use a font other than the default font.

In the Document Designer editor and the Email Template editor, the default font for new text is Helvetica.

ClosedSession Currency

This functionality is no longer available in version 2015 R1 and later.  Instead, by default, Session Currency is now available only as a Web Service or as dynamic data in email and document templates.  It is no longer available on the UI; the Login, User Profile, and General Site Option pages no longer contain any options for Session Currency.  A currency can still be specified by the Currency Preference option on a user’s My Profile page, and can be manually changed for any given Transaction.

Session Currency is still respected in the following situations:

  • Dynamic data in the Document Engine
  • Dynamic data in the Document Designer
  • Dynamic data in Email Templates
  • A variable in Web Services
  • A query parameter in URL queries


For some system defined messages and components, some strings have been removed and others have been added. If strings have been previously translated, some strings will no longer appear and other strings will appear in English. The strings that appear in English are new, and need to be translated.

Most of these messages and components are on the administration side of CPQ Cloud, 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.


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



Related Topics Link IconSee Also