Create a Flexible Explorer Object Node

Full Name

The full name of the element is populated by the application and cannot be modified.

Name

Input a valid short name for the element in the text box, special characters are not allowed.

Description

Input a brief description of the element (can contain up to 120 characters of text).

Flexible Explorer Text

Input a value to specify the display text on the root node of the hierarchy.

The text can contain any of the attributes of the element such as Name and Description, or any other valid PML1 expression.

For example:

NAMN + ' - ' + DESC

The syntax places a dash (-) between the name and description of the element.

Another example is:

<ISNAMED ? NAMN : TYPE + ' ' + STRING(TYSEQUENCE)>

The syntax uses the NAMN attribute if the element is named, otherwise uses the TYSEQUENCE attribute.

Pseudo attributes can also be used in the text field.

Alternatively, click to display the FlexibleExplorer Expression Editor window. Refer to Create a Flexible Explorer Expression for further information.

Flexible Explorer Formula Type

Select a formula type from the drop-down list for the generated nodes.

The available options are:

• PML expression

• PML function

• External method

• From owners attribute

Refer to Flexible Explorer Formula Types for further information.

Flexible Explorer Formula

Input a valid Flexible Explorer formula corresponding to the Flexible Explorer Formula Type.

Refer to Create a Flexible Explorer Formula for further information.

Flexible Explorer Sorting

Select a sorting method from the drop-down list for the node. The available options are:

• None.

• Same as on Parent.

• Default set on toplevel.

• Natural Alpha Numeric.

• Database Sequence.

• Natural unless Type Forces Sequence.

Flexible Explorer Context Menu

Context menus can be defined via a PML expression and look for standard CAF menus defined in the UIC files. A set of menus can be defined to allow the system to use the first menu found. The user can define special menus for particular element types. For example:

'AVEVA.PBS.Element_' + TYPE + '.Menu' > AVEVA.PBS.Element.Menu > AVEVA.PBS.Default.Menu

In this example, the system searches for a context menu called 'AVEVA.PBS.Element_' + TYPE + '.Menu' (for example, AVEVA.PBS.Element_PIPE.Menu). If that is not defined, the system searches for AVEVA.PBS.Element.Menu and if that is not defined, it searched for AVEVA.PBS.Default.Menu.

Alternatively, click to display the FlexibleExplorer Expression Editor window. Refer to Create a Flexible Explorer Expression for further information. Context menus can be defined via a PML expression and look for standard CAF menus defined in the UIC files. A set of menus can be defined to allow the system to use the first menu found. The user can define special menus for particular element types. For example:

'AVEVA.PBS.Element_' + TYPE + '.Menu' > AVEVA.PBS.Element.Menu > AVEVA.PBS.Default.Menu

In this example, the system searches for a context menu called 'AVEVA.PBS.Element_' + TYPE + '.Menu' (for example, AVEVA.PBS.Element_PIPE.Menu). If that is not defined, the system searches for AVEVA.PBS.Element.Menu and if that is not defined, it searched for AVEVA.PBS.Default.Menu.

Alternatively, click to display the FlexibleExplorer Expression Editor window. Refer to Create a Flexible Explorer Expression for further information.

Flexible Explorer Icon

Input a value to specify the display icon for the node in the hierarchy. The icon can be assigned statically by inputting the icon name or dynamically generated with a PML1 expression. If no icon is specified, the icon representing the object type displays, for example EQUI.

Note:
The icon must exist in the resource file with name AvevaSharedIcons.recources

Alternatively, click to display the FlexibleExplorer Expression Editor window. Refer to Create a Flexible Explorer Expression for further information.

Flexible Explorer Group By

Input a valid expression to group elements beneath the current node by attribute or Programmable Macro Language (PML) 1 expression. An additional level is created in the hierarchy.

For example, a number of Equipment (EQUIP) elements have the attribute FUNC set to B, C, and unset. The Flexible Explorer Group By attribute is set to the Function (FUNC) value and the EQUIP elements are grouped accordingly. Note that the value of the additional folder nodes is the value of the FUNC attribute. If the value of FUNC on /C1101 is changed from B to C the EQUIP element moves from folder B to folder C.

Flexible Explorer Recurrent Node

Nodes that follow a repeating structure can be defined as recursive to allow an infinite depth with a simple definition.

For example, a PBSOBN (named PBSOBN1) is created to display the EQUI elements in a project. A second PBSOBN (named PBSOBN1) is created immediately beneath PBSOBN1, with settings as follows:

Set the Flexible Explorer Formula attribute to MEMB (the Member (MEMB) attribute of the owning element), the hierarchy displays the child elements beneath each EQUI element. In order for the hierarchy to display the child elements beneath each subsequent element at all levels in the hierarchy it is required to set the Flexible Explorer Recurrent Node to the owning PBSOBN (PBSOBN1 in this example).