Attribute-Dependent Exclusion

Prove that an attribute value excludes a child product from the configuration.

What it proves

When a trigger attribute is set to a specific value, a child product is excluded (Salesforce exclude() / hide treatment, or a custom message() rule). Attempting to add that child while the attribute is set should fail the expected assertion.

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.

Named Platinum coverage is not sold on shared multi-tenant deployments: it creates over-entitlement and incorrect SLA expectations.

Bundle: Meridian Enterprise Pack (Support group)
Attribute: Deployment Model
Trigger value: Multi-tenant
Excluded child: Platinum Support

With Deployment Model set to Multi-tenant, adding Platinum Support should be rejected. Salesforce may surface this as an exclude / hide treatment, or as a message such as:

Platinum Support is not available for Multi-tenant deployments. Choose Standard or Premium Support.

What Revsnap does at runtime

1. Starts from your valid base quote
2. Sets the trigger attribute to the excluding value (Multi-tenant)
3. Attempts to add the excluded child product (Platinum Support)
4. Asserts the expected configurator signal (default pattern hide, severity error)
5. Corrects the transient invalid selection
6. Saves the valid configuration

Screenshot coming soontest-runs-configurator-attribute-exclusion-timelineTest run detail showing Scenario Proof Timeline for Attribute-Dependent Exclusion

The proof timeline shows the attribute trigger, exclusion assertion, correction, and save phases.

How to capture it

1. Capture a Configurator → Scenario Builder snapshot with a valid base quote for the bundle that owns the attribute.
2. On Rule Type, choose Attribute-Dependent Exclusion.
3. In Scenario Builder, set:
   • Trigger attribute: for example Deployment Model
   • Trigger value: for example Multi-tenant
   • Excluded child to add: for example Platinum Support
4. On Review, confirm or edit the expected pattern and severity.
5. Save the snapshot.

Screenshot coming soonsnapshots-configurator-attribute-exclusion-setupScenario Builder for Attribute-Dependent Exclusion with attribute and excluded child selected

Scenario Builder: set the trigger attribute value and the excluded child to attempt.

Review assertion tips

Setting	Default / guidance
Expected pattern	hide: matches exclude() UI treatments from the Configurator API
Severity	error by default
Custom message() orgs	If your org uses message() instead (for example Platinum Support is not available for Multi-tenant), replace the pattern with that text or a matching regex

Screenshot coming soonsnapshots-configurator-attribute-exclusion-reviewExpectation and review step for an Attribute-Dependent Exclusion scenario

Review: confirm the expected hide or message pattern and severity before saving.

Related

• Configurator testing: message vs product-presence proofs
• Attribute-Dependent Inclusion: include / auto-add instead of exclude
• Mutual Exclusivity (Message Rule): product-vs-product exclusion via message()