...
The easiest way to see how to access the Advanced Tools is to use the existing built-in App Expenses Claims. Here are the steps:
| Steps | Screens (Click to view) |
|---|---|
|
Figure 1
Figure 2
Figure 3 |
Advanced Tools Properties
Tree Viewer
| Description | Screens (Click to view) |
|---|---|
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 |
Permission
| Description | Screens (Click to view) | |||||
|---|---|---|---|---|---|---|
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 setting for a role/group based on a permission type and determining which element will be visible for the selected role. (see Figure 6) Visibility controls differ based on Builder types (see Figure 5, 7 & 8)
|
Figure 5 Form Builder Permission
Figure 6 Configure Permission |
Usages
| Description | Screen (Click to view) |
|---|---|
| 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. |
|
Table
| Description | Screen (Click to view) |
|---|---|
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. |
|
i18n Internationalization
| Description | Screen (Click to view) |
|---|---|
| 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. |
|
Tooltip
| Description | Screen (Click to view) | |||||
|---|---|---|---|---|---|---|
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.
|
|
Diff Checker
| Description | Screen (Click to view) | ||
|---|---|---|---|
The Diff Checker capability makes collaborative works possible without losing the modifications done by other teammates who are working on the same entity at the same time. In this section, one can tell which are the changes that have been made since the initial first load of his/her builder against the copy in the server. Click on the Merge & Update button will ensure that all modifications are merged.
|
|
JSON Definition
| Description | Screen (Click to view) |
|---|---|
| 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. |
|
