All Collections
Next-gen pages
Creating a back office in next-gen
Creating a back office in next-gen
Discover how to visualize and work with your data in a next-gen application with the back office page template.
Betty Blocks avatar
Written by Betty Blocks
Updated over a week ago

After reading this article you’ll know the following:

  • What the back office is

  • How to create your back office using a page template

  • How to configure permissions for roles in your application

The transition of Betty Blocks to the next-gen embraces some changes in the way users are going to interact with data. Previously, we had a whole Back office section visible within the builder bar to enable citizen developers to manage their applications' data. Now things get much more accessible and the back office feature is available in the page builder as a separate template having all essential functionality to comfortably view, edit and create new data records in an application.

What is back office?

The back office is used for managing the data in your application. Within the back office, it’s possible to create tables for models made in the data model section. These tables are aimed to create, update and delete data in your application, and also view data from your models in a rather convenient way.

Here you can see the example of a new back office view. This one displays the client base and enables an application’s administrator to organize the overview, view, and manage the personal information of each client. More about creating such tables in the next chapter.

Setting the back office template

As already mentioned, now it’s possible to create and manage your application’s data simply through the page builder with help of the back office template. When creating a new page, pick up the Back office template.

Then you would have to come up with a name, type of page, set partials, and model with your database that will be shown within this page.

As the page is generated, you’ll see it in a page builder overview. Mind the warning on top of it saying that you need to configure the permissions of the “create”, “update” and “delete” actions in order to use this template. It means you can select roles in your application that will be granted permission to perform certain actions.

In the example below, we are going to enable the ‘admin’ role to view and perform actions in the back office. To do this, just click once on the free space on the right side of a page, then hit “Edit permissions” in the actions section (the options menu on the left). In the slide-out setting menu, tick the needed role and set the permission to ‘Allowed’. Press 'Save' as you finish configuring it.

Don’t forget that there are also model permissions and they have to be set as well. Check this article to learn more about it.

In case you need another back office page, let’s say, not only for clients but also for companies, you can create it separately but then easily create switching between these two back office pages. In order to enable this, you need to select a side menu (if you’re using partial) and click on ‘Edit partial’ (1), then pick up the needed list item (2) and select a page with another back office page (3) - “Companies” in our case.

Note: If you’re not using a partial, start from step 2.

Press the 'Play' button in order to compile the page and enable the changes you've made.

Did this answer your question?