There are two major focus areas in the Oracle CPQ Cloud 22C release affecting the CPQ User Interface and Fonts related to Document Designer generated output documents.
User Interface (UI) change
The Oracle CPQ Product Group is in the process of removing Legacy Commerce Transaction UI (user interface) from the 22C release for both Commerce and Configuration. This may impact your business if you are still using Legacy UI for Oracle CPQ Cloud.
· It’s mobile ready so the UI refactors are based on the screen of the CPQ users
· There is multi-language support for up to 28 languages
· The design is modern and clean and has more functionality than the Legacy UI
· It allows for fuzzy logic searching and selection of items
There are also many visual improvements that Jet UI brings with it, but one of the other most important things that it does is bring about an upgrade in performance.
More control is now available on what can be displayed, and who gets to see it. Role-based views are now easier than ever to set up, which means sensitive price build up information can remain in the hands of only those who really need to see it. Jet UI also prevents the entire page for refreshing whenever data influencing content is modified, offering the ability to only refresh sections of the page, further improving UI responsiveness.
Also, in the Oracle CPQ 22C release, they are changing the supported fonts available for use with Oracle CPQ. This change impacts several areas of CPQ including Document Designer, Email Designer, Document Engine, and Rich Text Editor (RTE). To minimize the impact of the font changes, Oracle CPQ has determined substitute fonts which closely resemble the now unsupported font selections. If the output for the template is RTF or DOCX, there will be no effect on the document output.
If your document output templates contain unsupported fonts (particularly impacting PDF output) the following options are available:
· If you are using Document Designer or Email Designer and you prefer to change unsupported fonts to supported fonts, you may do this after the upgrade to 22C. Afterwards, unsupported fonts will automatically be substituted for a similar but supported fonts. The unsupported font displays in the Font field until it is replaced with a supported font.
· If you are using Document Engine XSLs to generate PDF output documents, you will need to take action immediately following the 22C upgrade.
If your Oracle CPQ environments still rely on Legacy Commerce UI, it’s essential to ensure a smooth transition to the new Jet Responsive UI without delay.
Following your 22C upgrade, the unsupported fonts will need to be identified and warning messages to be provided in the Text Element Properties and the Heading Styles Editor. The warning message will include all unsupported fonts that are used in the current selection.
Walpole Partnership recommends that you provide the necessary licensed font file(s), transition your templates to Document Designer and select supported fonts, or replace font designation within the XSLs.
Our CPQ technical experts are available to help you with this transition. Please contact us if you’re interested in joining our short webinar on this topic which is scheduled for the second half of August, and we will send you a link to the event and recording.