What you can build
Liberty Next combines a few building blocks — connectors and their queries, screens, menus, dashboards, jobs, roles — configured from Settings. This page lists what teams build with them, what each case relies on, and where to start.
The pattern is always the same: connect the database, write the queries, build the screens, organise the menu, set the roles.
1. Admin apps over existing tables
A database (customers, products, contracts, tickets…) and a team that must read, filter, edit and export it.
| Provided | Where |
|---|---|
| Grid with sorting, filters, grouping and saved views | Screens, Saved views |
| Edit dialog with tabs, lists of values, conditional fields | Dialog builder, Form conditions |
| Add / edit / delete, in the dialog or in the grid, with Excel / CSV import | Screens |
| Excel export | Excel export |
Audit columns filled by the server (LOGIN, SYSDATE) and a history table (audit_table) | Dictionary, Audit trail |
| Record locks: two users cannot edit the same row at once | Monitoring |
| Interface in English and French, translated labels | i18n |
To configure: the pool, the queries (the CRUD wizard writes them from a table), the screens and the menu. Most of the time goes into the SQL.
Start with: Tutorial — Build a CRM, or CRUD over an existing table for a single screen.
2. Dashboards
| Provided | Where |
|---|---|
| KPI, chart (bar, line, area, pie) and table widgets on a 12-column grid | Dashboards, Charts |
| A period with presets, and the change compared with the previous period | Dashboards |
| Filters from the dictionary, shared by every widget | Dashboards |
| A cache with a Refresh button | Dashboards |
| Free analysis by the users themselves — pivot, charts, drill, calculated fields, saved analyses, Excel / PDF export | Data Explorer |
To configure: the aggregate queries (usually GROUP BY on the period), then the widgets.
Start with: Tutorial — CRM → Dashboard.
3. An interface over an ERP database
A faster interface for the ERP's operators, reading and writing its database without changing the ERP.
| Provided | Where |
|---|---|
| Oracle, SQL Server and PostgreSQL pools; Oracle thick mode for older servers | Connectors |
| One app on several environments (development, test, production) through a Pool picker | Connectors → Multi-pool |
| JD Edwards conventions: Julian dates, right-justified codes, data dictionary import | Dictionary, Scan a table |
| Read-only screens, writes enabled screen by screen | Screens |
For JD Edwards, the ready-made apps cover the common needs: Nomajde for administration and master data, Nomasx-1 for security analysis over any connected application. For another ERP, the CRM tutorial shows the pattern: point the pool at the database and write the queries.
4. Integration and data loading
Nomaflow runs scheduled or manual jobs made of steps.
| Provided | Where |
|---|---|
| Jobs on a cron schedule or run by hand, with retries (fixed or exponential wait) and a timeout | Schedules, Steps |
| Steps: SQL query, SQL copy between databases, file load, HTTP call, LDAP sync, Python, call of another job | Steps |
| API connectors with Basic, Bearer, API key or OAuth2 authentication | Connectors |
| Run history per step, live log | Run history |
| Notifications on failure, success or a missed schedule — in the app, by e-mail, or through a connector | Notifications |
To configure: the source and target connectors, then the job's steps. Python only for what the steps cannot express — see Plugins.
Start with: Getting started with Nomaflow.
5. Apps for outside users
An app opened to users outside the team, each seeing only their own rows.
| Provided | Where |
|---|---|
| Sign-in through an OpenID Connect provider | Sign-in, OIDC SSO |
| Roles: which menus, screens and queries each user reaches | Roles & permissions |
| Data scope: rows filtered by user attributes, applied by the server | Row-level access |
Queries filtered on the signed-in user with {{LOGIN}} | Parameter binding |
| App name, colours and fonts | Liberty Next → Administer → Theme |
6. Workflows
Approve, reject, escalate: a status column and screens that adapt to it.
| Provided | Where |
|---|---|
| Fields shown, required or locked depending on the status | Form conditions |
Rows read-only once closed (editable_when) | Form conditions |
| Buttons running queries, with confirmation and a prompt for a reason | Actions and lifecycle |
| Notifications when a screen writes a row, or from an action | Notifications |
| Reminder jobs on a schedule | Nomaflow |
Start with: Multi-step form.
When another tool fits better
- Consumer-facing apps. The grid-and-dialog interface is made for operators.
- Mobile-first apps. The application works on a tablet but is designed for a desktop screen.
- Real-time co-editing. Record locks prevent conflicting edits; there is no shared live editing.
- Screens with a unique layout (Kanban board, Gantt chart, map): the grid-and-dialog model does not suit them.
Liberty Next fits when most screens list and edit data from a database, with dashboards, jobs and integrations around them.
Pick your path
| You want to… | Start with |
|---|---|
| Learn the framework on a full example | Tutorial — Build a CRM |
| See every feature working on real-looking data | The sales demo |
| Build a first screen quickly | First app walkthrough |
| Administer JD Edwards | Nomajde |
| Install the framework | Installation |
| Find how to do one thing | The cookbook, starting with CRUD over an existing table |