Prerequisites

The steps below are made under the assumption that the underlying Component, upon which the form is based, and all the required fields, have already been defined.

It is also assumed that this Component has the correct relationships which allow it to be used as a Hierarchical Component

Please see the Web Application Component Management Tool for more details.

When you create a new Tree View, the complete form will only be shown once you selected AND saved the first two fields.

Tree View Properties

For the task of ...

I need to ...

(Re-) Naming the List View Name

Update the Tree View Name.

Selecting the Component for which to define this Tree View

Select the Root Component (select and save to continue).

When you create a NEW Tree View, you must SAVE the View at this stage to reveal the remaining fields in this form.

Defining which Relationship shall be used to build this Tree View

Select the Hierarchical Relationship (select the "Parent Relationship for the Tree).

Note:
it is the nature of Hierarchical Relationships that they always have two sides of the same relationship, Parent and Child.

For a Tree View to work, you will need to always select the "Parent" Relationship.

Selecting which Field Name is to be used to show on the Tree View

Select the Display Field.

Instead of using the Component Name for Heading the Tree View, use a different name (Optional).

Enter the required name into the field Display Label.

Defining which Form shall be opened when a user is selecting a record from the Tree View

Select the Detail Form View.

Defining Filters which shall be applied to this List View.

If you decide to define a Filter, you have the option between:

• Mandatory Filter:
  this filter will always be applied, and cannot be disabled by the Users.
• Optional Filter:
  while this filter will be applied every time the User does access this View, Users will have the option to turn off this Filter to access more records.

Should you define BOTH filters, the system will also the Mandatory Filter AND the Optional Filter.

NOTE:
you can only select a Filter from already existing Component Filters.

Defining Top Node Filters which shall be applied.

NOTE:
Top Node Filters can be used to significantly improve the time it takes to load Tree Views, which

a) Have a large number of records
b) Have (complex) filtering applied.

Please see Filters: Overview for more details.

Again, it is possible to define Optional and Mandatory Filters - like described above.

Important:
Top Node filters MUST return results which ARE included in the above-mentioned mandatory and optional filters.

Controlling access to a Tree View.

Define the Tree View Security as necessary. You need to set the

• Default Access:
  No Roles have access
  All Roles have access

which you can refine by adding Exceptions:

• Except Roles:
  Select all the Roles which are excepted from the Default Access.

Adding the Tree View to the Menu

Access the Menu Designer, and place the Tree View into the required location within the Workspace Menu Structure.