Tree (report component)

The report component type Tree can display nested lists as well as the hierarchical structure of the model or other relationships. In comparison to the list, the tree is output in a table and can therefore be assigned a table format.

In addition, nesting must not/cannot be done explicitly analogous to the list components. The attributes and queries defined under node objects are executed recursively to a maximum depth. At each level of recursion, the lines of the specific objects are indented one level further.

The tree can also be combined with a table in the Tree table component.

Configuration:

Property	Description
Node objects	This shows which queries or attributes are configured for determining the node objects. You also have the option here to reference or create queries and attributes using the text box or the buttons to the right of the text box, which are used to determine the objects from one level of the tree to the next. The application is recursive. This means that the context objects represent the first level. The objects found on the basis of the context objects in the first step represent the second level. Based on these objects, the attributes and queries are consulted to determine the next level. This happens either until no more objects are found or the Maximum depth termination condition is reached.
Maximum depth	Enter the maximum depth of the tree here. When it is reached, then no further queries or attributes are evaluated to determine the subsequent levels.
Report empty tree	With this property, the heading is reported even if no content can be determined for the rows of the tree.
Column widths	Specify the following values: In the first place the indentation per level In the second place the width of the last column (the minimum width of the output of the objects). How to enter column widths in the Enter String Array dialog is described under Enter column widths.
List in index of tables	If a table directory is included in the print report, this property will include the generated tree in it.
Display	Categories can be referenced under this attribute. This can limit the visibility / execution. Most application scenarios require category and access control related visibility. The logic of the evaluation is as follows: If at least one category is specified, the object must be an instance of that category. Otherwise, no evaluation of the category are carried out If at least one user group is specified, the current user must be a member of at least one of these user groups If at least one Access Control List is specified, the user must have the View permission in the Access Control List If at least one condition component is specified, at least one condition must apply. If this logic is not sufficient, a differentiated logic can be configured via the condition components.
Report parent nodes in every row	With this property, the parent objects in the row are also output for entries from the second level.
Collapsed from level	Enter here the number of the level (starting from the first level) from which the tree is displayed collapsed. The number is entered as an integer. For example, the tree table is collapsed from the third level on if the value 3 is entered. By default, the value 5 is entered.
Column headings	Enter headings here for the columns of the sublevels. Enter the headings in descending order as a comma-separated list.
BPM Portal
Maximum number of rows	For example, if the maximum number of rows is set to 10, the tree will be split from the 11th row. You can switch between the parts of the tree with arrow buttons (pagination).
Excel export	If this property is activated, the tree can be exported to an Excel file. You can define a template for the Excel export.