Configuring Attributes Conditionally as Required
Attribute-Based Configuration allows you to create the dependency for the target attribute if an attribute must be made conditionally mandatory while selection. This helps to prevent the user from missing any important attribute that must be entered.
The system will auto-select the remaining value if only one value is remaining in a Required attribute after the constraints are fired through a matrix or a product attribute rule.
The following table displays the data types on which you can perform this action and the value of Value Expression required.
Action | Datatypes supported | Value Expression |
Make Required | Number Text Picklist Multi-picklist |
For example, Amttus, a leading laptop manufacturer, wants to use the attributes to drive the product selection of their users. A laptop has five attributes: Color, HDD, RAM, Screen Size, and Fingerprint Reader. The following table describes the products and its attributes.
Product | A-560 | A-560m | A-440 | A-440m | A-320 | A-320m |
Color | Black | Black | White | White | Black | White |
HDD | 1 TB | 2 TB | 500 MB | 500 MB | 1 TB | 1 TB |
RAM | 8 | 16 | 4 | 8 | 8 | 16 |
Screen Size | 14 HD | 14 HD | 15 | 15 HD | 14 | 14 HD |
Fingerprint Reader | Yes | Yes | Yes | Yes | No | Yes |
The following table describes scenarios where you can use this feature.
Scenario | Target Attribute | Value Expression |
---|---|---|
You want to ensure that the user selects Screen Size. | Laptop Screen Size |