You forgot to mention the configuration on the table features.... For the tree table to work you need to make sure these two are according to the calculations on the fields.

Hi,

I'll try to be short:

So, a table that you want to represent as a tree, its recommended to have at least 2 areas:

• The one that represent the upper level and has no connections (to the other areas of the tree);

• The one that represent all the other levels and can connect to an upper level (with a foreign key to the area above);

Besides the foreign key (lower level area to the upper area), you'll need the following fields in the lower area:

• Parent Tree Level, so it knows where in group tree the record belongs (Tree table-Parent)

• • This is usually a selection as formula/replica of the field that has this information in the upper area, that will be the Tree table-Level of the above area) (i.e: 001) 

• Own Tree Level, so it knows the record own tree level (003) (Tree table-Level)

• • Typically, it calculates 1 if itself is the upper level (foreign key empty) or the next number after the above.
    

• Auxiliary field to calculate its ID within the tree level (that can itself represent the order, or another field to order the records within the tree levels) (i.e:004)
  

• Tree Record ID, usually a concatenation of all tree (ie: 001.003.004) (Tree table-Design)

These 3 in bold are the main ones that are absolutely needed for a tree to work. Other fields (including the foreign key) are optional, but recommended for an auto-filled tree.

Example with Processes -> Group (with tree representation):

EDIT: Inside the forms, you can use them as "Tree List" (with "In Tree" option selected) with the columns that you want to be shown. The rendering will be similar to the menu tree available on Genio. Furter options are available with some tweaking.