M2 · Platform foundations
Test 1 - Mike's Review · 8 questions · printed Oct 21, 2026
Revenue Cloud pricing, configuration, approvals, and orchestration all read transaction data through Context Service context definitions, so any custom field that should affect them must be named here.
2.0 Which transactions do reps create: Quote, Order, or both? Are orders created only from quotes, or also directly?
Pending
2.1 List every custom field needed on Quote, Quote Line Item, Order, Order Item, Asset, and Contract. For each: object, label, API name, type, picklist values, who fills it (rep, automation, pricing, integration).
Files: C-01 (not uploaded)
Pending
2.2 Of those fields, which must influence pricing, configuration rules, approvals, qualification, or fulfillment? Each one will be added to the Sales Transaction context definition and mapped.
Pending
2.3 Do you need custom attributes on the transaction itself (for example, deal region or sales motion)? List them and say whether they affect price.
Pending
2.4 Do transaction types behave differently: new, amendment, renewal, cancellation, partner? For each, say how pricing, validation, and cloning differ. This sets up transaction processing types and procedure plans.
Pending
2.5 Which Revenue Settings must be on? Check: groups in quotes and orders, transaction cloning, delta pricing, automatic line item sequencing, ramp deals for groups, auto-refresh in the line editor.
Pending
2.6 Inventory existing Flows, Apex, and validation rules that run on Quote, Order, or Asset records. For each, say keep, replace, or retire.
Pending
2.7 Do you expect custom Apex hooks in procedure plans (for example, external pricing)? If yes, describe the call and answer M22.
Pending