#CPQ5 discussing

What I'm building

A custom Lightning Web Component that embeds inside a cloned Product Configurator Screen Flow (the standard "Save As" third-party-configurator extension pattern — lightning__FlowScreen). The component calls the Product Configurator Business APIs directly via Apex HTTP callout (Named Credential auth, OAuth 2.0 Client Credentials Flow via an External Client App — not UserInfo.getSessionId(), which is rejected for interactive-UI sessions anyway).

Environment

• Developer Edition org with Revenue Cloud / Agentforce Revenue Management enabled (enableProductConfigurator = true)
• API version v64.0
• Not a scratch org, no source tracking — deployed directly
• Native in-app configurator UI works correctly for the running user; this is only about the headless REST layer

What works

POST /services/data/v64.0/connect/cpq/configurator/actions/configure — works reliably. Returns transactionContext.SalesTransaction[].SalesTransactionItem[], prices lines correctly, runs configuration rules, surfaces rule violations in messages. This endpoint alone is not gated.

What fails

Every other documented action in the same family returns a 403:

POST /services/data/v64.0/connect/cpq/configurator/actions/load-instancePOST /services/data/v64.0/connect/cpq/configurator/actions/get-instancePOST /services/data/v64.0/connect/cpq/configurator/actions/add-nodesPOST /services/data/v64.0/connect/cpq/configurator/actions/save-instance

Response body:

{  "errorCode": "FUNCTIONALITY_NOT_ENABLED",  "message": "[IHeadlessConfiguratorFamily]"}

(403 status, same error regardless of payload shape or whether the call carries a transactionContextId.) 

#Revenue Cloud  #Salesforce Revenue Cloud  #Lightning Product Setup Configurator  #CPQ  #Revenue Management System @* Salesforce Revenue Cloud *

Hello, 

I am trying to understand best practice for discount schedules when applying to a brand new sale and when applying to an amendment. Here are the scenarios:

1. New Sale - pulls in current discount schedule. The discount schedule is using either the SBQQ__Quantity__c field or a custom quantity field. Cross Orders is checked true. Some discount schedules have aggregation scope blank and some have aggregation scope set to Product.
2. Amendments - subscriptions lines being pulled in through the amendment process apply the original discount schedule as expected. Any new lines added are applying old discount schedules without a tier. But we want the new discount schedule to apply to new lines. Things to note are in number 1 above the SBQQ__QuoteLineQuantityField__c and the fact that Cross Order is checked as true. I have written a price rule that does the following and is working as expected on the new lines but I am not getting the Discount Tiers. Do I need an additional price rule to apply the tier or do I need to create duplicate Discount Schedules that look at the SBQQ__EffectiveQuantity__c field for amendments?
   1. Price Rule Header
      1. Evaluation Scope: Calculator
      2. Lookup Object: SBQQ__DiscountSchedule__c
      3. Calculator Evaluation Event: Before Calculate
   2. Price Conditions
      1. SBQQ__Existing__c equals false
      2. SBQQ__Product__c not equal to blank
   3. Lookup Query
      1. Query 1
         1. Tested Object: Quote Line
         2. Match Type: Field Value
         3. Tested Field: SBQQ__Product__c
         4. Operator: equals
         5. Lookup Field: SBQQ__Product__c
      2. Query 2
         1. Tested Object: Quote
         2. Match Type: Field Value
         3. Tested Field: SBQQ__PricebookId__c
         4. Operator: equals
         5. Lookup Field: SBQQ__Pricebook__c
      3.   Query 3
         1. Match Type: Static Value
         2. Tested Value: true
         3. Operator: equals
         4. Lookup Field: Active_for_New_Quote_Lines__c
      4.  Query 4
         1. Match Type: Static Value
         2. Tested Value: 2026
         3. Operator: equals
         4. Lookup Field: APricing_Year__c
   4.  Price Actions
      1. Price Action 1
         1. Target Object: Quote Line
         2. Target Field: SBQQ__DiscountSchedule__c
      2. Price Action 2
         1. Target Object: Quote Line
         2. Target Field: SBQQ__DiscountSchedule__c
         3. Source Lookup Field: Id

Thank you. 

Hi Kugamoners, 

Kugamon v10.4 is here!

🚀 

We’re continuing to enhance the Kugamon experience with new configuration controls, improved Salesforce Lightning compatibility, and a more consistent user interface. 

✨ New Features & Enhancements:

• Added new Hide Configuration Option setting to the [Manage Configuration] function.
• Updated the Quote and Order Lightning Configurator [Edit Lines] to support the new Hide Configuration Option setting.
• Updated [Manage Configuration], [Manage Kit/Bundle], and [Manage Catalog] functions to support Salesforce Lightning Design System (SLDS2).
• Updated Product Name Font for improved consistency across all views in Manage Catalog, Manage Kit/Bundle, Manage Configuration, and Quote and Order Lightning Configurator [Add Lines].

These updates continue our commitment to delivering a seamless, modern, and powerful Quote-to-Cash experience directly within Salesforce. 

Have questions or feedback? Drop us a comment below! 

Cheers, 

Customer Success Team 

#CPQ #Quotetocash #Kugamon #SalesforceApps #SaaSInnovation #ReleaseUpdate #RevopsWith

Kugamon Major Release v10.3 is live! 

We're excited to deliver performance enhancements, UI improvements, and support for the latest Salesforce platform updates to help keep your Quote-to-Cash processes running smoothly. 

Enhancements: 

• Updated Line Description positioning in Quote, Order, and Invoice PDF Templates to align with equivalent Online Template layouts. 

• Updated Line Description positioning in the Quote and Order Lightning Configurator for a more consistent user experience. 

• Refactored Quote and Order page load and line update logic to optimize performance. 

• Updated the Quote and Order Lightning Configurator to support Salesforce Lightning Design System (SLDS2). 

• Added support for Salesforce Lightning Design System changes introduced in the Salesforce Summer '26 Release. 

This release focuses on improving usability, consistency, and performance while ensuring continued compatibility with the latest Salesforce innovations. 

Have questions or feedback? Drop us a comment below! 

Cheers, 

Customer Success Team 

At Kugamon, we believe successful Salesforce projects start with understanding the customer's goals before a single solution is designed. 

We're grateful for this feedback from Christiaan Feast

, who recently worked with our team during the discovery and scoping phase of a new initiative: 

Early project planning is one of the most important stages of any Salesforce implementation. Taking the time to ask the right questions, understand business requirements, and provide meaningful guidance helps set the foundation for long-term success. 

Thank you, Christiaan, for your kind words and for trusting Kugamon to be part of your journey. 

If you're evaluating solutions for CPQ, Quote-to-Cash, Revenue Operations, or Salesforce transformation projects, we'd love to connect. 

#Kugamon #Salesforce #CPQ #Quotetocash #DigitalTransformation

Hi Kugamoners, 

Kugamon v10.0 and v10.1 are here! 

We’re excited to introduce major enhancements focused on payment processing, operational efficiency, and platform modernization for your Quote-to-Cash workflows inside Salesforce. 

New Features & Enhancements: 

• Copy & PasteAdded Stripe Processor Connection Support 

• Updated the Online Payment Page to support Stripe Payment Processing 

• Added new Lightning Payment Terminal for Orders and Invoices supporting both Stripe and Manual Payments 

• Updated descriptions for all Validation Rules 

• Deleted deprecated object: Custom Payment Source 

🐞 Fixes (v10.1.1): 

• Resolved issue preventing Orders with Service Lines from releasing by updating the creation logic for related Service Delivery records 

•Fixed Payment Terminal cancel return behavior from the new Payment Page 

These updates continue our mission to deliver flexible, modern, and Salesforce-native Revenue Operations solutions. 

Have questions or feedback? Drop us a comment below! 

Cheers, 

Customer Success Team 

#SaaSInnovation

“A new bar for RevOps.” 

We’re incredibly grateful for this thoughtful review from Dave Moudy and proud to share it with the Kugamon community. 

Hearing that Kugamon helped simplify quoting, collections, renewals, and onboarding — while reducing implementation time from months to weeks — is exactly why we do what we do. 

One line especially stood out to us:

We’ve included a screenshot of the full review so you can read it directly in Dave’s own words. 

Thank you to Dave AND every customer who trusts Kugamon to power their Revenue Operations inside Salesforce. 

#Kugamon #CPQ #Quotetocash #Salesforce #RevenueOperations