Quantity Boundaries
Prove that a product quantity must stay within min/max or fixed bounds.
What it proves
A line’s quantity cannot be set outside the allowed range. An out-of-bounds quantity should raise a configuration message from Salesforce.
Example
Map these Meridian product names to equivalents in your org. Pick a valid base quote that already reflects the rule, then select the matching products in Scenario Builder.
API throughput capacity is sold in packs. Quantities below the minimum cannot be fulfilled; quantities above the maximum exceed supported capacity bands.
Product: API Throughput Booster (often sold within a Meridian Data Fabric Bundle)
Bounds: Min = 10, Max = 100
A valid base quote might have quantity 25. Setting quantity to 5 or 150 should violate the boundary and return a message such as:
API Throughput Booster quantity must be between 10 and 100.
What Revsnap does at runtime
- Starts from your valid base quote with the target product already on the quote
- Sets the product quantity to the invalid value you captured
- Asserts the expected configurator message (default severity warning)
- Corrects the quantity back to a valid state
- Saves the valid configuration
How to capture it
- Capture a Configurator → Scenario Builder snapshot with a valid base quote that already includes the target product.
- On Rule Type, choose Quantity Boundaries.
- In Scenario Builder:
- Select the Target product (must already be in quote)
- Enter the Invalid quantity: it must be outside the real min/max in Salesforce
- On Review, set the expected message pattern and confirm severity (warning by default).
- Save the snapshot.
Review assertion tips
| Setting | Guidance |
|---|---|
| Expected pattern | Match Salesforce range text (often similar to group cardinality: isn't in the specified range, or your org’s quantity message) |
| Severity | Prefer warning unless your org returns error |
| Out-of-bounds required | An in-bounds “invalid” quantity produces no messages: the assertion fails the same way a disabled rule does |
| Rule must be active | Confirm the quantity constraint is enabled in the target org |
Related
- Configurator testing: severity and operator notes
- Cross-Product Quantity Dependency: ratio between two products instead of a single-product min/max
- Group Selection Cardinality: group selection counts