Architecture
Pricing architecture
From a context to a net price, and the one decision that keeps catalogs maintainable: when you do not need a decision table.
Salesforce docs documented by SalesforceField experience observed on a real orgRecommended pattern what we recommendTo verify unverified
Pricing architecture
context → procedure → price
Scroll the diagram sideways
The rule that keeps a catalog maintainable: a decision table only when there is a condition or a tier. A flat price belongs on the PricebookEntry. Decision tables added by reflex are what fills a procedure up to its element ceiling.
And the procedure that runs is the compiled _Auto version, not the source you edit.
The objects involved
Select one to open its detail.
Guide