The Liberty Next workspace
The framework's own pages — the editors of the configuration, the administration of the install, its operation, its deployment and its documentation — form a workspace of their own, Liberty Next, offered to superusers in the application picker after the applications. The applications' menus keep their space for the end users.
At a glance
Opening it
- In the application picker of the sidebar, Liberty Next comes after the applications.
- The button at the right of the top bar — Liberty Next — the framework's pages — opens it from any application; inside the workspace, the same button reads Back to <app> and returns to the last application used.
Users who are not superusers see neither the entry nor the button.
The menu
Build — the configuration of the applications, in the order an application is built:
| Page | Edits | See |
|---|---|---|
| Assistant | Opens the AI assistant. | AI assistant |
| Connectors | Queries, tables, sequences and lookups of SQL connectors; endpoints of API connectors; connector settings. | Connectors, Queries |
| Dictionary | Entries, enums, lookups, sequences. | Dictionary |
| Screens | Grids, dialogs, tabs, actions — the Screen Designer. | Screens |
| Menus | The sidebar tree of each application. | Menus |
| Actions | Shared actions reused by screens. | Actions and lifecycle |
| Charts | Saved charts. | Charts |
| Dashboards | Dashboards and their widgets. | Dashboards |
| Explorer | The Data Explorer's models. | Build a model |
| Report templates | The report templates written by the operators; the PDF branding of the install is under App. | — |
| Notifications | Notification rules. | Notifications |
| AI | What each application ships for the AI assistant: starter questions and playbooks. | AI assistant |
| Integrity | The cross-checks of the whole configuration. | — |
Administer — the install:
| Page | Edits | See |
|---|---|---|
| App | Every setting of the install: application, server log, sign-in, Nomaflow, change packages, licence, AI assistant, notifications, OpenID Connect, PDF branding. | App settings |
| Pools | Database connections: address, credentials, size, schema and DB-link maps. | Connectors |
| Access | Users and roles. | Users, Roles and permissions |
| Theme | Colours and branding. | — |
Operate — Monitoring (The Monitoring page) and Jobs, the Nomaflow jobs (Jobs).
Deploy — Package (Packages), Changes (Change packages), History (Configuration history).
Document — the Developer reference, the Documentation reports and the Release notes of the running version.
Each page has its own address — /liberty/screens, /liberty/app… —, so a page can be bookmarked or sent as a link. The former addresses of the Settings page and of the Nomaflow Package, Changes and Integrity pages lead to the new pages.
Saving
- Save sends the edited configuration; the server validates it against its model and refuses an invalid one with the reason.
- The file is written. A version of the previous content is kept in Deploy → History.
- The change is applied: at once when the server watches its files (Hot reload in Administer → App, the default), or with Reload config otherwise.
Reload config, at the top of every editor page, re-reads every configuration file into the running server — Reloaded — 12 connectors, 340 dictionary entries, 4 apps. A reload rebuilds the connectors from the new files; if they fail, the previous configuration stays active. The pools are not reloaded by the file watcher, so that a running query never loses its connection: after changing a pool, use Reload config.
Files are rewritten from the saved model: comments written by hand in a file are not kept.
Tips
- Save one editor at a time and check the result before moving to the next.
- Keep the configuration under version control on the server; History keeps the recent versions, not the whole story.
- Prefer the editors to hand edits: they refuse what the server would refuse. The Developer reference says, for every setting, which page edits it.