This table describes the available parameters and settings
for menu objects that represent navigation trees for object types.
For
specific instructions on how to create menu objects using Business Modeler
or MQL, refer to the Business Modeler Guide or MQL Guide.
Parameter
Description
Accepted Values/Examples
Alt
Not applicable to menu objects for trees because
the root node for a tree doesn't have a ToolTip.
--
Commands
(specified in the Items tab in
Business Modeler)
The command objects that represent the categories
in the tree.
The order of the commands is the order the categories
appear in the trees in the user interface.
Names of command objects, such as:
ENCBOMTreeCategory
AEFRelToItemTreeCategory
TMCRoutesTreeCategory
ENCPartDesignInfoTreeCategory
href
The URL executed when a user clicks the root
node for the tree. It is the Properties page for the object by default.
This page is always displayed in the right frame, called "detailsDisplay",
and not in another window or frame.
The value for the href parameter
should be a JSP and any associated parameters. You can specify the path
of the JSP using any of the standard directory macros or you can leave
off the path designation to use the registered directory. For more information,
see Macros and Expressions in UI Components.
emxDynamicAttributes.jsp
${COMMON_DIR}/emxPartInfo.jsp
${SUITE_DIR}/emxViewPartAttr.jsp
Icon
Icon for the object within ENOVIA Live Collaboration.
This setting is NOT the image that displays next to the root node
on the dynamic user interface. The emxFramework.smallIcon.SYMBOLIC_NAME
property in emxSystem.properties is used to specify that image. For more
information, see About the Icon for a Type's Tree.
The name of an image file, such as Part.gif.
Label
The text to label the tree root node. The label
can contain:
Any of the regular expression macros supported by
applications are evaluated at run time to display the current object
type name and revision.
Static text.
String resource ID
defined in the string resource property file. To internationalize the
text, you must use a string resource ID. See Internationalizing Dynamic UI Components. The system initially considers every label
text as a string resource ID. If it finds the value for this ID in the
resource file, it displays the obtained value. If not, the text is displayed
as is.
There are two other ways to define the label for a tree
node: using the TreeLabel URL parameter passed to emxTree.jsp and using
a JPO (specified with the Label Program and Label Function settings).
The order of precedence in which the tree handles these methods of getting
the root node label is:
TreeLabel URL parameter--Overrides all
other methods.
JPO--Used if TreeLabel parameter is not defined.
Label
parameter--Used only if TreeLabel and JPO are not defined.
$<type> $<name>
$<attribute[attribute_Weight].value>
Engine
- $<type> $<name>
Connected ECR
emxFramework.Common.Part
Menus
Not applicable to menu objects for trees because
trees do not have submenus.
--
Settings
Additional settings that define the behavior
and appearance of the tree.