Reference: Catalogue UI Levels

in 15 5 major, the catalogue toolbox system was revamped to be more data driven based on the table of contents, in contrast to the old system which relied on the component tab creator to design component tabs note that there are no changes for existing catalogues, and all will work as they have previously until the new features are adopted, such as by turning on the "use toc toolbox" option in product catalogues if the option is off, only the documentation for "undefined", "none", "subsection", and "section" are applicable all others will have no effect to facilitate this, the old and unclear ui levels that were previously present in the toolbox have been renamed to make their purpose more clear, and to align better with the extension content docid\ k9e w3zzkehm38jtvqkyu cet 15 0 major and below cet 15 5 major and above card tab section section subsection subsection tool group icon none undefined undefined none invisible the practical effect of any ui level that existed in cet 15 0 has been unchanged, with only their display names changed ui level definitions invisible this ui levels hides itself and all of its child entries useful for hiding product lines without losing the data associated with its entry in the table of contents undefined a default ui level that is assigned when a table of contents entry is created has no meaning, and should be changed to one of the other ui levels defined in this document none a ui level that acts that it doesn't exist, with all of its children acting as though it was at the same level as the parent entry useful for applying grouping and organisation, especially when the grouping is internal and should not be visible to the user the below example shows two examples side by side using tabs, where the "hanging" product level is functionally the same as having the two hanging plants directly under "small plants" tool group this ui level specifies that this particular entry in the table of contents is a product button docid\ l2jrbivjudj7ixbuu tgz , with all child entries being located within the group's popup window, instead of being directly in the toolbox itself subsection this ui level specifies that this entry should represent a extension content docid\ k9e w3zzkehm38jtvqkyu , as defined in the toolbox guidelines section this ui level specifies that this entry should represent a extension content docid\ k9e w3zzkehm38jtvqkyu , as defined in the toolbox guidelines this section is collapsible, and can be sent to custom tools tab this ui level specifies that the entry represents a extension header docid 329vj0pqzc4rwqu qmv3d , and automatically modifies the extension header to use a tab switcher to allow switching between each defined tab if a tab entry is present in the table of contents, it is required that all sibling entries are also tabs (since it wouldn't be clear where the other entries should be located) card this ui level specifies that this entry should appear in the toolbox as a component tab, with all of its child entries appearing within that component tab all table of contents must start with at least one card entry an entry with this ui level will have a button on the right of the ui level drop down that can be used to do some basic configuration of the component tab that is generated by the system at this point in time, the only configurable aspect is the icon used within the header and toolbox component tab