Creating a Pricing Procedure
Pricing Procedures in Agentforce Revenue Management (formerly known as Revenue Cloud Advanced and Revenue Lifecycle Management) define how pricing calculations are performed. They consist of pricing rules, conditions, and calculations that dictate the final price of a quote or order.
You can create a Pricing Procedure using an out of the box Expression Set Template or configuring one from the app launcher. Salesforce also has a simple Pricing Procedure example here.
Before you build your first Pricing Procedure check out these prerequisites and make sure you have the correct permissions.
Finding your Pricing Procedure in a comparison
Through the Salesforce Metadata API, Pricing Procedures are represented as ExpressionSetDefinitions, which is the metadata type you will need to search for in Gearset to deploy your Pricing Procedures.
Expression Sets are part of the Business Rules Engine which is also used in other Salesforce clouds,.
Breakdown of Pricing Procedures
A Pricing Procedure can consist of several components:
Component name | Description |
ExpressionSetDefinition | The metadata representation of the Pricing Procedure, which encapsulates pricing logic. |
Pricing Rules | Defines the conditions and actions that drive price adjustments, often linked as child elements within an Expression Set |
Conditions & Calculations | Expressions written using the Salesforce formula language or Apex-based conditions, all housed within the Expression Set. |
Inputs & Outputs | Expressions written using the Salesforce formula language or Apex-based conditions, all housed within the Expression Set. |
Constraint Model Language (CML) | Constraint Modeling Language (CML) code defines constraints and rules for a constraint model. |
ExpressionSetConstraintObj | A junction component that connects the Expression Set to Revenue Management data (note: in the process of being supported). |
How to deploy a Pricing Procedure
To deploy a Pricing Procedure:
Include
Expression Set DefinitionandExpression Set Definition Versionin your metadata filter. The Pricing Procedure may also depend upon other component types likeContext Definition,Product Attribute,Product Classification,Product2and other Product related components, so you may want to include these in your comparison filter as well.Run a comparison.
Select your Pricing Procedure and the version of it that you want to deploy (you may want to filter for the metadata type
ExpressionSetDefinition) from your comparison results page.
Check the problem analysers for any missing dependencies, and then proceed to validation and deployment.
After deploying a Pricing Procedure, the target org will automatically create a new version of the Pricing Procedure.
After deployment
After the Pricing Procedure has been created in the target org you may want to refresh your decision tables to ensure the latest pricing data is available.
Call for feedback
We want to hear from you how we can improve our support for Salesforce Revenue Management 360, so please share any feedback you have on our support via the in-app chat.