Release Notes — WUIC Framework v1.7.20

Date: 1 October 2026 Previous published version: 1.7.18 (1 October 2026) Backend: .NET 10 + IIS / Linux nginx Frontend: Angular 21

A maintenance release: it collects the defects found while building an application with the five documented development patterns, starting from the sample project of the source packages, and speeds up the RAG engine on machines without a GPU. It also contains the fixes of 1.7.19, which was released only as NuGet and npm packages: these notes cover both. In short:

• running scaffolding again with "Create Menu" no longer duplicates the menu entry;
• on PostgreSQL and Oracle the server-side sorting requested by the grid is applied, also when the list brings a highlighted record to the top;
• with ng serve, exports can be downloaded from the dev server too;
• RAG engine searches on CPU are up to about three times faster on machines with few cores;
• the pages of the five development patterns have code samples that compile, in all five languages.

No changes to metadata, translations or database schema: the upgrade requires no scripts.

🗄️ PostgreSQL and Oracle providers

• Server-side sorting. With server-side operations enabled, the sort chosen on a grid column never reached the query: records always came back ordered by primary key, even when descending order on another field was requested. The ORDER BY now uses the requested columns and appends the primary key only as the last criterion, as on SQL Server and MySQL.
• Sorting with a highlighted record. When the list brings a specific record to the top, the requested sort was still discarded in 1.7.19. The order is now: highlighted record, requested columns, primary key.

🤖 RAG engine

• Faster searches on CPU. Without a GPU, the model compute threads kept spinning between one operation and the next, and the background cache warm-up ran in parallel with the first search: on machines with few cores they competed for the CPU. The threads no longer busy-wait and model computations run one at a time within the process. Searches (chat and MCP tools) are up to about three times faster on machines with few cores, and the first search is no longer slowed down by the warm-up in progress. On PCs with spare cores the timings do not change.

🐛 Notable bug fixes

• Duplicate menu entry on scaffolding. Running "Scaffold Table" or "Scaffold View" again with "Create Menu" on a table or view that was already scaffolded added a second menu entry for the same route. The entry is now created only if the route does not have one yet.
• Exports with the dev server. In the client project of the source packages, proxy.conf.js did not forward the /Tmp_export path to the backend: with ng serve the link to the exported file (Excel, CSV, PDF) returned the application page instead of the file. The path is now forwarded and the download works as in the published installation.

📚 Documentation

The pages of the five development patterns have been corrected in every language:

• Framework + manual: the sample passes the data source with [hardcodedDatasource] and sets [autoload]="true"; without autoload the list loads only the schema, not the records.
• Framework data + custom component: new sample of setCurrent, addNewRecord, syncData and fetchData called from the custom component.
• Framework component + custom data: client-side filters build one filter per column, the way the list-grid reads it.
• Full custom: the component declares the required imports (TableModule, CheckboxModule, ButtonModule, FormsModule).
• Full autogeneration: the spreadsheet requires the licensed feature (without it, the route opens as a list); the dashboard is not a route archetype and the page no longer lists it among the generated pages.

The documentation is included in the npm library and published on the website.

📦 Updated packages

If you already upgraded the packages to 1.7.19, 1.7.20 adds sorting with a highlighted record, the faster RAG engine and the fix to the full autogeneration pattern page.

🔧 Recommended operational updates when upgrading

1. Projects created from the source packages: the project's proxy.conf.js is not overwritten by the package upgrade. Add the '/Tmp_export' entry with the same configuration as the other backend entries (or copy it from the package's proxy.conf.js), then restart ng serve.
2. Duplicate menus: if running scaffolding again with an earlier version left duplicate menu entries, delete the extra ones from the menu management.
3. PostgreSQL and Oracle: no action needed; after the upgrade, grids with server-side operations sort as requested.
4. RAG engine: no action needed; the updated engine is in the package's rag-engine folder and the fix applies to CPU execution.