Product Relationships

Estimated reading: 3 minutes 5 views

Introduction

Products can be simple or compound/complex. When refer to them as compound/complex because they are not just the single root product with its attributes but also have different child components or products.

These child components are specified by using Product Relationships at the Product Version configuration.

When you define a Relationship you have to set not only which child products are related to that relationship but also the Type and the Cardinality.

For instance, you could setup the different scenarios:

  • Make optional to select an insurance component / product.
  • Make an Optional Insurance be selected by default.
  • Make a Water Distribution be selected by default and mandatory..
  • Offer the user the option to select one product between a set of them.
  • Be able to force the user to select at least one component from a set.
  • Force to select one and only one Component from a set.
  • etc

It’s important to note that Relationships will not be shown in the Product Setup at least that you add them to a [ Product Configurator Section ]({{< relref “configuratorSections” >}}) as they are the tool to organize and show the Relationships in the UI.

Relationship Types

A relationship can be of one type of the following:

Type Description Setup Example
Product It relates a single product to the parent product. You need to selecte a record in the Product field in the Relationship A root Energy Suppply product could have a child Insurance component.
Product Set It relates a Product Set (Group of Products) You have to select an existing Product Set in the Product Set field A root product, with different optional Discount components

Cardinality

When you define a relationship you can also set the cardinality for that relationship. The cardinality control the minimun, default and maximun number of Products in a relationship to consider it valid.

Field Description
Minimun Cardinality The lower number of products to be selected to consider the configuration valid.
Default Cardinality The default number of products selected in the relationship when a new configuration is started
Maximun Cardinality The highest number of products allowed to be selected

In the followin table we share some examples:

| Min | Default | Max | Description |
|—–|——––|—–|————-|
| 0 | 0 | 0 | The component would be optional (min=0) but it couldn’t be selected (max=0) |
| 0 | 1 | 1 | The product (for Product type relationships) would be selected by default, but it would be optional |
| 1 | 1 | 1 | The product would be selected by default and readonly, as it’s mandatory to have one (min=1) |
| 0 | 0 | 4 | You could select up to 4 products from the relationship |

Required and Readonly

Note that the 1/1/1 it’s an special case, as the configurator will not only select it by default but it would also make the product selection readonly as it wouldn’t be valid to unselect it.

Leave a Comment

       
Euphoria, forever till the end of times

Euphoria

Share this Doc

Product Relationships

Or copy link

CONTENTS