What it requires. A sequence of conditional elements enumerates cases (per-segment rates, per-product uplifts) that a single decision table lookup would serve.
Why it matters. [reasoned; corroborated by practitioner literature] Each ladder step is a sequential evaluation inside the procedure's runtime budget (one-minute default, two-minute maximum for a pricing procedure; a discovery procedure gets 10 seconds by default and 60 at most) and an element against the 130-per-version cap; a decision table is one compiled, indexed lookup - the platform's stated purpose for them. Adding a tier becomes a row plus refresh, not a version edit. Two guards on the fix: a decision table answers from its last refresh, so the conversion must arrive WITH refresh discipline (see RC-008) or it introduces a stale-price failure the ladder never had; and trivial logic stays inline - a single condition is not a ladder, and converting it buys nothing.
How to fix it. Collapse the ladder into one decision table and one lookup element.
Source. Kavaliro: RLM Pricing Procedures (practitioner); Salesforce Pricing Limits (budgets)
Is this rule worth checking?
Votes and comments are published here. We read them, and we publish what we change with the reasoning — a vote does not move a rule on its own.