Building an application might sound like a huge challenge. Where are you going to start: in the datamodel or with some webpages? In this article we’ll show you how all the different options the UI builder overview has to offer.

In the left menu, you can see the group structure of your application. In there, you can view the hierarchy of the groups your application uses. These groups include the pages of your application.

In the window on the right, occupying the rest of your screen, you can see the pages located in each specific group.

​New page: This button adds a new page to your application.
​New group: A group is a helpful function to help you organize your web structure, a group can be filled with pages or other groups.
​Question mark [ ? ]: Displays the following panel.

​Searchbar: The searchbar enables you to easily find your webpages. Search on the full path, description, group or redirect to URL and see the results pop up.

​Name: The name is only visible to you and your colleagues, so this is a good way for you to make groups to organize and quickly find your pages.
​Path: With the path field it is possible to set a pathname addition to your webpages.
​Inherit authentication profile: if you select this option the group inherits the authentication profile of the group it is in.
​Authentication profile: With this option you can select which authentication profile you want to use on all the pages inside the group. More information about Authentication profiles can be found here: What are Authentication profiles?
​Enable page caching: The enable page caching function lets you define whether the page can be cached locally on the visitors' device. Caching a page results in faster loading times when a user revisits that page.
​Enable debug logging: If you activate debug logging on your page, a log record will be created every time the page is visited. You also can turn on the debug logging for a page's Action in page settings (open the action and click edit) in order to see exactly what the action does. The debug logging feature in the page settings is only for the page, not for its action.

As mentioned above, grouping your pages keeps you application organized and easier to implement Authentication profiles.

​Root: The root map is available in every application, it is the “highest directory in the hierarchy", you can think of it as the start or beginning of the group structure. The root map contains all other folders and/or files in your application.
​Gear: Opens the settings of the group. Done by either clicking the gear in the breadcrumb or by clicking the gear on the group itself.

The group options let you change what you assigned to the group while making it, if you would change the path name, the path of the pages you created within the group will automatically change to the changed name as well.

​Name: The name is only visible to you and your colleagues, so this is a good way for you to make groups to organize and quickly find your pages.
​Path: With the path field it is possible to set a pathname addition to your webpages. If you would change the path name, the path of the pages you created within the group will automatically change to the new path name.
​Authentication profile: With this option you can select which authentication profile you want to use on all the pages inside the group. More information about Authentication profiles can be found here: What are Authentication profiles?
​Enable page caching: The enable page caching function lets you define whether the page can be cached locally on the visitors' device. Caching a page results in faster loading times when a user revisits that page.
​Enable debug logging: If you activate debug logging on your page, a log record will be created every time the page is visited. You also can turn on the debug logging for a page's Action in page settings (open the action and click edit) in order to see exactly what the action does. The debug logging feature in the page settings is only for the page, not for its action.

​Dependencies: Dependencies are combinations of different functionalities and parts of your application the current group is dependent on. See What are Dependencies? for more information.

​Type: The type of the page is one of the two options you choose when creating the page: HTML for custom HTML pages or UI for pages made with the UI builder.
​Method: Methods on web pages are used for handling requests between your web browser and the Betty Blocks server. The chosen method on a single web page either defines to retrieve data or to create new data. More information about HTTP methods can be found here: What are HTTP methods on web pages?
​Full path: Show the full path of your webpages. Does not include the host, but is combined of all (nested) groups the page is in, and its path. So let's say your webapp is

then the folder part is the group and the mypage part is the path.
​Description: A short description to describe the page.
​Group: The group tag shows which group the page belongs to.
​Redirect to: This shows the page that your webpage is redirecting to.
​Cached: This shows if you have enabled the page caching function for the certain page.
​Debug: This show if you have enabled the debug logging function for the certain page.

​Collapse sidebar button: To collapse/expand the application’s groupstructure menu.
​Number of pages: The records function shows the amount of records you have in the current group.
​Refresh: By clicking Refresh or pressing R on your keyboard, your data will be updated, if recently altered.