Default language.

Arranging nodes in tree view tables


 The nodes in each level of a tree view table are sorted alphanumerically. To arrange nodes in a logical order, use hidden sort levels. For example, suppose your source form contains this data:

tree_view_data_no_sort.gif

If you use the Type, Severity, Priority, and Description fields as levels in a tree view table, their data is sorted alphabetically and appears in an unintuitive order:

tree_view_alpha_sort.gif

To arrange each level in a logical manner, add Type Sort, Severity Code, and Priority Code sort fields to the form:

tree_view_data_and_sort.gif

Then add the new sort fields as levels to the tree view table field in the order shown in the preceding figure. The following figure shows the resulting tree view table when the new sort levels are visible and when they are hidden:

tree_view_logical_sort.gif

For information about how to set the sort order and visible levels, see Setting-sort-order-and-visible-levels.

When the sort levels are hidden, child nodes of a node in a hidden level appear as children of the first visible ancestor of the hidden node.

Best practice
We recommend that you hide only levels used for sorting. Do not hide levels that contain data leaf nodes. If a visible parent node with multiple hidden leaf nodes is selected, workflow selects only the request represented by the first hidden leaf node in most instances. It does not select the entire set of leaf nodes associated with the parent node. See Selecting-requests-in-list-view-and-tree-view-tables.

Using PERFORM-ACTION-TABLE-SELECT-NODE

The PERFORM-ACTION-TABLE-SELECT-NODE command selects nodes according to a specified row and column (level) offset. If a tree view table contains hidden levels, this action might select a hidden node. If it does, the selection is rejected and the first visible ancestor is selected instead.

For example, in both of the following tables, the action was instructed to select row 1, column (level) 2:

tree_view_select_hidden.gif

If the action is instructed to select row 1, column 3 in the preceding example, it selects the Change node in both tables.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*