Revenue Cloud Advanced: How to Use CML Logic at the Product Classification Level Without Adding Products Individually

When multiple products share the same attributes and require identical constraint logic (for example, making an attribute picklist value default), a common challenge is that standard CML import requires each product to be added to the Constraint Model individually. This becomes unmanageable when dealing with a large product catalog.

In Revenue Cloud Advanced (RCA), CML supports type hierarchies — an inheritance model where a parent type (mapped to a Product Classification) can hold all shared logic, and child products inherit it automatically.

When this is applied:

• Multiple products share the same attributes
• The same require/constraint logic should apply to all those products
• You want to avoid duplicating rules or importing dozens of products individually into the Constraint Model

Important:

Product Classification import in CML is currently only available via the CML Editor. It is not supported in the Visual Builder at this time.

Additionally, The CML structure used to achieve classification-level logic differs depending on the product context:

1. Standalone products and bundle parent products → Use the standard classification type approach (see Resolution — Scenario A)
2. Child products within a bundle → A different CML structure is required that imports the bundle and uses property allowMissingRelation = true (see Resolution — Scenario B)

Prerequisites:

1. Create a Product Classification in the Product Catalog.
2. Define the attributes in the Product Classification.
3. Assign the Product Classification to those products where you want to apply the constraint logic.

Sample Code - When the product is a standalone product or a bundle parent:

@(virtual = true)
type Quote {
    @(sourceContextNode = "SalesTransaction.SalesTransactionItem")
    relation beyondProducts : Classification[0..999];

    constraint(beyondProducts[Classification].TestAttribute == 'B');
}

type Classification {
    string TestAttribute = ["A", "B"];
}

In this example:

Classification is the type mapped to a Product Classification record in Salesforce. All products assigned to that Product Classification already inherit the TestAttribute.

Sample Code - When the product is a child product:

For the CML logic to work on a child product within a bundle, the bundle must be imported into the Constraint Model. The child product then inherits the classification logic from the type hierarchy. Avoid importing all attributes unnecessarily when doing this, as it can increase the CML size.

property allowMissingRelation = true;

type LineItem;

@(virtual=true)
type Quote{
    @(sourceContextNode = "SalesTransaction.SalesTransactionItem")
    relation clsCmp: classification;
}

type classification : LineItem  {
    @(defaultValue = "i5-CPU 4.4GHz")
    string Windows_Processor = ["i5-CPU 4.4GHz", "i7-CPU 4.7GHz", "Intel Core i9 5.2 GHz"];
    constraint(Windows_Processor == "Intel Core i9 5.2 GHz");

type LaptopBasicBundle : classification {
    relation bundlep : BundleP {
        default BundleP(1);
    }

    relation laptopbag : LaptopBag;

    relation laptop : Laptop[1..999] {
        default Laptop(1);
    }

    relation antivirus : Antivirus[1..999] {
        default Antivirus(1);
    }
}

type BundleP : classification;

type LaptopBag : classification {
    @(defaultValue = "true")
    boolean Advance_Ecommerce;
    string Size;
}

type Laptop : classification;

type Antivirus : classification;

In this example:

1. The bundle (LaptopBasicBundle) must be imported into the Constraint Model and the bundle type must extend classification.
2. Child product types (e.g., Laptop, Antivirus, LaptopBag) also extend classification directly, inheriting its attributes and constraints.