^{Figure 1}

^{Figure 2}

^{Figure 3}

The tree viewer in the first tab provides the app designer with the overall structure/definition view so that one can easily spot any anomaly and fixes it immediately without too much hassle and time spent.

Clicking on the edit (pencil) icon on the right of the node allows one to configure/edit its properties right away. Upon saving the properties, the tree viewer will refresh itself.

^{Figure 4 Tree Viewer}

^{Figure 5 Editing a node}

The Permission tab provides the app designer with fine-grain control over managing the permissions of each individual element in the builder.

Clicking on the "Add Permission" button allows one to configure the permission rule for a role/group based on a permission type (see Figure 6).

For each Permission rule added, determine which element will be visible for the selected role under the Authorized column.

Visibility controls differ based on Builder types (see Figure 5, 7 & 8)

For the Form Builder, additional permission can be set at the Section element and determine whether they are hidden or read-only under the Unauthorized column on the right.

For the Datalist Builder, determine which column/filter is visible. Additionally, determine which columns is visible during export.

For the Userview Builder, additional permission can be set at the Userview Category element.

^{Figure 5 Form Builder Permission}

^{Figure 6 Configure Permission}

^{Figure 7 Datalist Builder Permission}

^{Figure 8 Userview Builder Permission}

In the second tab, the app designer can inspect where the current entity is being used. From the screenshot example above, we can tell that the form is being used in another form and also being part of a workflow process. With such a feature, the app designer will be able to manage the form design well within the scope of its usages.

The table tab is available in the Form Builder. With this feature, the app designer can tell on which other entity is sharing/writing into the same database table the current form is currently pointing too. From the screenshot example above, we can see that the table is being accessed by multiple process tools and forms.

We can also click on the Show Table Usage In Other Apps to check if there are other apps that are writing to the same table too.

At the bottom of it, existing table columns are listed down for the app designer's reference.

Labels defined in the builder will be automatically listed down here for internationalization purposes. We can define in as many languages as we want to.

Labels defined in the builder will be automatically listed down here for tooltip purposes. We can define in as many languages as we want to.

We can inspect the actual definition of the entity that we are working on here. If required, we can amend the definition within the text editor itself and click on the Update button to commit.