Example - Adding a Custom Sub-Palette to a System Palette
Looking again at the number of model builder nodes on the Supervised sub-palette, you realize that users may not notice your new node easily. One way to give your node more prominence is by adding your own sub-palette to the Modeling palette and placing the node there.
First, then, you must define your custom sub-palette by adding a User Interface (Palettes) section to the file:
<UserInterface>
<Palettes>
<Palette id="modeling.av_modeling" systemPalette="modeling" label="AV Modeling"
labelKey="av_modeling.LABEL" description="Contains AV mining-related modeling
nodes" descriptionKey="av_modeling.TOOLTIP"/>
</Palettes>
</UserInterface>
Note that you must explicitly specify systemPalette to identify the system palette that you are extending.
Then, in the main User Interface section for the node, you specify that it is to appear on this sub-palette:
<Node id="my.avmodeler" type="modelBuilder" customPalette="modeling.av_modeling"
label="AV Modeler">
Custom sub-palettes are always placed after the system sub-palettes.
Note: If you wanted to add more nodes to the AV Modeling sub-palette, their specification files would
not need a User Interface (Palettes) section provided that the AV Modeler extension was
loaded first.