Kill Switches
Configurator Settings carries a set of Disable… toggles that turn off
whole engines. They exist so you can isolate a problem in production
without a deploy — flip one off, confirm the symptom clears, then fix the
underlying rule / data. They are not routine configuration.
The switches
| Field | When on… |
|---|---|
DisableProductRules__c | Product-rule evaluation stops firing. |
DisablePricingRules__c | Pricing-rule evaluation stops firing. |
DisableApprovalRules__c | The approval engine stops: no rules fire on submit, no preview gating; existing pending requests are preserved but not enforced. |
DisableServerSideRules__c | Rule evaluation runs client-side only (the server pass is skipped). |
DisableServerSidePricing__c | The server-side pricing path is disabled. |
DisableServerSideRecompute__c | The server-side recompute (the tamper-protection pass) is disabled — usage / quantity / base-price services key off this. |
DisableRuleScoping__c | Rules load org-wide instead of scoped to the deal (a diagnostic / compatibility fallback). |
There is also AllowSaveFailureSeam__c, a test/diagnostic seam that
lets an injected save failure surface — leave it off in a real org.
Polarity — null means active
Every switch is off by default, and the polarity is deliberate: an absent Configurator Settings record, or an existing record whose field is null, reads as not disabled — i.e. the engine is active. This matters on upgrades: an org whose Default record predates a given switch reads it as null, so the engine stays on rather than silently switching off.
To re-enable an engine, uncheck the field; the change takes effect on the next evaluation (next submit / next save), no deploy required.
Related
- Configurator Settings — the record these toggles live on.
- Approvals — Runtime & Troubleshooting — the approval kill switch in context.
- Pricing — The Big Picture — why the server recompute is authoritative.
- Troubleshooting — the “a total looks wrong” checklist.