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.
This patch is for Salesforce CPQ 210.15.7
|W-4575329||This bug occurred when contracted order products with the same end date, where both orders products had a Contracting Method of Inherit, on an order with a Contracting Method of By Subscription End Date. In this case, Salesforce CPQ made separate contracts for each order product instead of using one contract for both subscriptions. This has been fixed.|
|W-4585141||For some users, Salesforce CPQ did not populate the Master Contract lookup on co-terminated quotes. This has been fixed.|
|W-4595498||Previewing a quote document based off a quote template without any template section caused Salesforce CPQ to display an error. Fixed so that Salesforce CPQ will still generate a PDF for previewing.|
This patch is for Salesforce CPQ 210.15.6
|W-4409162||Salesforce CPQ would delete price book lookups from quote records after the quote was saved or quick-saved. This has been fixed.|
|W-4564856||When the order object's Opportunity field was marked read-only, clicking Create Order on an opportunity record caused Salesforce CPQ to display an error. This has been fixed.|
|W-4573357||In some cases, lookup tables with multiple configure attributes would apply disable options during the application of Disable & Remove actions. This has been fixed.|
|W-4576127||Setting the Quote.SBQQ__LineItemsGrouped__c field to True within a trigger on renewal quote creation would sometimes create extra MDQ product lines if the quote's renewal term was shorter than its contract term. This has been fixed.|
|W-4582330||If users triggered a calculation from the quote line detail page, Salesforce CPQ would not fire price actions that targeted fields on the related quote record.
|W-4582795||Price rules that used a lookup query to find their injection values would not run in response to a Calculate action. Instead, they would run only upon the user saving, quicksaving, or adding a product. This has been fixed.|
|W-4582836||This bug occurred for fields that were part of the Segmented Line Editor Summary fieldset. Users could edit these fields in segmented summary rows. Fixed so that users cannot edit those fields in segmented summary rows.|
|W-4588796||The value of the quote line Description field would not populate|
|W-4591071||This bug occurred when a quote had at least one non-optional subscription and at least one optional subscription with a different end date. Contracting the quote created a contract record that did not contain a subscription record for the optional subscription quote line. Fixed so that Salesforce CPQ does not create a contract record for optional quote line subscription products.|
This patch is for Salesforce CPQ 210.15.5
|W-4438457||This bug occurred when on renewal quotes made from an amended contract, where the amended contract contained subscription products with a discount schedule applied. When Salesforce CPQ created the renewal quote, it applied an unwanted value to the Additional Discount field of quote lines for any such subscription products. This has been fixed.|
|W-4524543||Percent of Total child products did not display with correct values on forecasted renewals where an add-on opportunity had been contracted. This has been fixed.|
|W-4559978||Salesforce CPQ Calculate API did not work correctly when called via REST. This has been fixed.|
|W-4581434||This bug occurred on quotes that contained a bundle with a Percent of Total component, where the Percent of Total component had a 100% Additional Discount. When users tried to order this quote, Salesforce CPQ displayed an error. This has been fixed.|
This bug occurred when users renewed a contract that contained a subscription bundle with 2 options:
- A first-level nested subscription parent with a second-level nested asset
- A first-level asset option
Renewing this contract would not pull over the second-level nested asset, even if Preserve Bundle Structure was checked. This has been fixed.
|W-4583950||Salesforce CPQ displayed an error if users tried to save a primary quote in orgs with 50,000 or more opportunities. This has been fixed.|
|W-4584983||When users added too many Favorite records and once and then clicked select, Salesforce CPQ did not add the favorites to the quote and instead stayed on the Favorites selection screen. This has been fixed.|
This patch is for Salesforce CPQ 210.15.3
|W-3556508||In some cases, Salesforce CPQ did not generate Percent of Total subscription prices and subscribed assets following multiple amendments. This has been fixed.|
|W-3810330||This bug occurred when a template section had an additional document and no template content. When previewing a related quote document, the document sometimes displayed only template section additional documents. This has been fixed.|
|W-3880646||When some users upgraded two of the same asset (across different quote lines), Salesforce CPQ upgraded only one asset. This has been fixed.|
|W-4035676||After users changed their opportunity's currency, and then changed the primary quote's currency to the same value, Salesforce CPQ did not synchronize their quote lines and opportunity products. This has been fixed.|
|W-4446633||Using blank merge fields within template content caused any related quote documents to display an error. This has been fixed.|
|W-4490587||For some users, ordering a quote with one asset product caused the order process to fail. This has been fixed.|
|W-4495133||This bug occurred for quotes with several quote line groups displayed in the quote line editor. Scrolling to a group, clicking the date picker icon and then clicking outside the date picker did not cause the date picker to close. This has been fixed.|
|W-4523453||When Enable Multi-Language Translations package setting was checked, if a quote template ID was specified on a quote record, users could change the quote template selection on generate and preview document pages. This has been fixed.|
|W-4528403||Salesforce CPQ did not display MDQ segments with negative net totals under the year label.|
|W-4530522||For some users on Firefox, saving in the quote line editor caused Salesforce CPQ to load indefinitely. This has been fixed.|
|W-4537277||[Service Cloud]: When users clicked Amend Subscriptions in the quote line editor, Salesforce CPQ erroneously queried all custom fields on the Contract Line Item object. This has been fixed.|
External configurators did not load correctly for users on any google chrome 63.x version. This has been fixed.
Clicking Create Order on a quote containing a percent of total product and covered asset sometimes caused order generation to fail. This has been fixed.
This patch is for Salesforce CPQ 210.14
|W-4007313||This bug occurred when users clicked Clone with Related on a quote, changed an MDQ product's subscription term, then saved. In some cases, the MDQ product on the cloned quote did not have an updated subscription term. This has been fixed.|
|W-4126004||Lookup price rules did not update the earlier segments of an MDQ product until the final segment of the MDQ product queried the desired row. This has been fixed.|
|W-4146134||Renewal quote lines inherited the value of their Bundled field from the original product option instead of the renewal product option. This has been fixed.
|W-4152042||[Lightning]: When users saved in the quote line editor, the quote detail page did not reflect new quote totals until the user manually refreshed the page. This has been fixed.
|W-4152099||In some cases, lookup product rules did not function correctly when the target quote contained quote line groups. This has been fixed.|
|W-4172622||This bug occurred for contracts with a single-contract contracting method. In some cases, these contracts inherited their renewal term value from the first quote line's term. This has been fixed.|
|W-4188583||When users made an order from the opportunity, the order took its products from the most recently-created quote and not the primary quote. This has been fixed.
|W-4199219||When users changed the month in the date picker widget, Salesforce CPQ sometimes erroneously updated date fields in the quote line editor. This has been fixed.|
|W-4236294||When users amended a contract that contained only completely-refunded subscriptions, Salesforce CPQ displayed a "list index out of bounds" error. This has been fixed.|
|W-4249831||In some cases, quote-scoped product rules did not evaluate date formula fields. This has been fixed.|
This bug occurred for nested selection rules that were driven by summary variables on the nested parent bundle. These rules did not activate on load. This has been fixed.
This bug occurred for nested selection rules that were driven by summary variables on the nested parent bundle. These rules did not activate upon reconfiguring the target bundle. This has been fixed.
|W-4380924||When users contracted an add-on opportunity, Salesforce CPQ set the contract's Renewal Term field to null. This has been fixed.
This bug occurred for nested asset component children of asset bundles, where the bundle parent had one-per-unit asset conversion. When you renewed these children, their renewal quote lines had incorrect quantities. This has been fixed.
[Service Cloud]: When users clicked Amend Assets on their account detail page, Salesforce CPQ sometimes displayed a blank service selection page. This has been fixed.
|W-4468274||This bug occurred for fields in the quote line drawer fieldset that did not have a default value. Users could not edit these fields if they made the related quote line a favorite. This has been fixed.|
|W-4471690||The Effective Start Date field did not display in managed line editor fieldsets. This has been fixed.|
|W-4473096||Nested bundle parents displayed their dropdown caret icon in the quote line editor only if users added a nested option in that configuration session. This has been fixed.
When a background contracting process for an order fails, Salesforce CPQ now sends an email notification to all related users and logs error details in the related record job.
Creating an amendment order for an asset-based account sometimes failed and caused Salesforce CPQ to display a "Choose a master contract for this amendment quote" message. This has been fixed.
When you ordered a Percent of Total product, Salesforce CPQ did not respect the value of ApplyAdditionalDiscountLast on the quote.
When users saved within a nested bundle configuration, Salesforce CPQ did not return users to the correct category tab if the category label and category API name were not equal. This has been fixed.
Users could not amend or renew MDQ products that defaulted to a standard pricing table and were later segmented. This has been fixed.
Cannot Amend or Renew MDQ Products that default to Standard pricing table and are later segmented.
This patch is for Salesforce CPQ 210.13
|W-4132935||This bug occurred when you used the dataloader to update several lines on several quotes. In this case, Salesforce CPQ sometimes performed calculations on only one quote. This has been fixed.|
|W-4175646||This bug occurred on subscription products (with a charge type set to Recurring) that had a one-time price dimension. When added such a product to your quote, Salesforce CPQ did not update the one-time segment's charge type to a value of One-Time. This has been fixed.|
|W-4308157||Prorate multipliers did not always correctly for quote lines that started and ending on the last date of the same month one year and one day apart. (For example, 1/31/2017 through 1/31/2018 or 2/28/2017 through 2/28/2018). This has been fixed.|
|W-4444617||This bug occurred for bundle products with a dynamic feature and a product option with a cost-based price method. That option did not always appear on bundle reconfiguration. This has been fixed.|
|W-4445432||Contracting an amendment order (while the billing trigger was disabled) caused an Apex CPU time limit error. This has been fixed.|
|W-4446072||Bundle parents did not display the reconfigure wrench icon on amendment and renewal quotes when the legacy contract service was set to false. This has been fixed.|
|W-4468147||On some amendment quotes, Salesforce CPQ calculated Percent of Total values off of the unprorated total (using the quote's subscription term) and then multiplied that value by the Percent of Total product's prorate multiplier. Fixed so that Salesforce CPQ calculates Percent of Total in this case off the unprorated total using the proration multiplier of the covered products, then multiplying that value by the Percent of Total product's prorate multiplier.|
|W-4469681||This bug occurred when you viewed the segmented line summaries of two or more MDQ products that each had different price dimensions (for example, yearly and one-time.) In some cases, Salesforce CPQ did not display the fields for one of the products. This has been fixed.|
|W-4470024||In orgs where legacy contract service was set to false, users encountered an error when they contracted an opportunity containing only fixed price subscription products. This has been fixed.|
This patch is for Salesforce CPQ 210.12
|W-3848318||Contracting order products at the order product level sometimes resulted in a "REQUIRED_FIELD_MISSING" error. This has been fixed.|
|W-4259359||This bug occurred if you had an MDQ product option as part of a bundle in a quote where the subscription term was greater than 24. If you deleted the bundle parent, Salesforce CPQ still displayed the segmented child product. Fixed so that the child product no longer displays.|
|W-4408370||In some cases, large bundles with many product rules and configuration attributes would not apply selection rules that fired immediately or after edits. This has been fixed.|
|W-4420202||If several users attempted to save in the quote line editor around the same time, Salesforce CPQ would sometimes display the "unable to connect to the server" error message. This has been fixed.|
|W-4429781||In some cases, Salesforce CPQ did not display a bundle's checkboxes when users reconfigured the bundle. This has been fixed.|
|W-4443528||On some amendment quotes, Salesforce CPQ calculated Percent of Total values off of a prorated price and then multiplied that value by the Percent of Total product's prorate multiplier. Fixed so that Salesforce CPQ calculates Percent of Total off the unprorated total of the covered products and then multiplies that value by the prorate multiplier.|
This patch is for Salesforce CPQ 210.11
|W-3838788||Rich text editor fields on the quote object would not format correctly when they had HTML markup. This has been fixed.|
|W-3904833||Fields set to be hidden by the Page Security Plugin would still display in line item drawers. This has been fixed.|
|W-4251796||Selection rules would not hide an option when its bundle parent's option layout was set to Tabs. This has been fixed.|
|W-4305961||For some users, multi-select picklists with three or more values would cover other fields in the quote line group's field set.|
|W-4313610||This bug occurred for users with an MDQ product that contained a time-based dimension and a one-time fee. Users could not delete the product from the quote line. This has been fixed.|
|W-4335363||Users couldn't close a date picker in the quote line group's fieldset if the fieldset contained enough fields to require side-scrolling. This has been fixed.|
|W-4365303||Salesforce CPQ would not calculate the Package Total field in time for it to be available for evaluation under After Calculate price rules. This has been fixed.|
|W-4369767||This bug occurred for users working in Visualforce and in the Tabs community. When users clicked the classic Clone with Related button on a quote with quote lines, Salesforce CPQ displayed "Error: Error occurred while loading a Visualforce page." This has been fixed.|
|W-4419992||This bug occurred when users made a net, customer, or regular Percent of Total product's quantity 0 on an amendment, when the covered product had a non-12 subscription term. In this case, the Percent of Total value calculated off a prorated net unit price field, then Salesforce CPQ sent the prorated price into the list unit price and prorated the remaining term on the contract. This process incorrectly caused double proration. We've fixed this so that Salesforce CPQ calculates the Percent of Total value off the unprorated net total field before following the rest of the calculation steps.|
|W-4423947||Ordering a product with block prices in multiple price books caused the order's price calculation to display Not Started and a price calculation error message indicating overlapping tiers. This has been fixed.|
This patch is for Salesforce CPQ 210.10
|W-4152042||Lightning UI: When you made edits in the quote line editor and then saved, the quote detail page did not reflect the changes until you manually refreshed the page. This has been fixed.|
|W-4216856||Editing an order while its Price Calculation Status is set to Queued would sometimes cause Price Calculation Status to stay queued indefinitely. We've fixed this by changing Price Calculation Status from an editable field to a read-only field. Users may encounter price calculation errors if they change Price Calculation Status from read-only to editable.|
|W-4345446||For some users, Salesforce CPQ would not calculate accurate pricing for percent of total subscriptions if Exclude from Percent of Total and/or Include in Percent of Total fields were selected on covered products.|
|W-4390062||Batch processes to select Renewal Quoted on an already-forecasted contract would sometimes fail due to too many queued jobs. This has been fixed.|
|W-4412937||When installing Salesforce CPQ, users would sometimes encounter a "Field: Product2Id must not be Readonly" error. This has been fixed.|
|W-4415765||Salesforce CPQ sometimes encounter a "too many SOQL queries" error when trying to update a large number of order products. This has been fixed.|
This patch is for Salesforce CPQ 210.9
|W-3995463||When you deleted more than two groups in the quote line editor and saved, Salesforce CPQ returned all but the last group you deleted to the quote. This has been fixed.|
|W-4079370||For some users, configurator-scoped price rules with Event set to Edit did not fire when users made an edit in the configurator. These price rules only fired on saving instead. This has been fixed.|
|W-4342206||Added Advanced Services to the quote line editor.|
|W-4362773||This bug occurred for some users with multiple quote-scoped product rules that fired upon the same criteria. In this case, only the first rule by evaluation order would fire. This has been fixed.|
|W-4363037||This bug occurred for users who amended an order so that the quantity of an order product on the amendment order was reduced to zero. In this case, Salesforce CPQ did not populate the Termination Date on the amended order product. This has been fixed.|
|W-4390097||Salesforce CPQ would not follow evaluation order for multiple quote-scoped selection rules that fired at the same time. This has been fixed.|
This patch is for Salesforce CPQ 210.8
|W-4157805||Cross-order discount schedules would not consider prior purchases when setting the price of an asset on an amendment quote. This has been fixed.|
|W-4327572||This bug occurred when you contracted an order that contained a percent of total product and subscribed assets, renewed the contract, and then contracted the renewal quote. The renewal contract would not contain all your subscribed assets. This has been fixed.|
|W-4342129||Improved processing functionality for amending or renewing subscriptions across multiple contracts|
This patch is for Salesforce CPQ 210.7
|W-4166398||This bug occurred when users added two copies of a nested bundle to a parent bundle via the option selection method Add. If those nested bundles contained twin fields that each had a different value, the second bundle's twin field value overwrote the first bundle's twin field value. This has been fixed.|
|W-4257068||Salesforce CPQ did not create price tiers correctly for block-priced products if the Block Price record did not have a Pricebook lookup. This has been fixed.|
|W-4312104||Users can use block pricing with slab Discount Schedules as long as the lower bound of the first slab discount tier equals the upper bound of the last block tier.|
|W-4331948||Users upgrading from 210.4 to 210.5 encountered errors when running the 210.5 post-install script. These have been fixed.|
Subscription Products now have a Root ID field. Salesforce CPQ populates this field on net-new (non-revision) bundled subscription products. The Root ID reflects the Record ID of the bundle parent that was first added to the Quote. (I.e., the net-new child of an amended parent product would have a Root ID that matched the original parent's Record ID, not the amended parent's Record ID.)
Previously, Salesforce CPQ evaluated every subscription record on the Renew Subscriptions page when identifying related subscriptions from a given bundle. Identifying and choosing only the bundle parent improves processing time during the Subscription renewal process.
|W-4352056||Cloning a Quote Line Group (by selecting the Clone Group action) did not clone custom Quote Line Group fields. This has been fixed.|
This patch is for Salesforce CPQ 210.6
|W-4180185||This bug occurred in some cases for users who amended a contract to change the quantity of an asset covered by a percent of total subscription. Renewing this contract caused the renewed percent of total subscription to have an amount of zero on the renewal opportunity This has been fixed.|
|W-4276232||This bug occurred for products covered by a cross-order discount schedule. These products received incorrect discount calculations when a customer owned the exact quantity of a pricing tier's lower bound. This has been fixed.|
|W-4313773||This bug occurred sometimes when users created a quote on an opportunity in an org with Large Quote Experience enabled. In this case, the Customer Amount on the opportunity line items would be equal to the Customer Amount on the corresponding quote line items. Fixed so that the Customer Amount on the opportunity lines inherits its value from the Net Total on the related quote lines.|
This patch is for Salesforce CPQ 210.5.1
|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-3832224||Salesforce CPQ now displays error messages indicating improper price rule configuration for price rules with a lookup object and lookup source field but no lookup query.|
|W-4163812||During initial bundle configuration Salesforce CPQ would display pre-selected options above non-pre-selected options, ignoring feature number or option number. This has been fixed.|
|W-4230631||This bug occurred when users changed a field value on a quote line while using quote line drawers, then cloned that quote line. In some cases, Salesforce CPQ applied the changed field value to another non-cloned quote line. This has been fixed.|
|W-4240312||Revised Attribute Item detail page layout|
|W-4241027||Twin fields between a quote line and an opportunity product would not map when an org had large quote experience enabled and quote lines (on a related quote) that exceeded the large quote threshold. This has been fixed.|
|W-4249153||This bug occurred on the Renew Subscriptions page when users filtered subscriptions. If the number of subscriptions displayed moved from greater than 100 to less than 100, Salesforce CPQ would disable the Select All checkbox. Fixed so that Salesforce CPQ does not disable the Select All checkbox in this scenario.|
|W-4252392||Changed default contract line item date filters from a single field to a range|