Manual · 8

Managing apps

Apps in the main menu lists all apps with address, access and status. Only admins build and manage apps.

Creating

New app asks for the name and the access. IllusionDB derives the address from the name (“Warehouse & Shipping” → /app/warehouse-shipping/); if it is taken, a number is appended. A new app has an empty start page and is not published yet.

Templates

Instead of an empty page an app can start from a template. You pick a table, and IllusionDB builds the app from its columns, with texts in your current interface language. Afterwards it is an ordinary app that you keep adapting in the App-Builder.

Template Content
Empty one empty start page
Data entry list with a search over the display column, newest first; New opens a dialog to create, a click on a row a dialog to edit (filled in) with Delete and a confirmation
Form a form that creates one record per submission, with a thank-you message – fits a public app
Overview number of records, a chart per selection column (label format) and the ten newest records

Each column gets the fitting control: yes/no becomes a checkbox, dates a date field, numbers a number field, label columns and foreign keys a select (filled from the target table, labelled with its display column), long texts a multi-line field. Computed columns and keys the database fills in itself stay out of the forms. Data entry and Form need a table with exactly one primary key.

Settings

  • Name and description appear in the app overview at /app/.
  • Address – lower-case letters, digits and dashes. Changing it changes the link too (installed apps then have to be installed again).
  • Icon – own image for the installed app and the browser tab (PNG, JPEG, GIF, WebP; cut to a square). Without one: the initial on the accent colour.
  • Access – With login (admins plus the granted users and groups) or Public (no login).

Granting

For apps with login, Users and groups decides who may open the app. Admins always may. You can grant viewers and app users as well as groups – app users can be group members too.

Draft and publishing

You always work on the draft. Users see the published version – only Publish makes changes visible. The status shows “Unpublished changes” as long as the draft differs from the live version.

  • Every publish creates a new version (v1, v2 …). Under Versions you can restore an older one – it becomes the draft; publish afterwards to make it live.
  • Take offline locks the app until you publish it again. Draft and versions are kept.

Definition

Internally an app is a definition in JSON: pages with their elements on the grid, the menu bar and the queries. Under Definition you can edit it directly as JSON. The server checks every change (for example whether an element fits the 12-column grid) and only stores valid definitions.

Export and import

Export downloads the draft as <address>.app.json. Import (in the overview) creates a new, unpublished app from such a file. Grants are not exported – users and groups differ between instances.

The app overview

At /app/ every logged-in account sees the published apps it may open, plus the public ones. For app users this is the start page: they always land here after logging in.