The following document contains useful information for managing user interface in SAP CPQ. Will discuss the following modules in UI Design in SAP CPQ
Responsive templates are building blocks of all pages in SAP CPQ’s Responsive Design. Templates define the look and feel of the application – colors, icons, the order in which buttons are displayed and so on.
In the Responsive Templates page, you can see the list of all customized templates which exist in your environment, as well as the Freeze Templates functionality. You can also create new customized templates.
In the History tab of a custom template, you can see a chronological list of all versions of that template.
This feature gives you an option to roll back the no customized (original) templates to the state they were in the previous SAP CPQ release.
Responsive templates are building blocks of all pages in SAP CPQ’s Responsive Design. Templates define the look and feel of the application – colors, icons, the order in which buttons are displayed and so on.
Points to Note:
|
QuoteListFilterEditor
In the Responsive Templates page, you can see the list of all customized templates which exist in your environment, as well as the Freeze Templates functionality. You can also create new customized templates.
Templates can be customized in the Responsive Templates page (Setup > UI
Design > Responsive Templates) by copying the provided original template, editing it and making it Default in the environment.
In
Template Versions
This feature gives you an option to roll back the no customized (original) templates to the state they were in the previous SAP CPQ release.
The SAP CPQ development team only manages the original templates that customized templates are derived from. So, when a new release occurs, bear in mind that:
If the breaking changes occur in a page when the release A is deployed, and you didn’t manage to apply the necessary fixes to the customized templates before the release B is deployed, you can use the Freeze Templates feature to roll back all no customized templates on the broken pages to the state they were in during the release A. In this way, you will have more time to deal with incompatibilities between templates.
Rollback from SAP CPQ to version A can be applied only until the version C is released. Once that occurs, all pages will be deployed to the version C, new breaking changes may occur, and the no customized templates can only be rolled back to the version B.
Page rollback is only a temporary solution. If you roll back no customized templates, the pages will work as they did in the previous release, but you may not see new functionalities or fixes that were applied to the environment with the new release. For this reason, once you freeze templates, you need to apply necessary changes to templates as soon as possible, or try to avoid using this feature altogether by fixing templates on broken pages before the release is deployed.
This feature should ONLY be used in the following cases:
Implementing SAP CPQ can lead to significant improvements in sales processes, driving efficiency, accuracy, and overall customer satisfaction. In this article I have written a User Interface of SAP CPQ. Stay tuned for Other Informative blogs related to SAP CPQ. |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.