Context Service, Business Rules Engine, Omnistudio and APIs
What Context Service definitions, tags, mappings, transposable nodes and transient instances do, how to extend SalesTransactionContext, how Business Rules Engine expression sets, decision matrices and decision tables are called from Flow, Omnistudio and APIs, and which Revenue Management business APIs and events a consultant points developers to.
Identify and describe Agentforce Revenue Management features, such as Context Service, Omnistudio, Business Rules Engine (BRE), and application programming interfaces (APIs).
~8 min read · 15 practice questions ·
What the exam expects
- Explain what Context Service adds to pricing and other processes, and name the parts of a context definition (nodes, attributes, tags, mapping, transposable nodes).
- Choose between extending, cloning and building a context definition, and load the predefined definitions.
- Describe the run-time instance and when data reaches the database.
- Pick the Business Rules Engine component and call route (Flow, Omnistudio, Connect API) for a rule, and explain version and multi-result behaviour.
- Describe Omnistudio's role, including Document Generation token data.
- Point developers to the right business API or platform event, and spot licence limits on API use.
Key terms: context definition (metadata model of the data a process needs); context tag (alias for a node or attribute); context instance (run-time copy of the data in a transient store); expression set (Business Rules Engine calculation engine); lookup table (decision matrix or decision table); business API (Revenue Management Connect API such as Place Sales Transaction).
Key facts
- Detail
- Components can't be modified; extend or clone
- Detail
- Inherits standard components and their updates; listed under Custom Definitions
- Detail
- Child nodes only, custom definitions or nodes only
- Detail
- Context Service Settings, Context Definitions toggle
- Detail
- persistContext writes the current context data to a database
- Detail
- Today
- Detail
- Read only from CSV-based tables
- Detail
- Business Rules Engine Connect APIs
- Detail
- 1000 quote line items per quote; 1000 order products per order
- Detail
- QuoteSaveEvent platform event
- Detail
- No Experience Cloud site access, so no external API use
Sources for this section (9)
- Explore Context Service Componentstrailhead.salesforce.com (opens in a new tab)
- Turn On Context Definitionshelp.salesforce.com (opens in a new tab)
- Get to Know Context Servicetrailhead.salesforce.com (opens in a new tab)
- Decision Matriceshelp.salesforce.com (opens in a new tab)
- Decision Tableshelp.salesforce.com (opens in a new tab)
- Business Rules Enginehelp.salesforce.com (opens in a new tab)
- Place Sales Transactiondeveloper.salesforce.com (opens in a new tab)
- Developer Resourcesdeveloper.salesforce.com (opens in a new tab)
- Get Startedhelp.salesforce.com (opens in a new tab)
- When you extend SalesTransactionContext, how should Effective From compare with the pricing procedure's start date?
- Which design-time step comes last when you build a context definition?
- Why should Place Sales Transaction lines carry a group ID when reps will open the quote in the line editor?
- Which two permissions does extending a standard context definition need?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Revenue Management Consultant pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 25 lessons of the Revenue Management Consultant guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (15 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Choose guide-only, practice-only, or save $4 with both