pgkiln 0.45.0 → 0.46.0

package/db/migrations/106_form_designer.sql

@@ -0,0 +1,102 @@
+-- ---------------------------------------------------------------------
+-- 106: Form Designer: the application's administrators build their own
+-- data entry forms in the running application.
+--
+-- The developer places a region of type 'form_designer' and lists in its
+-- settings (config.sources) the tables and views it offers: the columns
+-- forms may show and change, the column that identifies a row, and what
+-- forms on it may do at most (add, change, delete rows). Who may design
+-- forms is an authorization scheme (config.design_authz); without one
+-- nobody can. Those settings are part of the region, so they travel with
+-- the application export.
+--
+-- A user form is a definition (source, fields with labels, help, required,
+-- display and default, the columns of its row list, the actions it allows)
+-- under a name, kept per region; published forms are used by everyone who
+-- can see the region, drafts only by designers. User forms are data of the
+-- installation (like meta.data_report): not part of the application export,
+-- kept when an application is replaced. Applications reach the table only
+-- through meta.user_forms and the two functions; the runtime checks every
+-- definition against the region's offered columns before it renders or
+-- saves, and reads and writes rows as the application's database role, so
+-- grants and row level security apply.
+-- ---------------------------------------------------------------------
+alter table meta.region drop constraint region_type_check;
+alter table meta.region add constraint region_type_check
+  check (type in ('report', 'form', 'chart', 'cards', 'static', 'grid', 'calendar', 'dynamic', 'facets', 'tasks', 'workflows', 'map', 'tree',
+                  'template_component', 'smart_filters', 'display_selector', 'list', 'data_reporter', 'ai_assistant', 'plugin', 'url', 'search',
+                  'login', 'form_designer'));
+
+create table meta.user_form (
+  id          serial primary key,
+  app_id      int  not null references meta.app on delete cascade,
+  region_id   int  not null references meta.region on delete cascade,
+  name        text not null check (length(btrim(name)) between 1 and 80),
+  description text check (length(description) <= 500),
+  published   boolean not null default false,
+  definition  jsonb not null check (jsonb_typeof(definition) = 'object' and length(definition::text) <= 32000),
+  created_by  text not null,
+  updated_by  text not null,
+  created_at  timestamptz not null default now(),
+  updated_at  timestamptz not null default now(),
+  unique (region_id, name)
+);
+create index user_form_app_idx on meta.user_form (app_id);
+revoke all on meta.user_form from public;
+
+create view meta.user_forms with (security_barrier) as
+  select id, region_id, name, description, published, definition, created_by, updated_by, created_at, updated_at
+    from meta.user_form
+   where app_id = meta.app_id();
+grant select on meta.user_forms to public;
+
+-- Save a form of a Form Designer region of the current application: a new
+-- one (p_id null) or an existing one (p_id). Returns its id. Whether the
+-- user may design forms (the region's authorization scheme) is checked by
+-- the runtime before it calls this.
+create function meta.save_user_form(p_region int, p_id int, p_name text, p_description text, p_definition jsonb, p_published boolean default false)
+returns int
+language plpgsql security definer set search_path = meta, pg_catalog as $$
+declare
+  v_user text := meta.app_user();
+  v_app  int  := meta.app_id();
+  v_id   int;
+begin
+  if v_user is null or v_user = 'nobody' then
+    raise exception 'sign in to design forms';
+  end if;
+  if not exists (select 1 from region r join page p on p.id = r.page_id where r.id = p_region and p.app_id = v_app and r.type = 'form_designer') then
+    raise exception 'unknown form designer region %', p_region;
+  end if;
+  begin
+    if p_id is null then
+      insert into user_form (app_id, region_id, name, description, published, definition, created_by, updated_by)
+      values (v_app, p_region, btrim(p_name), nullif(btrim(p_description), ''), coalesce(p_published, false), p_definition, v_user, v_user)
+      returning id into v_id;
+    else
+      update user_form
+         set name = btrim(p_name), description = nullif(btrim(p_description), ''), published = coalesce(p_published, false),
+             definition = p_definition, updated_by = v_user, updated_at = now()
+       where id = p_id and app_id = v_app and region_id = p_region
+      returning id into v_id;
+      if v_id is null then
+        raise exception 'form % does not exist', p_id;
+      end if;
+    end if;
+  exception when unique_violation then
+    raise exception 'There is already a form named "%".', btrim(p_name) using errcode = 'P0001';
+  end;
+  return v_id;
+end
+$$;
+
+-- Delete a form of a Form Designer region of the current application.
+create function meta.delete_user_form(p_region int, p_id int) returns boolean
+language sql security definer set search_path = meta, pg_catalog as $$
+  with d as (delete from user_form where id = p_id and region_id = p_region and app_id = meta.app_id()
+                and meta.app_user() is not null and meta.app_user() <> 'nobody' returning 1)
+  select exists (select 1 from d)
+$$;
+
+revoke all on function meta.save_user_form(int, int, text, text, jsonb, boolean), meta.delete_user_form(int, int) from public;
+grant execute on function meta.save_user_form(int, int, text, text, jsonb, boolean), meta.delete_user_form(int, int) to public;

package/db/migrations/107_app_version.sql

@@ -0,0 +1,9 @@
+-- ---------------------------------------------------------------------
+-- 107: an application's version (APEX: Application Definition → Version,
+-- "Release 1.0"), shown in the footer of its pages with "Back to top".
+-- New applications start with 'Release 1.0'; existing ones have none (no
+-- version in the footer) until a developer sets one in Settings. It travels
+-- with the export like the other columns of meta.app.
+-- ---------------------------------------------------------------------
+alter table meta.app add column version text check (length(version) <= 40);
+comment on column meta.app.version is 'The application''s version, e.g. Release 1.0: shown in its pages'' footer (107)';

package/docs/apex-feature-parity.md

@@ -7,7 +7,7 @@ open item and open an issue or pull request; see [CONTRIBUTING.md](../CONTRIBUTI
 Legend: ✅ available · 🟡 partial (see notes) · ❌ not yet · ➖ not planned (a deliberate choice,
 or better served by the PostgreSQL ecosystem; see the notes and [extensions](guide/15-extensions.md))
 
-Last reviewed: 2026-10-15 (sprint 83: Component Settings and Component Groups; sprint 82: Report Queries; sprint 81: Application Computations and Shortcuts in Shared Components; sprint 80: the master grid's first row selected when the page opens and after a search; grid cells as text with their format mask until edited, with cell navigation by arrow keys, Enter, F2 and Escape; sprint 79: generated dashboards with sums, donuts and lines, leaving out charts that say nothing; applications open in their own light or dark mode until the user chooses, per application; a user menu with Appearance and Sign in when signed out; the developer toolbar's App and Page texts and debug state; the report search's column scope in the magnifier; sprint 78: generated faceted search reports with one column per foreign key, the faceted search's total row count, Show all and Yes/No values, one search field, friendly headings and number formats in generated grids and master-detail pages, friendly names in the Create Application wizard's page list; sprint 77: the Page Designer's layout and tree by display position, button positions, the tree's context menu with Duplicate and Copy to other page, Show Common / Show All, Go to group and the Template Options dialog; display positions, button positions and side-column page templates at runtime; sprint 76: the interactive report's menus and pagination, date items in the date format; sprint 75: the SQL Workshop's Object Browser and tabs; sprint 74: the builder's information architecture: Shared Components grid, Settings tabs, application home search and tasks; sprint 73: the Create Application wizard on one page with page types and features; sprint 72: the runtime chrome compared with APEX 26.2's: the developer toolbar, the Iris look, the navigation bar's Help menu and Install button; sprint 71: generated applications compared with APEX 26.2's: labels, foreign key names in reports, file columns, format masks, the Home page and the dashboard; sprint 70: treemap, sunburst and timeline charts; sprint 69: dragging tasks on a Gantt chart; sprint 68: the Data Reporter's welcome page, Find my workspace; sprint 67: REST source catalogs from OpenAPI documents, a workspace's export and import (two rows added); sprint 66: a blueprint from an existing application; sprint 65: facet charts; sprint 64: approval vacation rules and expiration policies; sprint 63: range, box plot and stock charts; sprint 62: workspace preferences (SQL Workshop and RESTful services per workspace), extension links, Manage backups across applications, SQL Workshop utilities with object reports, About Database and a database monitor; sprint 61: the builder's screens compared with APEX 26.1: the workspace sign-in page, the Administration menu with workspace message, environment banner and utilization, the SQL Workshop home, the App Gallery, application groups and cross application reports (four rows added); sprint 60: isolated workspaces with their own database logins, row-level security on pgkiln's tables and workspace database roles, workspace administrators; sprint 59: the Page Designer's help pane, Quick edit from the developer toolbar; sprint 58: page groups; sprint 57: region templates hero, title bar, buttons container, inline dialog and drawer, wizard with wizard progress, the carousel; sprint 56: Generate DDL and Schema Comparison in the SQL Workshop, `pgkiln ddl` and `pgkiln compare`; sprint 55: an editable login page with a Login region and the Minimal page template, Forgot password through the application's mail service; sprint 54: interactive grid views, the single row view, group by and chart; sprint 53: application settings, user preferences and items kept per user, dynamic translations, `meta.data_export` and data export downloads, display image and geocoded address items; sprint 52: every dynamic action event and action, Ajax callbacks, an error handling function, the session timeout warning; sprint 51: checked imports, application backups, availability and Run only, feedback, type-specific attribute help; sprint 50: lost update detection, warn on unsaved changes, the URL and search regions with search configurations, the developer toolbar with a session state viewer, and e-mail through SMTP with OAuth2, Microsoft Graph, Amazon SES and HTTP APIs; import checks, application availability, property help and e-mail compared again; 2026-10-06: pgkiln 0.31.0, in progress: static application files and the Execute JavaScript dynamic action; region, item, dynamic action and process plug-ins; conditional and dynamic theme styles; XML and Excel in `meta.parse_data`, zips in SQL, `meta.v_boolean`; file items in S3-compatible object storage; map layers by the visible area and as vector tiles; a graphical query builder; tenants for workflows and tasks; application files as YAML and region static IDs; Lucide icons and icon modifiers; PWA push notifications; 0.30.0: 136 icons and an icon picker; an axe-core accessibility audit; cropping pictures; session sharing between applications; twenty-two built-in languages; 0.29.0: workspaces; the Iris base style; drawers; built-in template components including the metric card; Theme Roller dark-mode colours, live preview and template options on items and report columns; report selection across pages; instance settings; fourteen built-in languages; 0.28.0: AI with Claude and OpenAI; 0.27.0: Data Reporter; sample data generator; create application from several sheets, pasted data or existing tables; 0.26.0: working copies with a three-way merge; theme, library and boilerplate applications with subscriptions; 0.25.0: Gantt, pyramid and polar charts; map layers, clustering and server-side spatial filters; REST data sources that write back from forms and grids and synchronise into tables, OAuth2 password and refresh-token grants; debug messages per request and an install/upgrade log; `meta.web_request()` and `meta.parse_data()`; Theme Roller style variants and template options; 0.24.0: automations with several actions, error handling per row and runs from SQL; invoke-API workflow steps; Unload Data in the Data Workshop; create page wizards for cards, calendar, chart, map, faceted search, form and master-detail; create an application from a file; 0.23.0: interactive grid aggregates, frozen/moved/resized columns, layouts and saved grid reports, master-detail, row actions and copy/paste; download processes, execution chains in the background, workflow processes, branches to a function's URL or another app, the Dialog Closed event; number format masks, automatic time zone, runtime messages in German, French and Spanish; SQL scripts, Quick SQL, a query builder, XML loading and data load definitions; custom authentication, lists, page and application locks with developer comments, supporting objects; 0.22.0: keyset paging, report PDFs and REST collections streamed from a cursor, database-account authentication; 0.21.0: HTTP-header authentication behind a reverse proxy; 0.20.0: a popup list of values with server-side search; 0.19.0: row-range pagination, maximum row counts and row limits, lazy loading and caching of regions, streamed CSV/Excel downloads; 0.18.0: calendar week/day/list views with drag and drop, bubble/gauge/funnel/radar charts and drill-down, smart filters, a region display selector and more facet types, computations, conditional branches, build options, menu buttons, REST data sources and web credentials, rich text/Markdown, rating, combobox, date range and QR code items; 0.17.0: an App Builder home, workspace dashboard and utilities like APEX's; 0.16.0: a Page Designer with drag-and-drop layout, a code editor with autocomplete, template components and plug-ins, parallel branches and versions of workflows, the `pgkiln` command line with one file per component; 0.15.0: drop and paste files, heat maps, filtering a report by the map area; 0.14.0: stacked, combo, scatter and pie charts, several files per upload item; 0.13.0: map and tree regions; 0.12.0: REST modules in the builder; 0.11.0: workflows and Progressive Web Apps; 0.10.0: LDAP, SAML, "Keep me signed in", document templates, JSON loading, approvals and the task list; pgkiln installs no application, HR is an example).
+Last reviewed: 2026-10-15 (sprint 90: Comment Out in the page designer, gallery labels in title case; sprint 89: the Object Browser's schema, one row of tabs, blank NULLs, Modify column; sprint 88: home cards with colour bands and round icons, the hero on the page background, a page footer with the version and Back to top; sprint 87: the Create Application wizard reloads the page list for a schema, RLS badges, the alias from the name; sprint 86: the page designer by page number, HTML error pages in the builder; sprint 85: the Form Designer, beyond APEX; sprint 84: the date picker, facet menus; sprint 83: Component Settings and Component Groups; sprint 82: Report Queries; sprint 81: Application Computations and Shortcuts in Shared Components; sprint 80: the master grid's first row selected when the page opens and after a search; grid cells as text with their format mask until edited, with cell navigation by arrow keys, Enter, F2 and Escape; sprint 79: generated dashboards with sums, donuts and lines, leaving out charts that say nothing; applications open in their own light or dark mode until the user chooses, per application; a user menu with Appearance and Sign in when signed out; the developer toolbar's App and Page texts and debug state; the report search's column scope in the magnifier; sprint 78: generated faceted search reports with one column per foreign key, the faceted search's total row count, Show all and Yes/No values, one search field, friendly headings and number formats in generated grids and master-detail pages, friendly names in the Create Application wizard's page list; sprint 77: the Page Designer's layout and tree by display position, button positions, the tree's context menu with Duplicate and Copy to other page, Show Common / Show All, Go to group and the Template Options dialog; display positions, button positions and side-column page templates at runtime; sprint 76: the interactive report's menus and pagination, date items in the date format; sprint 75: the SQL Workshop's Object Browser and tabs; sprint 74: the builder's information architecture: Shared Components grid, Settings tabs, application home search and tasks; sprint 73: the Create Application wizard on one page with page types and features; sprint 72: the runtime chrome compared with APEX 26.2's: the developer toolbar, the Iris look, the navigation bar's Help menu and Install button; sprint 71: generated applications compared with APEX 26.2's: labels, foreign key names in reports, file columns, format masks, the Home page and the dashboard; sprint 70: treemap, sunburst and timeline charts; sprint 69: dragging tasks on a Gantt chart; sprint 68: the Data Reporter's welcome page, Find my workspace; sprint 67: REST source catalogs from OpenAPI documents, a workspace's export and import (two rows added); sprint 66: a blueprint from an existing application; sprint 65: facet charts; sprint 64: approval vacation rules and expiration policies; sprint 63: range, box plot and stock charts; sprint 62: workspace preferences (SQL Workshop and RESTful services per workspace), extension links, Manage backups across applications, SQL Workshop utilities with object reports, About Database and a database monitor; sprint 61: the builder's screens compared with APEX 26.1: the workspace sign-in page, the Administration menu with workspace message, environment banner and utilization, the SQL Workshop home, the App Gallery, application groups and cross application reports (four rows added); sprint 60: isolated workspaces with their own database logins, row-level security on pgkiln's tables and workspace database roles, workspace administrators; sprint 59: the Page Designer's help pane, Quick edit from the developer toolbar; sprint 58: page groups; sprint 57: region templates hero, title bar, buttons container, inline dialog and drawer, wizard with wizard progress, the carousel; sprint 56: Generate DDL and Schema Comparison in the SQL Workshop, `pgkiln ddl` and `pgkiln compare`; sprint 55: an editable login page with a Login region and the Minimal page template, Forgot password through the application's mail service; sprint 54: interactive grid views, the single row view, group by and chart; sprint 53: application settings, user preferences and items kept per user, dynamic translations, `meta.data_export` and data export downloads, display image and geocoded address items; sprint 52: every dynamic action event and action, Ajax callbacks, an error handling function, the session timeout warning; sprint 51: checked imports, application backups, availability and Run only, feedback, type-specific attribute help; sprint 50: lost update detection, warn on unsaved changes, the URL and search regions with search configurations, the developer toolbar with a session state viewer, and e-mail through SMTP with OAuth2, Microsoft Graph, Amazon SES and HTTP APIs; import checks, application availability, property help and e-mail compared again; 2026-10-06: pgkiln 0.31.0, in progress: static application files and the Execute JavaScript dynamic action; region, item, dynamic action and process plug-ins; conditional and dynamic theme styles; XML and Excel in `meta.parse_data`, zips in SQL, `meta.v_boolean`; file items in S3-compatible object storage; map layers by the visible area and as vector tiles; a graphical query builder; tenants for workflows and tasks; application files as YAML and region static IDs; Lucide icons and icon modifiers; PWA push notifications; 0.30.0: 136 icons and an icon picker; an axe-core accessibility audit; cropping pictures; session sharing between applications; twenty-two built-in languages; 0.29.0: workspaces; the Iris base style; drawers; built-in template components including the metric card; Theme Roller dark-mode colours, live preview and template options on items and report columns; report selection across pages; instance settings; fourteen built-in languages; 0.28.0: AI with Claude and OpenAI; 0.27.0: Data Reporter; sample data generator; create application from several sheets, pasted data or existing tables; 0.26.0: working copies with a three-way merge; theme, library and boilerplate applications with subscriptions; 0.25.0: Gantt, pyramid and polar charts; map layers, clustering and server-side spatial filters; REST data sources that write back from forms and grids and synchronise into tables, OAuth2 password and refresh-token grants; debug messages per request and an install/upgrade log; `meta.web_request()` and `meta.parse_data()`; Theme Roller style variants and template options; 0.24.0: automations with several actions, error handling per row and runs from SQL; invoke-API workflow steps; Unload Data in the Data Workshop; create page wizards for cards, calendar, chart, map, faceted search, form and master-detail; create an application from a file; 0.23.0: interactive grid aggregates, frozen/moved/resized columns, layouts and saved grid reports, master-detail, row actions and copy/paste; download processes, execution chains in the background, workflow processes, branches to a function's URL or another app, the Dialog Closed event; number format masks, automatic time zone, runtime messages in German, French and Spanish; SQL scripts, Quick SQL, a query builder, XML loading and data load definitions; custom authentication, lists, page and application locks with developer comments, supporting objects; 0.22.0: keyset paging, report PDFs and REST collections streamed from a cursor, database-account authentication; 0.21.0: HTTP-header authentication behind a reverse proxy; 0.20.0: a popup list of values with server-side search; 0.19.0: row-range pagination, maximum row counts and row limits, lazy loading and caching of regions, streamed CSV/Excel downloads; 0.18.0: calendar week/day/list views with drag and drop, bubble/gauge/funnel/radar charts and drill-down, smart filters, a region display selector and more facet types, computations, conditional branches, build options, menu buttons, REST data sources and web credentials, rich text/Markdown, rating, combobox, date range and QR code items; 0.17.0: an App Builder home, workspace dashboard and utilities like APEX's; 0.16.0: a Page Designer with drag-and-drop layout, a code editor with autocomplete, template components and plug-ins, parallel branches and versions of workflows, the `pgkiln` command line with one file per component; 0.15.0: drop and paste files, heat maps, filtering a report by the map area; 0.14.0: stacked, combo, scatter and pie charts, several files per upload item; 0.13.0: map and tree regions; 0.12.0: REST modules in the builder; 0.11.0: workflows and Progressive Web Apps; 0.10.0: LDAP, SAML, "Keep me signed in", document templates, JSON loading, approvals and the task list; pgkiln installs no application, HR is an example).
 
 ## At a glance
 
@@ -38,7 +38,7 @@ two, REST source catalogs and the workspace export, with their features.)
 | App Builder: create, edit, delete, run apps | ✅ | Builder at `/builder` |
 | Create application wizard | ✅ | Blank app with its own database role and schema, started from a **boilerplate application** if wanted; **from a file**: CSV/TSV/XLSX/JSON/XML, where an Excel workbook with several sheets (or JSON with several arrays) becomes several tables, with a preview to include or leave out each sheet, edit table/column names, types and primary keys, and **foreign keys proposed** from matching columns; **from pasted data** (CSV/TSV text); **from existing tables** (pick the tables and views of a schema). Each gives a report and form per table, navigation and an optional dashboard (a chart per table), plus an optional faceted search for a single table, all created in one transaction. (sprint 73) **One page like APEX's**: name, icon and description, appearance (theme style, side or top menu, accent), a **page type per table** (interactive report with form, faceted search, cards, calendar, master detail, interactive grid, report, none; large tables proposed as a grid), **features** (About page, access control roles, activity reporting, feedback, theme style selection, PWA, push), settings (alias, authentication, first user, language) and a boilerplate under Advanced; a progress message, then straight to the new application. (sprint 71) The generated pages read like APEX's: human labels (abbreviations, run-together words, column and table comments), plural page and menu names with singular form titles, foreign keys shown by the parent's name in reports, `bytea` columns as one file item with their name/mime/size/updated columns, number format masks, a pencil per report row, the Dashboard after Home with *(none)* and top-N charts, and a Home page with a hero and a card per page. **Missing:** blueprints (26.1) |
 | Create page wizards | ✅ | Report and form, interactive grid, form, cards, calendar, chart, map, faceted search and master-detail (stacked grids) from any table or view, with defaults from the catalog (columns, key, dates, positions, foreign keys), an optional modal form page and a navigation entry; also from SQL (`meta.generate_page`). No side-by-side or drill-down master-detail, no wizard for smart filters or trees |
-| Page Designer | ✅ | IDE-style window (dark or light): component tree, a layout canvas with drag and drop (with keyboard and button alternatives) and a gallery of regions, items and buttons, a filterable property editor; undo/redo; panes become tabs on phones. Settings forms for report, grid, chart, cards, calendar, faceted search, smart filters, display selector, map, tree and template component regions. A code editor for SQL, PL/pgSQL, JSON and HTML with highlighting and autocomplete of tables, columns and `:ITEM` binds (no extra libraries). Drag and drop needs a mouse; on touch screens the Arrange buttons move components. (sprint 77) The layout draws the page template's display positions (banner, breadcrumb bar, left/right column, body, footer) as drop zones and a region's button positions; the rendering tree groups by position and has a context menu (create in or below, Duplicate, Copy to other page, expand/collapse all, delete); the property editor has Common / All, Go to group and a Template Options dialog; a page number in the toolbar. No nested regions (APEX's sub regions) and no Comment Out |
+| Page Designer | ✅ | IDE-style window (dark or light): component tree, a layout canvas with drag and drop (with keyboard and button alternatives) and a gallery of regions, items and buttons, a filterable property editor; undo/redo; panes become tabs on phones. Settings forms for report, grid, chart, cards, calendar, faceted search, smart filters, display selector, map, tree and template component regions. A code editor for SQL, PL/pgSQL, JSON and HTML with highlighting and autocomplete of tables, columns and `:ITEM` binds (no extra libraries). Drag and drop needs a mouse; on touch screens the Arrange buttons move components. (sprint 77) The layout draws the page template's display positions (banner, breadcrumb bar, left/right column, body, footer) as drop zones and a region's button positions; the rendering tree groups by position and has a context menu (create in or below, Duplicate, Copy to other page, expand/collapse all, (sprint 90) Comment out with a COMMENTED_OUT build option, delete; no Create Sub Region: no nested regions); the property editor has Common / All, Go to group and a Template Options dialog; a page number in the toolbar. No nested regions (APEX's sub regions) and no Comment Out |
 | Shared components | ✅ | (sprint 74) A grid of ten groups with counts like APEX's, a searchable, sortable list per type with Create, and Settings-backed types linking to their Settings tab ([mapping below](#shared-components-apex-links-and-pgkiln)). Navigation menu, **lists** (static entries with nesting, badges, conditions, authorization and build options, or a query; for list regions, the navigation menu and the navigation bar), authorization schemes, build options, lists of values, application items and processes, access control, globalization, template components and plug-ins, web credentials, REST data sources, data load definitions, supporting objects |
 | Export / import | ✅ | `meta.export_app()` / `meta.import_app()`: portable JSON, also in the builder (new applications; `pgkiln import --replace` and the MCP `import_app` update one in place, live for every user at the commit). (sprint 51) **Checked imports**: `pgkiln import --check` (`--dry-run`, `--force`), the MCP import (by default) and the builder's import run the Advisor inside the import's transaction (SQL planned as the application's role: missing tables, columns, functions, types, grants; references) and refuse on errors, so nothing changes; APEX doesn't check. The version an import replaces is [backed up](guide/03-builder.md#backups) first ([chapter 18](guide/18-cli.md#checking-before-an-import)) |
 | APEXlang: human-readable, diffable app files; static IDs (26.1) | ✅ | `pgkiln export --format dir`: one JSON file per component with sorted keys, SQL and HTML in sibling files, references by static id instead of database ids; `pgkiln import --replace` updates an app in place, `pgkiln diff` compares ([chapter 18](guide/18-cli.md)). (0.31) **`--format text`**: the same files as YAML (a strict subset any YAML tool reads) with the SQL and templates inline, read back losslessly ([text files](guide/18-cli.md#text-files-apexlang)); regions have a stored **Static ID** (exported as their key, rendered as `data-static-id`), other components are named by their stored names. The syntax is YAML rather than APEXlang's own, so APEXlang files don't import |
@@ -176,7 +176,7 @@ two, REST source catalogs and the workspace export, with their features.)
 | Translated applications (26.1: text-message-based translation of one app) | ✅ | One app with translations, like 26.1; XLIFF 1.2 and CSV export/import, coverage per language |
 | Text messages (`APEX_LANG.MESSAGE`, `&APP_TEXT$…`) | ✅ | `meta.message()`, `&APP_TEXT$NAME.`, fallback to the base and primary language |
 | Language from browser, preference or session | ✅ | Browser, user preference or primary; `?lang=`; right-to-left languages |
-| Date and timestamp format masks | ✅ | Per app or per language; (sprint 76) date items show and read the application's date format (or their own) with a calendar button |
+| Date and timestamp format masks | ✅ | Per app or per language; (sprint 76) date items show and read the application's date format (or their own) with a calendar button; (sprint 84) pgkiln's date picker (keyboard, week start, Today, Clear) for date items, date ranges, grid date cells and facet date ranges; timestamps keep the browser's field |
 | Dynamic translations (`APEX_LANG.LANG`: translated data values, e.g. list of values entries) | ✅ | (sprint 53) Shared Components → Dynamic translations; `meta.lang(text)` in a query returns the value in the session's language (base language fallback); exported with the application |
 | Number format masks, automatic time zone | ✅ | Oracle-style number masks (`999G999G990D00`, `FML…`, `0000`, `%`, `S`/`MI`/`PR`, `EEEE`, `X`, `RN`) on report, grid and cards columns, charts and number/display items, in the language's separators with the app's currency; Automatic Time Zone (browser, My account, app or database), `timestamptz` shown in it ([chapter 14](guide/14-globalization.md)) |
 
@@ -269,6 +269,9 @@ Small but real differences, for teams comparing the two:
 - An import can be checked before it commits (`pgkiln import --check`): SQL that names a missing
   table or column refuses the deployment instead of failing at run time.
 - E-mail through SMTP with OAuth2, Microsoft Graph, Amazon SES and HTTP APIs, not only SMTP with a password.
+- (sprint 85) A **Form Designer** region ([chapter 4](guide/04-pages-and-regions.md#form_designer-form-designer)): the
+  application's administrators build and publish data entry forms in the running application, on the tables and
+  columns the developer offers, with grants, row level security and lost update detection applying.
 
 ## Roadmap (proposed priority)
 

package/docs/guide/03-builder.md

@@ -199,6 +199,11 @@ Every builder page has the same frame, modelled on an IDE:
 
 On phones the rail gets narrower and the breadcrumb shows only the current page.
 
+(sprint 86) An address under `/builder` that leads nowhere (a deleted application or page, a typo, an
+application of a workspace you are not a member of) shows a **Page not found** page in the builder's
+theme with a link to the App Builder home; a server error shows **Something went wrong** (the error
+is in the server log, not on the page). Scripts get the plain answers they always got.
+
 ## App Builder home
 
 The home page is laid out like APEX's App Builder:
@@ -251,15 +256,15 @@ start from a file, pasted data, a blueprint or the App Gallery instead. Then:
 
 | Section | Field | Meaning |
 |---|---|---|
-| Data | Pages on the tables of | The parsing schema: an existing schema (*Show its tables* lists them under Pages), or a new, empty one named after the alias |
+| Data | Pages on the tables of | The parsing schema: an existing schema, or a new, empty one named after the alias. (sprint 87) Choosing a schema lists its tables under Pages at once, with the name and alias proposed for it (unless you already typed them); without JavaScript, *Show its tables* does it |
 | Application | Name | Display name, shown in the header. Proposed from the schema and selected when you click it, so typing replaces it |
 | | Description, Icon | Shown on the home page's hero and the About page |
 | Appearance | Theme style, Navigation, Accent colour | Iris, Lavender or Standard; a side or top menu; an own accent colour |
-| Pages | a page type per table | *Interactive report with form*, *Faceted search*, *Cards*, *Calendar* (a table with a date column), *Master detail* (a table another table refers to), *Interactive grid*, *Report* or *No page*. Tables with a single-column primary key get a modal form with their report, faceted search, cards and calendar; views and tables without such a key can't have a form or a grid. Proposed: a report with form, an interactive grid for a table of more than 100,000 rows, a report for a view. *Dashboard*: a chart per table |
+| Pages | a page type per table | *Interactive report with form*, *Faceted search*, *Cards*, *Calendar* (a table with a date column), *Master detail* (a table another table refers to), *Interactive grid*, *Report* or *No page*. Tables with a single-column primary key get a modal form with their report, faceted search, cards and calendar; views and tables without such a key can't have a form or a grid. Proposed: a report with form, an interactive grid for a table of more than 100,000 rows, a report for a view. (sprint 87) A table with [row level security](08-security.md) shows *RLS · n* (its number of policies), or *RLS, no policies* in red: the application's role would see no rows. *Dashboard*: a chart per table |
 | Features | | *About page* (in a Help menu), *Access control* (authorization schemes `CONTRIBUTOR` and `READER` next to `ADMIN`, for the roles admin, contributor and reader), *Activity reporting* (page 9010 for administrators: page views per day and the latest activity, from `meta.app_activity`), *Feedback*, *Theme style selection* (users may choose light or dark), *Install as an app* (PWA) and *Push notifications* (needs `PGKILN_SECRET_KEY`) |
-| Settings | Alias | Lowercase URL name: `inventory` gives `/a/inventory` |
+| Settings | Alias | Lowercase URL name: `inventory` gives `/a/inventory`. (sprint 87) It follows the name as you type it (*Café Orders* → `cafe-orders`) until you change it yourself |
 | | Authentication | *App users* (a login page and a user list), *HTTP header* (a trusted reverse proxy names the user, see [chapter 8](08-security.md#http-header-authentication-reverse-proxy)), *Database accounts* (PostgreSQL login roles and their passwords, see [chapter 8](08-security.md#database-accounts-postgresql-roles)), *Custom* (your own PL/pgSQL function, see [chapter 8](08-security.md#custom-authentication-a-plpgsql-function)) or *None* (a public app) |
-| | First user / Password | The first user; they get the `admin` role. An existing account is reused (its password isn't changed) |
+| | First user / Password | The first user; they get the `admin` role. An existing account is reused (its password isn't changed). (sprint 87) Hidden while Authentication is *None* |
 | | Language | The application's primary language |
 | Advanced | Start from | Shown when there are **boilerplate** applications (Settings → Application type): their pages, shared components and settings are copied into the new application, which keeps its own name, alias, role and authentication ([application types](#application-types-and-subscriptions)) |
 
@@ -268,7 +273,9 @@ Creating the app also:
 - creates the database role `app_<alias>` with `SELECT/INSERT/UPDATE/DELETE` on all tables,
   `USAGE` on sequences and `EXECUTE` on functions in the schema, plus **default privileges**,
   so tables you create later (as the owner, e.g. in the SQL Workshop) are usable by the app straight away;
-- creates page 1 *Home*, a navigation entry, and an authorization scheme `ADMIN` (role `admin`);
+- creates page 1 *Home*, a navigation entry, and an authorization scheme `ADMIN` (role `admin`); (sprint 88) the home
+  page is a hero with the name and icon on the page background and a card per page, each with a colour band and its
+  icon in a round badge; the version is *Release 1.0*;
 - shows a progress message while it works and then opens the new application's page in the builder,
   with what was created (and anything left out) as a message.
 
@@ -539,6 +546,11 @@ its pages in four groups.
 
 ## The page designer
 
+(sprint 86) A page's address in the page designer is its application's id and its number:
+`/builder/apps/<app id>/pages/<page number>`, with `?c=region-<id>` (and so on) for the selected
+component, so a link names the page you mean. The older `/builder/pages/<internal id>` still works:
+a browser that opens it is sent to the page's number.
+
 The page designer has three panes, as in APEX's Page Designer. From 1024 pixels wide they sit
 side by side; on phones and portrait tablets they are tabs (**Tree**, **Layout**, **Properties**):
 choosing a component opens the Properties tab.
@@ -567,8 +579,12 @@ choosing a component opens the Properties tab.
   *Create dynamic action*, *Create region below*, **Duplicate** (a copy right after it; a region comes with its
   items and buttons, names get `_2`), **Copy to other page…** (to the end of a page of the same application; items
   named `P<n>_` get that page's number, a region's buttons and items come along, references in SQL are not changed),
-  *Expand all below*, *Collapse all below* and *Delete*. The arrow keys move through the menu, Escape closes it.
-  APEX's *Create Sub Region* (pgkiln has no nested regions) and *Comment Out* (use a build option) are not there.
+  *Expand all below*, *Collapse all below*, (sprint 90) **Comment out** and *Delete*. The arrow keys move through the
+  menu, Escape closes it. **Comment out** (APEX's) leaves a component (a region, item, button, dynamic action,
+  validation, process, computation or branch) out of the page without deleting it: it gets the
+  [build option](#shared-components) `COMMENTED_OUT`, made with the status *Exclude* when first needed, and is struck
+  through in the tree; **Uncomment** takes it off again (another build option of the component is left alone).
+  APEX's *Create Sub Region* is not there: pgkiln has no nested regions.
 - **Middle: the Layout**: the page template's display positions as labelled zones (Banner, Breadcrumb bar,
   the side column of a side-column template beside the Body, Footer), each with its regions on the 12-column
   grid, each region with its items and its buttons in their button positions, as they will be placed on the page; under it a **gallery** of region types, item types
@@ -692,6 +708,7 @@ out, other keys are kept, columns the query no longer returns stay listed so you
 | `ai_assistant` | The AI service (those the application may use), system prompt, welcome text, placeholder, error message, tool rounds per question, questions per conversation, public or not, and the context queries and tools as JSON (checked when saving: query shapes, parameter types, REST data sources and authorization schemes that exist) ([AI assistant](04-pages-and-regions.md#ai_assistant-ai-assistant)) |
 | `report` (also) | *Ask in your own words (AI)*: the AI service and placeholder of the [natural-language filters](04-pages-and-regions.md#natural-language-filters-ask-in-your-own-words) |
 | `data_reporter` | Data sources (a table or view each: static id, label, description, offered columns with labels and format masks), who may share reports, rows per page ([Data Reporter](04-pages-and-regions.md#data_reporter-data-reporter)) |
+| `form_designer` | Who may design forms (an authorization scheme), data sources (a table or view each: static id, label, description, key column, may add / change / delete rows, offered columns with labels and lists of values), rows per page ([Form Designer](04-pages-and-regions.md#form_designer-form-designer)) |
 
 Links, lists of values and the facets' report are checked when saving: a form can only point to
 pages and shared lists of values of the same application, and to report regions on the same page.
@@ -1011,7 +1028,9 @@ on Definition (`?tab=…` opens another). *Save settings* saves the first five t
 you were on. The Security tab shows only the fields of the chosen authentication type (HTTP header, database
 accounts or custom).
 
-- **Application**: name, alias, home page.
+- **Application**: name, alias, home page, and (sprint 88) the **version** (APEX: Version, e.g. *Release 1.0*): shown
+  at the bottom of the application's pages, next to *Back to top*. New applications start at *Release 1.0*; empty: no
+  version in the footer.
 - **Security**: authentication (*App users*, *HTTP header*, *Database accounts*, *Custom* or
   *None*), the database role, and **debug mode** (shows full database errors to users; development
   only). The state of the [debug messages](06-processing.md#debug-messages) is shown below it,
@@ -1241,17 +1260,22 @@ others (Quick SQL, Query Builder, Load and Unload Data, Sample Data, DDL, Compar
   statements are allowed; the result of the last one is shown (up to 500 rows). Press
   **Ctrl/Cmd + Enter** to run. The [code editor](#the-code-editor) suggests every schema, table,
   column and function the owner sees.
-- **Object Browser** (APEX's): the **schema** in the header (the session's schema by default) and a tree with a
+- **Object Browser** (APEX's): the **schema** in the header and a tree with a
   folder per object type (tables, views, materialized views, indexes, sequences, types, functions, procedures,
   triggers) and a **filter** by name. pgkiln's own schemas (`meta`, `pgkiln_plugins`) and objects that belong to an
   extension show only with **Show system objects**. **Create** (and the tiles shown when nothing is selected) opens
   SQL Commands with a CREATE TABLE, VIEW, FUNCTION, SEQUENCE or INDEX statement to fill in. A table opens in tabs:
-  **Columns** (with comments; *Add*, *Rename* and *Drop column* write the ALTER TABLE statement into SQL Commands to
-  review and run: nothing changes until you press Run), **Data** (25 rows a page), **Indexes**, **Constraints**
+  **Columns** (with comments; the toolbar's *Add*, *Modify* (type, nulls, default), *Rename* and *Drop column* write
+  the ALTER TABLE statement into SQL Commands to review and run: nothing changes until you press Run), **Data** (25
+  rows a page; NULL is a blank cell), **Indexes**, **Constraints**
   (primary key, foreign keys with the table they refer to, unique, check), **Triggers**, **Grants**, **Row level
   security** (on or off, the policies), **Dependencies** (views and foreign keys that use it, and what it uses),
   **Statistics** (rows, sizes, analyze and vacuum times) and **DDL**. A view has the same tabs where they apply; a
-  function or procedure shows its source, a trigger, index, sequence or type its definition.
+  function or procedure shows its source, a trigger, index, sequence or type its definition. (sprint 89) The tabs stay
+  on one row: Columns, Data, Indexes, Constraints and DDL (and the current one), the others under **More**. The
+  schema shown is the one you chose last (remembered for the session), else the session's schema of SQL Commands,
+  else the **parsing schema** of the application changed last in your workspace (the schema its database role
+  uses).
 - **SQL Scripts**: saved scripts, shared by the developers of the workspace. Create one in the editor, upload a
   `.sql` file (UTF-8, up to 5 MB) or save one from Quick SQL; download it again as `.sql`. **Run**
   splits the script into statements at semicolons (outside strings, comments, quoted identifiers,

package/docs/guide/04-pages-and-regions.md

@@ -819,7 +819,9 @@ Counts take the search and all *other* facets into account. Three kinds of facet
 
 - **checkbox** (the default): the most frequent values of a column, each with a checkbox; after the seventh
   the rest sit under *Show all (n)* (open when one of them is chosen), and a boolean's values read *Yes* and
-  *No*. With
+  *No*. Its ⋮ menu (APEX: the facet's menu) has *Clear* (when values are chosen) and *Sort by count* (the
+  default) or *Sort by name*; the order is a URL parameter (`r<report id>_fo_<column>=name`) that Apply and
+  Reset keep. With
   `"exclude": true` the facet gets an *Exclude the selected values* switch: the chosen values are
   then left out instead (rows where the column is empty stay).
 - **range**: a number or date column in ranges, as radio buttons ("Any", then each range). A
@@ -1127,7 +1129,7 @@ Attributes (the region's **Settings** in the page designer):
 | Key | Meaning |
 |---|---|
 | `list` | The list's name (upper case) |
-| `template` | `links` (default: nested links), `badges` (a row of tiles with the badge as the value), `cards` (a card per entry with its description), `tabs` (the top-level entries as tabs) or `wizard_progress` (numbered steps: the entry of the current page is the current step, the ones before it are done and link back; APEX: Wizard Progress) |
+| `template` | `links` (default: nested links), `badges` (a row of tiles with the badge as the value), `cards` (a card per entry with its description; (sprint 88) a colour band and the icon in a round badge, in the chart palette's order), `tabs` (the top-level entries as tabs) or `wizard_progress` (numbered steps: the entry of the current page is the current step, the ones before it are done and link back; APEX: Wizard Progress) |
 
 The HR example's page 31 (Shortcuts) shows a static list with each template (with a badge from an
 item, child entries, a manager-only entry and one of an excluded build option) and a department
@@ -1198,6 +1200,76 @@ region when an application is replaced. The HR example's page 36 (*My reports*)
 (a view without the user name and photo columns) and leave requests (row level security: an
 employee sees only their own), with King's shared report *Salary by department*.
 
+### `form_designer` (Form Designer)
+
+A **Form Designer** region (sprint 85; pgkiln's own, APEX has no counterpart) lets the application's
+administrators build their own data entry forms in the running application, without a developer
+and without a new release. Like the [Data Reporter](#data_reporter-data-reporter), the developer
+decides *what* may be edited; the administrators decide *how* the forms look and who uses them.
+
+**The developer** places the region (page designer gallery: *Form Designer*) and, in its
+**Settings**, chooses **who may design forms** (an [authorization scheme](08-security.md); without
+one nobody can) and adds **data sources**: a table or view each (pgkiln's own `meta` schema and the
+system schemas are never offered), with a static id, a label and a description. Per source:
+
+- the **columns** forms may show and change, with a label and, for a select list or radio group,
+  a **list of values**: a shared one of the application (`LOV:NAME`) or `STATIC:Display;value,…`
+  (never SQL: designers can't write queries);
+- the **key column** that identifies a row (the primary key of a new table; choose one for a view),
+  needed to change and delete rows;
+- what forms on it **may** do at most: **add**, **change** and **delete** rows.
+
+A new source offers all its columns except binary and JSON ones, allows adding and (with a key)
+changing rows, never deleting. Untick generated keys and audit columns; the builder warns when the
+application's database role lacks a privilege a source needs.
+
+**Designers** (users that pass the scheme) see *New form* and a *Design form* link under each
+form. The designer is a plain form (it works without JavaScript): a name, a description, what
+users may do (within what the source allows) and a row per offered column: *On the form*,
+*Order*, *Label*, *Help text*, *Required*, *Display* (a field by the column's type; a text area for
+text; a select list or radio group for a column with a list of values) and a *Default* for new
+rows, and *In the list* for the columns of the form's list of rows. A form is a **draft** until
+*Published* is ticked: only designers see drafts.
+
+**Users** see the published forms as cards. A form with list columns opens on its rows (newest
+first, paged, `page_size`) with *Add* and an *Edit* link per row; a form without list columns
+only adds rows: it opens on an empty form, and after *Save* on the next empty one. Fields follow
+the column's type: a number field, the [date picker](05-items.md#the-date-picker) in the
+application's date format for dates, the browser's date and time field for timestamps, a
+checkbox for booleans.
+
+How it stays safe:
+
+- rows are read and written as the **application's database role**: grants and [row level
+  security](08-security.md) apply (in the HR example an employee changes only their own meetings);
+- a form's definition is checked against the region's settings before it renders or saves: only
+  offered columns that exist and can be read, displays the column's type allows, actions the
+  source allows; anything else is dropped. Only the form's fields are written; identifiers are
+  only the developer's schema, table and column names, always quoted; values and row keys are
+  always parameters; a value of a list of values must be in the list;
+- **lost updates** are refused: a row changed since its form was opened is not overwritten (the
+  user sees what they typed, with a message);
+- forms are stored in `meta.user_form`, reached by applications only through the view
+  `meta.user_forms` (the forms of the application) and the functions `meta.save_user_form` /
+  `meta.delete_user_form`; saving rows and forms needs the CSRF token and a region the user can
+  see, designing also the region's authorization scheme. Every saved, changed or deleted row and
+  form is in the activity log (event `form_designer`).
+
+Attributes (written by the region's **Settings**):
+
+| Key | Default | Meaning |
+|---|---|---|
+| `sources` | | `[{"id": "orders", "label": "Orders", "description": "…", "schema": "sales", "table": "orders", "key": "id", "columns": [{"name": "customer", "label": "Customer"}, {"name": "status", "lov": "LOV:ORDER_STATUS"}], "insert": true, "update": true, "delete": false}]` |
+| `design_authz` | | The authorization scheme designers pass; none: nobody designs |
+| `page_size` | `25` | Rows per page of a form's list (5 to 200) |
+| `empty` | `No data found.` | Text when a form's list has no rows |
+
+The sources travel with the application export (they are the region's attributes); the forms are
+data of the installation, like Data Reporter reports: not exported, and they stay with their
+region when an application is replaced. The HR example's page 45 (*Forms*, under Administration)
+offers departments, meetings and employees (changing only) to administrators, with the published
+forms *Departments* and *Book a meeting*.
+
 ### `ai_assistant` (AI assistant)
 
 An **AI assistant** region (APEX: AI Assistant, AI agents and tools) is a chat with an

package/docs/guide/05-items.md

@@ -11,7 +11,7 @@ page, optionally inside a region. Name them `P<page>_<NAME>` (uppercase letters,
 | `text` | text field | text |
 | `textarea` | multi-line text (always full width) | text |
 | `number` | number field (numeric keyboard on phones) | e.g. `1250.50` |
-| `date` | date picker: the browser's, or (sprint 76) with an application date format or a date format mask on the item a text field in that format with a calendar button; typed dates are read back in the format | `YYYY-MM-DD` |
+| `date` | a text field in the item's date format mask, else the application's date format, else `YYYY-MM-DD`, with pgkiln's [date picker](#the-date-picker) (sprint 84; was the browser's); typed dates are read back in the format | `YYYY-MM-DD` |
 | `datetime` | date-time picker | `YYYY-MM-DDTHH:MM` |
 | `email`, `tel`, `url` | typed fields with the matching phone keyboard | text |
 | `password` | password field; never shown back, empty = unchanged | text |
@@ -31,7 +31,7 @@ page, optionally inside a region. Name them `P<page>_<NAME>` (uppercase letters,
 | `markdown` | Markdown textarea with a toolbar; shown formatted when read-only | the Markdown text |
 | `rating` | star rating (radio buttons drawn as stars) | `1` … `max` (default 5) |
 | `combobox` | free text with suggestions from the list of values; several values become tags | **colon-separated** values, e.g. `SQL:Sales` |
-| `daterange` | two date pickers, *From* and *To* | `from:to`, e.g. `2026-01-01:2026-06-30` |
+| `daterange` | two date fields, *From* and *To*, in the date format with the date picker (the picker keeps *From* on or before *To*) | `from:to`, e.g. `2026-01-01:2026-06-30` |
 | `qrcode` | display only: the value as a QR code (SVG drawn on the server) | whatever was set |
 | `image` | display only: a picture from a URL in the value, or a BLOB from a query ([Display image](#display-image-and-geocoded-address)) | a URL, or nothing |
 | `address` | a text field with *Check address*: the installation's geocoder offers matching addresses ([Geocoded address](#display-image-and-geocoded-address)) | the address as text |
@@ -51,6 +51,18 @@ where hiredate between nullif(split_part(:P20_PERIOD, ':', 1), '')::date
                    and coalesce(nullif(split_part(:P20_PERIOD, ':', 2), '')::date, 'infinity')
 ```
 
+
+### The date picker
+
+(sprint 84; APEX: the date picker) A date item, a date range item, an interactive grid's date cell and a
+faceted search's own date range and the task list's vacation rule are text in the date format: the item's date format mask, else the
+application's date format (Settings → Globalization), else `YYYY-MM-DD`. The calendar button next to the
+field (or Alt+↓ in it) opens a month of days under it: the chosen day marked, today outlined, the week
+starting on the language's first day. Arrow keys move a day or a week, Page Up and Page Down a month
+(with Shift a year), Home and End to the week's first and last day, Enter or Space choose, Escape
+closes; *Today* and *Clear* below. Typed dates are read back in the format (and `YYYY-MM-DD` always
+works), so the field works without JavaScript. Timestamp items and grid timestamp cells still use the
+browser's date and time field.
 ## Properties
 
 | Property | Meaning |

package/docs/guide/09-reference.md

@@ -427,7 +427,7 @@ navigation entries and application processes have the same `build_option` column
 | Column | Description |
 |---|---|
 | `page_id`, `seq`, `title` | |
-| `type` | `report`, `grid`, `form`, `chart`, `cards`, `calendar`, `facets`, `smart_filters`, `display_selector`, `map`, `tree`, `template_component`, `list`, `data_reporter`, `ai_assistant`, `tasks`, `workflows`, `static`, `dynamic` |
+| `type` | `report`, `grid`, `form`, `chart`, `cards`, `calendar`, `facets`, `smart_filters`, `display_selector`, `map`, `tree`, `template_component`, `list`, `data_reporter`, `form_designer`, `ai_assistant`, `tasks`, `workflows`, `static`, `dynamic` |
 | `source` | SELECT (or HTML for `static`) |
 | `table_name`, `pk_column` | For `form` and `grid` |
 | `pk_item` | For `form`: the item holding the key |

package/docs/guide/11-from-apex.md

@@ -169,7 +169,8 @@ Tips:
   together.
 - **Errors are hidden by default**: unexpected errors show a reference number unless the app is in
   debug mode.
-- **Dates**: date items use ISO format (`2026-10-01`) and the browser's date picker; format masks
+- **Dates**: date items, date ranges, grid date cells and facet ranges are text in the application's date format
+  (else ISO, `2026-10-01`) with pgkiln's date picker; format masks
   apply to report, grid and cards columns and to number and display items
   ([number formats](14-globalization.md#number-formats)).
 - **Modal pages** open over the calling page, and close and refresh it after a successful submit,

package/docs/guide/12-development.md

@@ -154,6 +154,8 @@ src/
     tasks.ts               task list region and task actions (approvals); (094) the vacation rule panel and route
     data-reporter.ts       Data Reporter region (migration 057): sources from the region's config, checkDef (offered columns, whitelists),
                            reportQuery/chartQuery, the list and editor (GET form), save/delete routes (meta.save_data_report)
+    form-designer.ts       Form Designer region (migration 106): sources from the region's config, checkFormDef (offered columns, displays,
+                           actions), forms as cards, a form's rows, a row's form (lost update hash), the designer; row/design/delete routes
     workflows.ts           workflow console region and its actions
     ai.ts                  Generate text with AI: the ai_generate process (config checks, &ITEM. as delimited escaped data,
                            schemas from items, answers into items), aiInputs/aiOutputs for its dynamic action (route in routes.ts)
@@ -209,7 +211,9 @@ src/
     mail.ts                Workspace utilities → Mail services (administrators: providers, write-only secret, allowed senders,
                            applications with From and daily limit, test) and Applications → Activity → Mail (retry, cancel)
     shared.ts              Shared Components and access control
-    designer.ts            page designer: component tree (with computations and branches), layout canvas and gallery, property editor, toolbar
+    designer.ts            page designer: component tree (with computations and branches), layout canvas and gallery, property editor, toolbar;
+                           (sprint 86) GET /builder/apps/:app/pages/:no, /builder/pages/:id redirects browsers there (designerUrl in ui.ts)
+    errors.ts              (sprint 86) the builder's HTML 404 and 500 pages for browsers (wantsHtml, a not-found handler and an onSend hook)
     arrange.ts             page designer layout changes: move, column span, create from the gallery, undo / redo
     sql.ts                 SQL Workshop: the home and SQL commands (templates and drafts to review)
     object-browser.ts      (sprint 75) the Object Browser: objects by type, system objects hidden, a table in tabs, column actions as SQL to review
@@ -241,6 +245,7 @@ src/
     themeroller.ts         Settings → Theme Roller: style variants (add, edit, rename, delete), default style, users may choose
     subscriptions.ts       Shared Components → Subscriptions: subscribe, refresh, unsubscribe, subscribers and publish; the note under a component
     reporter.ts            page designer: Data Reporter settings (sources: table or view, offered columns, labels, masks; sharing)
+    form-designer.ts       page designer: Form Designer settings (designers' scheme; sources: key, actions, offered columns, labels, lists of values)
     workingcopies.ts       Working copies: list and create, compare with differences, merge or refresh with conflict choices, delete
     rest.ts                REST module endpoints list and curl example (Shared Components)
     workflows.ts           workflow versions, diagram and instances (Shared Components)

package/examples/hr/hr_61_form_designer.sql

@@ -0,0 +1,80 @@
+-- =====================================================================
+-- HR example, part 61: a Form Designer (docs/guide/04-pages-and-regions.md,
+-- "Form Designer")
+--
+-- Page 45 "Forms": the application's administrators (authorization scheme
+-- ADMIN) build data entry forms on three tables the developer offers in the
+-- region's settings, and publish them for every employee:
+--   - "Departments": hr.dept, add and change rows;
+--   - "Meetings": hr.meeting, add, change and delete rows; its row level
+--     security still applies (an employee changes only their own meetings);
+--   - "Employees": hr.emp, change rows only, with the job and department
+--     as lists of values.
+-- Two published forms are there to start from: "Departments" (a list of
+-- departments with Add and Edit) and "Book a meeting" (no list: the form
+-- only adds rows). Forms are installation data: not part of the export.
+-- =====================================================================
+
+insert into meta.page (app_id, page_no, name, title, parent_page)
+select id, 45, 'Forms', 'Forms', 1 from meta.app where alias = 'hr';
+
+insert into meta.region (page_id, seq, title, type, columns, template, config)
+select p.id, 10, 'Form Designer', 'form_designer', 12, 'standard', $j${
+  "design_authz": "ADMIN",
+  "page_size": 15,
+  "sources": [
+    {"id": "departments", "label": "Departments", "description": "Department names and locations.",
+     "schema": "hr", "table": "dept", "key": "deptno", "insert": true, "update": true, "delete": false,
+     "columns": [{"name": "dname", "label": "Department"}, {"name": "loc", "label": "Location"}]},
+    {"id": "meetings", "label": "Meetings", "description": "Meetings in the planner; employees change only their own.",
+     "schema": "hr", "table": "meeting", "key": "id", "insert": true, "update": true, "delete": true,
+     "columns": [{"name": "title", "label": "Title"}, {"name": "starts_at", "label": "Starts"}, {"name": "ends_at", "label": "Ends"}, {"name": "private", "label": "Private"}]},
+    {"id": "employees", "label": "Employees", "description": "Job, department and salary of employees.",
+     "schema": "hr", "table": "emp", "key": "empno", "insert": false, "update": true, "delete": false,
+     "columns": [{"name": "ename", "label": "Name"}, {"name": "job", "label": "Job", "lov": "LOV:JOBS"}, {"name": "deptno", "label": "Department", "lov": "LOV:DEPARTMENTS"},
+                 {"name": "hiredate", "label": "Hire date"}, {"name": "sal", "label": "Salary"}]}
+  ]}$j$::jsonb
+  from meta.page p join meta.app a on a.id = p.app_id
+ where a.alias = 'hr' and p.page_no = 45;
+
+-- two published forms to start from (forms are installation data: not part of the export)
+insert into meta.user_form (app_id, region_id, name, description, published, definition, created_by, updated_by)
+select a.id, r.id, f.name, f.description, true, f.definition, 'king', 'king'
+  from meta.app a join meta.page p on p.app_id = a.id and p.page_no = 45 join meta.region r on r.page_id = p.id and r.type = 'form_designer',
+       (values
+  ('Departments', 'Add a department or change its name and location.',
+   '{"source": "departments",
+     "fields": [{"column": "dname", "label": "", "help": "", "required": true, "display": "auto", "default": ""},
+                {"column": "loc", "label": "", "help": "The city.", "required": false, "display": "auto", "default": ""}],
+     "list": ["dname", "loc"], "actions": {"insert": true, "update": true, "delete": false}}'::jsonb),
+  ('Book a meeting', 'Put a meeting in the planner.',
+   '{"source": "meetings",
+     "fields": [{"column": "title", "label": "What", "help": "", "required": true, "display": "auto", "default": ""},
+                {"column": "starts_at", "label": "", "help": "", "required": true, "display": "auto", "default": ""},
+                {"column": "ends_at", "label": "", "help": "Leave empty for a meeting without an end.", "required": false, "display": "auto", "default": ""},
+                {"column": "private", "label": "Only visible to me", "help": "", "required": false, "display": "auto", "default": "false"}],
+     "list": [], "actions": {"insert": true, "update": false, "delete": false}}'::jsonb)
+  ) as f (name, description, definition)
+ where a.alias = 'hr';
+
+insert into meta.nav_entry (app_id, parent_id, seq, label, icon, target_page)
+select a.id, n.id, 60, 'Forms', 'file', 45
+  from meta.app a join meta.nav_entry n on n.app_id = a.id and n.label = 'Administration' and n.parent_id is null
+ where a.alias = 'hr';
+
+insert into meta.translation (app_id, language, source, target)
+select a.id, 'nl', t.source, t.target
+  from meta.app a, (values
+  ('Forms', 'Formulieren'),
+  ('Form Designer', 'Formulierbouwer'),
+  ('Department names and locations.', 'Namen en vestigingsplaatsen van afdelingen.'),
+  ('Meetings', 'Vergaderingen'),
+  ('Meetings in the planner; employees change only their own.', 'Vergaderingen in de planner; medewerkers wijzigen alleen hun eigen.'),
+  ('Job, department and salary of employees.', 'Functie, afdeling en salaris van medewerkers.'),
+  ('Title', 'Titel'),
+  ('Starts', 'Begint'),
+  ('Ends', 'Eindigt'),
+  ('Private', 'Privé')
+  ) as t (source, target)
+ where a.alias = 'hr'
+on conflict do nothing;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pgkiln",
-  "version": "0.45.0",
+  "version": "0.46.0",
   "description": "Open source low-code, SQL-driven application builder for PostgreSQL, inspired by Oracle APEX",
   "keywords": [
     "postgresql",