close

Filter

loading table of contents...

Blueprint Developer Manual / Version 2512.1

Table Of Contents

5.6.2.1 Variant Model

The class ContentVariantModel defines, similar to the SiteModel, the names of the content types and properties used for personalization variants. You rarely need to change the property names, unless they conflict with existing content type extensions.

Configuration keyDefaultDescription
variant.model.basePropertybaseName of the property that holds the baseline content reference.
variant.model.variantConditionPropertyvariantConditionName of the struct property that holds the variant condition.
variant.model.segmentsPropertysegmentsName of the property that holds the user segments that should see this variant.
variant.model.segmentLinksPropertysegmentLinksName of the property that links to condition content items representing the segments.
variant.model.abTestCasePropertyabTestCaseName of the property that holds the A/B test case whose users should see this variant.
variant.model.abTestCaseLinkPropertyabTestCaseLinkName of the property that holds a link to a condition content item representing the A/B test case.
variant.model.abTestPropertyvariantAbTestName of the property that holds the A/B test id.
variant.model.abTestLinkPropertyvariantAbTestLinkName of the property that holds a link to a condition content item representing the A/B test.
variant.model.abTestControlPropertyabTestControlName of the property that holds the A/B test control id.
variant.model.abTestControlLinkPropertyabTestControlLinkName of the property that holds a link to a condition content item representing the A/B test control.
variant.model.priorityPropertypriorityName of the property that holds the variant priority.

Table 5.25. Content variant property names


You may need to mark additional content types added to the Blueprint as either supporting or not supporting variants. By default, the subtypes of CMLocalized support variants, with the exception of CMFolderProperties, CMImage, CMSettings, CMResourceBundle, CMSite, CMSitemap, CMSymbol, CMTaxonomy, and CMTheme. See variant-blueprint.properties for the default configuration.

Configuration keyDefaultDescription
variant.model.type.TYPENAMEInherited from super type, or false if not defined for any super typeWhether content items of this type can have variants.

Table 5.26. Variant support per content type


You can also define stable properties, that is, properties that must not change between a baseline and its variants. A content type inherits the stable properties of its supertype and may define additional ones.

Configuration keyDefaultDescription
variant.model.stablePropertiesNoneA list of stable properties that apply to all content types.
variant.model.stablePropertiesByType.TYPENAMENoneA list of stable properties that apply to this type and all its subtypes.

Table 5.27. Stable property configuration


Search Results

Table Of Contents
warning

Your Internet Explorer is no longer supported.

Please use Mozilla Firefox, Google Chrome, or Microsoft Edge.