CPQ Summer '17 Patch Release Notes

by Community Manager on ‎07-05-2017 02:06 PM - edited 8 hours ago

Salesforce CPQ Patch Release Notes provide a high-level overview of bugs that were fixed and the specific features and/or enhancements used in order to solve them.

 

Summer '17 Patch 9 Hotfix 2

This patch is for Salesforce CPQ 208.9.2.

Bug # Description
W-3872793 Option constraints would not evaluate selections on other tabs until users clicked into and loaded a given tab. This let users save invalid configurations when reconfiguring. This has been fixed.
W-4061215 This bug occurred when users amended a percent of total product. Salesforce CPQ would not calculate a prorated refund or credit based on the full price that was calculated on the original quote. This has been fixed.
W-4143633 Show and Add product rules with error conditions driven by summary variables were not applied to a reconfigured bundle. This has been fixed.  
W-4269674 Quote lines would not sync to an opportunity if any quote line (on the primary quote to be synced) had a quantity of 0 and the quote exceeded the org's large quote threshold. This has been fixed.
W-4286839 This bug occurred when Salesforce CPQ attempted to sync a quote with an opportunity where a quote line (on the primary quote to be synced) had an inactive pricebook entry and the quote exceeded the org's large quote threshold. In this case, Salesfroce CPQ would not sync products and displayed a "Cannot read property 'Id' of undefined" error message on the quote detail page. Fixed so that the quote syncs without error and Salesforce CPQ does not sync any products without active pricebook entries.
W-4303380 Salesforce CPQ sometimes failed to contract an order if that order contained an order product with a contracting method set to Do Not Contract. Fixed so that Salesforce CPQ will contract the order and ignore any order products set to Do Not Contract.
W-4325162 Price rules did not calculate summary variables correctly when determining a price for a price tier. This has been fixed.

 

Summer '17 Patch 9 Hotfix 1

This patch is for Salesforce CPQ 208.9.1

Bug # Description
W-4241741 Reduction orders cannot be activated.
W-4164221

In some cases, subscription-only bundles would pull in an extra asset or assets (from the original opportunity) upon renewal. This has been fixed.

 

Summer '17 Patch 9

This patch is for Salesforce CPQ 208.9.

Bug # Description
W-3622991 Very long Group description values in the Line Editor would sometimes push the Save and Cancel buttons out of view, without any ability to scroll down. This has been fixed.
W-3722498

This bug occurred for users using a Page Security plugin. Changing some (but not all) of the segment quantities on an MDQ option and then reconfiguring caused an error. This has been fixed.

W-4146003 Adding a new group to an amendment Quote and then trying to delete that group caused a "You cannot delete this Group as it contains Quote Lines being amended" error. Fixed so that users can delete such a group.
W-4174875 This bug occurred for when a Rich Text Area field (in the quote line's Line Editor field set) contained quotation marks. Quotation marks would display as HTML markup in the Quote Line Editor. This has been fixed.
W-4188597 Discount Schedules would not populate on a quote line if that line was added as a product option from a favorite bundle. This has been fixed.
W-4202452 Users could not add the Distributor field to the Quote's Line Editor field set. This has been fixed.
W-4227343

This bug occurred for Bundles that contained a Percent of Total product and where Asset conversion was One Per Unit. These bundles had incorrect quantities on amendment Quotes and renewal Quotes. This has been fixed.

Magic Field Fixes Contract queries would not include magic fields. This has been fixed.

 

Summer '17 Patch 8

This patch is for Salesforce CPQ 208.8.

Bug # Description
W-4164098 On the Modify Quote Terms page, users could not edit or save any Quote Terms displayed after a locked Quote Term. This has been fixed.

 

Summer '17 Patch 7

This patch is for Salesforce CPQ 208.7.

Bug # Description
W-3958307 (JSQC or Legacy calculator with Run Calculator in Background active): This bug occurred when users contracted an add-on opportunity and quote so that they were co-terminated with a contract that already a non-quoted renewal forecast. In this case, Salesforce CPQ did not add subscriptions to the contracts, and users encountered a "Too many queueable jobs" error. This has been fixed.
W-3978852 Twin Fields: Formula (Number) fields did not map from Product to Quote Line for system-added product options. This has been fixed.
W-4070823 Service Contracts: When users renewed a subscription that was part of a bundle, Salesforce CPQ did not pull that bundle into the renewal Quote, even if Preserve Bundle Structure was active. This has been fixed.
W-4184365 Selecting a Rich Text Editor field in the Quote Line Editor and changing the headings, font family, or font sizes caused Salesforce CPQ to freeze temporarily and remove the formatting bar from the display. This has been fixed.
W-4188572 (Installed orgs only): Saving a reduction Order where a Quote Line-to-Order Product twin field was present caused an error. This has been fixed.

 

Summer '17 Patch 6

This patch is for Salesforce CPQ 208.6.2.

Bug # Description
W-4062476 Large Quote Experience: When users left full-screen mode, Quote Lines with large descriptions had the description text overlap or hide any subsequent Quote Lines. This has been fixed.
W-4072450 This bug occurred when users saved a primary Quote in an org that had met its Large Quote Threshold. In this case, Salesforce CPQ did not synchronize related Opportunity Products. This has been fixed.
W-4184096 Large Quote Experience: While Large Quote Experience was enabled, Salesforce CPQ would not render drawer icons next to individual Quote Lines in the Quote Line Editor. This has been fixed.
W-4187577 This bug occurred for some users with Accounts where Contract Co-Termination was set to Active. In this case, users who created a new quote from an opportunity could not navigate past the active contract selection screen. This has been fixed.
W-4188552 This bug occurred in orgs where Ensure Bundle Structure was active. Clicking Renew Subscriptions in the quote line editor and then choosing certain subscriptions would bring all of the Quote's subscriptions into the renewal, regardless of which subscriptions the user left unselected. This has been fixed.
W-4203784 Some users who amended assets from an Account record encountered a "Too many query rows" error after they clicked Amend in the Asset Selection screen. This has been fixed.
W-4236952 SOQL query error reporting missing field when Amending/Renewing Contract with mapped custom fields between Contract and Opportunity.

 

 

Summer '17 Patch 5

This patch is for Salesforce CPQ 208.5.

Bug # Description
W-3611162 Bullet lists rendered in incorrect horizontal positions within HTML and Quote Term content. This has been fixed.
W-3975822 After clicking Amend Contracts, users could select expired Contracts from the contract selection page. This has been fixed.
W-4012245 This bug occurred when users renewed a Contract that had been amended with asset quantity changes. In this case, Additional Discount and Customer Unit Price values on the renewed assets were calculated incorrectly. This has been fixed. 
W-4030936 Configuration attribute values for twice-nested bundles would not persist when users saved within the configurator. This has been fixed.
W-4095739 When users added a Percent of Total product outside of a bundle, Salesforce CPQ would pull in all related assets when renewing the quote. Fixed so that Salesforce CPQ only renews the bundle parent and its children in this circumstance.
W-4139653 This bug occurred when a validation rule fired on a quote line item field within the Quote Line Editor. In this case, Salesforce CPQ displayed the validation error message and prevented saving, but did not show the calculated values that were results of the change in quote line item formula fields where the original value was used. This has been fixed.
W-4142526 Some users with many quote line fields on each of a quote's lines encountered an "input too long" error when reconfiguring a bundle. This has been fixed.
W-4147119 Corrected help text for the pricing package-level setting Calculate Immediately. The text now reads as "Enable real-time calculation on the Edit Lines page. Calculations occur when any field value is changed."
W-4152321 In some cases, ordering, contracting and amending a quote twice caused bundle parent products to have incorrect Quantity values. This has been fixed.
W-4152808 Using conn.apex.post in a QCP to call gave an "HTTP Method 'GET' not Allowed" error. This has been fixed.
W-4175262 Amending an active contract that contained custom fields in its Active Contract Lookup field set sometimes caused an error. This has been fixed.
W-4175480 This bug occurred when users saved a quote within the Salesforce Tabs + VisualForce section of a Community using a non-default URL. In this case, users encountered a "Site Under Construction" error. Fixed so that users are returned to the quote detail page after the quote saves.
W-4187576 In some cases, creating a Quote and associating it with a Contract where Contract Co-Termination was set to Prompt caused Salesforce CPQ to query all Contract fields upon quote creation, causing an error. This has been fixed.
W-4188537 Line Editor does not load in Internet Explorer

 

 

Summer '17 Patch 4

This patch is for Salesforce CPQ 208.4.

Bug # Description
W-4067145 Saving a Quote with Quote Lines above the Large Quote Threshold value would not fire the validation that prevents price changes if the Quote was marked as Primary. In this case, Salesforce CPQ encountered a validation error when attempting to save an Opportunity Product as well. This has been fixed.
W-4069844 In some cases, users encountered an "Unsafe URL" error if they selected Clone with Related on a Product and then selected Cancel on the Clone options page. This has been fixed.
W-4074106 The JS Quote Calculator plugin could not use the conn.sobject fuction. This has been fixed.
W-4090837 As of Salesforce CPQ 26.0, users could renew Contracts past their expiration date if CustomActiveContract was set to 1. CustomActiveContract could not be used this way as of 27.0. This has been fixed.
W-4146081 In some cases, Quote-scoped validation rules fired unexpectedly when users selected Renewal Forecast on a Contract and then saved the Contract. This has been fixed.
W-4152418 Salesforce CPQ would not include renewed products in Renewal Opportunities and Renewal Quotes. In some cases, this happened when the Start Date and calculated End Date included February 2017, and/or when the original Quote's Subscription Term was less than 6 months. Fixed so that the above dates and Subscription Terms no longer cause Salesforce CPQ to miss products in Renewal Opportunities and Renewal Quotes.
W-4094063 Some users encountered an error when creating a new Quote from the Opportunity's Quotes related list. This error occurred if the org had Entitlements enabled and Contract Co-Termination was set to Prompt or Always on the relevant account. This has been fixed.

 

 

Summer '17 Patch 3

This patch is for Salesforce CPQ 208.3.

Bug # Description
W-3729066 Changing an Order's Start Date after initial order creation caused Salesforce QTC to recalculate Order Product End Dates in correctly. In this case, the End Date was set as the Order's Start Date plus the length of the Subscription Term, which was incorrect when dealing with partial months. Fixed so that the Order Product End Date preserves the Quote's Term.
W-3880757 Creating a solution group and then trying to add it to an ungrouped Quote resulted in Group 1 appearing on the Quote first. The solution group only appeared if users tried to add it a second time. This has been fixed.
W-3883338 Dragging and dropping MDQ product lines across groups caused those lines to disappear. The lines would only reappear if the user quick-saved the Quote. This has been fixed.
W-3933163 For some users, translated Product values did not display in the Quote Line Editor or Product Search. This has been fixed.
W-3958796 When Preserve Bundle Structure was active (for Contract-based workflows), amendment and renewal Quotes would sometimes pull in extra asset-only bundles from the related Account. This has been fixed.
W-3987902 Users could only select "None" or a single search filter value from a dependent picklist whenever the controlling picklist search filter was hidden. Fixed so users can select from all available values on the dependent picklist.
W-3997495 If users set an Account's Contract Co-Termination field to Prompt, creating a Quote on that Account caused Salesforce QTC to query all Contract fields upon creation. Fixed so Salesforce QTC only runs a query for Contracts on that Account that contain fields relevant to the packaging process.
W-4041729 Contracting from an Order and then making two amended Quotes sometimes caused incorrect quantities for products on the second amended Quote. This has been fixed.
W-4070823 (Service Contracts): This bug occurred for users who selected Renew Subscriptions in the Quote Line Editor while Preserve Bundle Structure was active. If the user selected a subscription that was part of a bundle, Salesforce QTC only renewed the subscription itself and not the entire bundle. Fixed so that Salesforce QTC honors Preserve Bundle Structure in this situation and renews the entire bundle.
W-4083362 When using Product Rules with summary variables, using the API (QuoteProductAdder) to add a quote line resulted in an error. This has been fixed.
W-4084808 This bug occurred when users tried to create an Order for a Renewal Quote that contained a Percent of Total Subscription with a block-priced Subscribed Asset. In this case, the Order would not finish calculation and users encountered an error indicating that the Subscribed Asset did not contain a block price for its quantity. Fixed so that the Order creates properly.
W-4106285 This bug occurred for when users set quantity to 0 on the first segment of an MDQ Product. In this case, Contracts created from any Orders with this Product would have a Start Date set to the second segment's Start Date. This has been fixed.
W-4125868 Backport of W-4025115 from Patch 1For some users, Order Product records did not populate their List Price fields from the Quote Line's List Price. This has been fixed.
W-4126189 This bug occurred for users who had created partial Orders from a Quote that contained assets and a Percent of Total line. Creating a second partial Order that fully-ordered the Quote caused Salesforce QTC to create a new Order for the full quantity of the Percent of Total, which meant the Orders contained more instances of the Percent of Total product than were quoted. Fixed so that Salesforce QTC does not create a new Order in this situation.
W-4140978 When users fully ordered a Quote and then selected Create Order, Salesforce QTC did not display a message indicating that all products on the primary Quote had been ordered. This has been fixed.
W-4151742 Creating the first group on a Quote caused Salesforce QTC to display the group's description (or the "Click to add description" text) in orange (indicating a field that had been modified but not yet saved). Fixed so that either description texts display as the standard black or blue color.

 

 

Summer '17 Patch 2

This patch is for Salesforce CPQ 208.2.

Bug # Description
W-3976788 This bug occurred when users ordered a Quote containing a block-priced Product with price tiers. In this case, the related Price Schedule only contained one price tier and had a Pricing Model set to Per Unit. Fixed so that the Price Schedule in this scenario has one price tier per block tier and has a Pricing Model set to Flat Fee.
W-4007781 Dragging and dropping a product option between groups would often delete that option. This has been fixed.
W-4038447 Note: Originally corrected in 27.0.38 and documented in Winter 17 Patch Release Notes. In some cases, making a change on a quote's record page and then saving would cause Salesforce QTC to recalculate indefinitely. This has been fixed.
W-4042604 Bundles did not preserve on amendments (where Preserve Bundle Structure was checked) if the bundle parent did not have a Percent of Total Category and contained a child asset with a Percent of Total Category. In this case, the bundle parent did not carry over to the amendment quote. This has been fixed.
W-4088871 Bundles did not preserve on renewals (where Preserve Bundle Structure was checked) if the bundle contained a non-Percent of Total asset, and an asset with Percent of Total that referenced a Percent of Total product outside the bundle. In this case, only the Percent of Total asset and related Percent of Total product carried over to the renewal quote while the bundle parent and non-Percent of Total asset did not. This has been fixed.
W-4091315 Bundles did not preserve on renewals (where Preserve Bundle Structure was checked) when the bundle parent was a subscription product and the bundle contained a non-Percent of Total asset and a Percent of Total asset as its children. In this case, only the Bundle Parent and the Percent of Total asset carried over to the renewal quote. This has been fixed.
W-4094063 Editing an Order Product on an Order without a Quote lookup caused an error. This has been fixed.

 

 

Summer '17 Patch 1

This patch is for Salesforce CPQ 208.1.

Bug # Description
W-3936367 The Create Order page did not automatically populate its Quote lookup field when users selected Create Order from a Quote record. This has been fixed.
W-3970218 Optional products were available for selection when ordering from a quote, and were added to orders when users selected Ordered on an opportunity. This has been fixed so optional products are not present on the order screen and are not added to generated orders.
W-3992034 Salesforce CPQ always changed a renewal opportunity's Close Date to the contract's End Date whenever a user selected Renewal Quoted. This prevented users from manually changing the renewal opportunity's Close Date after selecting Renewal Forecast from the Contract. This has been fixed so users can set the renewal opportunity's Close Date after selecting Renewal Forecast on the Contract.
W-3997416 Option Constraint help text did not always match the user-defined Option Constraint logic. For example, text would indicate that users needed to select "Option B AND Option C" when the constraint record actually required the user to select "Option B OR Option C." This has been fixed.
W-4025115 For some users, Order Product records did not populate their List Price fields. This has been fixed.
W-4036581 During order creation, Price Rule lookup queries would not consider "less than" or "less than or equal" operators, which caused the query to return incorrect row values. This has been fixed.
W-4064649 Externally configuring a pre-selected option with a configurationData set does not carry the set value over to the option's quote line unless a twin field is present. This has been fixed.
W-4048468 Referencing a checkbox field in a Price Action formula and then selecting Renewal Quoted on a Service Contract causes an error. This has been fixed.
W-4061899 Orgs with Japanese currency and day-level proration would calculate prices differently between a quote line record and the quote template. This has been fixed.
W-4064550 Externally configuring a selected option with a configurationData set does not carry the set value over to the option's quote line unless a twin field is present. This has been fixed.
W-4064649 Externally configuring a pre-selected option with a configurationData set does not carry the set value over to the option's quote line unless a twin field is present. This has been fixed.
W-4069991 iOS SF1 users could not scroll past the first page of a quote document PDF. This has been fixed.
W-4076539 Some users encountered an Unexpected Exception error when attempting to contract an Order. This has been fixed.
W-4077206 Setting the Account-level Renewal Pricing Method to Uplift caused renewals to encounter an error if a Contract on the renewal contained a percent-of-total subscription. This has been fixed.
W-4100707 For some users, editing a quote line record created more than one RecordJob__c records. Fixed so that editing a quote line record only creates one RecordJob__c record.

 

Comments
by soniaflamm
on ‎07-06-2017 09:52 AM

I have a question regarding bug fix W-3970218 - Optional products were available for selection when ordering from a quote, and were added to orders when users selected Ordered on an opportunity. This has been fixed so optional products are not present on the order screen and are not added to generated orders.

 

We are currently implementing CPQ and Billing and are heavily reliant on adding optional products to our orders. There is not mention on the community or on the field description that optional products will not flow down to the order. Can someone please point me in the right direction for this? Are there are other options for not allowing a product added to a quote not count towards the total while also having it flow down to the order?

by chickman_pwc
on ‎07-06-2017 03:31 PM

@soniaflamm What would be the use case for ordering products marked optional on a quote? If the product is "optional" it does not add revenue to the quote or opportunity, nor is it something the customer agreed to buy...therefore by making an optional product orderable, you are allowing fulfillment of a product or service for which delivery was never agreed. If the product should be orderable, it should not be optional on the quote, or if a deal was closed that way originally, an amendment should be created to add that product to their contract.

 

For example, if I order a car with red paint, and quote an optional metallic paint job at +$500, if the customer says no to the metallic paint but yes to the car, I close the deal and I can then generate an order for the car with standard paint, but not the more expensive metallic paint. Another example would be standard support vs. premium support - I can quote anything I want (another scenario might be good/better/best rather than a regular upgrade), but I shouldn't be able to generate an order for anything the customer did not agree to buy, because I have nothing that shows the customer has agreed to pay for it.

by soniaflamm
on ‎07-06-2017 08:41 PM

@chickman_pwc thank you for the quick, detailed response. I can understand why you have questions about the business use cases.  

 

I am currently implementing both CPQ and Billing for a client and we have usage products that can be prepaid on an annual basis. In some cases the prepaid usage can also occur overage if they go over the allotted amount for each month which will be invoiced on top of the prepaid amount. Sometimes the usage recorded is used as data to send to FMS for revenue recognition. In every use case where we have prepaid usage, we send information back and forth through an integration with the actual product to determine customer entitlements.

 

Since there isn't a concept of prepaid usage for SFDC billing, we have created a custom workaround to accomplish the above use cases. All usage products are eligible for prepaid and postpaid billing options. For prepaid options we have a subscription product nested as an option under our usage product. This product is automatically selected for prepaid scenarios and inherits all pricing from the usage product. It's marked as 'Optional' so that it doesn't count towards the quote total. 

 

Currently, when the order is created and activated the subscription products (prepaid usage) will be ready to be invoice for the entire year in advance with the correct total (inherited from the actual usage line). Depending on which prepaid option was selected, the usage product will either charge usge when it occurs or just record usage through the integration for rev rec and entitlement purposes. We want both the prepaid line to have pricing so the customer is charged a prepayment amount and we also want the usage line to have pricing to determine overage, rev rec, etc. 

 

We are trying to minimize the amount of code/customizations for these scenarios since we already have quite a few built for CPQ and Billing. Please let me know if there are other options I am not thinking of. Thanks!

by Community Manager
on ‎07-10-2017 04:33 PM

@lvoelz2 - Can you add that this is version 208.1? Customers will not know that Summer '17 Patch 1 = 208.1

by jamesm
on ‎07-13-2017 03:26 AM

@lvoelz2 @fshapiro

 

Please could you confirm

Patch 1 = 208.1 or 208.1.1?

Patch 2 = 208.2?

by Community Manager
on ‎07-13-2017 08:47 AM

@jamesm Patch 1 = 208.1 and Patch 2 = 208.2. I've updated the titles here accordingly.

by ckamin
on ‎07-13-2017 11:28 AM

I'm still seeing tons of issues with amendments and renewals of bundles where the renewable Product Options are not maintaining their place inside the bundle structure, while all the non-renewable/assetized Product Options are. The system-set quantities on amendments and renewals are also completely jacked.

 

Re: the above, I am Contracting via the Order(s), and using Quote Groups, if that makes a difference.

Contributors