Release Notes — WUIC Framework v1.8.0
Date: 8 November 2026 Previous published version: 1.7.32 (4 November 2026) Backend: .NET 10 + IIS / Linux nginx Frontend: Angular 21
1.8.0 adds three new features and gives the free apps an upgrade path that keeps the customer's changes. In short:
- Metadata lifecycle: history of every artifact, comparison, releases,
.wuicpkgpackages and promotion between environments with a three-way plan, verification and roll back; - Ask your data: plain-language questions on the application data, with the user's permissions, read-only and with cited sources;
- App generator: an installed app built from a description, from tables of an existing database or from an Excel/CSV file;
- free apps (FatturazioneElettronica, CrmApp, FlottaMezzi) upgradable from 1.7.28 to 1.8.0 keeping data and customizations;
- behaviour change: workflow column restrictions and transitions are now enforced by the server too.
🗂️ Metadata lifecycle
The new page Administration → App lifecycle, reserved to superadmins verified against the database, treats the app metadata as versioned artifacts: routes, menus, permissions, translations, themes, jobs, dashboards, pivots, workflows, reports, 3D scenes. Users, companies, connection strings, secrets, logs and business data stay out.
- History: a job running every minute records the artifacts saved from designers or from the metadata CRUD, only when the content actually changed; once a day a reconciliation also records changes made outside the APIs. In the workflow, dashboard, pivot and theme designers and in the metadata editor the History / Compare button shows the versions with per-property differences, and for workflows and dashboards a visual comparison too.
- Going back: Restore this version, Shelve and Reapply always go through a three-way plan. If the artifact changed again on the same properties, the conflict is shown and you choose. These operations can also run in bulk, on several items or commits.
- Releases and packages: a release freezes the version of every artifact with the changelog against the previous one. It exports to a full or delta
.wuicpkgpackage, in the background with a clickable notification; with a key configured the package is signed (RSA). - Promotion: in the Packages tab an import is always a plan first, comparing base, package and installation. It updates what changed only in the source, keeps hotfixes made in the target and flags as a conflict what changed on both sides, to be resolved per artifact or per property.
- Apply and verification: apply takes a snapshot, runs in one transaction, re-exports the artifacts and compares their hashes with the package. If it fails or the verification doesn't match, the metadata go back on their own; Roll back on the promotion row undoes a successful apply.
- Production: design lock (
MetaLifecycle:DesignLock=off,warn,on), second approver (MetaLifecycle:RequireSecondApprover) and required signatures (MetaLifecycle:RequireSignature) are on by default only when the environment role isprod. Plans, resolutions, applies and roll backs are audited with user, IP, hash and signature. - Framework system rows: each version ships the baseline of its own system rows. At startup untouched rows are updated, customized ones are kept and conflicts are listed in the Changed from the framework tab, where you keep your version, take the framework's or merge column by column. The Updates tab tells you, read-only, whether a newer framework or free app version exists.
- Automation: every operation is exposed under
api/meta-lifecycle/*, with a superadmin cookie or an API token with themeta-lifecyclescope. Thewuic-meta.ps1command-line client (PowerShell 7, included in the free app source zips) calls the same APIs, with exit codes designed for pipelines:0ok,2open conflicts,3rejected,1error.
History, releases, three-way plan, apply, verification, roll back, design lock, signatures and multi-tenant are verified by tests on SQL Server, MySQL, PostgreSQL and Oracle. Limits: promotion works only between databases of the same type; the data DB of existing apps does not travel in packages (only tables created by the app generator); there is no direct push between environments, the transport is the .wuicpkg file; with multi-tenant, history and promotions are per tenant and installation files are shared. History is kept for MetaLifecycle:History:KeepDays days (180 by default).
💬 Ask your data
The Ask your data menu item and the Ask your data button in the toolbar of every list-grid open a chat where an authenticated user asks questions about the application data. From the grid button the question starts with the route and the active filter as context.
- Same permissions as the grid: the model does not write SQL and never sees physical table or column names. It produces a restricted query plan that the server validates and translates into the list-grid filter, executed with the session user: routes, columns, row restrictions, company and default filters apply as in the grid, and aggregates are computed on the same rows.
- Read-only: none of the tools available to the model writes data.
- Verified sources: every number cites its source
[n]and a deterministic check verifies that it appears in the result; otherwise the answer comes with the "Numbers not verified" warning (NlQuery:UnverifiedMode). From a source, Show data re-runs the plan with the viewer's permissions and Open in grid opens the rows with the same filter. - Ambiguous questions: the turn ends with a clarifying question and options taken from the real candidates. The turn runs in the background and the result also arrives in the notification bell.
- Views from recurring questions: the model can propose a view (view builder or pivot, optionally materialized in a table refreshed by a job) that only a superadmin can apply. A proposal from a regular user reaches every superadmin as a notification.
- Configuration (Configure button, superadmin): exclude or add routes, descriptions and synonyms for the model, "aggregates only" routes, sensitive columns. It is saved in the route and column props bags, so it follows the lifecycle history and packages.
Settings live in the NlQuery section of appsettings.json (Enabled, SendRowValues, SensitiveColumns, TimeZone, per-question and per-user limits). The model is the RAG chat's (rag-llm-provider, rag-llm-api-key, or agent-sdk with the claude CLI, which runs with no built-in tools and only the backend's read-only MCP server). Without a license the engine reads at most 20 rows: questions needing more are refused rather than answered incompletely. Verified by tests on SQL Server, MySQL, PostgreSQL and Oracle.
🏗️ App generator
The new Administration → New app item, reserved to superadmins, creates an app from a plain-language description, from tables and views of an existing database (adopted without changing them) or from an .xlsx, .csv or .txt file (up to 20 MB, 20 sheets, 200 columns and 100,000 rows per sheet, with rows imported after installation).
- The model proposes, the compiler builds: the model only produces a validated JSON blueprint, it does not write to the database and does not generate code or SQL. The blueprint can also be edited by hand in the wizard (entities, fields, relations, roles and permissions, menu).
- What gets installed: tables with audit columns and logical delete, routes created by scaffolding, lookups, translated dictionaries, kanban, calendar and chart views, roles and permissions (including a row restriction on the current user), menu, translations, consistent demo data, dashboards and workflows. Installation goes through the lifecycle plan, with preview, verification and roll back, and the app is then promoted like any other package.
- Changes in plain language: an installed app, generated or not, is changed by describing the change. The plan is three-way against the changes made by hand in the designers; risky operations on the data DB (dropping, narrowing or renaming columns) are refused.
- Generated tests: every app comes with an API-level suite (metadata, permissions, CRUD, validations, row filters, menu, dashboards, workflow transitions) that uses temporary users and records and does not run in a
prodenvironment. Results are in the App check tab of App lifecycle, which keeps the last 50 runs and can also build the suite for an existing app; a UI suite can be downloaded as.mjstests. - Limits: no custom code (logic that doesn't fit the blueprint is listed as
codeHooksto complete), no maps and no file, image, geographic or computed fields; row filters only in the form "user field = current user". The model is the RAG chat's, with token budgets per turn, per session and per day; Excel cell values reach the model only withAppGenerator:SendSampleValues.
The generated DDL covers SQL Server, MySQL, PostgreSQL and Oracle; the installations of the evaluation with the real model were run on SQL Server.
🧩 Free apps: upgrade from 1.7.28
FatturazioneElettronica, CrmApp and FlottaMezzi are released on 1.8.0. Whoever installed the 1.7.28 binary zip (IIS, SQL Server) upgrades by following the documentation page «Upgrading a free app».
- The 1.8.0 zip has an
upgrade\folder withUpgrade-Database.ps1(backup, data DB scripts and restore, with Windows PowerShell 5.1 and no sqlcmd), the data DB scripts from 1.7.28 and two metadata packages: 1.7.28 as published (the base) and 1.8.0. appsettings.json,Upload,Conservazione,logsandApp_Dataare kept. Metadata and reports are compared three-way from the App lifecycle page: what only the customer changed stays, what only 1.8.0 changed arrives, what both changed is a conflict to choose.- Roll back on the promotion brings the metadata back to before the apply; the backups of the first step bring everything back to 1.7.28.
- The path was tested from a clean VM on all three free apps. On FlottaMezzi keeping the uploaded files is not verified: in the published 1.7.28 the users form answers with a 500 error.
- The data DB
.bakships with an empty change history, without the changes made during development and testing.
🔀 Workflow: rules enforced on the server
- Column edit restriction: the restriction written in a step's bundle now applies on the server too. An update that changes that column is refused with
errors.workflow.column_not_editable, unless it is a valid workflow action; an update that doesn't change it passes, a file import with update on that route is refused. - Transitions: for an action with a transition declared by the graph, the record must be in a source state (
errors.workflow.transition_source_state) and the new state must be the target one (errors.workflow.transition_target_state). - Initial state: if the bundle forbids the state field, an insert or a copy accepts only an initial state or no value for the field; otherwise it answers 403
errors.workflow.initial_state. Before, these rules were checked only in the browser.
✨ Other new features
- Server-side grouping by period:
GroupInfo.bucket(day,month,quarter,year) groups a date on the first day of the period, in time order. Verified on SQL Server, MySQL and PostgreSQL; on Oracle it is present but not verified. - PrimeNG built-in texts (empty lists of select, multiselect and autocomplete, confirmations, upload, filters, datepicker, paginator) in the user's language, updated on language change.
- Kanban and calendar: card fields and event titles show the lookup and dictionary text, not the ID or the code.
- RAG chat: structured question with options as buttons; clicking sends the answer.
- API tokens: dedicated scopes for lifecycle, data questions and app generator, used by WUIC Assistant and Claude Code.
🛡️ Security
Best-effort hardening on the new features: lifecycle and generator APIs reserved to superadmins verified against the database, "Ask your data" always with the permissions of the session user, API tokens limited to their scope, agent-sdk CLI started with no built-in tools and only the backend's read-only MCP server, text from data and uploaded files treated as data and never as instructions, model answers rendered as safe markdown.
🐛 Notable bug fixes
- "Change Master" page: on SQL Server the framework aligns at startup the tables, routes and menu item of the change history, also in apps that didn't have them or had them in the previous form. Before, the page failed on a missing table.
- Lifecycle plan, missing tables: the data DB check misread the schema and physical names of routes and flagged as "without table" routes on existing tables, for example in the
wuicschema. - Roll back "not congruent": the history job could record between the snapshot restore and its verification; it now skips its round while a roll back is running. The verification also ignores the last and next execution of jobs, which the scheduler rewrites.
- Roll back with jobs already run and rows deleted in cascade: a job brought by the package that had already run made the roll back fail on a foreign key; rows tied to a parent deleted in cascade (for example column permissions) were lost. Both cases now return to the snapshot state.
- History with thousands of items: the tables of the History tab are paged by 50; before, an app with many files froze the browser.
- Menu after apply or roll back: the menu cached in the browser was refreshed only by menu operations; it is now compared with the metadata version and reloaded when older.
- Unsaved changes dialog: the title showed the
confirmkey instead of the translated text. - Translations on MySQL, PostgreSQL and Oracle: first-run scripts now hold the same 1.8 keys as SQL Server; 234 were missing and 3 had a different text.
- Charts: saved options (legend, title, grids, tooltip, animation, doughnut cutout) are applied on load, not only when opening the settings.
- Oracle, texts over 4000 bytes: inserting or copying a record with a long text failed with
ORA-01704; the text now travels as a CLOB. - Invisible route and insert without columns: on SQL Server, MySQL, PostgreSQL and Oracle they answer with a typed error (404
errors.metadata.route.not_found, 400errors.metaservice.crud.empty_insert). - SQL Server, record translations from the API: an update without the grid's changes didn't update the translation in the user's language, and the next read showed the old text.
- Row button denied to a role: when acting on the key column, it made every key-filtered read return 403; a button no longer denies the column it acts on.
- MySQL and PostgreSQL first run: new installations no longer receive Webhook Hub routes tied to the name of the development database.
- SQL Server first run: removed four legacy migration procedures that referenced a development database; a migration removes them from existing installations only if their text references those databases.
📦 Updated packages
| Package | From | To |
|---|---|---|
WuicCore (NuGet) |
1.7.32 | 1.8.0 |
Wuic.Webcore (NuGet) |
1.7.32 | 1.8.0 |
WuicOData (NuGet) |
1.7.32 | 1.8.0 |
RuntimeEfCore (NuGet) |
1.7.32 | 1.8.0 |
Wuic.MySqlProvider / Wuic.PostgresProvider / Wuic.OracleProvider (NuGet) |
1.7.32 | 1.8.0 |
wuic-framework-lib (npm) |
1.7.32 | 1.8.0 |
🔧 Recommended operational updates when upgrading
- Update the npm library and the NuGet packages together. The library now lists
frappe-ganttamong its peer dependencies, andthree,three-mesh-bvh,three-gpu-pathtracerand@dimforge/rapier3d-compatare no longer optional: add them to the project'spackage.jsonif missing, otherwise the build stops with "Could not resolve three". - First startup after the upgrade: migrations create the lifecycle tables and the framework records the baseline of the system rows. The first realignment overwrites nothing and only inserts missing rows: review the differences in the Changed from the framework tab.
- Production environments: set
MetaLifecycle:Environment:Roletoprodto get design lock onwarn, second approver and required signatures; to sign packages configureMetaLifecycle:SigningKeyon the source andMetaLifecycle:TrustedPackageKeyson the target. - Workflows with column restrictions in the bundle: check code, API calls and file imports that change the state field or a restricted column directly; they now get an error instead of passing.
- Ask your data and App generator: they need a model configured for the RAG chat.
NlQuery:Enabled=falseturns Ask your data off; with confidential data considerNlQuery:SendRowValues=false(only counts and aggregates reach the model) andNlQuery:SensitiveColumns. - Update check: once a day the server reads
https://wuic-framework.com/downloads/releases.jsonwithout sending any data;Updates:Check=falseturns it off. - Free apps 1.7.28: upgrade by following the page «Upgrading a free app», without extracting the new zip over the application folder and without restoring its
.bakfiles.