Cross-Product Quantity Dependency

Prove that a dependent product’s quantity scales with a driver product (for example a required staffing ratio).

What it proves

When the driver quantity changes, the dependent quantity must satisfy a ratio (or similar cross-product quantity rule). Setting the dependent below the required amount should raise a configuration message.

Example

How to use this 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.

Data and Integration engagements are staffed so build capacity keeps up with architecture. A Technical Architect needs enough developers to execute the design.

Offer: Meridian Data and Integration Services

Role	Product
Driver	Meridian Technical Architect
Dependent	Meridian Developer

Rule: Developer quantity must be at least 2 × Technical Architect quantity.

• Driver: Technical Architect qty = 2 → at least 4 Developers required
• Invalid attempt: leave Developer qty at 2 while Architect qty is 2

Expected message such as:

Developer quantity must be at least twice the Technical Architect quantity for Data and Integration Services.

What Revsnap does at runtime

1. Starts from your valid base quote with both products on the quote
2. Sets up the driver quantity (when needed) so the ratio is in force
3. Sets the dependent quantity below the required ratio
4. Asserts the expected configurator message
5. Corrects quantities back to a valid state
6. Saves the valid configuration

Screenshot coming soontest-runs-configurator-cross-product-quantity-timelineTest run detail showing Scenario Proof Timeline for Cross-Product Quantity Dependency

The proof timeline shows the ratio violation, message assertion, correction, and save phases.

How to capture it

1. Capture a Configurator → Scenario Builder snapshot with a valid base quote that already includes both the driver and dependent products.
2. On Rule Type, choose Cross-Product Quantity Dependency.
3. In Scenario Builder, set:
   • Driver product (in quote): for example Technical Architect
   • Dependent product (in quote): for example Developer
   • Driver quantity
   • Ratio (for example 2 for a 2× staffing rule)
4. On Review, enter the expected message text from Salesforce and severity (usually error, unless your org returns warnings).
5. Save the snapshot.

Screenshot coming soonsnapshots-configurator-cross-product-quantity-setupScenario Builder for Cross-Product Quantity Dependency with driver and dependent products

Scenario Builder: select the driver and dependent products and set the ratio for the proof.

Review assertion tips

Setting	Guidance
Expected pattern	Org-specific: paste a distinctive fragment of the live ratio / quantity message
Severity	Often error; match whatever Salesforce returns
Both products in quote	Driver and dependent must already be on the base quote
Rule must be active	Disabled cross-product rules produce empty messages and failed assertions

Screenshot coming soonsnapshots-configurator-cross-product-quantity-reviewExpectation and review step for a Cross-Product Quantity Dependency scenario

Review: set the expected ratio message pattern and severity before saving.

Related

• Configurator testing: message assertion tips
• Quantity Boundaries: single-product min/max