Skip to main content

Mutual Inclusivity (Auto Add)

Prove that Salesforce auto-adds a dependent product when a trigger product is present.

This is a product-presence proof: Review does not ask for an expected configuration-rule message.

What it proves​

When Product A (the trigger) remains in the configuration, Product B (the dependent) is added automatically by the mutual-inclusivity / include rule.

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.

In a Meridian Data Fabric Bundle, zero-copy sharing depends on a live ingestion path:

RoleProduct
TriggerZero Copy Data Share
Dependent (auto-add)Streaming Ingestion Gateway

Selecting Zero Copy without Streaming Ingestion leaves an incomplete Data Fabric configuration. The rule auto-adds Streaming Ingestion Gateway and keeps it selected while Zero Copy remains.

Revsnap proof: start from a valid quote that already includes both products. Revsnap omits Streaming Ingestion Gateway, runs rules, and asserts Salesforce restores it.

What Revsnap does at runtime​

  1. Starts from your valid base quote (with both products present in the captured baseline)
  2. Omits the dependent product from the recreated configuration
  3. Runs configuration rules
  4. Asserts the dependent product exists in the live configurator context
  5. Saves the valid configuration
  6. Asserts the dependent product is present on the saved quote lines
Screenshot coming soontest-runs-configurator-mutual-inclusivity-timelineTest run detail showing Scenario Proof Timeline for Mutual Inclusivity
The proof timeline shows omit, auto-add assertion, and save phases for this rule.

How to capture it​

  1. Capture a Configurator → Scenario Builder snapshot with a valid base quote that already includes the trigger and dependent products.
  2. On Rule Type, choose Mutual Inclusivity (Auto Add).
  3. In Scenario Builder:
    • Select the Trigger product (must already be on the quote)
    • Select the Dependent product (auto-add) (must already be on the quote)
  4. On Review, confirm the product-presence proof timeline, no expected-message regex is required.
  5. Save the snapshot.

Use Baseline Products or Standalone Products as allowed by the picker. Both products must be in quote.

Screenshot coming soonsnapshots-configurator-mutual-inclusivity-setupScenario Builder for Mutual Inclusivity with trigger and dependent products selected
Scenario Builder: select the trigger and the dependent product expected to auto-add.

Review assertion tips​

SettingGuidance
Expected messageNot used: this pattern asserts product presence
SeverityNot applicable
Success signalDependent product reappears after rules run and remains after save
Screenshot coming soonsnapshots-configurator-mutual-inclusivity-reviewExpectation and review step for a Mutual Inclusivity scenario
Review shows the product-presence proof timeline before you save the snapshot.