Winter 19 CPQ Advanced features

Something that we’ve been waiting…  Here are all winter 2019 CPQ  advanced features:

1. General Subscription without End Date

Can create Contract without End Date so the subscription should not be renewed.
Can be useful for companies that bill monthly and do not need to renew the contract until the customer ask to cancel the subscription.

There are 2 setup types for Evergreen products:

  • Evergreen – the product is set up to continue without contract end date.
  • Renewal/Evergreen – allow the product to be Evergreen with the option to switching to Renewal subscription.

What you need to know about this feature:

  • If you create mixed quote the system automatically will create two types of contracts.
  • Evergreen subscription do not support: Sales Billing, Partial Amendment, Dynamic Bundles w/evergreen products, Renewal for asset-based models

To activate Subscription without End Date, you need to setup this functionality:

2. Price Percent of Total (POT) Products Based on the Entire Bundle

Base your percent of total product’s price off the entire bundle configuration that it’s a part of, including all parent and child bundles.
Previously, percent of total scopes couldn’t cover child bundles or anything above the first level of a parent bundle.
The POT product can be located in any hierarchy level of the bundle and still will calculate the correct price for all the bundle levels.

Setup your POT products is very easy:

  • Add new value pick list for Percent of Total Scope on Product Option object: Hierarchy.
  • On your product option for a percent of total product, choose the Hierarchy value for the Percent of Total Scope field.
3. Order Fields Pre-Populated in Lightning defaults from Opportunity and Quotes

You only need to drag and drop action Create Order on Quote/Opportunity layouts.

Make sure to select the button with the name Opportunity.CreateOrderLightning or Quote.CreateOrderLightning

4. Improved Rich Text Editor on Salesforce CPQ

Allow you to use the same HTML tags as Lightning Experience.

Main changes to keep in mind:

  • Most content is wrapped in <p> instead of <div>. Rich text content that you formatted before Winter ’19 is wrapped in <p> after you open and save it with the new rich text editor.
  • Closing tags are removed if they’re not required. For example, <img src=”someSource”></img> becomes <img src=”someSource”>.
  • Content usually ends with <p><br></p>.

Don’t warry if your Sales rep saved Rich text fields in an earlier version of Salesforce an alert when you first open a rich text field that you saved in an earlier CPQ version.




By Mirela Cohen