Apps
In Liberty Next, an app is a connector that has a menu: its name appears in the app picker at the top of the sidebar, and picking it shows its menu. There is no separate app object to create — the connector is the app.
At a glance
What belongs to an app
Everything an app shows is filed under its connector's name:
| Element | Where it is set | Stored under |
|---|---|---|
| Queries (tables, queries, sequences, lookups) | Liberty Next → Build → Connectors | The connector itself. |
| Dictionary entries, enums, lookups, sequences | Liberty Next → Build → Dictionary, the connector's scope | [connectors.<app>.*] — on top of the shared entries. |
| Screens | Liberty Next → Build → Screens, the app's chip | [screens.<app>.<id>] |
| Menu | Liberty Next → Build → Menus, the app's chip | [menus.<app>] |
| Charts | Liberty Next → Build → Charts, the connector's scope | [charts.<app>.<id>] |
| Dashboards | Liberty Next → Build → Dashboards, the app | [dashboards.<app>.<id>] — a menu item opens it with the target <app>.<id>. |
Shared actions have a single namespace. Nomaflow jobs are not tied to an app.
The app picker
The picker sits at the top of the sidebar:
- it lists the apps whose menu the user can see, and appears only when there are at least two;
- picking an app switches the sidebar menu and the workspace tabs to that app — it is a switch, not a filter;
- the choice is remembered in the browser;
- when the app's connector has several pools, a Pool picker next to it chooses the database instance every screen runs against — see Connectors → Multi-pool.
A connector's show_in_switcher (on by default) and home settings decide whether it is offered in the picker and which menu item opens first. See Make a connector an app.
Creating an app
- Liberty Next → Build → Connectors — create the SQL connector and its pool, then its queries (the CRUD wizard writes them from a table).
- Liberty Next → Build → Screens — build the screens on these queries.
- Liberty Next → Build → Menus — + Add scope, pick the connector, add the items that open the screens.
- Back on the connector, check show_in_switcher and, optionally, set home.
The Screen Creation Assistant chains steps 1 to 3 for one table. The CRM tutorial builds a complete app.
Copying and moving an app
| Need | Tool |
|---|---|
| A second app built on an existing one (another database, a test copy). | Clone on the connector: copies the queries with the dictionary scope, screens, menu, charts and dashboards under the new name. See Clone a query or a connector. |
| Move an app, or part of it, to another environment (development → production). | Packages: pick the screens, menus, dashboards… to ship, download the ZIP with everything they depend on, import it on the target. See Packages. |
| Rename a connector, a screen or a query. | Rename in its editor — every reference is rewritten. |
Ready-made apps
Nomasx-1 and Nomajde are delivered as ready-made apps with their Nomaflow jobs. They are installed and upgraded as described in Deploy the licensed apps. Their screens, menus and dictionary are visible and editable in Settings like any app; an entry marked override keeps local changes through upgrades.
Who sees an app
An app appears for a user when its menu has items that user may open. Roles decide which menu items, screens and queries each user reaches — see Roles & permissions and Menus → Permissions and roles.
What's next
- Make a connector an app — the two settings that put a connector in the picker.
- Plugins — Python functions called from jobs and screen actions.
- Translations — labels per language.