What should the Revenue cloud consultant recommend to address the issue?

Universal Containers is reporting a platform governor limit issue while saving a quote with a large number of quote line items.

What should the Revenue cloud consultant recommend to address the issue?
A . Enable the CPQ package setting for “quote batch size” to a value which is less than the number based on the volume testing to avoid platform gov.limits
B . Enable the CPQ Package setting for “Large Quote Experience”
C . Enable the CPQ package setting for “Large Quote Threshold” to a value which is less than the number based on the volume testing to avoid platform gov.limits
D . Enable the CPQ package setting for “Large Quote Threshold” to a value which is less than the number of lines which triggered the error during testing.

Answer: D

Explanation:

The Large Quote Experience is a feature of Salesforce Revenue Cloud that allows businesses to handle quotes with a large number of quote line items more efficiently and avoid platform governor limit issues. The Large Quote Experience optimizes the performance of the Quote Line Editor and the Quote Calculator by using asynchronous processing, caching, and pagination. By enabling the Large Quote Experience, businesses can improve the user experience and reduce the risk of hitting CPU time, heap size, or SOQL query limits when saving or calculating large quotes. The Large Quote Experience can be enabled by setting the CPQ Package setting for “Large Quote Experience” to True. The Large Quote Experience also requires the CPQ Package setting for “Quote Batch Size” to be set to a value between 50 and 200, which determines the number of quote line items processed in each batch. The optimal value for this setting depends on the complexity and configuration of the quote line items

Reference:

https://rainmakercloud.com/blog/2022/07/12/5-ways-to-overcome-governor-limits-in-salesforce/

https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_limits_intro.htm

Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments