As long as your content types are setup as subtypes of each other then its possible. Add something similar to the types in your content model definition:
<type name="yg:doc"> <title>Basic YG Document</title> <parent>cm:content</parent> <!– rest of your definition of your type goes here –> </type>
Once your types are defined correctly, file out the config for Action Wizards in your web-client-config-custom.xml. This is a snipet from my file:
<config evaluator="string-compare" condition="Action Wizards"> <!– The list of aspects to show in the add/remove features action –> <!– and the has-aspect condition –> <aspects> <aspect>yg:docVariables</aspect> <aspect>yg:taxAudience</aspect> <aspect>yg:taxGeography</aspect> <aspect>yg:taxIndustry</aspect> <aspect>yg:taxMarketSegment</aspect> <aspect>yg:taxProduct</aspect> <aspect>yg:taxResearchArea</aspect> <aspect>yg:taxCategory</aspect> <aspect>yg:taxFramework</aspect> <aspect>yg:taxReportType</aspect> <aspect>ygarticipants</aspect> <aspect>ygueDate</aspect> <aspect>yg:ClientInfo</aspect> <aspect>yg:CustomDocType</aspect> <aspect>yg:CustomDocType</aspect> <aspect>yg:FormatType</aspect> <aspect>yg:MarketingDocType</aspect> </aspects> <!– The list of types shown in the is-subtype condition –> <subtypes> <type name="yg:research"/> <type name="yg:marketing"/> <type name="yg:survey"/> <type name="yg:data"/> <type name="yg:consulting"/> <type name="yg:doc"/> </subtypes> <!– The list of content and/or folder types shown in the specialise-type action –> <specialise-types> <type name="yg:research"/> <type name="yg:marketing"/> <type name="yg:survey"/> <type name="yg:data"/> <type name="yg:consulting"/> <type name="yg:doc"/> </specialise-types> </config>
Filling out this entire set of configs makes life much easier in the long run. Even though all you'd need is the 'specialise type' section the rest will come in handy.