Skip to main content

Attribute-Dependent Inclusion

Prove that choosing an attribute value auto-adds one or more required child products (include()).

This is a product-presence proof: Review does not require an expected-message regex.

What it proves​

When a trigger attribute is set to a specific value, Salesforce includes one or more child products in the configuration.

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.

Healthcare customers handling PHI need residency enforcement and auditable evidence before an accelerator can be delivered.

Bundle: Meridian Healthcare Accelerator Bundle
Attribute: Compliance Profile
Trigger value: HIPAA

Children auto-added when Compliance Profile is HIPAA:

  • Data Residency Control Pack
  • Audit Evidence Vault

Salesforce should keep both children selected while the Compliance Profile value is HIPAA.

What Revsnap does at runtime​

  1. Starts from your valid base quote
  2. Sets the trigger attribute to the value that should require the children (while those children are missing from the proof path, as compiled by the builder)
  3. Runs rules / evaluates the configuration
  4. Asserts the expected child products exist
  5. Saves the valid configuration
Screenshot coming soontest-runs-configurator-attribute-inclusion-timelineTest run detail showing Scenario Proof Timeline for Attribute-Dependent Inclusion
The proof timeline shows the attribute trigger, product-presence assertion, and save phases.

How to capture it​

  1. Capture a Configurator → Scenario Builder snapshot with a valid base quote for the bundle (or standalone) that owns the attribute.
  2. On Rule Type, choose Attribute-Dependent Inclusion.
  3. In Scenario Builder, set:
    • Trigger attribute
    • Trigger value (picklist or value as shown in the builder)
    • Children expected to auto-add (one or more products)
  4. Attributes for bundle lines are loaded from the quote line when available so they match what the Salesforce configurator shows.
  5. On Review, confirm the product-presence proof, no expected-message field is required.
  6. Save the snapshot.
Screenshot coming soonsnapshots-configurator-attribute-inclusion-setupScenario Builder for Attribute-Dependent Inclusion with attribute and children selected
Scenario Builder: set the trigger attribute value and the children expected to auto-add.

Review assertion tips​

SettingGuidance
Expected messageNot used: this pattern asserts product presence
Success signalListed children appear after the attribute trigger is applied
AttributesPrefer a configured bundle line so attribute discovery matches Salesforce
Screenshot coming soonsnapshots-configurator-attribute-inclusion-reviewExpectation and review step for an Attribute-Dependent Inclusion scenario
Review shows the product-presence proof timeline before you save the snapshot.