Overview and Studio
Two pages give the whole picture before any editor is opened. Overview lists the applications of the installation and the path that builds one. The Studio shows one application as a map — its menu, its screens, the data they use, the services they call — and edits any of it without leaving the page.
Access: Liberty Next → Overview and Liberty Next → Build → Studio, for superusers.
At a glance
Overview
The page has a header and two sections.
Header — Open the Studio, A new screen, with the assistant (the Screen Assistant), and two status pills: the integrity of the configuration — Nothing broken, or the number of errors and warnings, which opens Deploy → Integrity — and, once test cases exist, the totals of the tests, which opens Operate → Test results.
The applications — one card per application: its number of screens, menu entries, data (queries and endpoints) and services, and one line on its state: Every screen is reachable, or how many screens nothing opens and how many references are broken. A card opens the application in the Studio.
How an application is built — eight steps, in order; each says in one sentence what it is for, shows what the installation already holds, and opens the page where it is done.
| # | Step | Opens |
|---|---|---|
| 1 | Connect the data — a connector reaches a database or an API; its queries and endpoints are the only place where data is read and written. | Data → Connectors |
| 2 | Name the fields — the dictionary gives every field its label, its format, its list of values, once for every screen. | Data → Dictionary |
| 3 | Build the screens — a screen is a query shown as a grid, with its filters, its record form, its actions. | Build → Studio |
| 4 | Organise the menu — folders and entries that open a screen, a dashboard, a page. | Screens → Menus |
| 5 | Add the logic — a service is steps composed into one call; a job runs steps on a schedule; a notification tells someone. | Logic → Services |
| 6 | Show the figures — dashboards and charts for what is watched every day; the Data Explorer for what is asked freely. | Insight → Dashboards |
| 7 | Give access — roles say who sees which menu, runs which query, and which rows are theirs. | Administer → Access |
| 8 | Check and deliver — the integrity check finds what is broken; a package carries the configuration to another environment. | Deploy → Package |
The Studio
Pick an application at the top left. Its map has four columns, each with its count:
| Column | Holds |
|---|---|
| Menu | The entries of the application's menu. |
| Screens | Its screens. Icons say Has a record form and Read only. |
| Data | The queries and endpoints its screens use. A pen marks what changes data. |
| Services | The services its screens call. All services… opens the Services page. |
The search box — Find a screen, a query, a service… — narrows every column at once.
Follow the links
A click selects an item: everything it is linked to lights up, the links are drawn across the columns, and the rest fades. The selection follows the links all the way — a query lights the screens that use it and their menu entries; a menu entry lights its screen and everything that screen leads to. A second click clears the selection.
This answers, in one click, the questions that otherwise mean opening five editors: what breaks if I change this query? which screens call this service? how does a user reach this screen?
What is loose
The Studio shows what an application carries for nothing, and what is broken:
| Sign | Meaning |
|---|---|
| Warning on a screen | No menu entry and no form opens this screen. |
| Warning on a data item or a service | It no longer exists: what points at it is broken. |
| Show the N no screen uses (Data column) | The application's queries and endpoints no screen uses. |
| Orange chip at the top | The number of screens nothing opens. |
The integrity chip beside it opens the full check.
Edit in place
The panel on the right says what the selection is, what it uses and what uses it — and carries the way to change it:
| Selection | The panel shows | Buttons |
|---|---|---|
| Nothing | To look at (what is loose) and the application's dashboards, tagged not in the menu when no entry opens them. | — |
| A screen | Data it uses — each tagged reads, saves or calls —, Services it calls, Screens inside its form. | Design, Open the screen |
| A query or an endpoint | Used by, Served by the service. | Edit the query / Edit the endpoint |
| A service | Its number of steps, Used by, Exposed as. | Design the flow, Run |
| A menu entry | Opens. | Edit the menu |
The editors open over the map and come back to it, reloaded: the Screen Designer, the query editor, the endpoint editor, the service designer, the menu and the dashboards. A double click on a screen or a service opens its editor directly.
Tips & best practices
- Open the Studio before changing a shared query or service: the lit items are the test plan.
- Clear the loose items before a delivery — a screen nothing opens is either a missing menu entry or dead configuration.
- New to an application? Select its menu entries one by one: the map is its documentation.
- The Studio is one application at a time; Find usages, in each editor, searches the whole installation.
Related
- The Liberty Next workspace — the menu and how a save is applied.
- Services, Tests, API endpoints.