Salesforce CPQ

Setting the Order Status to Activated should run the triggers and perform the same actions as using the button.  

Note that Order creation runs some async processes that must complete before you Activate. Check the documentation for this. Some of the processes include creating price schedules (if needed) or contracting an amendment (if needed). You may need to build in a delay before triggering activation automatically. There may be some documentation or a knowledge article with more details. 

-Frank 

Antonio - I just tested this out and was able to update a quote line field with the script outside of the cart.  I tested both the Calculate button on the quote as well as triggering a re-calc by updating a field in the Calculating Fields field set.  In both scenarios, the script ran and I am seeing my desired outcomes (in my case, I am simply updating a quote line text field via the script).

Have you tried all of the methods available with the QCP?  Something has to be getting in the way of the calculate.

Hi Subham 

Salesforce Billing's managed package triggers generally can't be selectively disabled from custom Apex. If CPQ/Billing automatically rolls Usage records into Usage Summaries, there isn't a supported API to bypass the trigger for only one Usage Type (such as Rebate). A better approach is to:

•  Verify whether the managed package provides a custom setting, custom metadata, or feature flag to exclude specific usage types. 
•  If possible, prevent Rebate usage records from being processed by the Billing engine through configuration rather than trying to disable the trigger. 
•  If you're creating Usage records in a scheduled Apex job, consider staging the rebate records in a custom object and only creating Billing Usage records for the types that should be summarized. 

If this behavior isn't configurable, I'd recommend opening a Salesforce Billing support case, as managed package trigger behavior isn't intended to be bypassed from custom Apex. 

Best, 

Golla

Hi @Melissa Driscoll,

If the tax field already exists on your Quote, you can add it to the Quote Template by creating a Template Content or Template Section that references that field. 

If you're trying to display Subtotal, Tax, and Total together at the bottom of the quote, another option is to create custom merge fields or use a custom HTML content block, depending on how your template is configured. 

Are you using the standard CPQ Quote Template, or a custom template with Template Sections and Line Columns?

@Ragini Shukla

This is awesome detail. And answers questions that have come up through some digging and thought this week.  

1. Create New Products
   • Should these new products have the same product code? Thinking of billing on current contracts (especially multi-year contracts)
   • We use bundles so that will mean rebuilding all bundles as well. Along with all product rules no matter the type and possbily price rules need to be re-evaluated.
   • How is this handle during the Add Products process? We now have duplicate, for lack of a better word, products. 
   • How is this handled during Amendments when we are doing a rip/replace or adding a new product?
2. New Sales
   • You mention product selection rules - what do you mean by this statement? That on new sales we say use the product flagged as let's say "new pricing" or one that is not flagged as "legacy"?
   • Can you clarify on what is meant by "deactivation" flags? Is that similar to what I mentioned in the above bullet point?
3. Amendments
   • What if we are doing an amendment where we are doing a rip/replace and we need to keep historic pricing? Do I need a price rule that somehow says which product to select?
   • If we want to add a new product and adjust the quantity on an old product? How is that handled? You end up with mixed prce models.
4. Renewals
   • I know in CPQ you can use the "Renewal Product" field to map from an old product to a new product but how accurate is that if there is a bundle for example?
   • How does this mapping work in terms of Multi Year Contracts.

I think some of my difficulty is how they do contract creation and maintenance here. They have some customization (that I don't know yet how it works) that the time of contracting an order 

1. New Sales
   1. For a new customer it creates a contract called "Master Agreement" which has the 36 month term (or whatever the term of the contract is. Set via a field on the quote). It does not have any subscriptions tied to it and it is not used during the renewal process.
   2. It also creates a contract called "Subscription Agreement" which is 99% of the time for 12 months and creates the first 12 months worth of subscription within that 36 month contract. It does not create one contract for all three years and it does not create individual contracts for each year. Only the first year.
2. Renewals
   1. Many Renewals go through an auto renewal process for the second or third renewal so it isn't necessarily being reviewed by a Sales Team. Do we continue that?
      1. At the end (last 90) days of year 1 they create a renewal opp via renewal forecasted that is called a Subscription Renewal opp and then a quote is created like 7 days before the Renewal Date and it auto renews.
      2. Then it does the same process for year 2 and at then the same to create Year 3.
   2. At the end of the third year (last 90 days) the system creates a renewal opp via renewal forecast that they call a Contract Renewal Opportunity. The quote is then generated with quote that has a Contract Term of 36 and a Subscription Term of 12. And once closed begins the process of having a new Master Contract and a new Subscription Contract. How would we handle the pricing switch then if we have to maintain historical pricing until Contract renewal.