Displaying Actions Menu on an Information Page
1. Define the actions in an actions.xml file. See Defining a new action for more information.
2. Add the actions to an action model. See Defining a new action for more information. When defining the action model, you will need to add the attribute “menufor” for the object type that you are defining the actions for.
<model name="part actions" menufor="wt.part.WTPart">
<action name="view" type="object"/>
.....
</model>
<action name="view" type="object"/>
.....
</model>
To get a menu to fly out from the main menu, add a submenu to the action model.
 | PTC recommends including the incremental attribute in the action and model elements to customize an OOTB action and action model definition, respectively. For more information, see Defining a New Action, Defining a New Action Model. |
Recommended method:
<model name="part actions" menufor="wt.part.WTPart" incremental="">
<submodel name="submenu_new"/>
</model>
<model name="submenu_new">
<action name="newViewVersion" type="part"/>
</model>
<submodel name="submenu_new"/>
</model>
<model name="submenu_new">
<action name="newViewVersion" type="part"/>
</model>
Legacy method:
<model name="part actions" menufor="wt.part.WTPart">
<action name="action_1" type="object"/>
<submodel name="submenu_new"/>
</model>
<model name="submenu_new">
<action name="newViewVersion" type="part"/>
</model>
<action name="action_1" type="object"/>
<submodel name="submenu_new"/>
</model>
<model name="submenu_new">
<action name="newViewVersion" type="part"/>
</model>
3. If you don’t want to rely on the “menufor” action model, you can specify an action model by calling setActionListName(action_model_name) in your info page builder:
public InfoConfig buildInfoConfig(ComponentParams params) throws WTException {
InfoComponentConfigFactory factory = getComponentConfigFactory();
InfoConfig infoConfig = factory.newInfoConfig();
// override the “menufor” action model with a different Action Model
infoConfig.setActionListName("my type infopage actions");
....
return infoConfig;
}
InfoComponentConfigFactory factory = getComponentConfigFactory();
InfoConfig infoConfig = factory.newInfoConfig();
// override the “menufor” action model with a different Action Model
infoConfig.setActionListName("my type infopage actions");
....
return infoConfig;
}
| | Your builder should extend DefaultInfoComponentBuilder or AbstractInfoComponentBuilder. |
Trouble Shooting
Problem Description | Solution |
|---|---|
Icons for some actions are missing | Only the actions that are displayed in a table toolbar have icons in the actions menu. |
Some actions don’t appear in the list in the UI | There may be a validator configured on it which may hide the action in certain conditions. See Action Framework for Windchill Client Architecture for information on configuring an action with a validator. Add jcaDebug=true to the url to see even the hidden actions. With the jcaDebug option enabled, you’ll see more information in the menu, and there will be an action at the end of the list that takes you to the action model report for that menu.  |