Tree Views (Hierarchical Views)

What are Tree Views used for?

The main uses for Tree Views are:

• Listing of hierarchical records, where records are organized and grouped in hierarchies. This allows users to "drill down" to identify and select the required record.
• But they are also used in "Component Lookups", which are needed to allow users to select related records from within a Business Process.

  The most common examples for Tree Views are

  • Department (e.g. "Which Department is responsible?")
  • Location (e.g. "Which Location is being Audited?")

What is required to define a Tree View?

Before defining a Tree View, you will need to decide:

• Which is the primary field to best to identify the record. The most common examples are
  • Department (Department Name)
  • Location (Location Name)
• You will need to know which Relationship is used to describe the "Parent-Child" relationship.
• What kind of filter, if any, needs to be applied to the List View? Examples could be:
  • Active Departments
  • "My" Location, and all Locations below it
• What additional fields maybe needed to identify the record. Some examples are
  • Department Code
  • Location Code
  • Location Type
• Who has access to this Tree View?

Note: Upgrade from a version prior to v2025.2.1 will convert the deprecated tree view to the list tree view with only the primary field in it. Additional columns will need to be added manually to the list view