Designing the Catalog in Version 6.x and 7.x
The tree structure of catalogs and items in version 6.x maps in version 7.0 and 7.5 to a hierarchy of relationships within the customizable product. A relationship is roughly equivalent to a category and functions as a named group that contains one or more items. The following table maps version 6.x features to version 7.0 and 7.5 for designing a catalog.
Version 6.x | Version 7.0 and 7.5 | Comment |
---|---|---|
Design a tree structure |
Create a hierarchy of relationships within a customizable product. |
The hierarchy defines component relationships rather than being a grouping mechanism. Relationship definition includes cardinality (maximum quantity, minimum quantity, default quantity). |
Create a category |
Create a relationship. |
A relationship is a named part of a customizable product. Relationships contain one or more items. |
Add a product to a catalog |
Add a product to a relationship. |
None. |
Set item sequence in a catalog |
Set sequence of items in Structure view and sequence of group in Product UI Designer. |
None. |
Hide items in the catalog |
Can hide an item by not adding it to a UI group in the Product UI Designer. |
All products included in a customizable product, plus all attributes, resources, and links can be made visible to users. |
Show all excluded items |
Select UI control in Product UI designer that displays all items. |
Excluded items are unavailable. |
Create virtual product |
Replaced with hidden attributes. |
Virtual product functionality can be created by defining product attributes and then marking them hidden. Hidden attributes do not appear in quotes, orders, or agreements. |