1. Order Management Guide
  2. Example: Handling Attribute Defaults

Example: Handling Attribute Defaults

The following example shows the expected output for attribute defaults when you apply a promotion to a customizable product. In this example, a customizable product named CP-A is defined and a promotion named Promo-D is defined. In this example:

  1. A customizable product named CP-A is defined and a promotion named Promo-D is defined as shown in the following figure.

  2. CP-A is then customized as shown in the second figure in this topic.

  3. The expected output for attribute defaults when you apply a promotion (Promo-D) to a customizable product (CP-A) that is based on the Promotion Automatch argument value is shown in the third figure in this topic.

    Note: The expected output for attribute defaults when you apply a promotion (Promo-D) to a customizable product (CP-A) is the same whether Promotion Automatch is set to Default Cardinality or Min Max Cardinality.

    Product Structure for CP-A and Promo-D. This image is described in surrounding text.

The first figure in this topic shows a product named CP-A with the following structure: CP-A has a simple product relationship named SP-A defined and a Product Class named ClassB. Another simple product relationship named SP-B is defined and associated with ClassB. SP-A is associated with an attribute, Attrib-A, which has the values {1,2,3,4,5}. SP-B is associated with an attribute, Attrib-B, which has the values {1,2,3,4,5}.

Note: The relationships SP-A and SP-B have Domain Type set to Product. The ClassB relationship has Domain Type set to Class.

The first figure in this topic shows a promotion named Promo-D, where CP-A has the following structure: CP-A has a simple product relationship named SP-A defined and a Product Class named ClassB. Another simple product relationship named SP-B is defined and associated with ClassB. For SP-A, Default is set to 1 and the attribute values 2 and 4 (of Attrib-A) are included for this relationship. For SP-B, Default is set to 2 and the attribute values 4, 1, and 2 (of Attrib-B) are included for this relationship.

Customized CP-A. This image is described in surrounding text.

The second figure in this topic shows the customized CP-A with the following structure: CP-A has a simple product relationship named SP-A defined and a Product Class named ClassB. Another simple product relationship named SP-B is defined and associated with ClassB. SP-A has a default quantity of 1 and the attribute value 3. SP-B has a default quantity of 1 and the attribute value 2.


Expected Output for Handling Attribute Defaults Example. This image is described in surrounding text.

The third figure in this topic shows the expected output when Promotion Automatch is set to Default Cardinality, which is as follows: SP-A has a default quantity of 1 and the attribute value 2. SP-B has a default quantity of 1 and the attribute value 2. SP-B has a default quantity of 1 and the attribute value 4.

The third figure in this topic shows the expected output when Promotion Automatch is set to Min Max Cardinality, which is as follows: SP-A has a default quantity of 1 and the attribute value 2. SP-B has a default quantity of 1 and the attribute value 2. SP-B has a default quantity of 1 and the attribute value 4.

In both cases (that is, when Promotion Automatch is set to Default Cardinality and Min Max Cardinality), the expected output is the same. Note the following:

  • The attribute value of 3 on SP-A is changed to 2 , because 3 was not specified in the include list in Promo-D for SP-A.

  • The existing SP-B remains unchanged, because its attribute value of 2 is permitted in Promo-D, although it is not the first in the list.

  • The added SP-B has an attribute value of 4.

To apply a promotion to a customizable product

  1. Create the product structure for CP-A and Promo-D as shown in .

  2. Add CP-A to a quote or order line item, and then customize CP-A as shown in .

  3. Associate Promo-D to CP-A using the promotion picker.

The third figure in this topic shows the expected output for attribute defaults when Promotion Automatch is set to Default Cardinality, and when Promotion Automatch is set to Min Max Cardinality.

Note: The expected output for attribute defaults when you apply a promotion to a customizable product is the same whether Promotion Automatch is set to Min Max Cardinality or Default Cardinality.

For more information about how Siebel CRM behaves depending on the Promotion Automatch argument value, see ApplyPromotionDefaults Method.