Salesforce Revenue Cloud Advanced / Agentforce Revenue Management Tips

 1.Workflow Services :

It’s a handy salesforce feature that lets you track and manage automated processes running behind the scenes - like Data Processing Engine (DPE) runs, Batch jobs, Billing Scheduler, data syncs or even decision table refreshes.you’ll find it in setup under workflow services.

2.AppUsageAssignment :

AppUsageAssignment provides application context for a record - meaning salesforce can decide  what actions are allowed and which related objects should be created based on that context.

3.Decision Table refreshes

1. Record-Triggered Flow - Refresh a Decision Table automatically when a related record changes.
2. Screen Flow (Manually Refresh) - Display Decision Tables in a Data Table component and let admin users select which ones to refresh.
3. Scheduled Flow - Run Periodic refreshes at defined intervals (daily, weekly etc)

Pro tip :

 Leverage the Incremental Refresh option in the Apex action to improve performance - especially helpful for larger tables.

4.“Is Price Impacting” on Product Classification Attribute :

Is Price Impacting allows us to adjust the price based on selection of the attribute value later on.

What does “ Price Impacting” RCA?

When an attribute is marked as price impacting , it tells Salesforce to adjust the product price automatically based on the selected value of that attribute .

Why using price impacting attributes ?

1. To automate pricing based on product options. To reduce quoting mistakes and manual calculations.
2. To Simplify the sales process - sales reps just choose options, and the system calculates pricing dynamically.

5.Product Won’t Appear During Quoting :

1. Check the Product details

  —> is it active?

  —> Is it assigned to the correct Product Selling Model?

  —> Does it have a valid price book entry for the corresponding product selling model in the right Price Book?

     2. Verify the Product Catalog

—> Is the product is added to a category and is the category added to the right catalog?

—> Has the index has been rebuilt after the product was added to the category and catalog?

    3. Make sure the Product Qualification works

  —> If product qualification/disqualification rules apply, are the product qualification/disqualification records are accurate and active?

—> Do the product qualification/disqualification look up tables have the right filters and conditions?

—> Does the qualification procedure return the right results? You can try simulating the procedure to verify the output.

  4. Check the Set UP

  —> Does the product discovery settings refer to the right context definition and discovery procedure?

—> Have the decision tables been refreshed?

  5. Verify the Quote details

—> Is the price book selected on the quote the right one?

—> Do the qualification criteria during quoting match the qualification records created for the product?

6.Pricing Procedures :

Pricing Procedures are the heart of the Revenue Cloud pricing engine. They define every step that transforms a simple List Price into a final Net Price. Once you understand how they work, you gain real control over your entire Quote-to-Cash flow.

The Pillars of a Pricing Procedure

1. Context Definition: This is your data map. Context Tags pull values from your Salesforce objects into the pricing engine. If your context is wrong or incomplete, your entire procedure will misfire - so this is the first place to get right. 

2. Pricing Elements: These are the individual steps that make up your calculation logic. List Price Element, Volume Discount Element, Formula Element, Rating Lookups, and more.Each element performs one task- calculate something, fetch something, or transform something.

3 The Sequence (The Price Waterfall): This is the execution order of your Pricing Elements. One element’s output becomes the input for the next, so the sequence determines how your price waterfall unfolds. A misplaced element can completely change the final price.

Pro Tip: Use Price Logs to Verify Your Pricing Flow

One of the least known debugging tools in Revenue Cloud is Price Logs. They show exactly how your Pricing Procedure executed - step by step.

How to use them:

1. Go to Setup → Salesforce Pricing Setup and turn Price Logs Capture ON.

2. Open the Pricing Operations Console app.

3. Navigate to Pricing API Executions to view logs for each line item.

You’ll be able to see:

- Inputs passed into each Pricing Element

-Outputs generated

- The exact sequence the procedure followed

Perfect for validating logic, troubleshooting incorrect prices, and refining complex waterfalls.

Product Categories and Attributes

 A ) Category – Groups products inside a catalog and improves product discovery. Supports parent/child hierarchy for deeper organization.

B) Subcategory – A child category used to refine product grouping. Revenue Cloud Advanced supports up to five nested levels.

C) Picklist – A data record in Revenue Cloud Advanced that defines the allowed selectable values for an attribute.

D) Picklist Values – The individual options inside a picklist (for example, 128GB or 256GB), stored as AttributePicklistValue records.

E) Attribute Definition – Defines a product characteristic with properties like data type, required/optional, display type, price-impacting, and more.

 This is the master definition reused across products.

D) Attribute Category – A logical grouping of related attributes (such as Storage Specs or Display Specs) to streamline configuration and reuse.

E) Assign Attribute to Attribute Category – Links attributes to categories using AttributeCategoryAttribute, making them usable in product classifications and product setup.

Salesforce Contracts

Manage your end-to-end Contract Lifecycle.

Integrated to your Sales Process.

Key Features :

1.Create /Update Contracts from any objects.

—> Quick Actions to create or update contracts.

—> Context mapping to map data from source objects to contracts.

2.Document Clauses 

—> Reapproved and Prebuilt standardized template clauses.

3.Document Generation 

—> Leverage Omnistudio Document Generation.

—> Use Omnistudio Data mappers to Extract and Transform Data.

4.Obligation Management

—> Create/view Obligations from the contract Record.

5.Salesforce Contracts integrate  with Microsoft 365

—> Edit Documents in Microsoft 365

—> Create Documents Templates in Microsoft 365.

6.Docusign Integration for ESignature

—> Prebuilt Integration to Docusign for ESignature  flows.

7.Contracts AI 

—> Extract Contract details from existing contracts using AI.

—> Draft Clauses with Contracts AI.

Salesforce Agentforce Revenue management Foundational Modules

 Context Definitions :

Define consistent data structures and relationships across pricing and quoting

Ex: SalesTransactionContext for quoting and pricing.

Business Rules Engine :

Apply logic, decisions and calculations declaratively.

Ex : Decision Tables in Pricing Procedures.

Omnistudio :

Deliver guided user experiences and process orchestration with low-code tools.

Ex : Omniscripts for Quote-to-Contract flows.

Agentforce Vibes

 What is vibe coding ?

—>A new way to build software - using natural language.

—> you describe what you want - AI turns it into working code.

—> Fast , creative and fun for developers

Agentforce Vibes 

—> Salesforce’s vibe coding agent for anyone - not just developers.

—> Works inside vs code or the web-based Agentforce Vibes IDE.

—> Lets you plan, build , test and deploy salesforce solutions using plain language.

—> Makes creating on salesforce faster, simpler and safe within your environment.

Agentforce for developers vs Agentforce vibes :

Agentforce for Developers (A4D) :

Conversation-based assistant - it doesn’t perform any actions but helps you by suggesting and explaining code.

Agentforce Vibes :

Agentforce vibes is a vide coding agent - as an agent, it’s more powerful than an assistant. It can perform actions, create files, run tests and deploy not just suggest code.

Global rules vs Workspace rules in Agentforce vibes :

Global rules in Agentforce Vibes apply to all projects for consistency, while workspace rules are project-specific to allow for tailored behavior.

Context Definition (RCA)

 What Is a Context Definition?

A Context Definition is a metadata-driven structure used to pass data into Revenue Cloud services in a consistent and reusable way. It is defined by a set of core building blocks -

1. Nodes – Containers for attributes mapped to Salesforce objects. Each node can hold multiple attributes.
2. Attributes – Containers for data, mapped directly to fields on an object.
3. Context Tags – Simple aliases for nodes and attributes, used by consuming applications to query context data easily.
4. Context Mappings – The link between nodes/attributes and input data sources. A single context definition can support multiple mappings to serve different use cases.
   

A context definition typically follows four stages:

1. Creation (Design time) – Defining nodes, attributes, tags, and mappings.
2. Hydration – Populating the definition with actual record data at runtime.
3. Consumption – Querying or transforming hydrated data.
4. Persistence – Writing any changes back into mapped objects.

Context Service APIs

The Context Service provides a set of Apex APIs to interact with context definitions. In this post, we’ll focus on hydration, retrieval, and querying.

• Build: Load data into a context.
• buildContext – Create a context instance at runtime.
• getContext – Retrieve details of an existing context.
• deleteContext – Delete a context instance.
• Query: Explore data within the context.
• queryContextRecordsAndChildren – Retrieve records and child records.
• queryTags – Retrieve tag values.
• Update: Modify an existing context.
• updateContextAttributes – Update data in the context.
• addRecordToContext – Add new data.
• Persist: Save context data back to the database.
• persistContext – Write hydrated context data to mapped objects.

Applications of Context Definitions

Context Definitions appear in many Revenue Cloud scenarios, including :

• Pricing Procedures – Passing quote and product information into the pricing engine.
• Product Discovery – Determining which products or services are eligible for a customer.
• Contracts & Assets – Handling renewals, asset-based ordering, and related conditions.

Consuming Context Definitions from Apex

From a developer’s perspective, consuming a Context Definition directly in Apex is useful when:

• Triggering Apex hooks within a procedure plan.
• Testing or validating changes made to a Context Definition.
• Building custom solutions that consume or share a hydrated context.
  

Instead of writing SOQL queries and reproducing mappings manually, you can rely on the Context Service APIs to tap into hydrated data directly.