Release Notes — WUIC Framework v1.8.2
Date: November 15, 2026 Previous published version: 1.8.1 (November 10, 2026) Backend: .NET 10 + IIS / Linux nginx Frontend: Angular 21
1.8.2 brings column labels and reports into the language of whoever uses the application, and fixes the behaviors that emerged from forum questions and from the code audit. In short:
- translatable column labels with one key per column, distinct for list, form and filters;
- reports in the language of whoever opens them, without duplicating the
.mrtfiles; - typed validation
numberanddate; - validation callback that does not compile: it now blocks the save instead of letting it through;
- user language no longer replaced by the browser's;
- file import (Excel/CSV) with the same permissions as insertion from the grid;
- fixes on nested grids, designer, workflow, export and offline mode.
🌍 Column labels and reports in the user's language
- One key per column: a column label is translated with the key
meta-key.<route>.<column>in_wuic_translations. For the form you can use a separate.editkey, for filters.filter; without a translation the metadata text remains, as before. When the language changes, the labels of open datasources update immediately. - Generating the keys: the Generate column translation keys item of the metadata editor (super-admin only) creates the route's missing keys in the 5 languages, starting from the current labels. It never overwrites existing rows and can be repeated.
- Reports: reports created with Create report carry the column key in the header texts. On opening, the viewer passes the user's language and the server shows the translation for that language; the
.mrtfile does not change. For existing reports, the Reports → Add translation keys to reports item of the metadata editor adds the keys to the texts that match a column label. - Details in the Interface Translations and Reporting pages of the documentation.
🛡️ Security
Best-effort hardening of the import of .wuicpkg packages and of the tables adopted by the Excel import: a table, column or constraint name that contains the identifier delimiter, a single quote or a control character is rejected instead of ending up in the DDL; DDL string literals (defaults, allowed values) on MySQL also double the backslash. File import (Excel/CSV) applies the same permission checks as insertion and editing from the grid: only the super-admin imports rows into system tables, users and roles, and the audit columns always carry the logged-in user; a rejected import shows the reason in the log instead of a generic error.
🐛 Notable bug fixes
- Typed validation
numberanddate:mc_validation_typeonly recognizedemail,urlandcreditcard, and withnumberordateit rejected every value. Nownumberaccepts a number with an optional sign and a decimal separator (.or,, no thousands separators) anddatean editor date or an ISO dateyyyy-mm-dd, with optional time, that actually exists. The metadata editor offers the two items. - Validation callback that does not compile: an
mc_validation_custom_callbackscript with a syntax error was replaced by a rule that accepted everything, and the record was saved without any check. Now the rule fails and the user sees the callback's error. changeTrackinginput ofwuic-data-source:[changeTracking]="false"was ignored and tracking stayed active. Now the input applies; if the table sets thechangeTrackingextra property, that one prevails.- User language: on every app load, the language chosen from the selector or the one from the profile was replaced by the browser language. Now the browser language is used only during the first installation.
- Page stuck after a language change: when choosing from the selector a language not yet loaded, the application could enter a loop of translation reloads that kept the browser busy. Translations are now looked up in constant time even with tens of thousands of rows.
- Save blocked without a message: a required field that the form does not show (hidden in edit or with the value generated by the server) stopped the save without a message and without calling the server. Now the server performs that check; every client-side block shows the message of the violated rule (Invalid value:
if the rule has no text) and, when switching to another tab, lists the fields to correct. - Combo with a formula that uses another lookup: if the text formula of a lookup used the field of another lookup of the same table (alias
<column>_<entity>), the combo replied with an SQL error because the query did not contain that join. Now the join is included (tested with the real combo on SQL Server; MySQL, PostgreSQL and Oracle use the same rule). - Nested grids: the grid in the expanded row uses its own saved states, without the sorting, filters and columns of the parent grid's default state, and changes to its columns no longer overwrite the parent's saved layout. The export (and import) of a child grid in a data-repeater uses the grid's route, not the page's.
- Edit and detail of a route without a menu item: a route reachable only from a child grid opened the not authorized page. Now the detail opens if the user has read permission on the route, and edit if the route is editable or insertable for them; the other actions do not change.
- "Export XLS in progress" window: it stayed on screen after the export ended until another event refreshed the page; now it closes by itself.
- Offline mode (client-side CRUD): grid filters give the same result as online. Advanced OR filters no longer return zero rows, those combined with fixed filters or coming from the querystring are no longer ignored, and the "is not null" operator is applied.
- Date and multiline text fields: when the form opens, the column's value-change function receives the field's value (no longer an internal object), is not called when the field is empty and, on the first change, receives the initial value as the old value, as numeric and text fields already did.
- Designer: reducing the number of columns of a table no longer empties the remaining cells; clearing the numeric field of rows/columns of a TABLE or of areas/items of SPLITTER and ACCORDION to type a new value no longer deletes existing rows, areas and content.
- Workflow with converging branches: when several condition branches reach the same condition, switch or parallel node, the records of the second branch are routed to the intended step instead of stopping with the unmet-guard message.
onDialogCloseRequestedof the parametric-dialog: in dialog mode a click on cancel emitted the event twice, the first time withoutresult. It is now emitted once per close request.- Documentation corrected where it did not match the behavior: the reason for Trial mode (read from the Trial badge in the menu after login), license pasted from the AppSettings Editor without a restart,
lookup.filteras a replacement of the lookup filter,slimCombowith a computed text formula,trueresult and empty field in custom validations, shape of the row style conditions,skipUrlSyncandskipFetchinputs of the filter-bar, report dictionary generated at creation.
📦 Updated packages
| Package | From | To |
|---|---|---|
WuicCore (NuGet) |
1.8.1 | 1.8.2 |
Wuic.Webcore (NuGet) |
1.8.1 | 1.8.2 |
WuicOData (NuGet) |
1.8.1 | 1.8.2 |
RuntimeEfCore (NuGet) |
1.8.1 | 1.8.2 |
Wuic.MySqlProvider / Wuic.PostgresProvider / Wuic.OracleProvider (NuGet) |
1.8.1 | 1.8.2 |
wuic-framework-lib (npm) |
1.8.1 | 1.8.2 |
🔧 Recommended steps when upgrading
- Update the npm library and the NuGet packages together to 1.8.2. Nothing is needed for the schema: at startup the backend adds the
numberanddateitems to themc_validation_typemenu by itself. - Check the columns with
mc_validation_typeother thanemail,url,creditcard: they used to reject every value, nownumberanddatereally validate; any other value still makes the rule fail. - Check the custom validation callbacks: a script that does not compile now blocks the save. If a form stops saving after the upgrade, the browser console indicates the column and the error.
- Check imports into system tables, users and roles: since 1.8.2 only the super-admin can perform them; an import by another user is rejected with the reason in the log.
- Translate the column labels (optional): from the metadata editor, Generate column translation keys on each route, then complete the translations in
_wuic_translations. For existing reports, Reports → Add translation keys to reports. - Free apps: the 1.8.0 zips contain framework 1.8.0; if you build them from source, you get 1.8.2 by updating the
WuicCorepackage.