Container attributes are helpful when an attribute consists of other attributes or products. Instead of writing complex product rules where attributes need to be dynamically added to a configuration, an administrator can use an attribute container. An attribute container can dynamically expand, either by a set of attributes or another product.
For example, if a user is buying several computers with different configurations, each computer can be configured in the container attribute, ensuring that each product meets specific needs. A container attribute helps situations where the user wants to add similar items, but configure each one individually. They also work well when answering repetitive questions.
A container attribute's structure resembles a table with information provided in rows. Column elements are selection fields or informative labels.
Container attribute rows can either be added or deleted manually during a product's configuration or created automatically by a rule or script.
Common examples of container attributes include the following:
- Insurance questions for each member of a family
- Configuring a rack server
- Customized engineering
- Multiple billing or shipping addresses
- Site location information



