You are here:
Extend and Map Sales Transactions in Revenue Cloud
Extend or customize default features to meet business-specific requirements by creating and mapping custom fields in Revenue Cloud.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions of Revenue Cloud where Transaction Management is enabled |
For example, if your business requires delivery or installation dates that aren’t available by default on sObjects, you can add these custom fields to your sales process objects. Mapping these fields in context definitions makes sure that they appear during transactions and that entered values persist after a refresh.
Before you Begin
Complete these requirements before configuring your extended transactions:
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions of Revenue Cloud where Transaction Management is enabled |
- Turn on Context Service in Salesforce Setup.
- Verify Permissions: Make sure that you have the Context Service Admin and Manage Revenue Cloud permissions to extend definitions.
- Assign Pricing Permissions: Assign the Salesforce Pricing Design Time User permission to edit pricing procedures.
- Set Security: Configure field-level security for all fields you intend to extend so they map correctly.
- Grant Access: Provide read access to source custom fields and edit access to destination custom fields to help APIs to populate data.
- Review Mapping Paths: Confirm that your business process aligns with supported mapping flows, such as Product to Quote Line or Order to Asset.
This table maps the business process and mapping required between their objects.
| Business Process or API | Source Object | Destination Object | Context to Context Mapping Required? |
|---|---|---|---|
| Browse Catalog | Product | Quote Line | Y |
| Product | Order Product | Y | |
| Configuration | Product | Quote Line | Y |
| Product | Order Product | Y | |
| Quote to Order | Quote | Order | N |
| Quote Line | Order Product | ||
| Quote Action | Order Action | ||
| Order to Asset | Order Product | Asset Action Source | Y Use the AssetToSalesTransactionMapping |
| Order Item Detail | Asset Action Source | ||
| Order Action | Asset Action | ||
| Asset to Quote and Asset to Order | Asset Action Source | Quote Line Detail | Y Use the SalesTransactionToAssetMapping |
| Asset Action Source | Order Item Detail | ||
| Quote to Contract | Quote | Contract | Y |
| Order to Contract | Order | Contract | Y |
Extend the Sales Transaction Context Definition
Extend the standard definition to preserve necessary nodes and attributes for your custom requirements.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions of Revenue Cloud where Transaction Management is enabled |
| User Permissions Needed | |
|---|---|
| To extend context definitions: | Context Service Admin AND Manage Revenue Cloud |
| To edit pricing procedures: | Salesforce Pricing Design Time User |
- From Setup, in the Quick Find box, enter Context Service, and then select Context Definitions.
- Locate SalesTransactionContext in the Standard Definitions tab.
- Click the dropdown menu and select Extend.
- Give your extended context definition a name and save your changes.
- In the Custom Definitions tab, click Edit on your new definition.
- Set the Effective From date to occur earlier than your pricing procedure’s start date.
- Click Next, leave default structure options unchanged, and save.
- Optional: Under the Map Data tab, click Edit as SObject Mapping for Sales Transaction, select Mark as Default, and click Map.
- Select your custom definition and click Activate.
Create Custom Fields and Add Custom Attributes
After extending the definition, add the actual fields to Salesforce objects and the corresponding attributes to the context.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions of Revenue Cloud where Transaction Management is enabled |
- Create custom fields: Use Object Manager to add fields to relevant sales objects (for example, Quote, Order, Product).
- Add attributes: Add corresponding attributes and tag names to the extended context definition.
- Map attributes: Map these attributes to the custom fields on the entity.
Map Custom Fields in Context Service
Use Context Service to map custom fields across definitions to make sure that values persist during transactions. If you don’t map custom fields to their corresponding attributes, you can’t update those fields on records.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions of Revenue Cloud where Transaction Management is enabled |
Here are the list of key mapping types.
- sObject Mapping: Links a context definition node to a Salesforce object (for example, QuoteEntitiesMapping).
- Cross-context mapping: Links attributes between two different definitions (for example, Product Discovery to Sales Transaction).
- Context definition mapping: Links attributes within a specific flow (for example, Order to Asset).
| Context Definition | Mapping | Process | Source | Destination | Type of Mapping |
|---|---|---|---|---|---|
| ProductDiscovery Extended Context Definition | ProductDiscoveryMapping | Product Discovery | ProductDiscoveryExtended Context Definition | Product2 | sObject |
| Sales Transaction Context Definition | ProductDiscoveryContextMapping | Product Discovery to Sales Transaction | SalesTransaction Context Definition | Product Discovery Extended Context Definition | Cross-context definition mapping |
| QuoteEntitiesMapping | Quote | SalesTransaction Context Definition | QuoteEntities | sObject | |
| OrderEntitiesMapping | Order | SalesTransaction Context Definition | Order Entities | sObject | |
| ContractNodeMapping | Contract | SalesTransaction Context Definition | Contract Entities | sObject | |
| AssetEntitiesMapping | Assets | SalesTransaction Context Definition | Asset Entities | sObject | |
| ContractToSalesTxnMapping | Order to Contract Quote to Contract |
SalesTransaction Context Definition | SalesTransaction Context Definition | Context definition mapping | |
| AssetToSalesTransactionMapping | Order to Asset | SalesTransaction Context Definition | SalesTransaction Context Definition | Context definition mapping | |
| SalesTransactionToAssetMapping | Amend, Renew, Cancel | SalesTransaction Context Definition | SalesTransaction Context Definition | Context definition mapping |
Link Context Definitions to Pricing Procedures
Link your pricing procedure to your extended context definition to enable efficient data access.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions of Revenue Cloud where Transaction Management is enabled |
- From the App Launcher, find and select Pricing Procedures.
- Select your pricing procedure and deactivate the current version.
- Click Edit and select your extended context definition in the Context Definition field.
- Save your changes.
- Update the Pricing Procedure Properties start date to a time after you created the extended context definition.
- Save and activate the pricing procedure.
- In Revenue Settings within Setup, select this pricing procedure to apply it to all quotes and orders.
Example: Map an Installation Date Field
Follow these steps to track a custom InstallationDate__c field across the sales lifecycle.
Required Editions
| Available in: Lightning Experience |
| Available in: Enterprise, Unlimited, and Developer Editions of Revenue Cloud where Transaction Management is enabled |
Update Products and Quotes
- Add the custom field to Product and Quote Line Item via Object Manager.
- Edit the Product Discovery context definition to create a sub-node under Category with an InstallationDate attribute.
- Create a Product object mapping in ProductDiscoveryMapping to link the attribute to your custom field.
Update Orders and Contracts
- Add the field to Order Item, Quote, and Contract objects.
- In the Sales Transaction context definition, create an InstallationDate attribute under the SalesTransactionItem, SalesTransaction, and Contract nodes.
- Map these attributes in QuoteEntitiesMapping, OrderEntitiesMapping, and ContractNodeMapping.
- Use ContractToSalesTxnMapping to map the date from the Sales Transaction node to the Contract node.

