By: John Garvens

Revenue Cloud | 12:55

• The speaker plans to give an overview of Revenue Cloud, including its history and where it is going, using official Salesforce documentation and release notes
• Revenue Cloud has a complex history that dates back to CPQ (Configure, Price, Quote) tools
• The founders of BigMachines created a CPQ tool that was later sold to Oracle
• The same founders then created SteelBrick, a CPQ tool built on the Salesforce platform 

BigMachines to Oracle CPQ | 13:56

• BigMachines was a CPQ tool that was acquired by Oracle and rebranded as Oracle CPQ
• Oracle CPQ is still being sold and used by companies today

SteelBrick CPQ to Salesforce CPQ | 15:10

• SteelBrick was a CPQ tool built on the Salesforce platform, founded by the same people who created BigMachines 
• Salesforce acquired SteelBrick in 2015 for $300 million and rebranded it as Salesforce CPQ
• Salesforce CPQ is a product that many users are familiar with, and it has been used and implemented by hundreds of customers

Salesforce Billing | 21:30

• Salesforce Billing was first an acquired company, later remade into the current version, with most users now on version 2.0
• Salesforce Billing is a managed package, priced based on revenue processed, differing from Salesforce CPQ's per-user pricing model
• Salesforce Billing serves as the central hub for billing, with necessary knowledge available, although documentation may not always keep up with releases

Salesforce Introduces Salesforce Revenue Cloud | 24:20

• Salesforce CPQ and Billing became part of a cloud, initially branded as Salesforce Quote to Cash, later rebranded as Salesforce Revenue Cloud
• Becoming a cloud was a significant milestone for Salesforce, with Revenue Cloud being a major cloud at the time
• Salesforce Revenue Cloud includes CPQ, Billing, and other functions, now a standard cloud offering 

Subscription Management vs. Subscription Management | 25:32

• There are two different products: CPQ's subscription management and a separate Subscription Management product
• CPQ's subscription management is a function for managing subscriptions on contracts, while the separate product is an independent core product for managing subscriptions 
• The separate Subscription Management product is end-of-sale and will be replaced by Revenue Lifecycle Management 

Revenue Lifecycle Management to Revenue Cloud | 28:22

• Revenue Lifecycle Management is the next iteration of the product, now also referred to as Revenue Cloud 
• Revenue Cloud includes functions such as product catalog management, pricing, and rate management

Vlocity to Industries CPQ to Salesforce Industries | 29:00

• Salesforce acquired Vlocity in February 2020, which led to the development of Revenue life cycle management, a new product built on the Salesforce core platform.
• Revenue life cycle management is not a managed package, unlike Salesforce CPQ and Salesforce billing, and is more of a Vlocity 2.0 than a SteelBrick 2.0.
• The new Revenue Cloud is a result of merging two different CPQ tools acquired by Salesforce in 2015 and 2020.

Customer Asset Lifecycle Management | 35:04

• Customer Asset Lifecycle Management was a CPQ function that required a billing license and later became Asset Lifecycle Management and then Asset Management.

Order Management vs. Order Management vs. Manufacturing Cloud | 35:37

• Order management is part of the CPQ package, but there is also another order management product as part of the Manufacturing Cloud.

Conclusions and Predictions about Salesforce Revenue Cloud | 36:25

• Revenue life cycle management, which will be rebranded as Revenue Cloud, is the future of Salesforce Revenue Cloud.
• The product will continue to evolve and develop, and there is a lot to learn about its new features and capabilities.

Further reading about Salesforce Revenue Cloud | 37:28

• Salesforce Revenue Cloud was introduced in November 2020, transforming revenue lifecycle management
• Revenue Cloud includes product catalog management, price management, transaction management, CPQ, and contract lifecycle management
• Dynamic Revenue Orchestration is a feature that helps with demand planning, inventory management, and provisioning
• Omni Channel buying and selling is a core feature of Revenue Cloud, allowing for direct sales, partner sales, and self-service
• Revenue Cloud is a commercial system that helps businesses make money and manage different tools, systems, and processes

Comparing Star Trek and Salesforce Revenue Cloud | 42:03

• Revenue Cloud is like the next generation of revenue lifecycle management, with new features and enhancements
• The creator of Revenue Cloud is still making money from similar products, but with new and improved features

The Future of Salesforce Revenue Cloud | 47:56

• The product is currently frustrating to use, but its future looks bright with continued investment and development from Salesforce
• The product will evolve and improve over time, similar to any new software or product 
• Building something that will stand the test of time takes time, effort, and patience

By: Jean-Michel Tremblay

Introduction | 0:00

• Revenue Lifecycle Management (RLM) is a composable revenue management platform for unified product to cash, allowing for Omni Channel buying and selling
• RLM is built on the Salesforce platform and will be explored in the discussion
• The discussion will cover the pillars that make up RLM and include demos for each 

• RLM is a platform that allows for unified product to cash, enabling Omni Channel buying and selling 
• It is a composable revenue management platform, allowing for automation, AI, and API-first integration

Key Features of Revenue Lifecycle Management | 0:30

• RLM is built on the Salesforce platform, allowing for automation and AI
• It is API-first, enabling easier automation and integration with existing solutions
• RLM provides a unified tool for product to cash, allowing for easier management

Revenue Lifecycle Management Pillars | 1:05

• The composable product catalog and pricing pillar provides a centralized model for products and pricing methods 
• Transaction Management in CPQ offers a new line editor and transaction line editor for building quotes and orders
• Asset and subscription management allows for the creation and tracking of assets and subscriptions 

Product Catalog Management | 2:41

• Product catalog management allows for the organization and management of products and catalogs 
• It enables the creation of product attributes and classifications, which can impact pricing and downstream processes
• Product life cycle management allows for the management of products across all sales channels

Salesforce Pricing | 7:12

• Customizable pricing procedures with a price waterfall, offering total control over how it's built and calculated
• Different price adjustment methods, including price adjustment tiers, volume tier-based pricing, attribute-based adjustment, bundle base adjustments, and contract pricing
• Centralized pricing management available through the API, allowing for leverage on external tools

Salesforce Pricing Demo | 8:18

• A price waterfall feature shows the different inputs that affect the final price of a product
• The pricing procedure is fully editable, with customizable order of operations and the ability to add steps and elements

Product Configurator | 10:06

• A customizable screen flow that allows for automatic selection or restriction of product options
• Configuration rules can be built on top of the product configurator to control the user experience

Product Configurator Demo | 10:48

• The product configurator is a standard screen flow that can be modified to fit specific needs
• Instant pricing can be enabled to show price updates in real-time as selections are made

Quote and Order Capture | 12:53

• A new transaction line editor allows for editing quote lines and ordering products
• Quote and Order capture is available through the API, enabling easy creation of quotes and orders from external systems

Quote and Order Capture Demo | 13:27

• The quote and Order capture screen allows for modifying quantities, discounts, and adding products
• The screen is available for both quotes and orders, with pricing updates in real-time 

Asset Lifecycle Management | 14:46

• Asset lifecycle management provides a new screen on accounts to amend, cancel, and renew assets, and view current and historical MR for a given asset
• Assets are created automatically through a flow available out of the box, typically triggered on order activation
• Asset lifecycle management is available through the business API, allowing customers to control their own assets on different platforms

Asset Lifecycle Demo | 15:39

• The managed assets component on an account shows all the assets a customer owns, including start and end dates, and options added to bundles
• The asset detail page provides a dashboard to view the evolution of quantity and MR through amendments
• Assets can be selected for amendment, renewal, and cancellation, which can create a new quote or be sent directly to orders

By: Cloud | Salesforce

Revenue Cloud Overview | 0:36

• Revenue innovators are pioneering a future where the buying and selling experience is faster, easier, and more personal, with the all-new Revenue Cloud featuring API-first design and AI-driven automation.
• The new Revenue Cloud supports hybrid revenue models, multi-channel selling, and provides a unified revenue platform, allowing companies to manage complex products and services seamlessly.
• The Revenue Cloud platform can support one-time charges, subscription, evergreen subscription, usage-based, or consumption models, all in a single quote, and leverages AI to help users make data-driven decisions.
• The platform's journey started with building a product catalog and price engine, followed by orders and quotes, contracts, dynamic revenue orchestration, and most recently, invoice management on core and consumption-based selling.

User Persona-Driven Experiences | 11:21

• The Revenue Cloud features user persona-driven experiences, allowing product and pricing administrators to take products to market faster, with a visual builder for product administrators and dynamic attributes.
• Revenue Cloud offers hierarchical product models with templates for faster rollout to the market, as well as a visual drag-and-drop editor for pricing administrators to create pricing flows.
• The platform provides simulation capabilities to roll out changes with confidence and supports various pricing models, including volume, tier, and attribute pricing.
• Revenue Cloud offers an Excel-like experience in the transaction line editor, allowing for inline edits, column freezing, filtering, and more, all driven by rules and pricing.

Integrations and Customer Success | 15:11

• The platform integrates with Slack and Einstein to drive customer success, enabling users to access contract information, create renewal quotes, and more.

Product Catalog and Pricing | 17:03

• Revenue Cloud features product catalog management, which guides users through the sales process and provides a rich set of capabilities.
• The platform supports consumption-based or usage-based selling, allowing customers to buy in various ways, and features a pricing engine that clearly describes the price waterfall.
• Revenue Cloud also enables consumption-based pricing, supporting one-time, subscription, and usage-based models, and provides a clear understanding of pricing and discounts.

Automation and Channel Integration | 19:24

• The platform integrates with Einstein to automate tasks, such as creating tasks for the legal team to review and modify contract clauses.
• Revenue Cloud is designed to work with various channels, including Slack and direct selling channels, and provides the right user experiences regardless of the channel.
• Contracts can be used in the flow of work, making it easier for the end-to-end flow, and innovations with contracts include AI.

AI and Contract Management | 21:08

• Revenue Cloud is for everyone who wants to touch revenue throughout the lifecycle of a sale, and it brings critical information to the front office.
• The power of AI and vector search can be utilized to find relevant contracts and clauses, reducing the need for manual searching and increasing efficiency.
• Contract comparison is a new innovation in Revenue Cloud, allowing users to compare different versions of a contract and see the changes made.

Dynamic Revenue Orchestrator and Order Management | 26:07

• Dynamic Revenue Orchestrator is a feature that automates and intelligently decomposes orders, creating a fulfillment journey based on the products and services ordered.
• Revenue Cloud brings order management online, providing transparency and visibility into the flow of work and delivery of products to customers.
• Fulfillment plans show the flow of work and delivery of products, and provide visibility into any issues or delays, allowing for quick rectification.
• Revenue Cloud is designed to drive revenue success by bringing together sales, service, and finance teams to maximize customer success, with features such as fulfillment plans and invoice management.

Unified Platform and Best Practices | 36:23

• The platform provides a single platform for quote-to-cash processes, including CPQ, contract management, and billing, reducing the risk of integrations and common data model issues.
• Revenue Cloud has inherent best practices and standard industry practices built into it, allowing companies to leverage native capabilities and keep things simple to accelerate growth in the subscription space.

Revenue and Subscription Analytics

• The platform also provides revenue and subscription analytics, enabling companies to report on their contracts, subscriptions, and renewals.

By: KavaliroTV

RLM Architecture and Integration with Salesforce Billing and RightRev | 0:53

• The architecture being demoed includes RLM core objects, Salesforce Billing, and Right Rev, which work together to enable automated revenue recognition. 
• Right Rev is a product built on the Salesforce platform that uses activated orders to automatically create revenue contracts, which reference preconfigured revenue rules for complete revenue recognition management.

Creating a Quote and Order within RLM | 1:37

• Within the Salesforce Revenue Lifecycle Management app, an opportunity, quote, and associated account have been created, along with a few objects to make navigation easier. 
• Adding items within Revenue Lifecycle Management is simple by clicking "Browse Catalogs" and selecting the desired catalog, which displays an assortment of products and categories. 
• The demo showcases configuring a desktop product by selecting attributes such as screen size, graphics card, memory, and storage, which can be reused across product offerings. 
• The configured product is then saved, and the sales process is simulated by approving the quote, marking it as the current status, and creating an order from the quote. 

Salesforce Billing Integration and Product Configuration | 3:49

• The demo highlights the handshake between sales, provisioning, or fulfillment, and Salesforce Billing, which requires automation to fill out necessary fields such as billing type, billing frequency, and charge type. 
• The product selling model is set to one-time, which is a feature of Revenue Lifecycle Management that allows assigning multiple product selling models to a single product, enabling a more scalable and flexible product catalog. 
• The charge type for a product is set to one-time, which is determined by automation that matches the product selling model to the frequency of charging for the product, and the automation also sets the legal entity, billing rule, and billing treatment.
• For an antivirus product, the charge type is set to recurring with a billing frequency of annual, and automation helps fill out essential billing fields.

By: Anuj Vaishampayan (Stratus Carta) Salesforce Apex Hours

Introduction | 0:00

• Revenue Cloud (formerly RLM) is a solution for CPQ and DRO, and it was rebranded in September 2024 during Dreamforce 2024
• The correct product name is Revenue Cloud, not Revenue Cloud Advanced, which is a flavor of the product
• The solution is part of Salesforce Industries and provides expert services for communications, media, energy, and revenue cloud

Product Configurator | 3:34

• Product Configurator behaves like a CPQ, allowing customization of templates and configuration screens
• It supports different scenarios such as amend, renew, cancel, and add, and falls under CPQ
• Product Configurator gives users the capability to raise orders correctly, validate instantly, and run pricing with a user-friendly interface

Summary Panel | 5:27

• The Summary Panel provides a rich experience for sales agents, showing the items added, configurations, and pricing
• It helps sales agents to quickly configure or add product attributes and view the product and its configurations 

Key Features | 6:41

• Instant pricing and product configurator gives the capability to calculate and update prices in real-time 
• Configuration summary overview provides a summary of the product configuration, including selected attributes and prices 
• Real-time product validation instantly runs validation against the product as changes are made
• Actionable error messages present error messages on the product configurator screen to help rectify errors
• Customizable templates are provided to build a flow using the flow builder 
• Preview and assign template allows previewing the product configuration screen during design time
• Configuration rules help configure the product correctly to avoid errors during provisioning 

Key Terms | 10:29

• Summary component displays the summary of the configured bundle or simple product and provides real-time updates
• Option groups allow showing child products available inside a bundle and selecting them 
• Message component displays error, warning, or information messages on the screen 
• Default product configurator flow is a pre-built flow that drives the product configurator's appearance and screen flow 
• Instant pricing gives the capability to price the product in real-time during configuration 
• Product validation triggers rules or shows messages to validate the product and enhance performance
• Rules scope defines the scope or boundary for a rule's execution 

Flow Components | 13:11

• Product header serves as the main header for product configuration and provides essential details 
• Product attributes allow users to configure attributes for a product 
• Pricing summary component provides a real-time overview of the total cost and individual cost for a product 
• Data manager is an invisible flow component that maps config data between context and context definition and UI 

Product Configuration Flow | 16:07

• The product configuration flow allows users to map a flow to a product, assign products to a template, and assign product classifications to a template.
• Users can search for the product configuration flow from the App Launcher and create a new configuration flow or use an existing one.
• The flow can be used to assign products or product classifications to a template, giving users the capability to map to a single product or multiple products under one classification.

Product Configuration Preview | 17:28

• The product configurator preview feature allows users to see how their configuration screen will look like for a particular product.
• A preview button is available on the product configuration screen, enabling users to visualize how their product will look like on the console.

Product Configuration Overview | 18:33

• The product configurator feature allows users to update quantity, configure attributes, and configure add-ons available under a plan.
• Users can see default options available for a product, attribute categories, and attributes under each category.

Realtime Pricing Instant Validation | 19:37

• The product configurator screen has toggles for instant pricing and product validation, allowing users to instantly price a product or validate it.
• Users can choose to enable or disable these toggles, keeping in mind that enabling them may impact performance.

Configuration Rules | 22:49

• Configuration rules are important for any CPQ (Configure, Price, Quote) system, helping to run business rules, validate order codes, and guide salespeople through the sales journey.
• There are different types of configuration rules, including validate, exclude, require, auto-add, auto-remove, and set attribute.
• Configuration rules can be used to present messages, such as validation, warning, or information messages, to inform sales agents and guide them in making informed decisions.

• A rules library is a prerequisite for creating and executing configuration rule.
• When creating a rule, it is essential to define the context, scope, and conditions for the rule to execute.
• Configuration rules can have multiple conditions and actions, and can be used to set attributes, quantities, and execute business rules.

Amendment configuration | 31:47

• Amendment configuration is a crucial topic in Revenue Cloud, where users can modify assets by amending, renewing, or canceling them.
• The product configuration screen allows users to update pricing, view changes, and execute amend, renew, and cancel scenarios.
• The screen provides a clear picture of changes made during asset modification scenarios.
• There is a configuration flow for executing amend, renew, and cancel scenarios, which can be defined under Revenue Cloud settings.

• Users can create a flow by providing a name and configuring settings to identify and execute the flow.
• This flow helps users run scenarios for amending, renewing, or canceling products or assets.

Asset management | 35:02

• The asset tab allows users to manage assets, view a list of assets under an account, and select assets to proceed with amend, renew, or cancel scenarios.
• Users can trigger the desired flow for selected assets using buttons.

Third-party configurator support | 36:07

• Third-party configurator support allows users to integrate third-party UI components with the product configurator.
• APIs can be invoked to drive the sales flow, and users can develop custom widgets to integrate with the configurator.
• The third-party configurator provides headless config APIs to integrate with custom UI components.

Dynamic Revenue Orchestration Features | 41:37

• DRO enables businesses to decompose and orchestrate the order process with ease, allowing for the breakdown of products into fulfillment line items or products used by fulfillment plans.
• Key features of DRO include decomposition, which breaks down orders into several tasks or sub-orders to help the fulfillment process.
• Orchestration coordinates the fulfillment process, deciding the sequence of tasks to ensure accurate order fulfillment.
• Geopard management proactively monitors potential risks and creates alerts to help keep the order fulfillment process on track.
• Fallout management handles errors or exceptions that occur during the order fulfillment process, integrating with downstream systems or third-party systems.

DRO Functional Architecture | 45:52

• The functional architecture of DRO involves orders created using catalog data, pricing, product rules, and metadata, which are then submitted to the DRO engine for decomposition and orchestration.
• The decomposition engine breaks down products into several fulfillment requests, which are executed by the orchestrator according to predefined plans.
• The orchestration plan consists of several tasks that integrate with third-party systems, handle SLAs through geopard management, and handle exceptions through fallout management.

Prerequisite for DRO | 47:48

• DRO is not enabled by default in Revenue Cloud, and users must go into the dynamic revenue orchestrator setting to switch it on.
• Separate settings are available for switching on fallout and geopard management, which can be enabled or disabled as needed.

Design Time Decomposition | 49:00

• Design time decomposition involves planning how products will be decomposed into technical products and how they will be utilized for orchestration processes
• This process occurs during business requirement gathering and understanding the fulfillment process
• Decomposition can be set up through the fulfillment designer, where decomposition mappings and fulfillment processes can be created and designed

• Decomposition rules control the decomposition process by defining a set of rules and priorities 
• Conditions tell the system on which condition the rule should be executed, and rules can be set up during the design of decomposition
• Field and attribute mapping allows for the creation of mappings for fields and attributes during design time 
• Configure list mapping is a feature that allows for the creation of mappings for multiple values and characteristics
• Decomposition scope defines how products are decomposed into fulfillment requests, with options including orderline item, order, bundle, and account
• Each scope determines how many fulfillment requests are generated, such as one per orderline item or one per bundle
• The decomposition scope is set to orderline item by default if not specified

Fulfillment Designer | 1:04:38

• Fulfillment designer is used to create and visualize the fulfillment process, including defining fulfillment steps and dependencies
• Fulfillment steps can be linked to external systems or provisioning systems
• Conditions can be added to fulfillment steps to control their execution

Fulfillment Step Configuration | 1:13:53

• Fulfillment steps can be configured with different types, such as call out, pause event, autotask, milestone, and manual task 
• Each fulfillment step type has its own properties and execution properties 
• Dependencies can be created between fulfillment steps, and conditions can be added to control their execution 

Fulfillment Task Type | 1:16:36

• Call out is a task type used for interacting with external systems or fulfillment systems 
• Pause event is a task type that pauses the orchestration plan until a condition is satisfied 
• Autotask is a task type used for processing or preparing data during the fulfillment process
• Milestone is a task type that represents a point of interest in the fulfillment process 
• Manual task is a task type that requires manual input or interaction

Geer Configuration | 1:26:16

• Geer configuration is used to generate alerts or notifications when a fulfillment step is at risk of not meeting its SLA
• Estimated duration and threshold can be set for each fulfillment step to determine when it is at risk 

Fallout Configuration | 1:29:15

• Fallout configuration is used to handle exceptions or errors during the fulfillment process 
• Fallout rules can be defined for each step, including retry policies and error handling 
• Customizable failure handling allows for different rules to be defined for each step or task

Runtime Monitoring | 1:34:00

• Decomposition viewer provides real-time insights into how products are decomposed into fulfillment requests
• Fulfillment plan viewer provides a graphical interface to visualize the fulfillment process 
• Bulk retry allows for multiple failed tasks to be retried in bulk

By: Georgii Saveliev and Anuj Vaishampayan (Stratus Carta) Salesforce Apex Hours

Introduction to Revenue Lifecycle Management (RLM) | 0:03

• The video introduces Revenue Lifecycle Management (RLM), focusing on the product catalog and pricing, and outlines a series of sessions covering various aspects of RLM, including product configurator, dynamic revenue orchestration, and Salesforce contracts. 
• Revenue Lifecycle Management (RLM) is focused on Configure, Price, Quote (CPQ) and Order Management, integrating with Salesforce contracts and potentially other products in the future.
• RLM is built on the Salesforce platform, with Omni Studio providing a richer suite of automation tools, and sits primarily in the sales space, but can also be involved with the service side.
• The foundation of RLM includes a product catalog, where products, prices, and attributes are defined, and is broken into sub-modules such as Product Catalog Management (PCM), Salesforce Pricing, and Business Rules Engine (BR)
• The runtime side of RLM includes CPQ, with sub-modules such as the Product Configurator, Quote and Order Capture, and Salesforce contracts, which generate documents based on quotes and orders
• Order Management, also known as Dynamic Revenue Orchestrator (DR), takes the output of CPQ and breaks it down into smaller technical orders, orchestrating the steps involved in fulfilling the order
• The selection process for CPQ tools depends on the industry, and customers should talk to their Salesforce account team for guidance on which product to use.

Product Catalog Management (PCM) | 20:36

• Product Catalog Management (PCM) is a central piece of any CPQ implementation, where product managers and technical managers configure and manage products, product life cycles, and design-time information.
• Key features of PCM include catalogues, dynamic attributes, product classification, and products qualification tools.
• Catalogues are used to organize products into groups, making it easier for customers or agents to select products when browsing.
• Attributes are characteristics of products that customers or agents can select when configuring a product, and can be categorized and defined inside PCM.
• Product classification is a template that groups attributes or products under a common structure, allowing for inheritance and reuse of product structures and attributes.
• Products in PCM can be classified into simple products and bundle products, which can be further categorized into static and configurable products.
• Product types in the product catalog can be defined as static or configurable, with static products having no changes allowed and configurable products allowing for customization.
• Product selling models define how products are charged to customers, with options including one-time, term-defined, and Evergreen (subscription-based) models.
• Qualification rules determine whether customers are eligible for certain products based on conditions, with two types of rules: simple qualification rules and disqualification rules.
• Qualification rules use predefined product catalog management objects or custom objects, and decision tables to evaluate inputs and generate outputs.
• Product catalog management objects used in qualification rules include product qualification, product disqualification, product category qualification, and product category disqualification.
• The product catalog management entities have similar names to those in Salesforce industry, but with some differences, including category, product selling models, and product classification.

Product Catalog Management App | 40:53

• The product catalog management app allows users to configure various entities such as catalog products, product classifications, and product selling models. Users can create categories and subcategories within catalogs, and assign products to these categories. 
• Attributes and attribute categories can be defined and grouped, with options to configure pick lists and assign attributes to products during runtime configuration.
• Product classifications serve as templates to assign common attributes to products, which inherit these attributes when the classification is applied.
• Products can be simple or bundled, with options to define product details, types, and configurations. Bundles require a product component group to assign child products, and relationships between components can be mandatory or optional.

Pricing and Discounts in Product Catalog Management | 51:21

• Attributes can be marked as price impacting, affecting pricing calculations, and there is a pricing discount calendar feature for product managers. 
• Product catalogs can be viewed in terms of days, months, quarters, half years, or years, and discounts can be applied based on specific criteria.
• There are three types of product selling models: one-time, term-based, and Evergreen, each with its own pricing configuration.
• Qualification rules and procedures are used to determine whether a product is qualified for a specific customer, based on input data such as product ID, customer region, and number of employees.

Salesforce Pricing | 1:00:03

• Salesforce pricing allows for streamlined and optimized pricing strategies, with features such as price calculations, context mapping, and custom formulas.
• Salesforce pricing involves different roles, including price admins, designers, analysts, demand managers, and executives, and supports various pricing rules and categories.
• Context Service provides input data to pricing procedures during runtime execution, acting as a layer between design time and execution.
• Context Service is used to price products, and it consists of context definition, context mapping, and decision tables, which provide a common hierarchical layer to connect various pricing elements and data sources.
• Context definition is a hierarchical or canonical structure that defines how data flows under each node, and context mapping maps nodes and attributes to actual Salesforce objects and fields.
• Decision tables are used for business rules, pricing rules, and discounting rules, and they store input data, field names, data types, and conditions to provide an output or final price.
• Pricing Recipe enables users to create and manage detailed pricing strategies by tying up objects and lookup tables, and it tells what kind of lookup tables are used during pricing execution.
• Pricing Procedure is a customized or ordered stack of pricing elements used to calculate the final price of a product, and it allows users to define input parameters, conditions, and output for each element.
• Price Book is a standard feature that helps define the selling price of a product, and it can create different price books with entries for each product.
• Cost Book tracks expenses associated with creating a product or fulfilling a service, and it defines the cost price and selling price of a product.
• Price books and cost books are used to define selling prices and costs, with the margin between them being calculable. 
• Pricing adjustment schedules allow for customer promotions and discounts, with three types of adjustments: attribute-based, volume-based, and bundle-based.
• Bundle-based adjustments offer discounts when products are purchased as a set, such as a printer bundle under a laptop bundle.
• Attribute-based adjustments provide discounts based on product attributes, like display resolution, allowing for price overrides. 
• Volume-based adjustments encourage bulk purchases by offering discounts based on quantity thresholds. 
• The discount calendar provides a comprehensive view of product discounts, showing when and how different types of discounts apply.
• Pricing rules involve decision tables and adjustment rules to achieve complex or customized pricing solutions. 
• Third-party integration through pricing APIs allows for external pricing execution and customization, with examples of API usage provided.
• Custom objects can be priced using a predefined sales pricing action that requires a context ID and pricing procedure name, and can be invoked via REST or headless APIs. 
• Salesforce provides omnichannel pricing capabilities for both standard and custom objects, allowing for customized pricing solutions without coding, using configuration setups. 

Pricing Setup and Configuration | 1:28:02

• The end-to-end pricing flow involves executing pricing procedures that utilize design-time data, pricing tables, and decision tables to calculate final prices, including list, contract, and discounted prices. 
• The pricing setup requires defining a context service, which acts as the foundation for pricing procedures, and involves configuring canonical structures and attributes for data flow. 
• Attributes such as price adjustment status and list price are configured in the pricing procedure, defining their type, data type, and usage in input or output. 
• Tags are defined for nodes and attributes, which are used in the pricing procedure configuration. 
• Context mapping involves mapping nodes and attributes to their corresponding source fields, allowing data to be fetched and evaluated during pricing calculations.
• Decision tables can be pre-configured or custom-created, defining column names, fields, and operators for pricing or qualification rules.
• Pricing setup includes defining pricing recipes and procedures, synchronizing data changes, and configuring pricing elements like aggregate price assignments. 
• A pricing procedure is a complex pricing structure that can be simplified based on specific criteria, and it can be invoked from an API, flow, or directly from the platform or Apex.
• A price book is used to define the selling price of a product, and it can be configured to define both standard price books and cost books.
• There are three types of price adjustment schedules: volume-based, bundle-based, and attribute-based, which can be used to configure discounts based on different conditions.

Pricing Invocation and APIs | 1:56:27

• Pricing can be invoked from a flow using a predefined action, and the flow can be configured to use a specific pricing procedure.
• Salesforce pricing provides APIs that can be used to invoke pricing from third-party systems or internally using Apex or integration procedures.
• The APIs can be used to get price waterfall details, run pricing, and execute pricing accordingly.

By: Jean-Michel Tremblay

Adding a Product to a Quote | 0:20

• Demonstrates adding a product from the Tesla 2024 catalog to an existing quote, including modifying quantity and discount. 
• Explains the process of saving the quote to trigger recalculation in Revenue Lifecycle Management. 

Creating a New Product | 1:45

• Describes creating a new product in the product catalog, including setting attributes like name, product code, and active status. 
• Details assigning the product to a product selling model and adding it to the price book with a list price.
• Explains adding the product to a catalog category and syncing pricing data to make it available for quoting.

Testing the New Product | 5:54

• Confirms the new product is available in the catalog after syncing pricing data and demonstrates adding it to a quote. 
• Highlights the ability to modify quantity and discount, with pricing updates reflected in the quote.

By: Jean-Michel Tremblay

Creating a new Bundle | 4:08

• A new bundle product is created by going to the products page and creating a new product record
• The product record is configured with details such as product code, product family, and product type (bundle) 
• The product is made active and configured to create assets, with quantity set to "each" 
• A price book entry and product selling model option are added to the product record 
• The product structure is built using the visual bundle creation feature, starting with the parent product

Creating the Bundle Structure | 6:25

• To create a bundle structure, add product groups, which are categories of options available within the bundle.
• Each product group has a sequence, minimum, and maximum selection requirement.
• Add products to each group, specifying the default quantity and whether the product is required or included by default.

Testing the New Bundle | 12:56

• After creating the bundle structure, assign the new product to a catalog and sync the pricing data to make it available for quoting.
• Test the new bundle by adding it to a quote, configuring the options, and verifying the updated pricing.
• The configurator allows users to select options, choose between term-based or one-time pricing, and add products to the quote.

By: Jean-Michel Tremblay

Creating a New Dynamic Attribute | 1:36

• A new Dynamic attribute is created on a different product, with the attribute being a picklist for paint colors on a "Model Y" car.
• The picklist is created under the attributes section of the product catalog homepage, with the attribute being set to active, data type to text, and a description added.
• The picklist values are created, with two colors added: "Black" and "Red", each with a code, status set to active, display value, and sequence.
• The attribute is then created for the "Model Y Paint Color", with the name, label, and API name set, data type set to picklist, and the picklist field set to the created picklist.

• The attribute is set to required, active, and the default value is set to "Black".

Creating a Product Classification | 4:13

• A product classification is created to map the product to the attribute, allowing the attribute to be used in the product configurator.
• To create a product classification, give it a code, set the status to active, and assign attributes that should come along with that product classification, such as the Model Y Paint Bck List, under the attributes tab.

• To assign the product classification to a product, go to the product, edit it, and select the product classification, such as Model Y, under the based on field.

Making the Attribute Price-Impacting | 5:49

• To make the attribute price-impacting, go back to the product classification, edit the attribute, and set is price impacting to True.

Creating a Price Adjustment Schedule | 6:31

• To create a price adjustment schedule based on the attribute value, go to the price management app, select the attribute-based adjustment tab, and create a new one, specifying the product, adjustment type, and adjustment value.
• To select which attribute value triggers the attribute-based adjustment, specify the attribute value, such as paint color equals red, and save the adjustment.

By: Jean-Michel Tremblay

Asset Creation | 0:24

• A quote has been created with products added, including a subscription product for 10,000 miles of allowance for a year, from 11/1/24 to 12/3/24.
• To create assets for this quote, an order needs to be created by clicking the "Create Order" button, which results in the creation of Order 130.
• The order contains all the same products added to the quote, including the car and subscription.
• To create assets, the order needs to be activated by clicking on "Activate" and updating the status, triggering a standard flow that creates assets from the order using an Apex action.
• The Apex action takes over when the order status is updated to "Active" and creates all the assets from the order.
• The created assets can be viewed under the "Assets" tab on the account, showing a list of assets owned, including the subscription product with a quantity of 10,000.
• Clicking on the product shows all the details for that specific asset, including the current quantity, monthly recurring revenue, and evolution.
• The dashboard also shows the related asset actions, including the initial sale for a quantity of 10,000.
• If the customer needs to process an amendment, such as increasing the quantity, this can be done by selecting the parent product and processing the amendment.

Amendment Creation | 2:36

• An amendment is created by clicking on "Amend" and selecting a start date, in this case, May 8, 2024, and then submitting it to create a quote amendment.
• The amendment quote is created in the background through a standard flow that comes with Salesforce Revenue Lifecycle Management, which can be modified to handle different types of outputs and processes.
• Once the quote amendment is created, the products are listed with a quantity of zero, and the total price is zero, as no modifications have been made yet.
• The start dates of the products are updated to the selected start date, in this case, May 8, 2024.
• To modify the quantity, the new quantity to be added to the current total is entered, and the system calculates the new total price based on the remaining time of the year and the price rate.
• After modifying the quantity and saving the changes, the system calculates the new total price, in this case, $1368.
• To update the assets, an order needs to be created, and then the status of the order needs to be set to "Activated" to trigger the asset creation and update process.
• Once the order is activated, the asset creation and update process is triggered, and the assets can be viewed under the account.

Review Amended Asset | 4:12

• The related list can be scrolled down to view the full self-driving asset, which currently has a quantity of 15,000.
• The asset actions section shows the initial sale of $10,000 and the upsell of 5,000 additional paper miles credits.
• The dashboard displays the quantity of the asset over time, starting at 10,000 and increasing to 15,000 on a specific date.
• The monthly recurring revenue also increases on that date, and users can dive deeper to view the MRR changes on the dashboard.

By: Jean-Michel Tremblay

Configuration | 0:22

• The goal of this configuration is to showcase the flexibility of the product configurator and what can be accomplished with mostly point-and-click configuration to extend the capabilities of Revenue Lifecycle Management (RLM).
• To access the configuration option for usage-based products, the "Configure" button on the right-hand side is clicked, which opens the configuration screen.
• The configuration screen has been customized for this product and includes a minimum usage input field, where a simple number can be entered and saved.
• The configuration screen also includes different consumption rates for the product, with lower and upper bounds and various rates that can be updated within the screen flow.
• Any changes made to the configuration can be saved and will be updated on the transaction line editor upon exiting the configuration screen.
• The customized configuration flow allows for the setup of usage-based products, enabling the input of minimum usage and consumption rates for the self-driving payer miles option product.

Setup | 1:22

• To set up the usage-based product, a Consumption Rates object was created under the Product, which includes the rate lower bound, upper bound, and a lookup to Product.
• A matching object was created under Quote Line, including the rate lower bound, upper bound, and a lookup to Quote Lines.
• A flow was set up to run on creation of Quote Lines, which copies the consumption rates from Product to Quote Line.
• A Lightning Web Component data table was created to allow for edits during configuration.
• The setup includes a flow in Salesforce that can be accessed and reviewed.

Configuration Flow | 1:50

• The usage-based configuration flow was created by cloning the default configuration flow and modifying it to include getting quote line consumption rates, which are created against the quote line when it gets added to the quote.
• The configuration flow retrieves the ID of the current quote line using variables available in the configurator context and transaction line ID.
• The retrieved quote line ID is used to get all the consumption rates for that specific quote line item, which are then displayed on the product configuration screen.
• The product configuration screen was modified to remove unnecessary components and add a custom lightning web component data table, quote line rates data table, which allows modifying and saving different rates for a given product.
• The quote line rates data table takes the current quote line item ID and the record collection as inputs, and any changes made to the rates are saved directly to the database without waiting for the "save and exit" action.

By: Jean-Michel Tremblay

Configuration Rules in RLM | 0:15

• Configuration rules in Revenue Lifecycle Management (RLM) are rules that can be applied to either bundles or products within the Transaction Line Editor, allowing for various actions such as Auto Add, Auto Remove, Validate, Set Attribute Values, Set Quantity, Require Products, or Exclude Products, depending on the target scope.
• When targeting a bundle, configuration rules can perform actions like Auto Add, Auto Remove, Validate, Set Attribute Values, Set Quantity, Require Products, or Exclude Products.
• When targeting a product scope within the Transaction Line Editor, configuration rules can perform actions like Validate, Set Attribute Values, or Set Quantity.

Auto Add and Auto Remove | 0:54

• Auto Add and Auto Remove products allow adding or removing products based on other selections within a bundle, and Auto-added products can be locked to prevent removal by the user.

Require and Exclude Actions | 2:07

• Require and Exclude actions allow requiring or excluding products based on other selections, and they can trigger warning messages or prevent saving the bundle, depending on the selected message type.
• Message types for Require and Exclude actions include Error, Warning, and Informational, which can highlight products in red or yellow, prevent saving the bundle, or provide a message at the top of the configuration screen.

Creating a New Configuration Rule | 4:46

• When creating a new rule, a name, start date and time, and sequence must be set, and the status must be set to Active.
• In the scope detail section of the configuration rule, the rule scope must be set to Bundle, and the product must be selected, in this case, the Model X.
• Conditions must be set for the configuration rule to trigger, such as if a specific product is selected, and actions must be set, such as removing or adding products.

Setting Up a New Rule | 5:57

• Actions can be set to lock, making the option grayed out and unable to be removed, and messages can be added to actions, such as an informational message.

Scope Detail and Conditions | 5:41

• An example of a configuration rule is one that removes standard wheels and adds upgraded wheels when full self-driving is selected on a Model X.

By: Jean-Michel Tremblay

What is DRO | 0:12

• DRO is designed to automate order fulfillment within the end-to-end sales process 
• It provides a graphic UI to visualize fulfillment design and execution 
• DRO allows for decomposing products into multiple products and tracking SLAs and jeopardy management 

Decomposition | 0:55

• Decomposition in Salesforce involves breaking down order products into fulfillment order products
• Fulfillment order products create their own subset of assets, allowing for tracking of account ownership

Fulfillment Plan | 1:38

• A fulfillment plan can be created to organize different step groups and steps 
• Steps can have different step types, such as autotask, call out, manual, milestone, or pause

Fulfillment Work | 2:01

• The fulfillment work workspace allows for creating fulfillment step groups and assigning scenarios 
• Scenarios are combinations of products and actions that determine the steps to be taken 

Fulfillment Steps | 2:45

• Fulfillment steps have different types, including autotask, call out, manual, milestone, and pause
• Each step type has different implications, such as triggering Salesforce flows or making external system calls

Demo | 4:00

• A quote in Salesforce is used to create an order, which triggers the Dynamic Revenue Orchestrator (DRO) steps.
• Once the order is activated, a fulfillment plan and order products are generated, showing how order products decompose into fulfillment order products.
• The fulfillment plan can be viewed, showing different swim lanes and steps that need to be completed, which can be marked as complete manually or using automated step types.

Dynamic Revenue Orchestration Homepage | 7:32

• The homepage provides setup information, such as product and composition views, and the fulfillment workspace creation.
• End-users can view active fulfillment plans, pending manual fulfillment tasks, and assigned tasks.
• The homepage also displays information on fulfillment plans that are in progress, overdue, or have failed.

By: Wayne Salazar

• SETUP STEPS
• REVENUE CLOUD CONTEXT DEFINITION AND PRICING PROCEDURE SETUP
• CREATING PRODUCTS
• PRICE ADJUSTMENTS
• QUOTING
• DYNAMIC REVENUE ORCHESTRATOR
• MISCELLANEOUS TIPS

By: Salesforce

Pocket Guide

By: Salesforce

Revenue Cloud documentation for developers

By: Salesforce

Get Started with Revenue Lifecycle Management

By: Salesforce

Understand the Business Rules Engine

By: Salesforce

Data Model Overview