wuic-framework-lib 1.7.7 → 1.7.9

package/fesm2022/{wuic-framework-lib-framework-docs.component-Bi5Pm3vl.mjs → wuic-framework-lib-framework-docs.component-B2AdE4N0.mjs}

@@ -16,12 +16,12 @@ import * as i1$3 from 'primeng/image';
 import { ImageModule } from 'primeng/image';
 import * as i8$1 from '@ngx-translate/core';
 import { TranslateService, TranslateModule } from '@ngx-translate/core';
-import { v as getThemeOptions, T as TranslationManagerService, U as UserInfoService } from './wuic-framework-lib-wuic-framework-lib-DfDsWPDO.mjs';
+import { v as getThemeOptions, T as TranslationManagerService, U as UserInfoService } from './wuic-framework-lib-wuic-framework-lib-CNl2-wAT.mjs';
 import * as i1 from '@angular/router';
 
 const frameworkDocsContent = {
     "version": "1.0.0",
-    "generatedAt": "2026-09-11T12:50:19.123Z",
+    "generatedAt": "2026-09-17T18:27:06.604Z",
     "groups": [
         {
             "id": "primi-passi",
@@ -1147,13 +1147,17 @@ const frameworkDocsContent = {
                 {
                     "id": "sec_4",
                     "title": "Quick Start — primo componente"
+                },
+                {
+                    "id": "sec_5",
+                    "title": "Le prime liste mostrano 20 record: e' la modalita' Trial"
                 }
             ],
             "sections": [
                 {
                     "id": "overview",
                     "title": "Overview",
-                    "html": "<h1>Panoramica Framework</h1><p>WUIC Framework e&#39; una piattaforma metadata-driven per creare interfacce business in modo rapido e coerente.</p><h2>Cosa include</h2><ul><li>DataSource e DataRepeater per orchestrare dati e rendering.</li><li>Archetypes visuali (list, map, scheduler, chart, carousel).</li><li>Designer runtime per dashboard e template dinamici.</li><li>Workflow designer/runner per processi operativi.</li><li>RAG Chatbot per interrogare la codebase in linguaggio naturale.</li><li>Multi-DBMS: SQL Server, MySQL, PostgreSQL e Oracle tramite provider drop-in (<code>dbms</code>: <code>mssql</code> | <code>mysql</code> | <code>postgresql</code> | <code>oracle</code>).</li></ul><h2>First Steps — Avvio ambiente dev</h2><p>Lo stack WUIC e&#39; composto da piu&#39; servizi. Avviali nell&#39;ordine indicato.</p><h3>Prerequisiti</h3><table><thead><tr><th>Cosa</th><th>Verifica</th><th>Note</th></tr></thead><tbody><tr><td>.NET 10 SDK</td><td><code>dotnet --version</code></td><td>Hosting Bundle per IIS in produzione</td></tr><tr><td>Node.js 22 LTS</td><td><code>node --version</code></td><td>La 22 e&#39; la versione con cui il pacchetto e&#39; testato; con npm 10.9.x installa solo grazie al <code>package-lock.json</code> incluso</td></tr><tr><td>PowerShell 5.1+</td><td><code>$PSVersionTable.PSVersion</code></td><td>La PowerShell preinstallata su Windows basta: <code>rename-project.ps1</code> e gli script <code>llm-workspace/</code> girano anche su 5.1. PowerShell 7 e&#39; consigliata, non richiesta</td></tr><tr><td>SQL Server 2019+</td><td><code>sqlcmd -S localhost\\sqlexpress -E -C -Q &quot;SELECT 1&quot;</code></td><td>Se manca, <strong>il one-liner lo installa da se&#39;</strong> (SQL Server Express, o il motore scelto con <code>-Dbms</code>); su Windows Server no, vedi il riquadro sotto. 2019 basta per i pacchetti senza <code>.bak</code>; il tutorial <code>.bak</code> e&#39; un backup di SQL Server 2022 e richiede <strong>2022 o superiore</strong></td></tr><tr><td>Linux (installer <code>install.sh</code>)</td><td><code>lsb_release -ds</code></td><td><strong>Ubuntu 22.04 o 24.04 LTS</strong> (24.04 raccomandata): sono le uniche Ubuntu su cui Microsoft supporta SQL Server, la <strong>26.04 non e&#39; supportata</strong> (<a href=\"https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-setup?view=sql-server-ver17\" target=\"_blank\" rel=\"noopener noreferrer\">Supported platforms</a>). Stessa raccomandazione con MySQL, PostgreSQL e Oracle, perche&#39; l&#39;installer e&#39; provato su quelle</td></tr><tr><td>GPU NVIDIA (CUDA 12.x + cuDNN 9)</td><td><code>nvidia-smi</code></td><td>Opzionale: accelera il RAG Chatbot (senza GPU gira su CPU)</td></tr></tbody></table><p>&gt; <strong>Su Windows Server il database va installato prima.</strong> Il one-liner si procura i componenti</p><p>&gt; mancanti tramite <code>winget</code>, che su Windows Server non e&#39; presente: senza un&#39;istanza gia&#39;</p><p>&gt; raggiungibile l&#39;installazione si ferma con `No SQL Server instance reachable and winget is</p><p>&gt; missing`. Installa quindi il motore prima di lanciare la riga - per SQL Server serve la</p><p>&gt; <strong>2019 o superiore</strong> (la Express basta; <strong>2022 o superiore</strong> per il tutorial <code>.bak</code>), e una</p><p>&gt; 2017 non viene accettata. Se l&#39;istanza non e&#39; quella predefinita, passala con</p><p>&gt; <code>-SqlServer &#39;localhost\\NOMEISTANZA&#39;</code>. Vale per tutti i motori, non solo SQL Server.</p><h3>1. Scarica il template di progetto</h3><p>Su Windows fai tutto con una riga di PowerShell: scarica il pacchetto, verifica .NET SDK 10 e Node.js 22</p><p>(installando cio&#39; che manca), esegue <code>dotnet restore</code> e <code>npm install</code>, e installa</p><p>l&#39;estensione WUIC Assistant in VS Code.</p><p>Snippet 1:</p><p>Opzioni utili sulla stessa riga: <code>-Dbms mysql</code> (oppure <code>postgres</code>, <code>oracle</code>) per un motore</p><p>diverso da SQL Server — che l&#39;installer installa e configura da se&#39; — e <code>-WithTutorial</code> per</p><p>scaricare anche il database di esempio.</p><p>Quando ha finito, l&#39;ultima schermata e&#39; gia&#39; l&#39;elenco delle cose da fare:</p><p>Snippet 2:</p><p>La stringa di connessione e&#39; gia&#39; pronta: al primo avvio il wizard non chiede altro. Con</p><p><code>-Dbms mysql</code> o <code>-Dbms postgres</code> la riga cambia di conseguenza e porta dentro di se&#39; utente e</p><p>password, perche&#39; la password del superutente <strong>la genera l&#39;installer</strong>; la stessa password</p><p>viene salvata in <code>wuic-secrets.json</code>, accanto all&#39;installazione, ed e&#39; l&#39;unico posto in cui</p><p>resta scritta.</p><p>Il percorso manuale resta valido e funziona su qualunque sistema:</p><p>Parti dal pacchetto <code>WuicTest-src-*.zip</code> (link nella sezione <strong>Download</strong> del sito).</p><p>Estrailo in una cartella di lavoro, es. <code>C:\\dev\\WuicTest</code> (i file vanno direttamente nella root,</p><p>NON dentro una sottocartella <code>src/</code>). Il pacchetto contiene:</p><ul><li><code>WuicTest.csproj</code> → progetto host con <code>&lt;PackageReference Include=&quot;WuicCore&quot; Version=&quot;...&quot; /&gt;</code></li><li><code>wwwroot/</code> → app Angular con <code>package.json</code> che referenzia <code>wuic-framework-lib</code> da npm registry</li><li><code>appsettings.json</code> preconfigurato in modalita&#39; <code>firstRun = &quot;true&quot;</code> con placeholder <code>__SET_*__</code></li><li><code>appsettings-samples/</code> → 6 template pronti (<code>mssql</code>/<code>mysql</code>, firstRun/post-firstRun, <code>Development</code>)</li></ul><p>&gt; <strong>Non serve clonare il repository del framework</strong>: <code>WuicCore</code> arriva come pacchetto NuGet da</p><p>&gt; <code>nuget.org</code> e <code>wuic-framework-lib</code> come pacchetto npm da npm registry. Il sorgente del framework</p><p>&gt; serve solo se vuoi modificarlo — tipicamente non e&#39; il tuo caso.</p><p>&gt; <strong>npm 10.9.x e i pacchetti precedenti alla 1.7.1</strong>: quei pacchetti non contengono</p><p>&gt; <code>package-lock.json</code>, e senza lock npm 10.9.x (quello che installa Node 22 LTS) si ferma con</p><p>&gt; <code>Cannot read properties of null (reading &#39;edgesOut&#39;)</code> mentre risolve i peer. Scarica il lock</p><p>&gt; pubblicato accanto alla release — <code>https://wuic-framework.com/downloads/locks/&lt;nome-zip&gt;.package-lock.json</code></p><p>&gt; — mettilo in <code>wwwroot/</code> e rilancia <code>npm install</code>. Il one-liner <code>-Src</code> lo fa da solo.</p><h3>2. Database</h3><p>Serve un&#39;istanza del motore raggiungibile. <strong>Con il one-liner non devi fare niente</strong>: la</p><p>installa e la configura lui, e la stringa di connessione da incollare nel wizard e&#39; l&#39;ultima</p><p>cosa che stampa. Nel percorso manuale l&#39;istanza deve essere gia&#39; presente.</p><p>Connessioni in <code>appsettings.json</code>:</p><ul><li><code>MetaDataSQLConnection</code> — DB metadata (menu, tabelle, colonne, board, utenti)</li><li><code>DataSQLConnection</code> — DB dati applicativi</li></ul><p>Se e&#39; la prima installazione (<code>AppSettings.firstRun = &quot;true&quot;</code> nel template),</p><p>il wizard di scaffolding al primo avvio crea lo schema metadata e popola il DB dati.</p><p>Vedi la pagina <em>Scaffolding iniziale</em> per il flusso guidato.</p><h3>3. Backend (.NET)</h3><p>Dalla root della cartella estratta (es. <code>C:\\dev\\WuicTest</code>):</p><p>Snippet 3:</p><p>Il backend espone le API su <code>http://localhost:5000</code>.</p><h3>4. Frontend (Angular)</h3><p>In una seconda shell, dalla sottocartella <code>wwwroot/</code>:</p><p>Snippet 4:</p><p>Il frontend e&#39; disponibile su <code>http://localhost:4200</code>.</p><p>Login di default (post-firstRun): <code>admin</code> / <code>admin</code>.</p><h3>5. RAG Chatbot (opzionale)</h3><p>Il RAG Chatbot (<code>Amministrazione &gt; RAG Chat</code>) gira <strong>dentro il backend .NET</strong>:</p><p>il motore di retrieval (<code>rag-engine/WuicRagEngine.dll</code>, ONNX Runtime</p><p>in-process) viene caricato dal backend quando <code>AppSettings.rag-use-dotnet-engine</code></p><p>e&#39; <code>&quot;true&quot;</code> (default nei pacchetti di release). **Niente Python, niente venv,</p><p>nessun server separato da avviare.**</p><p>Alla <strong>prima</strong> apertura del chatbot (o a fine first-run) il backend scarica da</p><p>solo modelli ONNX (<code>bge-m3</code> + reranker), tokenizer e indice (~4,5 GB) da</p><p><code>rag-engine-models-url</code> (default <code>https://wuic-framework.com/rag-models</code>) in</p><p><code>rag-engine/artifacts/</code>. Serve una connessione internet una sola volta; il</p><p>download gira in background (1-5 min) e a inizio/fine download arriva una</p><p>notifica in-app. Nel frattempo il componente mostra lo stato <strong>RAG offline</strong> e</p><p>il resto dell&#39;applicazione funziona normalmente.</p><p>Chiavi <code>AppSettings</code> rilevanti (tutte con default gia&#39; pronti):</p><ul><li><code>rag-use-dotnet-engine</code> = <code>true</code> — attiva l&#39;engine .NET (<code>false</code> = fallback Python, vedi sotto)</li><li><code>rag-engine-device</code> = <code>auto</code> — <code>auto</code> | <code>cuda</code> | <code>cpu</code>: con GPU NVIDIA (CUDA 12.x + cuDNN 9) ~1 s/query, su CPU ~15-25 s/query</li><li><code>rag-engine-profile</code> = <code>release</code> — <code>release</code> = sorgenti framework solo come firma; <code>internal</code> = indice integrale</li><li><code>rag-engine-models-url</code> — sorgente del download al primo avvio</li><li><code>rag-engine-cuda-path</code> = (vuoto) — cartella delle DLL CUDA/cuDNN se non installate a livello di sistema</li></ul><p>Per la chat con LLM valorizza <code>rag-llm-provider</code> + <code>rag-llm-api-key</code> (Claude</p><p>via Anthropic, oppure un modello locale via Ollama con <code>rag-llm-base-url</code>).</p><p>Senza provider funziona solo la modalita&#39; retrieval (ricerca snippet).</p><p>Dettaglio delle chiavi nella pagina <em>AppSettings</em>.</p><p>&gt; Lo stack storico Python (<code>scripts/rag-setup.ps1</code> + <code>rag_server.py</code> su</p><p>&gt; <code>127.0.0.1:8765</code>) resta utilizzabile solo come fallback con</p><p>&gt; <code>rag-use-dotnet-engine = &quot;false&quot;</code> e non e&#39; incluso nei pacchetti di release.</p><h2>Riepilogo servizi</h2><table><thead><tr><th>Servizio</th><th>Porta</th><th>Obbligatorio</th><th>Comando rapido</th></tr></thead><tbody><tr><td>SQL Server</td><td>1433</td><td>si</td><td>(servizio Windows)</td></tr><tr><td>Backend .NET</td><td>5000</td><td>si</td><td><code>dotnet watch ... run</code></td></tr><tr><td>Frontend Angular</td><td>4200</td><td>si</td><td><code>npm run serve:dev</code></td></tr><tr><td>Engine RAG .NET (ONNX)</td><td>in-process</td><td>no</td><td>caricato dal backend alla prima chat</td></tr></tbody></table><h2>Quick Start — primo componente</h2><p>1. Configura endpoint AsmxProxy.</p><p>2. Definisci route metadata e colonne.</p><p>3. Monta <code>wuic-data-source</code> + <code>wuic-data-repeater</code>.</p><p>Snippet 5:</p>",
+                    "html": "<h1>Panoramica Framework</h1><p>WUIC Framework e&#39; una piattaforma metadata-driven per creare interfacce business in modo rapido e coerente.</p><h2>Cosa include</h2><ul><li>DataSource e DataRepeater per orchestrare dati e rendering.</li><li>Archetypes visuali (list, map, scheduler, chart, carousel).</li><li>Designer runtime per dashboard e template dinamici.</li><li>Workflow designer/runner per processi operativi.</li><li>RAG Chatbot per interrogare la codebase in linguaggio naturale.</li><li>Multi-DBMS: SQL Server, MySQL, PostgreSQL e Oracle tramite provider drop-in (<code>dbms</code>: <code>mssql</code> | <code>mysql</code> | <code>postgresql</code> | <code>oracle</code>).</li></ul><h2>First Steps — Avvio ambiente dev</h2><p>Lo stack WUIC e&#39; composto da piu&#39; servizi. Avviali nell&#39;ordine indicato.</p><h3>Prerequisiti</h3><table><thead><tr><th>Cosa</th><th>Verifica</th><th>Note</th></tr></thead><tbody><tr><td>.NET 10 SDK</td><td><code>dotnet --version</code></td><td>Hosting Bundle per IIS in produzione</td></tr><tr><td>Node.js 22 LTS</td><td><code>node --version</code></td><td>La 22 e&#39; la versione con cui il pacchetto e&#39; testato; con npm 10.9.x installa solo grazie al <code>package-lock.json</code> incluso</td></tr><tr><td>PowerShell 5.1+</td><td><code>$PSVersionTable.PSVersion</code></td><td>La PowerShell preinstallata su Windows basta: <code>rename-project.ps1</code> e gli script <code>llm-workspace/</code> girano anche su 5.1. PowerShell 7 e&#39; consigliata, non richiesta</td></tr><tr><td>SQL Server 2019+</td><td><code>sqlcmd -S localhost\\sqlexpress -E -C -Q &quot;SELECT 1&quot;</code></td><td>Se manca, <strong>il one-liner lo installa da se&#39;</strong> (SQL Server Express, o il motore scelto con <code>-Dbms</code>); su Windows Server no, vedi il riquadro sotto. 2019 basta per i pacchetti senza <code>.bak</code>; il tutorial <code>.bak</code> e&#39; un backup di SQL Server 2022 e richiede <strong>2022 o superiore</strong></td></tr><tr><td>Linux (installer <code>install.sh</code>)</td><td><code>lsb_release -ds</code></td><td><strong>Ubuntu 22.04 o 24.04 LTS</strong> (24.04 raccomandata): sono le uniche Ubuntu su cui Microsoft supporta SQL Server, la <strong>26.04 non e&#39; supportata</strong> (<a href=\"https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-setup?view=sql-server-ver17\" target=\"_blank\" rel=\"noopener noreferrer\">Supported platforms</a>). Stessa raccomandazione con MySQL, PostgreSQL e Oracle, perche&#39; l&#39;installer e&#39; provato su quelle</td></tr><tr><td>GPU NVIDIA (CUDA 12.x + cuDNN 9)</td><td><code>nvidia-smi</code></td><td>Opzionale: accelera il RAG Chatbot (senza GPU gira su CPU)</td></tr></tbody></table><p>&gt; <strong>Su Windows Server il database va installato prima.</strong> Il one-liner si procura i componenti</p><p>&gt; mancanti tramite <code>winget</code>, che su Windows Server non e&#39; presente: senza un&#39;istanza gia&#39;</p><p>&gt; raggiungibile l&#39;installazione si ferma con `No SQL Server instance reachable and winget is</p><p>&gt; missing`. Installa quindi il motore prima di lanciare la riga - per SQL Server serve la</p><p>&gt; <strong>2019 o superiore</strong> (la Express basta; <strong>2022 o superiore</strong> per il tutorial <code>.bak</code>), e una</p><p>&gt; 2017 non viene accettata. Se l&#39;istanza non e&#39; quella predefinita, passala con</p><p>&gt; <code>-SqlServer &#39;localhost\\NOMEISTANZA&#39;</code>. Vale per tutti i motori, non solo SQL Server.</p><h3>1. Scarica il template di progetto</h3><p>Su Windows fai tutto con una riga di PowerShell: scarica il pacchetto, verifica .NET SDK 10 e Node.js 22</p><p>(installando cio&#39; che manca), esegue <code>dotnet restore</code> e <code>npm install</code>, e installa</p><p>l&#39;estensione WUIC Assistant in VS Code.</p><p>Snippet 1:</p><p>Opzioni utili sulla stessa riga: <code>-Dbms mysql</code> (oppure <code>postgres</code>, <code>oracle</code>) per un motore</p><p>diverso da SQL Server — che l&#39;installer installa e configura da se&#39; — e <code>-WithTutorial</code> per</p><p>scaricare anche il database di esempio.</p><p>Quando ha finito, l&#39;ultima schermata e&#39; gia&#39; l&#39;elenco delle cose da fare:</p><p>Snippet 2:</p><p>La stringa di connessione e&#39; gia&#39; pronta: al primo avvio il wizard non chiede altro. Con</p><p><code>-Dbms mysql</code> o <code>-Dbms postgres</code> la riga cambia di conseguenza e porta dentro di se&#39; utente e</p><p>password, perche&#39; la password del superutente <strong>la genera l&#39;installer</strong>; la stessa password</p><p>viene salvata in <code>wuic-secrets.json</code>, accanto all&#39;installazione, ed e&#39; l&#39;unico posto in cui</p><p>resta scritta.</p><p>Il percorso manuale resta valido e funziona su qualunque sistema:</p><p>Parti dal pacchetto <code>WuicTest-src-*.zip</code> (link nella sezione <strong>Download</strong> del sito).</p><p>Estrailo in una cartella di lavoro, es. <code>C:\\dev\\WuicTest</code> (i file vanno direttamente nella root,</p><p>NON dentro una sottocartella <code>src/</code>). Il pacchetto contiene:</p><ul><li><code>WuicTest.csproj</code> → progetto host con <code>&lt;PackageReference Include=&quot;WuicCore&quot; Version=&quot;...&quot; /&gt;</code></li><li><code>wwwroot/</code> → app Angular con <code>package.json</code> che referenzia <code>wuic-framework-lib</code> da npm registry</li><li><code>appsettings.json</code> preconfigurato in modalita&#39; <code>firstRun = &quot;true&quot;</code> con placeholder <code>__SET_*__</code></li><li><code>appsettings-samples/</code> → 6 template pronti (<code>mssql</code>/<code>mysql</code>, firstRun/post-firstRun, <code>Development</code>)</li></ul><p>&gt; <strong>Non serve clonare il repository del framework</strong>: <code>WuicCore</code> arriva come pacchetto NuGet da</p><p>&gt; <code>nuget.org</code> e <code>wuic-framework-lib</code> come pacchetto npm da npm registry. Il sorgente del framework</p><p>&gt; serve solo se vuoi modificarlo — tipicamente non e&#39; il tuo caso.</p><p>&gt; <strong>npm 10.9.x e i pacchetti precedenti alla 1.7.1</strong>: quei pacchetti non contengono</p><p>&gt; <code>package-lock.json</code>, e senza lock npm 10.9.x (quello che installa Node 22 LTS) si ferma con</p><p>&gt; <code>Cannot read properties of null (reading &#39;edgesOut&#39;)</code> mentre risolve i peer. Scarica il lock</p><p>&gt; pubblicato accanto alla release — <code>https://wuic-framework.com/downloads/locks/&lt;nome-zip&gt;.package-lock.json</code></p><p>&gt; — mettilo in <code>wwwroot/</code> e rilancia <code>npm install</code>. Il one-liner <code>-Src</code> lo fa da solo.</p><h3>2. Database</h3><p>Serve un&#39;istanza del motore raggiungibile. <strong>Con il one-liner non devi fare niente</strong>: la</p><p>installa e la configura lui, e la stringa di connessione da incollare nel wizard e&#39; l&#39;ultima</p><p>cosa che stampa. Nel percorso manuale l&#39;istanza deve essere gia&#39; presente.</p><p>Connessioni in <code>appsettings.json</code>:</p><ul><li><code>MetaDataSQLConnection</code> — DB metadata (menu, tabelle, colonne, board, utenti)</li><li><code>DataSQLConnection</code> — DB dati applicativi</li></ul><p>Se e&#39; la prima installazione (<code>AppSettings.firstRun = &quot;true&quot;</code> nel template),</p><p>il wizard di scaffolding al primo avvio crea lo schema metadata e popola il DB dati.</p><p>Vedi la pagina <em>Scaffolding iniziale</em> per il flusso guidato.</p><p>#### Cosa chiede il wizard di primo avvio</p><p>Al primo avvio l&#39;applicazione non mostra il login ma la pagina **Configurazione iniziale</p><p>progetto**. Si compila una volta sola: al termine <code>firstRun</code> passa a <code>false</code> e la pagina non</p><p>ricompare piu&#39;.</p><ul><li><strong>Modalita&#39; setup</strong> — due voci: <strong>DB esistente</strong>, che registra un database gia&#39; tuo, e</li></ul><p>  <strong>Tutorial WideWorldImporters</strong>, che installa il database di esempio. La seconda compare</p><p>  solo se il pacchetto porta con se&#39; il tutorial (<code>tutorialAvailable</code>): nei pacchetti senza</p><p>  tutorial la tendina non c&#39;e&#39; affatto e la modalita&#39; e&#39; &quot;DB esistente&quot;.</p><ul><li><strong>DBMS</strong> — il motore. Cambiandolo, la stringa di connessione sotto viene riscritta nella</li></ul><p>  forma del provider scelto.</p><ul><li><strong>DataSQLConnection</strong> — la stringa verso il DB dati, ed e&#39; il campo da cui dipende tutto il</li></ul><p>  resto: finche&#39; non premi <strong>Test connessione e carica DB</strong> l&#39;elenco dei database resta</p><p>  disabilitato. Il test verifica le credenziali, elenca i database del server e, su SQL</p><p>  Server, corregge da se&#39; i parametri dei certificati</p><p>  (<code>Encrypt=False;TrustServerCertificate=True</code>) dicendotelo. <code>Integrated Security</code> vale solo</p><p>  su SQL Server: sugli altri motori servono utente e password.</p><ul><li><strong>Database dati</strong> e <strong>Nome DB metadati</strong> — il primo si sceglie dall&#39;elenco caricato dal</li></ul><p>  test (in modalita&#39; tutorial e&#39; un campo libero, default <code>WideWorldImporters</code>); il secondo e&#39;</p><p>  il nome del database metadati da creare (default <code>metadataDB</code>, <code>MetadataCRM</code> in modalita&#39;</p><p>  tutorial). Se quel database esiste gia&#39;, il wizard chiede conferma prima di ricrearlo.</p><ul><li><strong>Esegui scaffold automatico delle tabelle</strong> (solo &quot;DB esistente&quot;) — popola</li></ul><p>  <code>_metadati__tabelle</code> / <code>_metadati__colonne</code> da tutte le tabelle del database scelto. E&#39; la</p><p>  voce che allunga di piu&#39; il provisioning su database con molte tabelle.</p><ul><li><strong>Utente admin iniziale</strong> — username (default <code>admin</code>), password (minimo 4 caratteri) e</li></ul><p>  lingua. Non esiste una password predefinita: quella scritta qui e&#39; l&#39;unica con cui entrerai</p><p>  al primo login. La lingua scelta viene applicata all&#39;utente admin e a questa pagina stessa.</p><ul><li><strong>RAG Chatbot</strong> — solo la chiave Anthropic, opzionale. Niente da installare: vedi il punto 5.</li></ul><p>Premuto <strong>Conferma e genera metadataDB</strong> il provisioning va avanti da solo, con una barra e il</p><p>numero di batch elaborati. Quanto dura, misurato sulle installazioni di prova: <strong>30 s - 2 min</strong></p><p>in modalita&#39; tutorial, <strong>1-4 min</strong> su un database esistente con lo scaffold automatico attivo.</p><p>Finito, la pagina lascia il posto al form di login.</p><h3>3. Backend (.NET)</h3><p>Dalla root della cartella estratta (es. <code>C:\\dev\\WuicTest</code>):</p><p>Snippet 3:</p><p>Il backend espone le API su <code>http://localhost:5000</code>.</p><h3>4. Frontend (Angular)</h3><p>In una seconda shell, dalla sottocartella <code>wwwroot/</code>:</p><p>Snippet 4:</p><p>Il frontend e&#39; disponibile su <code>http://localhost:4200</code>.</p><p>Le credenziali sono quelle dell&#39;utente admin scelto nel wizard di primo avvio: lo username e&#39;</p><p><code>admin</code> se non l&#39;hai cambiato, la password e&#39; quella che hai scritto tu (non esiste una</p><p>password predefinita).</p><h3>5. RAG Chatbot (opzionale)</h3><p>Il RAG Chatbot (<code>Amministrazione &gt; RAG Chat</code>) gira <strong>dentro il backend .NET</strong>:</p><p>il motore di retrieval (<code>rag-engine/WuicRagEngine.dll</code>, ONNX Runtime</p><p>in-process) viene caricato dal backend quando <code>AppSettings.rag-use-dotnet-engine</code></p><p>e&#39; <code>&quot;true&quot;</code> (default nei pacchetti di release). **Niente Python, niente venv,</p><p>nessun server separato da avviare.**</p><p>Alla <strong>prima</strong> apertura del chatbot (o a fine first-run) il backend scarica da</p><p>solo modelli ONNX (<code>bge-m3</code> + reranker), tokenizer e indice (~4,5 GB) da</p><p><code>rag-engine-models-url</code> (default <code>https://wuic-framework.com/rag-models</code>) in</p><p><code>rag-engine/artifacts/</code>. Serve una connessione internet una sola volta; il</p><p>download gira in background (1-5 min) e a inizio/fine download arriva una</p><p>notifica in-app. Nel frattempo il componente mostra lo stato <strong>RAG offline</strong> e</p><p>il resto dell&#39;applicazione funziona normalmente.</p><p>Chiavi <code>AppSettings</code> rilevanti (tutte con default gia&#39; pronti):</p><ul><li><code>rag-use-dotnet-engine</code> = <code>true</code> — attiva l&#39;engine .NET (<code>false</code> = fallback Python, vedi sotto)</li><li><code>rag-engine-device</code> = <code>auto</code> — <code>auto</code> | <code>cuda</code> | <code>cpu</code>: con GPU NVIDIA (CUDA 12.x + cuDNN 9) ~1 s/query, su CPU ~15-25 s/query</li><li><code>rag-engine-profile</code> = <code>release</code> — <code>release</code> = sorgenti framework solo come firma; <code>internal</code> = indice integrale</li><li><code>rag-engine-models-url</code> — sorgente del download al primo avvio</li><li><code>rag-engine-cuda-path</code> = (vuoto) — cartella delle DLL CUDA/cuDNN se non installate a livello di sistema</li></ul><p>Per la chat con LLM valorizza <code>rag-llm-provider</code> + <code>rag-llm-api-key</code> (Claude</p><p>via Anthropic, oppure un modello locale via Ollama con <code>rag-llm-base-url</code>).</p><p>Senza provider funziona solo la modalita&#39; retrieval (ricerca snippet).</p><p>Dettaglio delle chiavi nella pagina <em>AppSettings</em>.</p><p>&gt; Lo stack storico Python (<code>scripts/rag-setup.ps1</code> + <code>rag_server.py</code> su</p><p>&gt; <code>127.0.0.1:8765</code>) resta utilizzabile solo come fallback con</p><p>&gt; <code>rag-use-dotnet-engine = &quot;false&quot;</code> e non e&#39; incluso nei pacchetti di release.</p><h2>Riepilogo servizi</h2><table><thead><tr><th>Servizio</th><th>Porta</th><th>Obbligatorio</th><th>Comando rapido</th></tr></thead><tbody><tr><td>SQL Server</td><td>1433</td><td>si</td><td>(servizio Windows)</td></tr><tr><td>Backend .NET</td><td>5000</td><td>si</td><td><code>dotnet watch ... run</code></td></tr><tr><td>Frontend Angular</td><td>4200</td><td>si</td><td><code>npm run serve:dev</code></td></tr><tr><td>Engine RAG .NET (ONNX)</td><td>in-process</td><td>no</td><td>caricato dal backend alla prima chat</td></tr></tbody></table><h2>Quick Start — primo componente</h2><p>1. Configura endpoint AsmxProxy.</p><p>2. Definisci route metadata e colonne.</p><p>3. Monta <code>wuic-data-source</code> + <code>wuic-data-repeater</code>.</p><p>Snippet 5:</p><h2>Le prime liste mostrano 20 record: e&#39; la modalita&#39; Trial</h2><p>Un&#39;installazione appena fatta gira <strong>senza licenza</strong>, cioe&#39; in modalita&#39; Trial, e in quella</p><p>modalita&#39; <strong>ogni query e&#39; limitata a 20 record</strong>. Non e&#39; un errore ne&#39; un limite del database:</p><p>una lista che dichiara &quot;20 di 20&quot; su una tabella con migliaia di righe sta semplicemente</p><p>girando senza licenza.</p><p>Come confermarlo in un secondo:</p><p>Snippet 6:</p><p><code>licenseValid: false</code> conferma la Trial, e <code>licenseReason</code> dice perche&#39; (<code>invalid_signature</code>,</p><p><code>license_expired</code>, <code>machine_fingerprint_not_authorized</code>, ...).</p><p>Come uscirne: si incolla la licenza da <strong>Amministrazione &gt; Editor AppSettings</strong>, scheda Licensing,</p><p>ed e&#39; valida subito — non serve riavviare il backend. I dettagli, compresi i limiti che la</p><p>Trial impone oltre al numero di record, stanno nella pagina <a href=\"licensing.md\">Licensing</a>.</p>",
                     "codeSamples": [
                         {
                             "id": "code_1",
@@ -1184,6 +1188,12 @@ const frameworkDocsContent = {
                             "title": "Snippet 5",
                             "language": "html",
                             "code": "<wuic-data-source [hardcodedRoute]=\"'cities'\"></wuic-data-source>\n<wuic-data-repeater [hardcodedAction]=\"'list'\"></wuic-data-repeater>"
+                        },
+                        {
+                            "id": "code_6",
+                            "title": "Snippet 6",
+                            "language": "bash",
+                            "code": "curl -s http://localhost:5000/api/Meta/LicenseStatus"
                         }
                     ]
                 }
@@ -1218,18 +1228,22 @@ const frameworkDocsContent = {
             "toc": [
                 {
                     "id": "sec_1",
-                    "title": "Quando usarlo"
+                    "title": "Con il pacchetto tutorial non c'e' niente da scaffoldare"
                 },
                 {
                     "id": "sec_2",
-                    "title": "Comportamento con firstRun=true"
+                    "title": "Quando usarlo"
                 },
                 {
                     "id": "sec_3",
-                    "title": "Operazioni tipiche"
+                    "title": "Comportamento con firstRun=true"
                 },
                 {
                     "id": "sec_4",
+                    "title": "Operazioni tipiche"
+                },
+                {
+                    "id": "sec_5",
                     "title": "Dopo il provisioning"
                 }
             ],
@@ -1237,7 +1251,7 @@ const frameworkDocsContent = {
                 {
                     "id": "overview",
                     "title": "Overview",
-                    "html": "<h1>Scaffolding iniziale</h1><p>Questa pagina descrive il bootstrap iniziale quando <code>AppSettings.firstRun = true</code>.</p><h2>Quando usarlo</h2><ul><li>Nuova installazione (DB metadata/dati non ancora pronti).</li><li>Ambiente locale da riallineare con setup iniziale.</li><li>Primo avvio dopo deploy dove vuoi forzare la procedura guidata di provisioning.</li></ul><h2>Comportamento con firstRun=true</h2><ul><li>L&#39;endpoint <code>GET /api/Meta/FirstRunStatus</code> espone <code>firstRun: true</code>.</li><li>In login compare il flusso di primo avvio (es. azione <code>Aggiorna</code> nello screen).</li><li>Il setup applica le configurazioni base (connessioni, impostazioni runtime, bootstrap metadata).</li></ul><h2>Operazioni tipiche</h2><ul><li>Verifica <code>AppSettings.firstRun</code> a <code>true</code> in <code>appsettings.{Environment}.json</code> dell&#39;host che stai eseguendo.</li><li>Avvia applicazione e completa la procedura di scaffolding iniziale da UI.</li><li>Controlla che connessioni e parametri principali risultino coerenti (<code>dbms</code>, <code>DataDBName</code>, <code>ConnectionStrings</code>).</li></ul><h2>Dopo il provisioning</h2><ul><li>La procedura di setup porta <code>firstRun</code> a <code>false</code> per evitare riesecuzioni ad ogni avvio.</li><li>Esegui login standard e valida l&#39;accesso alle route principali.</li></ul>",
+                    "html": "<h1>Scaffolding iniziale</h1><p>Questa pagina descrive il bootstrap iniziale quando <code>AppSettings.firstRun = true</code>.</p><h2>Con il pacchetto tutorial non c&#39;e&#39; niente da scaffoldare</h2><p>Lo scaffolding di cui parla questa pagina — leggere le tabelle di un database e registrarle in</p><p><code>_metadati__tabelle</code> / <code>_metadati__colonne</code> — riguarda <strong>solo</strong> la modalita&#39; &quot;DB esistente&quot; del</p><p>wizard di primo avvio: e&#39; li&#39; che compare la casella *Esegui scaffold automatico delle tabelle</p><p>del DB selezionato*.</p><p>Nei pacchetti <strong>tutorial</strong> quella casella non esiste. Il database metadati arriva gia&#39; popolato</p><p>(route, colonne, menu, traduzioni, dashboard di esempio) e il wizard si limita a ripristinarlo e</p><p>a creare l&#39;utente admin. Vedere route gia&#39; pronte subito dopo il primo avvio non e&#39; quindi il</p><p>risultato di uno scaffolding: e&#39; il contenuto del tutorial.</p><table><thead><tr><th>Modalita&#39; del wizard</th><th>Cosa succede ai metadata</th></tr></thead><tbody><tr><td>Tutorial WideWorldImporters</td><td>Metadata gia&#39; pronti, ripristinati dal pacchetto. Nessuno scaffolding.</td></tr><tr><td>DB esistente, casella spenta</td><td>DB metadati creato vuoto: le route si registrano a mano, o dopo dalla pagina Scaffolding.</td></tr><tr><td>DB esistente, casella accesa</td><td>A fine installazione ogni tabella del database scelto viene registrata come route.</td></tr></tbody></table><p>Il resto di questa pagina vale per le ultime due righe della tabella.</p><h2>Quando usarlo</h2><ul><li>Nuova installazione (DB metadata/dati non ancora pronti).</li><li>Ambiente locale da riallineare con setup iniziale.</li><li>Primo avvio dopo deploy dove vuoi forzare la procedura guidata di provisioning.</li></ul><h2>Comportamento con firstRun=true</h2><ul><li>L&#39;endpoint <code>GET /api/Meta/FirstRunStatus</code> espone <code>firstRun: true</code>.</li><li>In login compare il flusso di primo avvio (es. azione <code>Aggiorna</code> nello screen).</li><li>Il setup applica le configurazioni base (connessioni, impostazioni runtime, bootstrap metadata).</li></ul><h2>Operazioni tipiche</h2><ul><li>Verifica <code>AppSettings.firstRun</code> a <code>true</code> in <code>appsettings.{Environment}.json</code> dell&#39;host che stai eseguendo.</li><li>Avvia applicazione e completa la procedura di scaffolding iniziale da UI.</li><li>Controlla che connessioni e parametri principali risultino coerenti (<code>dbms</code>, <code>DataDBName</code>, <code>ConnectionStrings</code>).</li></ul><h2>Dopo il provisioning</h2><ul><li>La procedura di setup porta <code>firstRun</code> a <code>false</code> per evitare riesecuzioni ad ogni avvio.</li><li>Esegui login standard e valida l&#39;accesso alle route principali.</li></ul>",
                     "codeSamples": []
                 }
             ],
@@ -1296,7 +1310,7 @@ const frameworkDocsContent = {
                 {
                     "id": "overview",
                     "title": "Overview",
-                    "html": "<h1>Licensing</h1><p>Questa pagina spiega il licensing dal punto di vista utente finale: cosa serve, come ottenere la licenza e come applicarla.</p><h2>Come ottenere una licenza</h2><p>Consulta i piani, le feature incluse per ciascun tier (Developer / Professional / Software House) e procedi all&#39;acquisto sul sito pubblico:</p><ul><li><a href=\"https://wuic-framework.com/pricing\" target=\"_blank\" rel=\"noopener noreferrer\">Pricing e piani WUIC — wuic-framework.com/pricing</a></li><li><a href=\"mailto:licensing@wuic-framework.com\">Contatti commerciali</a> — la prova non richiede licenza: senza licenza il framework gira in modalita&#39; Trial (20 record per query)</li><li><a href=\"https://wuic-framework.com\" target=\"_blank\" rel=\"noopener noreferrer\">Homepage WUIC</a></li></ul><p>Dopo l&#39;acquisto riceverai una mail con <code>license-payload</code> + <code>license-signature</code> da installare come descritto nella &quot;Procedura utente finale&quot; qui sotto.</p><h2>Come funziona</h2><ul><li>La licenza e valida solo se:</li><li>firma corretta.</li><li><code>machineFingerprint</code> del server corrente presente nella lista <code>machineFingerprints</code> del payload firmato.</li><li>Se la licenza non e valida, la lettura dati (<code>getFlatRecordData</code>) viene limitata a massimo 20 record. Inoltre l&#39;hook host <code>customizeSelect</code> viene bypassato (non invocato).</li></ul><h2>Dove trovo il machineFingerprint</h2><p>Endpoint backend:</p><ul><li><code>GET /api/Meta/LicenseStatus</code> → campo <code>machineFingerprint</code> (sempre disponibile, anche senza licenza).</li><li>Durante il first-run lo espone anche <code>GET /api/Meta/FirstRunStatus</code>.</li></ul><h2>Procedura utente finale</h2><p>1. Recupera <code>machineFingerprint</code> dal tuo host.</p><p>2. Invia il valore al fornitore/licensor.</p><p>3. Ricevi i valori licenza:</p><ul><li><code>license-payload</code></li><li><code>license-signature</code></li><li><code>license-public-key-pem</code> (se previsto dalla tua installazione)</li></ul><p>4. Inserisci i valori nel file <code>appsettings.{Environment}.json</code> dell&#39;host in esecuzione, sezione <code>AppSettings</code>.</p><p>5. Riavvia il backend.</p><p>6. Verifica stato licenza da API:</p><ul><li><code>GET /api/Meta/LicenseStatus</code></li><li>atteso: <code>licenseValid = true</code>.</li></ul><h2>Licenza multi-macchina</h2><p>Un&#39;unica licenza puo autorizzare piu macchine includendo piu valori in <code>machineFingerprints</code>.</p><h2>Troubleshooting rapido</h2><ul><li><code>licenseReason = invalid_signature</code>:</li><li>payload/firma non coerenti tra loro oppure public key diversa.</li><li><code>licenseReason = machine_fingerprint_not_authorized</code>:</li><li>il fingerprint della macchina corrente non e presente nella licenza ricevuta.</li><li><code>licenseReason = machine_fingerprint_missing</code>:</li><li>il runtime non riesce a calcolare il fingerprint locale.</li><li><code>licenseReason = license_expired</code>:</li><li>la licenza e scaduta, richiedi rinnovo.</li></ul>",
+                    "html": "<h1>Licensing</h1><p>Questa pagina spiega il licensing dal punto di vista utente finale: cosa serve, come ottenere la licenza e come applicarla.</p><h2>Come ottenere una licenza</h2><p>Consulta i piani, le feature incluse per ciascun tier (Developer / Professional / Software House) e procedi all&#39;acquisto sul sito pubblico:</p><ul><li><a href=\"https://wuic-framework.com/pricing\" target=\"_blank\" rel=\"noopener noreferrer\">Pricing e piani WUIC — wuic-framework.com/pricing</a></li><li><a href=\"mailto:licensing@wuic-framework.com\">Contatti commerciali</a> — la prova non richiede licenza: senza licenza il framework gira in modalita&#39; Trial (20 record per query)</li><li><a href=\"https://wuic-framework.com\" target=\"_blank\" rel=\"noopener noreferrer\">Homepage WUIC</a></li></ul><p>Dopo l&#39;acquisto riceverai una mail con <code>license-payload</code> + <code>license-signature</code> da installare come descritto nella &quot;Procedura utente finale&quot; qui sotto.</p><h2>Come funziona</h2><ul><li>La licenza e valida solo se:</li><li>firma corretta.</li><li><code>machineFingerprint</code> del server corrente presente nella lista <code>machineFingerprints</code> del payload firmato.</li><li>Se la licenza non e valida, la lettura dati (<code>getFlatRecordData</code>) viene limitata a massimo 20 record. Inoltre l&#39;hook host <code>customizeSelect</code> viene bypassato (non invocato).</li></ul><h2>Dove trovo il machineFingerprint</h2><p>Endpoint backend:</p><ul><li><code>GET /api/Meta/LicenseStatus</code> → campo <code>machineFingerprint</code> (sempre disponibile, anche senza licenza).</li><li>Durante il first-run lo espone anche <code>GET /api/Meta/FirstRunStatus</code>.</li></ul><h2>Procedura utente finale</h2><p>1. Recupera <code>machineFingerprint</code> dal tuo host.</p><p>2. Invia il valore al fornitore/licensor.</p><p>3. Ricevi i valori licenza:</p><ul><li><code>license-payload</code></li><li><code>license-signature</code></li><li><code>license-public-key-pem</code> (se previsto dalla tua installazione)</li></ul><p>4. Incolla i valori dall&#39;interfaccia: <strong>Amministrazione &gt; Editor AppSettings</strong>, sezione</p><p>   <strong>License</strong> (campi <code>License email</code>, <code>License payload</code>, <code>License signature</code>,</p><p>   <code>Public key (PEM)</code>), poi salva. In alternativa si possono scrivere a mano nella sezione</p><p>   <code>AppSettings</code> del file <code>appsettings.{Environment}.json</code> dell&#39;host in esecuzione.</p><p>5. Verifica lo stato licenza:</p><ul><li>da API: <code>GET /api/Meta/LicenseStatus</code>, atteso <code>licenseValid = true</code>;</li><li>oppure dalla pagina stessa, che rilegge la licenza subito dopo il salvataggio.</li></ul><p><strong>Riavviare il backend non serve, se passi dall&#39;editor.</strong> Salvando <code>license-payload</code> /</p><p><code>license-signature</code> dall&#39;AppSettings Editor il backend ricarica da se&#39; il servizio di</p><p>validazione, e la licenza vale dalla richiesta successiva. Il riavvio serve solo nell&#39;altro</p><p>caso, quando i valori vengono scritti a mano nel file: quello viene riletto all&#39;avvio.</p><h2>Licenza multi-macchina</h2><p>Un&#39;unica licenza puo autorizzare piu macchine includendo piu valori in <code>machineFingerprints</code>.</p><h2>Troubleshooting rapido</h2><ul><li><code>licenseReason = invalid_signature</code>:</li><li>payload/firma non coerenti tra loro oppure public key diversa.</li><li><code>licenseReason = machine_fingerprint_not_authorized</code>:</li><li>il fingerprint della macchina corrente non e presente nella licenza ricevuta.</li><li><code>licenseReason = machine_fingerprint_missing</code>:</li><li>il runtime non riesce a calcolare il fingerprint locale.</li><li><code>licenseReason = license_expired</code>:</li><li>la licenza e scaduta, richiedi rinnovo.</li></ul>",
                     "codeSamples": []
                 }
             ],
@@ -1971,42 +1985,46 @@ const frameworkDocsContent = {
                 },
                 {
                     "id": "sec_2",
-                    "title": "Screenshot reference (manuale utente)"
+                    "title": "Cosa mostra la toolbar di default"
                 },
                 {
                     "id": "sec_3",
-                    "title": "Metadati inline editing"
+                    "title": "Screenshot reference (manuale utente)"
                 },
                 {
                     "id": "sec_4",
-                    "title": "Toolbar export/import"
+                    "title": "Metadati inline editing"
                 },
                 {
                     "id": "sec_5",
-                    "title": "Config metadata"
+                    "title": "Toolbar export/import"
                 },
                 {
                     "id": "sec_6",
-                    "title": "md_props_bag: toolbar"
+                    "title": "Config metadata"
                 },
                 {
                     "id": "sec_7",
-                    "title": "md_props_bag: archetypes.list"
+                    "title": "md_props_bag: toolbar"
                 },
                 {
                     "id": "sec_8",
-                    "title": "Paging: md_pagesize e md_page_size_choice"
+                    "title": "md_props_bag: archetypes.list"
                 },
                 {
                     "id": "sec_9",
-                    "title": "Forzatura virtualizzazione su page size alto"
+                    "title": "Paging: md_pagesize e md_page_size_choice"
                 },
                 {
                     "id": "sec_10",
-                    "title": "Eventi e subscriptions (host)"
+                    "title": "Forzatura virtualizzazione su page size alto"
                 },
                 {
                     "id": "sec_11",
+                    "title": "Eventi e subscriptions (host)"
+                },
+                {
+                    "id": "sec_12",
                     "title": "`rowCustomSelect` — signature reale (gotcha)"
                 }
             ],
@@ -2014,7 +2032,7 @@ const frameworkDocsContent = {
                 {
                     "id": "overview",
                     "title": "Overview",
-                    "html": "<h1>List Grid</h1><p>Componente principale per liste tabellari con filtri, sorting, paging server-side e azioni riga.</p><h2>Use cases</h2><ul><li>CRUD tabellari enterprise.</li><li>Report operativi con filtri multi-colonna.</li><li>Dataset molto grandi con <code>cursorMode</code>.</li></ul><h2>Screenshot reference (manuale utente)</h2><ul><li><code>manual__grid__01.png</code>: modalita <code>inline cell edit</code> in list-grid.</li><li><code>manual__grid__02.png</code>: modalita <code>inline edit</code> (row-level) in list-grid.</li></ul><h2>Metadati inline editing</h2><p>Configurazione nel <code>md_props_bag</code> della tabella metadata:</p><ul><li><code>md_inline_edit</code></li></ul><p>  - abilita l&#39;editing inline della riga in list-grid (celle editabili in contesto riga, senza apertura popup).</p><p>  - utile quando vuoi mantenere la UX di tabella con editing rapido per record.</p><ul><li><code>md_inline_cell_edit</code></li></ul><p>  - abilita l&#39;editing inline &quot;cell-by-cell&quot; (focus sulla singola cella).</p><p>  - nota: nelle configurazioni legacy puo comparire come <code>md_inline_cell_editing</code>; il comportamento runtime e lo stesso.</p><p>  - <strong>promozione runtime</strong>: quando <code>md_inline_cell_edit</code> e <code>true</code>, il componente forza</p><p>    a runtime anche <code>md_inline_edit = true</code> indipendentemente dal valore in DB.</p><p>    Entrambe le UX hanno bisogno della action column visibile, quindi sono mutualmente</p><p>    non-esclusive a livello di rendering.</p><ul><li><code>md_batch_save</code></li></ul><p>  - abilita il salvataggio batch delle modifiche pendenti (<code>Save changes</code> / <code>Cancel changes</code>).</p><p>  - se usato insieme a inline-cell, le modifiche restano pending fino al salvataggio esplicito.</p><p>  - <strong>prerequisito</strong>: <code>md_batch_save</code> ha effetto <strong>solo</strong> se <code>md_inline_cell_edit</code> e <code>true</code>.</p><p>    Con <code>md_inline_cell_edit:false</code> il flag viene ignorato a runtime e i bottoni</p><p>    &quot;Salva modifiche / Annulla modifiche&quot; non vengono renderizzati.</p><h3>Combinazioni valide</h3><table><thead><tr><th><code>md_inline_edit</code></th><th><code>md_inline_cell_edit</code></th><th><code>md_batch_save</code></th><th>Risultato runtime</th></tr></thead><tbody><tr><td><code>true</code></td><td><code>false</code></td><td>qualsiasi</td><td>Row-level inline edit con pencil. <code>md_batch_save</code> ignorato.</td></tr><tr><td><code>false</code></td><td><code>true</code></td><td><code>false</code></td><td>Cell-by-cell autosave on blur. <code>md_inline_edit</code> forzato a <code>true</code> a runtime.</td></tr><tr><td><code>false</code></td><td><code>true</code></td><td><code>true</code></td><td>Cell-by-cell con buffer pending + toolbar <code>Salva / Annulla modifiche</code>.</td></tr><tr><td><code>false</code></td><td><code>false</code></td><td>qualsiasi</td><td>Nessun inline editing. <code>md_batch_save</code> ignorato.</td></tr></tbody></table><p>Esempio row-level inline edit:</p><p>Snippet 1:</p><p>Esempio cell-by-cell con batch save:</p><p>Snippet 2:</p><h2>Toolbar export/import</h2><ul><li>Export XLS:</li></ul><p>  - mostra dialog di progress con percentuale realtime;</p><p>  - azioni: <code>Continua in background</code>, <code>Annulla task</code>, <code>Interrompi e scarica parziale</code>;</p><p>  - in background crea una notifica con progress; click riapre il dialog.</p><ul><li>Import XLS/XLSX (se <code>md_importable = true</code>):</li></ul><p>  - dialog di progress dopo la conferma;</p><p>  - azioni: <code>Continua in background</code>, <code>Annulla import (rollback)</code>, <code>Stop e commit parziale</code>;</p><p>  - a fine import crea una notifica di riepilogo che porta alla route.</p><h2>Config metadata</h2><p>Impostazioni chiave in <code>md_props_bag</code> e metadati colonna.</p><p>Snippet 3:</p><h2>md_props_bag: toolbar</h2><p>Flag opt-in che nascondono blocchi della toolbar della list-grid (<code>caption-bar</code>). Tutti sotto <code>md_props_bag.toolbar.*</code> (parsato in runtime come <code>tableMetadata.extraProps.toolbar</code>).</p><p>Snippet 4:</p><ul><li><code>hideManageState</code> (boolean, default <code>false</code>): nasconde nella <strong>caption-right</strong> il bottone &quot;Gestione stato&quot; (icona bookmark) + la <code>&lt;select&gt;</code> degli stati salvati. Utile per route hardcoded / demo dove il saved-state feature (persistenza per <code>user_id</code> + route via <code>MetaService</code>) non ha senso — es. Pattern 3 puro OData senza route metadata registrata.</li><li><code>hideBatchActions</code> (boolean, default <code>false</code>): nasconde nella <strong>caption-left</strong> i pulsanti &quot;Salva modifiche&quot; (<code>pi-save</code>) + &quot;Annulla modifiche&quot; (<code>pi-times</code>) + l&#39;indicatore conteggio changes (<code>grid-changes-indicator</code>, badge pencil + count). Generati dal framework quando <code>md_inline_cell_editing</code> + <code>md_batch_save</code> sono attivi. Pensato per <strong>nested grid in parametric-dialog</strong>: il save/cancel del padre persiste master + righe in un colpo via batch save framework, e i pulsanti duplicati sulla nested grid confondono l&#39;UX.</li></ul><p>Esempio nested rows in custom edit-form (runtime patch):</p><p>Snippet 5:</p><p>Tipo TS in <a href=\"../api/wuic-framework-lib.metadatitabella.html\">`metadati_tabella.ts`</a> (proprieta <code>extraProps.toolbar</code>). I flag NON disabilitano la logica <code>md_batch_save</code> sottostante (changes restano tracciate); rimuovono solo l&#39;UI toolbar — il save effettivo passa dal flusso del padre.</p><h2>md_props_bag: archetypes.list</h2><p>Il componente legge <code>md_props_bag.archetypes.list</code>.</p><p>Snippet 6:</p><ul><li><code>proportionalColwidth</code>:</li><li>tipo: boolean (con parser tollerante)</li><li>valori accettati: <code>true</code>, <code>false</code>, <code>1</code>, <code>0</code>, <code>&quot;true&quot;</code>, <code>&quot;false&quot;</code>, <code>&quot;1&quot;</code>, <code>&quot;0&quot;</code></li><li>default runtime: <code>true</code> quando assente o vuoto</li><li>effetto: distribuisce le larghezze colonna in percentuale (anziche px) quando non ci sono larghezze utente persistite.</li></ul><ul><li><code>virtualize</code>:</li><li>tipo: <code>boolean</code> oppure <code>object</code></li><li>valori accettati:</li><li><code>true</code>/<code>false</code>, <code>1</code>/<code>0</code>, <code>&quot;true&quot;</code>/<code>&quot;false&quot;</code>, <code>&quot;1&quot;</code>/<code>&quot;0&quot;</code></li><li>object con <code>enabled</code> (opzionale) e <code>itemSize</code> (opzionale)</li><li>default runtime: disabilitato (<code>false</code>) quando assente</li><li><code>enabled</code>:</li><li>default: <code>true</code> se il nodo <code>virtualize</code> e object senza <code>enabled</code>, altrimenti parser tollerante</li><li>effetto: abilita <code>virtualScroll</code> su <code>p-table</code></li><li><code>itemSize</code>:</li><li>default: <code>44</code></li><li>effetto: imposta <code>virtualScrollItemSize</code> (altezza riga virtuale in px)</li></ul><ul><li><code>advancedFilter</code>:</li><li>tipo: boolean (con parser tollerante)</li><li>default runtime: <code>false</code></li><li>effetto:</li><li>quando <code>true</code>, la griglia nasconde le icone filtro colonna (<code>p-columnFilter</code>) e usa la <code>wuic-filter-bar</code> sopra la tabella (a livello <code>data-repeater</code>/<code>bounded-repeater</code>) per applicare i filtri.</li></ul><p>Nota operativa:</p><ul><li>il suggest <code>md_props_bag</code> nel metadata editor espone anche il nodo checkabile <code>archetypes.list.advancedFilter</code>.</li></ul><h2>Paging: md_pagesize e md_page_size_choice</h2><p>La griglia usa <code>md_pagesize</code> come dimensione pagina di default e <code>md_page_size_choice</code> come elenco valori selezionabili nel paginator.</p><p>Regole runtime:</p><ul><li>se <code>md_pagesize</code> e maggiore del valore massimo presente in <code>md_page_size_choice</code>, il framework aggiunge automaticamente <code>md_pagesize</code> alla lista opzioni;</li><li>la lista viene normalizzata (numeri validi, deduplica, ordinamento crescente).</li></ul><p>Esempio:</p><ul><li><code>md_pagesize = 200</code></li><li><code>md_page_size_choice = &quot;10,25,50,100&quot;</code></li><li>risultato runtime: <code>10,25,50,100,200</code></li></ul><h2>Forzatura virtualizzazione su page size alto</h2><p>Quando l&#39;utente seleziona nel paginator un valore <code>pageSize &gt;= 1000</code>:</p><ul><li>la virtualizzazione viene forzata automaticamente anche se <code>md_props_bag.archetypes.list.virtualize</code> e assente o disabilitato;</li><li><code>virtualScrollItemSize</code> viene forzato al valore predefinito <code>44</code>.</li></ul><p>Questo comportamento protegge la resa della tabella su pagine molto grandi.</p><h2>Eventi e subscriptions (host)</h2><p><code>wuic-list-grid</code> espone eventi runtime utili per intercettare ciclo render e callback p-table lato progetto host.</p><p>Eventi disponibili:</p><ul><li><code>onAfterRender</code>: emesso a fine binding dati della griglia (<code>rows</code>, <code>totalRecords</code>, <code>metaInfo</code>, <code>datasource</code>).</li><li><code>onBeforeRowRender</code>: emesso prima del rendering logico della singola riga; supporta cancel tramite <code>event.cancelRender()</code>.</li><li><code>onAfterRowRender</code>: emesso dopo il rendering logico della singola riga.</li><li><code>onPaging</code>: emesso sugli eventi paging (<code>p-table onPage</code>).</li><li><code>onSorting</code>: emesso sugli eventi sorting (<code>p-table onSort</code>).</li><li><code>onFiltering</code>: emesso sugli eventi filtering (<code>p-table onFilter</code>).</li><li><code>onPTableSelectionChange</code>: emesso su cambio selezione righe.</li><li><code>onPTableRowExpand</code>: emesso su expand riga.</li><li><code>onPTableRowCollapse</code>: emesso su collapse riga.</li><li><code>onPTableColumnResize</code>: emesso su resize colonna.</li><li><code>onPTableColumnReorder</code>: emesso su reorder colonne.</li></ul><h3>Esempio 1: binding diretto nel template</h3><p>Snippet 7:</p><h3>Esempio 2: subscribe via ViewChild</h3><p>Snippet 8:</p><h2><code>rowCustomSelect</code> — signature reale (gotcha)</h2><p><code>&lt;wuic-list-grid&gt;</code> accetta un input <code>[rowCustomSelect]</code> per intercettare la selezione di una riga (apertura dialog &quot;scegli documento&quot;, master-detail, ecc.). La firma TypeScript dichiarata in <a href=\"../../src/lib/component/list-grid/list-grid.component.ts#L140\">list-grid.component.ts:140</a> è:</p><p>Snippet 9:</p><p><strong>Pero&#39; a runtime la callback viene invocata con argomenti invertiti</strong> — il framework chiama <code>rowCustomSelect($event, rowData, dt)</code> (vedi <a href=\"../../src/lib/component/dynamic-template/dynamic-template.component.ts#L447\">dynamic-template.component.ts:447</a> e <a href=\"../../src/lib/component/dynamic-template/dynamic-card-template.component.ts#L205\">dynamic-card-template.component.ts:205</a>).</p><p>Sintomo se sbagli ordine: <code>rowData?.id</code> e&#39; undefined → guard precoce nel handler → la callback ritorna senza side-effect e la dialog/azione non parte. Nessun errore in console.</p><p>Forma corretta (allineata all&#39;invocazione runtime):</p><p>Snippet 10:</p><p>Esempio integrato nel template:</p><p>Snippet 11:</p><p>&gt; Note: i test in <code>designer.component.spec.ts</code> (es. riga 512) chiamano la callback con <code>({currentTarget: rowCell}, {id: 42}, null)</code> confermando l&#39;ordine <code>($event, rowData, dt)</code>. Se in futuro il framework dovesse uniformare la signature dichiarata, si aggiornera&#39; anche questa pagina.</p>",
+                    "html": "<h1>List Grid</h1><p>Componente principale per liste tabellari con filtri, sorting, paging server-side e azioni riga.</p><h2>Use cases</h2><ul><li>CRUD tabellari enterprise.</li><li>Report operativi con filtri multi-colonna.</li><li>Dataset molto grandi con <code>cursorMode</code>.</li></ul><h2>Cosa mostra la toolbar di default</h2><p>Aprendo una route appena scaffoldata, sopra la griglia c&#39;e&#39; la caption-bar. A sinistra:</p><table><thead><tr><th>Pulsante</th><th>Quando compare</th></tr></thead><tbody><tr><td><strong>Aggiorna</strong></td><td>sempre, salvo <code>md_hide_refresh</code></td></tr><tr><td><strong>Aggiungi</strong></td><td>con <code>md_insertable</code></td></tr><tr><td><strong>Azioni</strong></td><td>se la tabella ha custom action</td></tr><tr><td>Import / Export</td><td>sempre; il ramo import solo con <code>md_importable</code></td></tr><tr><td><strong>Report</strong></td><td>se alla route e&#39; associato almeno un report</td></tr><tr><td><strong>Salva modifiche</strong> / <strong>Annulla modifiche</strong></td><td>solo con <code>md_inline_cell_edit</code> <strong>e</strong> <code>md_batch_save</code></td></tr></tbody></table><p>A destra: <strong>Gestione stato</strong> (preceduto dalla tendina degli stati salvati, se ce ne sono),</p><p><strong>Pulisci filtri</strong> quando i filtri stanno sulle colonne, e <strong>Performance</strong> se l&#39;inspector e&#39;</p><p>abilitato sulla route.</p><p>&gt; Le didascalie citate piu&#39; sotto in questa pagina <strong>non si trovano su questo schermo</strong>, e non</p><p>&gt; e&#39; un difetto: quelle di export/import (<em>Continua in background</em>, <em>Annulla task</em>, *Interrompi</p><p>&gt; e scarica parziale<em>, </em>Annulla import (rollback)<em>, </em>Stop e commit parziale*) vivono nella</p><p>&gt; dialog di avanzamento, che esiste solo mentre un export o un import e&#39; in corso; *Salva</p><p>&gt; modifiche<em> e </em>Annulla modifiche* compaiono solo con i due flag qui sopra. Appartengono a</p><p>&gt; momenti diversi dalla prima apertura della lista.</p><h2>Screenshot reference (manuale utente)</h2><ul><li><code>manual__grid__01.png</code>: modalita <code>inline cell edit</code> in list-grid.</li><li><code>manual__grid__02.png</code>: modalita <code>inline edit</code> (row-level) in list-grid.</li></ul><h2>Metadati inline editing</h2><p>Configurazione nel <code>md_props_bag</code> della tabella metadata:</p><ul><li><code>md_inline_edit</code></li></ul><p>  - abilita l&#39;editing inline della riga in list-grid (celle editabili in contesto riga, senza apertura popup).</p><p>  - utile quando vuoi mantenere la UX di tabella con editing rapido per record.</p><ul><li><code>md_inline_cell_edit</code></li></ul><p>  - abilita l&#39;editing inline &quot;cell-by-cell&quot; (focus sulla singola cella).</p><p>  - nota: nelle configurazioni legacy puo comparire come <code>md_inline_cell_editing</code>; il comportamento runtime e lo stesso.</p><p>  - <strong>promozione runtime</strong>: quando <code>md_inline_cell_edit</code> e <code>true</code>, il componente forza</p><p>    a runtime anche <code>md_inline_edit = true</code> indipendentemente dal valore in DB.</p><p>    Entrambe le UX hanno bisogno della action column visibile, quindi sono mutualmente</p><p>    non-esclusive a livello di rendering.</p><ul><li><code>md_batch_save</code></li></ul><p>  - abilita il salvataggio batch delle modifiche pendenti (<code>Save changes</code> / <code>Cancel changes</code>).</p><p>  - se usato insieme a inline-cell, le modifiche restano pending fino al salvataggio esplicito.</p><p>  - <strong>prerequisito</strong>: <code>md_batch_save</code> ha effetto <strong>solo</strong> se <code>md_inline_cell_edit</code> e <code>true</code>.</p><p>    Con <code>md_inline_cell_edit:false</code> il flag viene ignorato a runtime e i bottoni</p><p>    &quot;Salva modifiche / Annulla modifiche&quot; non vengono renderizzati.</p><h3>Combinazioni valide</h3><table><thead><tr><th><code>md_inline_edit</code></th><th><code>md_inline_cell_edit</code></th><th><code>md_batch_save</code></th><th>Risultato runtime</th></tr></thead><tbody><tr><td><code>true</code></td><td><code>false</code></td><td>qualsiasi</td><td>Row-level inline edit con pencil. <code>md_batch_save</code> ignorato.</td></tr><tr><td><code>false</code></td><td><code>true</code></td><td><code>false</code></td><td>Cell-by-cell autosave on blur. <code>md_inline_edit</code> forzato a <code>true</code> a runtime.</td></tr><tr><td><code>false</code></td><td><code>true</code></td><td><code>true</code></td><td>Cell-by-cell con buffer pending + toolbar <code>Salva / Annulla modifiche</code>.</td></tr><tr><td><code>false</code></td><td><code>false</code></td><td>qualsiasi</td><td>Nessun inline editing. <code>md_batch_save</code> ignorato.</td></tr></tbody></table><p>Esempio row-level inline edit:</p><p>Snippet 1:</p><p>Esempio cell-by-cell con batch save:</p><p>Snippet 2:</p><h2>Toolbar export/import</h2><ul><li>Export XLS:</li></ul><p>  - mostra dialog di progress con percentuale realtime;</p><p>  - azioni: <code>Continua in background</code>, <code>Annulla task</code>, <code>Interrompi e scarica parziale</code>;</p><p>  - in background crea una notifica con progress; click riapre il dialog.</p><ul><li>Import XLS/XLSX (se <code>md_importable = true</code>):</li></ul><p>  - dialog di progress dopo la conferma;</p><p>  - azioni: <code>Continua in background</code>, <code>Annulla import (rollback)</code>, <code>Stop e commit parziale</code>;</p><p>  - a fine import crea una notifica di riepilogo che porta alla route.</p><h2>Config metadata</h2><p>Impostazioni chiave in <code>md_props_bag</code> e metadati colonna.</p><p>Snippet 3:</p><h2>md_props_bag: toolbar</h2><p>Flag opt-in che nascondono blocchi della toolbar della list-grid (<code>caption-bar</code>). Tutti sotto <code>md_props_bag.toolbar.*</code> (parsato in runtime come <code>tableMetadata.extraProps.toolbar</code>).</p><p>Snippet 4:</p><ul><li><code>hideManageState</code> (boolean, default <code>false</code>): nasconde nella <strong>caption-right</strong> il bottone &quot;Gestione stato&quot; (icona bookmark) + la <code>&lt;select&gt;</code> degli stati salvati. Utile per route hardcoded / demo dove il saved-state feature (persistenza per <code>user_id</code> + route via <code>MetaService</code>) non ha senso — es. Pattern 3 puro OData senza route metadata registrata.</li><li><code>hideBatchActions</code> (boolean, default <code>false</code>): nasconde nella <strong>caption-left</strong> i pulsanti &quot;Salva modifiche&quot; (<code>pi-save</code>) + &quot;Annulla modifiche&quot; (<code>pi-times</code>) + l&#39;indicatore conteggio changes (<code>grid-changes-indicator</code>, badge pencil + count). Generati dal framework quando <code>md_inline_cell_editing</code> + <code>md_batch_save</code> sono attivi. Pensato per <strong>nested grid in parametric-dialog</strong>: il save/cancel del padre persiste master + righe in un colpo via batch save framework, e i pulsanti duplicati sulla nested grid confondono l&#39;UX.</li></ul><p>Esempio nested rows in custom edit-form (runtime patch):</p><p>Snippet 5:</p><p>Tipo TS in <a href=\"../api/wuic-framework-lib.metadatitabella.html\">`metadati_tabella.ts`</a> (proprieta <code>extraProps.toolbar</code>). I flag NON disabilitano la logica <code>md_batch_save</code> sottostante (changes restano tracciate); rimuovono solo l&#39;UI toolbar — il save effettivo passa dal flusso del padre.</p><h2>md_props_bag: archetypes.list</h2><p>Il componente legge <code>md_props_bag.archetypes.list</code>.</p><p>Snippet 6:</p><ul><li><code>proportionalColwidth</code>:</li><li>tipo: boolean (con parser tollerante)</li><li>valori accettati: <code>true</code>, <code>false</code>, <code>1</code>, <code>0</code>, <code>&quot;true&quot;</code>, <code>&quot;false&quot;</code>, <code>&quot;1&quot;</code>, <code>&quot;0&quot;</code></li><li>default runtime: <code>true</code> quando assente o vuoto</li><li>effetto: distribuisce le larghezze colonna in percentuale (anziche px) quando non ci sono larghezze utente persistite.</li></ul><ul><li><code>virtualize</code>:</li><li>tipo: <code>boolean</code> oppure <code>object</code></li><li>valori accettati:</li><li><code>true</code>/<code>false</code>, <code>1</code>/<code>0</code>, <code>&quot;true&quot;</code>/<code>&quot;false&quot;</code>, <code>&quot;1&quot;</code>/<code>&quot;0&quot;</code></li><li>object con <code>enabled</code> (opzionale) e <code>itemSize</code> (opzionale)</li><li>default runtime: disabilitato (<code>false</code>) quando assente</li><li><code>enabled</code>:</li><li>default: <code>true</code> se il nodo <code>virtualize</code> e object senza <code>enabled</code>, altrimenti parser tollerante</li><li>effetto: abilita <code>virtualScroll</code> su <code>p-table</code></li><li><code>itemSize</code>:</li><li>default: <code>44</code></li><li>effetto: imposta <code>virtualScrollItemSize</code> (altezza riga virtuale in px)</li></ul><ul><li><code>advancedFilter</code>:</li><li>tipo: boolean (con parser tollerante)</li><li>default runtime: <code>false</code></li><li>effetto:</li><li>quando <code>true</code>, la griglia nasconde le icone filtro colonna (<code>p-columnFilter</code>) e usa la <code>wuic-filter-bar</code> sopra la tabella (a livello <code>data-repeater</code>/<code>bounded-repeater</code>) per applicare i filtri.</li></ul><p>Nota operativa:</p><ul><li>il suggest <code>md_props_bag</code> nel metadata editor espone anche il nodo checkabile <code>archetypes.list.advancedFilter</code>.</li></ul><h2>Paging: md_pagesize e md_page_size_choice</h2><p>La griglia usa <code>md_pagesize</code> come dimensione pagina di default e <code>md_page_size_choice</code> come elenco valori selezionabili nel paginator.</p><p>Regole runtime:</p><ul><li>se <code>md_pagesize</code> e maggiore del valore massimo presente in <code>md_page_size_choice</code>, il framework aggiunge automaticamente <code>md_pagesize</code> alla lista opzioni;</li><li>la lista viene normalizzata (numeri validi, deduplica, ordinamento crescente).</li></ul><p>Esempio:</p><ul><li><code>md_pagesize = 200</code></li><li><code>md_page_size_choice = &quot;10,25,50,100&quot;</code></li><li>risultato runtime: <code>10,25,50,100,200</code></li></ul><h2>Forzatura virtualizzazione su page size alto</h2><p>Quando l&#39;utente seleziona nel paginator un valore <code>pageSize &gt;= 1000</code>:</p><ul><li>la virtualizzazione viene forzata automaticamente anche se <code>md_props_bag.archetypes.list.virtualize</code> e assente o disabilitato;</li><li><code>virtualScrollItemSize</code> viene forzato al valore predefinito <code>44</code>.</li></ul><p>Questo comportamento protegge la resa della tabella su pagine molto grandi.</p><h2>Eventi e subscriptions (host)</h2><p><code>wuic-list-grid</code> espone eventi runtime utili per intercettare ciclo render e callback p-table lato progetto host.</p><p>Eventi disponibili:</p><ul><li><code>onAfterRender</code>: emesso a fine binding dati della griglia (<code>rows</code>, <code>totalRecords</code>, <code>metaInfo</code>, <code>datasource</code>).</li><li><code>onBeforeRowRender</code>: emesso prima del rendering logico della singola riga; supporta cancel tramite <code>event.cancelRender()</code>.</li><li><code>onAfterRowRender</code>: emesso dopo il rendering logico della singola riga.</li><li><code>onPaging</code>: emesso sugli eventi paging (<code>p-table onPage</code>).</li><li><code>onSorting</code>: emesso sugli eventi sorting (<code>p-table onSort</code>).</li><li><code>onFiltering</code>: emesso sugli eventi filtering (<code>p-table onFilter</code>).</li><li><code>onPTableSelectionChange</code>: emesso su cambio selezione righe.</li><li><code>onPTableRowExpand</code>: emesso su expand riga.</li><li><code>onPTableRowCollapse</code>: emesso su collapse riga.</li><li><code>onPTableColumnResize</code>: emesso su resize colonna.</li><li><code>onPTableColumnReorder</code>: emesso su reorder colonne.</li></ul><h3>Esempio 1: binding diretto nel template</h3><p>Snippet 7:</p><h3>Esempio 2: subscribe via ViewChild</h3><p>Snippet 8:</p><h2><code>rowCustomSelect</code> — signature reale (gotcha)</h2><p><code>&lt;wuic-list-grid&gt;</code> accetta un input <code>[rowCustomSelect]</code> per intercettare la selezione di una riga (apertura dialog &quot;scegli documento&quot;, master-detail, ecc.). La firma TypeScript dichiarata in <a href=\"../../src/lib/component/list-grid/list-grid.component.ts#L140\">list-grid.component.ts:140</a> è:</p><p>Snippet 9:</p><p><strong>Pero&#39; a runtime la callback viene invocata con argomenti invertiti</strong> — il framework chiama <code>rowCustomSelect($event, rowData, dt)</code> (vedi <a href=\"../../src/lib/component/dynamic-template/dynamic-template.component.ts#L447\">dynamic-template.component.ts:447</a> e <a href=\"../../src/lib/component/dynamic-template/dynamic-card-template.component.ts#L205\">dynamic-card-template.component.ts:205</a>).</p><p>Sintomo se sbagli ordine: <code>rowData?.id</code> e&#39; undefined → guard precoce nel handler → la callback ritorna senza side-effect e la dialog/azione non parte. Nessun errore in console.</p><p>Forma corretta (allineata all&#39;invocazione runtime):</p><p>Snippet 10:</p><p>Esempio integrato nel template:</p><p>Snippet 11:</p><p>&gt; Note: i test in <code>designer.component.spec.ts</code> (es. riga 512) chiamano la callback con <code>({currentTarget: rowCell}, {id: 42}, null)</code> confermando l&#39;ordine <code>($event, rowData, dt)</code>. Se in futuro il framework dovesse uniformare la signature dichiarata, si aggiornera&#39; anche questa pagina.</p>",
                     "codeSamples": [
                         {
                             "id": "code_1",
@@ -3740,7 +3758,7 @@ const frameworkDocsContent = {
                 {
                     "id": "overview",
                     "title": "Overview",
-                    "html": "<h1>Designer</h1><p>Editor visuale per dashboard metadata-driven su route <code>#/cities/dashboard</code>.</p><h2>Scope</h2><ul><li>Composizione board via drag-and-drop di nodi e blocchi UI.</li><li>Layout e styling pilotati da <code>boardcontent</code> e metadata tabella/colonna.</li><li>Editing property panel senza hardcode nei componenti runtime.</li></ul><h2>Palette Designer</h2><ul><li><code>Datasource</code>: sorgente dati metadata (<code>route</code>, filtri, sort, paging).</li><li><code>DataRepeater</code>: visualizzazione lista/card collegata a datasource.</li><li><code>Dynamic Template</code>: rendering template dinamico con input metadata-driven.</li><li><code>Action/Button</code>: azioni utente agganciate a record e callback.</li><li><code>Container/Layout</code>: blocchi strutturali per colonne, righe e wrapper.</li></ul><h2>Feature principali</h2><ul><li>Drag-and-drop nodi sulla canvas con persistenza nel <code>boardcontent</code>.</li><li>Property panel contestuale con input coerenti ai componenti selezionati.</li><li>Binding tra nodi (<code>datasource -&gt; repeater/template</code>) con validazione minima.</li><li>Preview runtime integrata e riallineamento layout.</li><li>Gestione pending changes con guard prima dell&#39;uscita.</li></ul><h2>Context menu sugli elementi</h2><p>Right-click su un elemento del canvas, una voce del breadcrumb in basso o un nodo dell&#39;albero gerarchia mostra un context menu con tre voci:</p><ul><li><strong>Modifica proprietà</strong> (pi-cog) — seleziona l&#39;elemento come &quot;current tool&quot; e ne mostra il property panel a destra; equivalente al click nell&#39;albero. Utile per editare proprietà di elementi annidati senza dover cercare la voce nella gerarchia.</li><li><strong>Rinomina</strong> (solo breadcrumb in basso) — apre dialog per rinominare il <code>displayName</code>.</li><li><strong>Rimuovi</strong> — elimina l&#39;elemento dalla board.</li></ul><h2>Flusso operativo consigliato</h2><ul><li>Aprire route dashboard target.</li><li>Inserire/collegare nodi dalla palette.</li><li>Configurare <code>inputs</code> essenziali (es. <code>route</code>, <code>action</code>, <code>datasource</code>).</li><li>Salvare e validare il risultato in runtime.</li></ul><h2>Note operative</h2><ul><li>Per fix specifici dashboard, privilegiare patch del <code>boardcontent</code> invece di modifiche globali.</li><li>Evitare proprietà duplicate tra <code>inputs</code> e stile inline non coerente.</li><li>Verificare sempre che i datasource abbiano <code>inputs.route</code> valorizzata.</li></ul>",
+                    "html": "<h1>Designer</h1><p>Editor visuale per dashboard metadata-driven su route <code>#/cities/dashboard</code>.</p><h2>Scope</h2><ul><li>Composizione board via drag-and-drop di nodi e blocchi UI.</li><li>Layout e styling pilotati da <code>boardcontent</code> e metadata tabella/colonna.</li><li>Editing property panel senza hardcode nei componenti runtime.</li></ul><h2>Palette Designer</h2><p>La palette e&#39; divisa in tre gruppi. I nomi qui sotto sono quelli che leggi nella palette,</p><p>maiuscoli come li scrive il designer.</p><p><strong>HTML</strong> — i mattoni di markup:</p><table><thead><tr><th>Tool</th><th>A cosa serve</th></tr></thead><tbody><tr><td><code>TABLE</code></td><td>griglia di celle. <code>TR</code> e <code>TD</code> esistono come tool ma non si trascinano: li crea la tabella</td></tr><tr><td><code>DIV</code></td><td>contenitore libero, il blocco strutturale piu&#39; usato</td></tr><tr><td><code>SPAN</code>, <code>LABEL</code>, <code>Hx</code></td><td>testo databound; <code>Hx</code> sceglie il livello da h1 a h6</td></tr><tr><td><code>ANCHOR</code>, <code>IMG</code>, <code>IMAGE</code>, <code>IFRAME</code></td><td>link, immagini, contenuto esterno</td></tr><tr><td><code>UL</code></td><td>elenco</td></tr><tr><td><code>BUTTON</code></td><td>pulsante con callback</td></tr><tr><td><code>INPUT</code>, <code>TEXTAREA</code>, <code>CHECKBOX</code>, <code>SELECT</code>, <code>MULTISELECT</code>, <code>DATE</code></td><td>campi di input</td></tr><tr><td><code>KPI</code></td><td>valore singolo in evidenza</td></tr><tr><td><code>SEPARATOR</code>, <code>HR</code></td><td>separatori</td></tr></tbody></table><p><strong>DATA</strong> — i nodi collegati al backend:</p><table><thead><tr><th>Tool</th><th>A cosa serve</th></tr></thead><tbody><tr><td><code>DATASOURCE</code></td><td>sorgente dati metadata (<code>route</code>, filtri, sort, paging)</td></tr><tr><td><code>DATAREPEATER</code></td><td>visualizzazione lista/card collegata a un datasource</td></tr><tr><td><code>FILTERBAR</code></td><td>barra filtri sopra il repeater</td></tr><tr><td><code>PAGER</code></td><td>paginatore</td></tr></tbody></table><p><strong>CONTAINER</strong> — i layout:</p><table><thead><tr><th>Tool</th><th>A cosa serve</th></tr></thead><tbody><tr><td><code>TABVIEW</code> + <code>TABPANEL</code></td><td>schede</td></tr><tr><td><code>SPLITTER</code> + <code>SPLITTER-AREA</code></td><td>pannelli ridimensionabili</td></tr><tr><td><code>ACCORDION</code> + <code>ACCORDION-AREA</code></td><td>sezioni a fisarmonica</td></tr></tbody></table><p>Due nomi che si cercano invano: <strong>non esiste un tool &quot;Dynamic Template&quot;</strong> — il template dinamico</p><p>e&#39; cio&#39; che il <code>DATAREPEATER</code> renderizza, si configura dalle sue proprieta&#39; e non si trascina; e</p><p><strong>&quot;Container&quot; / &quot;Layout&quot; sono il nome del gruppo</strong>, non voci selezionabili.</p><p>A questi si aggiungono i tool custom registrati dal progetto host</p><p>(<code>MetadataProviderService.customDesignerTools</code>), che compaiono in coda con il gruppo che</p><p>dichiarano.</p><h2>Feature principali</h2><ul><li>Drag-and-drop nodi sulla canvas con persistenza nel <code>boardcontent</code>.</li><li>Property panel contestuale con input coerenti ai componenti selezionati.</li><li>Binding tra nodi (<code>datasource -&gt; repeater/template</code>) con validazione minima.</li><li>Preview runtime integrata e riallineamento layout.</li><li>Gestione pending changes con guard prima dell&#39;uscita.</li></ul><h2>Context menu sugli elementi</h2><p>Right-click su un elemento del canvas, una voce del breadcrumb in basso o un nodo dell&#39;albero gerarchia mostra un context menu con tre voci:</p><ul><li><strong>Modifica proprietà</strong> (pi-cog) — seleziona l&#39;elemento come &quot;current tool&quot; e ne mostra il property panel a destra; equivalente al click nell&#39;albero. Utile per editare proprietà di elementi annidati senza dover cercare la voce nella gerarchia.</li><li><strong>Rinomina</strong> (solo breadcrumb in basso) — apre dialog per rinominare il <code>displayName</code>.</li><li><strong>Rimuovi</strong> — elimina l&#39;elemento dalla board.</li></ul><h2>Flusso operativo consigliato</h2><ul><li>Aprire route dashboard target.</li><li>Inserire/collegare nodi dalla palette.</li><li>Configurare <code>inputs</code> essenziali (es. <code>route</code>, <code>action</code>, <code>datasource</code>).</li><li>Salvare e validare il risultato in runtime.</li></ul><h2>Note operative</h2><ul><li>Per fix specifici dashboard, privilegiare patch del <code>boardcontent</code> invece di modifiche globali.</li><li>Evitare proprietà duplicate tra <code>inputs</code> e stile inline non coerente.</li><li>Verificare sempre che i datasource abbiano <code>inputs.route</code> valorizzata.</li></ul>",
                     "codeSamples": []
                 }
             ],
@@ -7855,13 +7873,17 @@ const frameworkDocsContent = {
                 {
                     "id": "sec_4",
                     "title": "Quick Start — First Component"
+                },
+                {
+                    "id": "sec_5",
+                    "title": "The first lists show 20 records: that is Trial mode"
                 }
             ],
             "sections": [
                 {
                     "id": "overview",
                     "title": "Overview",
-                    "html": "<h1>Framework Overview</h1><p>WUIC Framework is a metadata-driven platform for building business interfaces quickly and consistently.</p><h2>What It Includes</h2><ul><li>DataSource and DataRepeater for orchestrating data and rendering.</li><li>Visual archetypes (list, map, scheduler, chart, carousel).</li><li>Runtime designer for dashboards and dynamic templates.</li><li>Workflow designer/runner for operational processes.</li><li>RAG Chatbot for querying the codebase in natural language.</li><li>Multi-DBMS: SQL Server, MySQL, PostgreSQL and Oracle via drop-in providers (<code>dbms</code>: <code>mssql</code> | <code>mysql</code> | <code>postgresql</code> | <code>oracle</code>).</li></ul><h2>First Steps — Starting the Dev Environment</h2><p>The WUIC stack is composed of several services. Start them in the order below.</p><h3>Prerequisites</h3><table><thead><tr><th>What</th><th>Check</th><th>Notes</th></tr></thead><tbody><tr><td>.NET 10 SDK</td><td><code>dotnet --version</code></td><td>Hosting Bundle for IIS in production</td></tr><tr><td>Node.js 22 LTS</td><td><code>node --version</code></td><td>22 is the version the package is tested with; on npm 10.9.x it installs thanks to the bundled <code>package-lock.json</code></td></tr><tr><td>PowerShell 5.1+</td><td><code>$PSVersionTable.PSVersion</code></td><td>The Windows PowerShell that ships with Windows is enough: <code>rename-project.ps1</code> and the <code>llm-workspace/</code> scripts run on 5.1 too. PowerShell 7 is recommended, not required</td></tr><tr><td>SQL Server 2019+</td><td><code>sqlcmd -S localhost\\sqlexpress -E -C -Q &quot;SELECT 1&quot;</code></td><td>If missing, <strong>the one-liner installs it for you</strong> (SQL Server Express, or the engine chosen with <code>-Dbms</code>); not on Windows Server, see the box below. 2019 is enough for the packages without <code>.bak</code>; the <code>.bak</code> tutorial is a SQL Server 2022 backup and needs <strong>2022 or newer</strong></td></tr><tr><td>Linux (<code>install.sh</code> installer)</td><td><code>lsb_release -ds</code></td><td><strong>Ubuntu 22.04 or 24.04 LTS</strong> (24.04 recommended): they are the only Ubuntu releases Microsoft supports for SQL Server, and <strong>26.04 is not supported</strong> (<a href=\"https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-setup?view=sql-server-ver17\" target=\"_blank\" rel=\"noopener noreferrer\">Supported platforms</a>). Same recommendation with MySQL, PostgreSQL and Oracle, because the installer is tested on those releases</td></tr><tr><td>NVIDIA GPU (CUDA 12.x + cuDNN 9)</td><td><code>nvidia-smi</code></td><td>Optional: speeds up the RAG Chatbot (runs on CPU without it)</td></tr></tbody></table><p>&gt; <strong>On Windows Server the database must be installed first.</strong> The one-liner pulls missing</p><p>&gt; components through <code>winget</code>, which is not present on Windows Server: without an instance</p><p>&gt; already reachable the installation stops with `No SQL Server instance reachable and winget is</p><p>&gt; missing`. Install the engine before running the line - SQL Server must be <strong>2019 or newer</strong></p><p>&gt; (Express is enough; <strong>2022 or newer</strong> for the <code>.bak</code> tutorial), and a 2017 instance is not</p><p>&gt; accepted. If the instance is not the default one, pass it with</p><p>&gt; <code>-SqlServer &#39;localhost\\INSTANCENAME&#39;</code>. This applies to every engine, not just SQL Server.</p><h3>1. Download the project template</h3><p>On Windows one PowerShell line does all of it: it downloads the package, checks the .NET SDK 10</p><p>and Node.js 22 (installing what is missing), runs <code>dotnet restore</code> and <code>npm install</code>,</p><p>and installs the WUIC Assistant extension in VS Code.</p><p>Snippet 1:</p><p>Useful options on the same line: <code>-Dbms mysql</code> (or <code>postgres</code>, <code>oracle</code>) for an engine other</p><p>than SQL Server — the installer installs and configures it for you — and <code>-WithTutorial</code> to</p><p>download the sample database as well.</p><p>When it is done, the last screen is already your to-do list:</p><p>Snippet 2:</p><p>The connection string is ready to use: at first start the wizard asks for nothing else. With</p><p><code>-Dbms mysql</code> or <code>-Dbms postgres</code> that line changes accordingly and carries user and password</p><p>inside it, because the superuser password is <strong>generated by the installer</strong>; the same password</p><p>is saved in <code>wuic-secrets.json</code>, next to the installation, and that is the only place where it</p><p>stays written.</p><p>The manual path still works, on any operating system:</p><p>Start from the <code>WuicTest-src-*.zip</code> package (link in the <strong>Download</strong> section of the site).</p><p>Extract it to a working folder, e.g. <code>C:\\dev\\WuicTest</code> (files go directly at the root —</p><p>NOT inside a <code>src/</code> subfolder). The package contains:</p><ul><li><code>WuicTest.csproj</code> → host project with <code>&lt;PackageReference Include=&quot;WuicCore&quot; Version=&quot;...&quot; /&gt;</code></li><li><code>wwwroot/</code> → Angular app whose <code>package.json</code> references <code>wuic-framework-lib</code> from the npm registry</li><li><code>appsettings.json</code> preconfigured in <code>firstRun = &quot;true&quot;</code> mode with <code>__SET_*__</code> placeholders</li><li><code>appsettings-samples/</code> → 6 ready templates (<code>mssql</code>/<code>mysql</code>, firstRun/post-firstRun, <code>Development</code>)</li></ul><p>&gt; <strong>No need to clone the framework repository</strong>: <code>WuicCore</code> ships as a NuGet package from</p><p>&gt; <code>nuget.org</code> and <code>wuic-framework-lib</code> as an npm package from the npm registry. The framework</p><p>&gt; source is only needed if you want to modify it — typically not your case.</p><p>&gt; <strong>npm 10.9.x and packages older than 1.7.1</strong>: those packages carry no <code>package-lock.json</code>, and</p><p>&gt; without a lock npm 10.9.x (the version Node 22 LTS installs) stops with</p><p>&gt; <code>Cannot read properties of null (reading &#39;edgesOut&#39;)</code> while resolving peer dependencies.</p><p>&gt; Download the lock published next to the release —</p><p>&gt; <code>https://wuic-framework.com/downloads/locks/&lt;zip-name&gt;.package-lock.json</code> — drop it in <code>wwwroot/</code></p><p>&gt; and run <code>npm install</code> again. The <code>-Src</code> one-liner does it for you.</p><h3>2. Database</h3><p>You need a reachable engine instance. <strong>With the one-liner there is nothing to do</strong>: it</p><p>installs and configures the instance, and the connection string to paste into the wizard is the</p><p>last thing it prints. On the manual path the instance must already exist.</p><p>Connections in <code>appsettings.json</code>:</p><ul><li><code>MetaDataSQLConnection</code> — metadata DB (menu, tables, columns, boards, users)</li><li><code>DataSQLConnection</code> — application data DB</li></ul><p>If this is the first installation (<code>AppSettings.firstRun = &quot;true&quot;</code> in the template),</p><p>the scaffolding wizard on first startup creates the metadata schema and populates the data DB.</p><p>See the <em>Initial Scaffolding</em> page for the guided flow.</p><h3>3. Backend (.NET)</h3><p>From the root of the extracted folder (e.g. <code>C:\\dev\\WuicTest</code>):</p><p>Snippet 3:</p><p>The backend exposes APIs on <code>http://localhost:5000</code>.</p><h3>4. Frontend (Angular)</h3><p>In a second shell, from the <code>wwwroot/</code> subfolder:</p><p>Snippet 4:</p><p>The frontend is available on <code>http://localhost:4200</code>.</p><p>Default login (post-firstRun): <code>admin</code> / <code>admin</code>.</p><h3>5. RAG Chatbot (optional)</h3><p>The RAG Chatbot (<code>Administration &gt; RAG Chat</code>) runs <strong>inside the .NET backend</strong>:</p><p>the retrieval engine (<code>rag-engine/WuicRagEngine.dll</code>, in-process ONNX Runtime)</p><p>is loaded by the backend when <code>AppSettings.rag-use-dotnet-engine</code> is <code>&quot;true&quot;</code></p><p>(the default in release packages). **No Python, no venv, no separate server</p><p>to start.**</p><p>The <strong>first</strong> time the chatbot is opened (or at the end of the first run) the</p><p>backend downloads by itself the ONNX models (<code>bge-m3</code> + reranker), tokenizer</p><p>and index (~4.5 GB) from <code>rag-engine-models-url</code> (default</p><p><code>https://wuic-framework.com/rag-models</code>) into <code>rag-engine/artifacts/</code>. An</p><p>internet connection is needed only once; the download runs in the background</p><p>(1-5 min) and an in-app notification is sent when it starts and when it ends.</p><p>Meanwhile the component shows the <strong>RAG offline</strong> status and the rest of the</p><p>application works normally.</p><p>Relevant <code>AppSettings</code> keys (all with ready defaults):</p><ul><li><code>rag-use-dotnet-engine</code> = <code>true</code> — enables the .NET engine (<code>false</code> = Python fallback, see below)</li><li><code>rag-engine-device</code> = <code>auto</code> — <code>auto</code> | <code>cuda</code> | <code>cpu</code>: with an NVIDIA GPU (CUDA 12.x + cuDNN 9) ~1 s/query, on CPU ~15-25 s/query</li><li><code>rag-engine-profile</code> = <code>release</code> — <code>release</code> = framework sources as signatures only; <code>internal</code> = full index</li><li><code>rag-engine-models-url</code> — download source on first start</li><li><code>rag-engine-cuda-path</code> = (empty) — folder of the CUDA/cuDNN DLLs when they are not installed system-wide</li></ul><p>For LLM chat set <code>rag-llm-provider</code> + <code>rag-llm-api-key</code> (Claude via Anthropic,</p><p>or a local model via Ollama with <code>rag-llm-base-url</code>). Without a provider only</p><p>the retrieval mode (snippet search) works. Key details on the <em>AppSettings</em></p><p>page.</p><p>&gt; The legacy Python stack (<code>scripts/rag-setup.ps1</code> + <code>rag_server.py</code> on</p><p>&gt; <code>127.0.0.1:8765</code>) is only usable as a fallback with</p><p>&gt; <code>rag-use-dotnet-engine = &quot;false&quot;</code> and is not shipped in release packages.</p><h2>Services Summary</h2><table><thead><tr><th>Service</th><th>Port</th><th>Required</th><th>Quick command</th></tr></thead><tbody><tr><td>SQL Server</td><td>1433</td><td>yes</td><td>(Windows service)</td></tr><tr><td>.NET Backend</td><td>5000</td><td>yes</td><td><code>dotnet watch ... run</code></td></tr><tr><td>Angular Frontend</td><td>4200</td><td>yes</td><td><code>npm run serve:dev</code></td></tr><tr><td>.NET RAG engine (ONNX)</td><td>in-process</td><td>no</td><td>loaded by the backend on the first chat</td></tr></tbody></table><h2>Quick Start — First Component</h2><p>1. Configure the AsmxProxy endpoint.</p><p>2. Define route metadata and columns.</p><p>3. Mount <code>wuic-data-source</code> + <code>wuic-data-repeater</code>.</p><p>Snippet 5:</p>",
+                    "html": "<h1>Framework Overview</h1><p>WUIC Framework is a metadata-driven platform for building business interfaces quickly and consistently.</p><h2>What It Includes</h2><ul><li>DataSource and DataRepeater for orchestrating data and rendering.</li><li>Visual archetypes (list, map, scheduler, chart, carousel).</li><li>Runtime designer for dashboards and dynamic templates.</li><li>Workflow designer/runner for operational processes.</li><li>RAG Chatbot for querying the codebase in natural language.</li><li>Multi-DBMS: SQL Server, MySQL, PostgreSQL and Oracle via drop-in providers (<code>dbms</code>: <code>mssql</code> | <code>mysql</code> | <code>postgresql</code> | <code>oracle</code>).</li></ul><h2>First Steps — Starting the Dev Environment</h2><p>The WUIC stack is composed of several services. Start them in the order below.</p><h3>Prerequisites</h3><table><thead><tr><th>What</th><th>Check</th><th>Notes</th></tr></thead><tbody><tr><td>.NET 10 SDK</td><td><code>dotnet --version</code></td><td>Hosting Bundle for IIS in production</td></tr><tr><td>Node.js 22 LTS</td><td><code>node --version</code></td><td>22 is the version the package is tested with; on npm 10.9.x it installs thanks to the bundled <code>package-lock.json</code></td></tr><tr><td>PowerShell 5.1+</td><td><code>$PSVersionTable.PSVersion</code></td><td>The Windows PowerShell that ships with Windows is enough: <code>rename-project.ps1</code> and the <code>llm-workspace/</code> scripts run on 5.1 too. PowerShell 7 is recommended, not required</td></tr><tr><td>SQL Server 2019+</td><td><code>sqlcmd -S localhost\\sqlexpress -E -C -Q &quot;SELECT 1&quot;</code></td><td>If missing, <strong>the one-liner installs it for you</strong> (SQL Server Express, or the engine chosen with <code>-Dbms</code>); not on Windows Server, see the box below. 2019 is enough for the packages without <code>.bak</code>; the <code>.bak</code> tutorial is a SQL Server 2022 backup and needs <strong>2022 or newer</strong></td></tr><tr><td>Linux (<code>install.sh</code> installer)</td><td><code>lsb_release -ds</code></td><td><strong>Ubuntu 22.04 or 24.04 LTS</strong> (24.04 recommended): they are the only Ubuntu releases Microsoft supports for SQL Server, and <strong>26.04 is not supported</strong> (<a href=\"https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-setup?view=sql-server-ver17\" target=\"_blank\" rel=\"noopener noreferrer\">Supported platforms</a>). Same recommendation with MySQL, PostgreSQL and Oracle, because the installer is tested on those releases</td></tr><tr><td>NVIDIA GPU (CUDA 12.x + cuDNN 9)</td><td><code>nvidia-smi</code></td><td>Optional: speeds up the RAG Chatbot (runs on CPU without it)</td></tr></tbody></table><p>&gt; <strong>On Windows Server the database must be installed first.</strong> The one-liner pulls missing</p><p>&gt; components through <code>winget</code>, which is not present on Windows Server: without an instance</p><p>&gt; already reachable the installation stops with `No SQL Server instance reachable and winget is</p><p>&gt; missing`. Install the engine before running the line - SQL Server must be <strong>2019 or newer</strong></p><p>&gt; (Express is enough; <strong>2022 or newer</strong> for the <code>.bak</code> tutorial), and a 2017 instance is not</p><p>&gt; accepted. If the instance is not the default one, pass it with</p><p>&gt; <code>-SqlServer &#39;localhost\\INSTANCENAME&#39;</code>. This applies to every engine, not just SQL Server.</p><h3>1. Download the project template</h3><p>On Windows one PowerShell line does all of it: it downloads the package, checks the .NET SDK 10</p><p>and Node.js 22 (installing what is missing), runs <code>dotnet restore</code> and <code>npm install</code>,</p><p>and installs the WUIC Assistant extension in VS Code.</p><p>Snippet 1:</p><p>Useful options on the same line: <code>-Dbms mysql</code> (or <code>postgres</code>, <code>oracle</code>) for an engine other</p><p>than SQL Server — the installer installs and configures it for you — and <code>-WithTutorial</code> to</p><p>download the sample database as well.</p><p>When it is done, the last screen is already your to-do list:</p><p>Snippet 2:</p><p>The connection string is ready to use: at first start the wizard asks for nothing else. With</p><p><code>-Dbms mysql</code> or <code>-Dbms postgres</code> that line changes accordingly and carries user and password</p><p>inside it, because the superuser password is <strong>generated by the installer</strong>; the same password</p><p>is saved in <code>wuic-secrets.json</code>, next to the installation, and that is the only place where it</p><p>stays written.</p><p>The manual path still works, on any operating system:</p><p>Start from the <code>WuicTest-src-*.zip</code> package (link in the <strong>Download</strong> section of the site).</p><p>Extract it to a working folder, e.g. <code>C:\\dev\\WuicTest</code> (files go directly at the root —</p><p>NOT inside a <code>src/</code> subfolder). The package contains:</p><ul><li><code>WuicTest.csproj</code> → host project with <code>&lt;PackageReference Include=&quot;WuicCore&quot; Version=&quot;...&quot; /&gt;</code></li><li><code>wwwroot/</code> → Angular app whose <code>package.json</code> references <code>wuic-framework-lib</code> from the npm registry</li><li><code>appsettings.json</code> preconfigured in <code>firstRun = &quot;true&quot;</code> mode with <code>__SET_*__</code> placeholders</li><li><code>appsettings-samples/</code> → 6 ready templates (<code>mssql</code>/<code>mysql</code>, firstRun/post-firstRun, <code>Development</code>)</li></ul><p>&gt; <strong>No need to clone the framework repository</strong>: <code>WuicCore</code> ships as a NuGet package from</p><p>&gt; <code>nuget.org</code> and <code>wuic-framework-lib</code> as an npm package from the npm registry. The framework</p><p>&gt; source is only needed if you want to modify it — typically not your case.</p><p>&gt; <strong>npm 10.9.x and packages older than 1.7.1</strong>: those packages carry no <code>package-lock.json</code>, and</p><p>&gt; without a lock npm 10.9.x (the version Node 22 LTS installs) stops with</p><p>&gt; <code>Cannot read properties of null (reading &#39;edgesOut&#39;)</code> while resolving peer dependencies.</p><p>&gt; Download the lock published next to the release —</p><p>&gt; <code>https://wuic-framework.com/downloads/locks/&lt;zip-name&gt;.package-lock.json</code> — drop it in <code>wwwroot/</code></p><p>&gt; and run <code>npm install</code> again. The <code>-Src</code> one-liner does it for you.</p><h3>2. Database</h3><p>You need a reachable engine instance. <strong>With the one-liner there is nothing to do</strong>: it</p><p>installs and configures the instance, and the connection string to paste into the wizard is the</p><p>last thing it prints. On the manual path the instance must already exist.</p><p>Connections in <code>appsettings.json</code>:</p><ul><li><code>MetaDataSQLConnection</code> — metadata DB (menu, tables, columns, boards, users)</li><li><code>DataSQLConnection</code> — application data DB</li></ul><p>If this is the first installation (<code>AppSettings.firstRun = &quot;true&quot;</code> in the template),</p><p>the scaffolding wizard on first startup creates the metadata schema and populates the data DB.</p><p>See the <em>Initial Scaffolding</em> page for the guided flow.</p><p>#### What the first-run wizard asks for</p><p>On the first start the application does not show the login form but the **Initial project</p><p>setup** page. You fill it in once: when it finishes <code>firstRun</code> flips to <code>false</code> and the page</p><p>never comes back.</p><ul><li><strong>Setup mode</strong> — two entries: <strong>Existing database</strong>, which registers a database of your own,</li></ul><p>  and <strong>Tutorial WideWorldImporters</strong>, which installs the sample database. The second one only</p><p>  appears when the package ships the tutorial (<code>tutorialAvailable</code>): in packages without it the</p><p>  dropdown is not rendered at all and the mode is &quot;Existing database&quot;.</p><ul><li><strong>DBMS</strong> — the engine. Changing it rewrites the connection string below in the shape of the</li></ul><p>  chosen provider.</p><ul><li><strong>DataSQLConnection</strong> — the string to the data database, and the field everything else</li></ul><p>  depends on: until you press <strong>Test connection and load databases</strong> the database list stays</p><p>  disabled. The test validates the credentials, lists the databases on the server and, on SQL</p><p>  Server, fixes the certificate parameters for you</p><p>  (<code>Encrypt=False;TrustServerCertificate=True</code>), telling you it did. <code>Integrated Security</code></p><p>  only works on SQL Server: the other engines need a user and a password.</p><ul><li><strong>Data database</strong> and <strong>Metadata database name</strong> — the first is picked from the list the test</li></ul><p>  loaded (in tutorial mode it is a free-text field, <code>WideWorldImporters</code> by default); the</p><p>  second is the name of the metadata database to create (<code>metadataDB</code> by default,</p><p>  <code>MetadataCRM</code> in tutorial mode). If that database already exists, the wizard asks before</p><p>  recreating it.</p><ul><li><strong>Scaffold the tables automatically</strong> (only in &quot;Existing database&quot;) — fills</li></ul><p>  <code>_metadati__tabelle</code> / <code>_metadati__colonne</code> from every table of the chosen database. It is</p><p>  what lengthens provisioning the most on databases with many tables.</p><ul><li><strong>Initial admin user</strong> — username (<code>admin</code> by default), password (at least 4 characters) and</li></ul><p>  language. There is no default password: the one you type here is the only one that will let</p><p>  you in at the first login. The language you pick is applied to the admin user and to this</p><p>  page itself.</p><ul><li><strong>RAG Chatbot</strong> — only the Anthropic key, and it is optional. Nothing to install: see step 5.</li></ul><p>Once you press <strong>Confirm and create the metadata database</strong> provisioning runs on its own, with</p><p>a progress bar and the number of batches processed. How long it takes, measured on the test</p><p>installations: <strong>30 s - 2 min</strong> in tutorial mode, <strong>1-4 min</strong> on an existing database with</p><p>automatic scaffolding enabled. When it ends, the page gives way to the login form.</p><h3>3. Backend (.NET)</h3><p>From the root of the extracted folder (e.g. <code>C:\\dev\\WuicTest</code>):</p><p>Snippet 3:</p><p>The backend exposes APIs on <code>http://localhost:5000</code>.</p><h3>4. Frontend (Angular)</h3><p>In a second shell, from the <code>wwwroot/</code> subfolder:</p><p>Snippet 4:</p><p>The frontend is available on <code>http://localhost:4200</code>.</p><p>The credentials are those of the admin user you chose in the first-run wizard: the username</p><p>is <code>admin</code> unless you changed it, and the password is the one you typed (there is no default</p><p>password).</p><h3>5. RAG Chatbot (optional)</h3><p>The RAG Chatbot (<code>Administration &gt; RAG Chat</code>) runs <strong>inside the .NET backend</strong>:</p><p>the retrieval engine (<code>rag-engine/WuicRagEngine.dll</code>, in-process ONNX Runtime)</p><p>is loaded by the backend when <code>AppSettings.rag-use-dotnet-engine</code> is <code>&quot;true&quot;</code></p><p>(the default in release packages). **No Python, no venv, no separate server</p><p>to start.**</p><p>The <strong>first</strong> time the chatbot is opened (or at the end of the first run) the</p><p>backend downloads by itself the ONNX models (<code>bge-m3</code> + reranker), tokenizer</p><p>and index (~4.5 GB) from <code>rag-engine-models-url</code> (default</p><p><code>https://wuic-framework.com/rag-models</code>) into <code>rag-engine/artifacts/</code>. An</p><p>internet connection is needed only once; the download runs in the background</p><p>(1-5 min) and an in-app notification is sent when it starts and when it ends.</p><p>Meanwhile the component shows the <strong>RAG offline</strong> status and the rest of the</p><p>application works normally.</p><p>Relevant <code>AppSettings</code> keys (all with ready defaults):</p><ul><li><code>rag-use-dotnet-engine</code> = <code>true</code> — enables the .NET engine (<code>false</code> = Python fallback, see below)</li><li><code>rag-engine-device</code> = <code>auto</code> — <code>auto</code> | <code>cuda</code> | <code>cpu</code>: with an NVIDIA GPU (CUDA 12.x + cuDNN 9) ~1 s/query, on CPU ~15-25 s/query</li><li><code>rag-engine-profile</code> = <code>release</code> — <code>release</code> = framework sources as signatures only; <code>internal</code> = full index</li><li><code>rag-engine-models-url</code> — download source on first start</li><li><code>rag-engine-cuda-path</code> = (empty) — folder of the CUDA/cuDNN DLLs when they are not installed system-wide</li></ul><p>For LLM chat set <code>rag-llm-provider</code> + <code>rag-llm-api-key</code> (Claude via Anthropic,</p><p>or a local model via Ollama with <code>rag-llm-base-url</code>). Without a provider only</p><p>the retrieval mode (snippet search) works. Key details on the <em>AppSettings</em></p><p>page.</p><p>&gt; The legacy Python stack (<code>scripts/rag-setup.ps1</code> + <code>rag_server.py</code> on</p><p>&gt; <code>127.0.0.1:8765</code>) is only usable as a fallback with</p><p>&gt; <code>rag-use-dotnet-engine = &quot;false&quot;</code> and is not shipped in release packages.</p><h2>Services Summary</h2><table><thead><tr><th>Service</th><th>Port</th><th>Required</th><th>Quick command</th></tr></thead><tbody><tr><td>SQL Server</td><td>1433</td><td>yes</td><td>(Windows service)</td></tr><tr><td>.NET Backend</td><td>5000</td><td>yes</td><td><code>dotnet watch ... run</code></td></tr><tr><td>Angular Frontend</td><td>4200</td><td>yes</td><td><code>npm run serve:dev</code></td></tr><tr><td>.NET RAG engine (ONNX)</td><td>in-process</td><td>no</td><td>loaded by the backend on the first chat</td></tr></tbody></table><h2>Quick Start — First Component</h2><p>1. Configure the AsmxProxy endpoint.</p><p>2. Define route metadata and columns.</p><p>3. Mount <code>wuic-data-source</code> + <code>wuic-data-repeater</code>.</p><p>Snippet 5:</p><h2>The first lists show 20 records: that is Trial mode</h2><p>A fresh install runs <strong>without a license</strong>, that is, in Trial mode, and in that mode</p><p><strong>every query is capped at 20 records</strong>. It is neither a bug nor a database limit: a list</p><p>that reads &quot;20 of 20&quot; on a table with thousands of rows is simply running unlicensed.</p><p>How to confirm it in a second:</p><p>Snippet 6:</p><p><code>licenseValid: false</code> confirms the Trial, and <code>licenseReason</code> says why</p><p>(<code>invalid_signature</code>, <code>license_expired</code>, <code>machine_fingerprint_not_authorized</code>, ...).</p><p>How to get out of it: paste the license from <strong>Administration &gt; AppSettings Editor</strong>, Licensing</p><p>tab, and it takes effect immediately - no backend restart needed. The details, including the</p><p>limits the Trial imposes beyond the record count, are in the <a href=\"licensing.md\">Licensing</a> page.</p>",
                     "codeSamples": [
                         {
                             "id": "code_1",
@@ -7873,25 +7895,31 @@ const frameworkDocsContent = {
                             "id": "code_2",
                             "title": "Snippet 2",
                             "language": "text",
-                            "code": "Developer workspace ready: C:\\Users\\<user>\\AppData\\Local\\WUIC\\app\r\n\r\n  code \"C:\\Users\\<user>\\AppData\\Local\\WUIC\\app\\WuicTest.code-workspace\"\r\n  then F5 > 'Fullstack: WuicTest + Chrome' (backend http://localhost:5000, frontend http://localhost:4200)\r\n\r\nFirst start opens the first-run wizard: paste this connection string (Windows authentication)\r\n  Data Source=localhost\\SQLEXPRESS;Integrated Security=SSPI;Initial Catalog=WuicData;Encrypt=False;TrustServerCertificate=True\r\nRename the project: .\\rename-project.ps1 -Name MyApp"
+                            "code": "Developer workspace ready: C:\\Users\\<user>\\AppData\\Local\\WUIC\\app\n\n  code \"C:\\Users\\<user>\\AppData\\Local\\WUIC\\app\\WuicTest.code-workspace\"\n  then F5 > 'Fullstack: WuicTest + Chrome' (backend http://localhost:5000, frontend http://localhost:4200)\n\nFirst start opens the first-run wizard: paste this connection string (Windows authentication)\n  Data Source=localhost\\SQLEXPRESS;Integrated Security=SSPI;Initial Catalog=WuicData;Encrypt=False;TrustServerCertificate=True\nRename the project: .\\rename-project.ps1 -Name MyApp"
                         },
                         {
                             "id": "code_3",
                             "title": "Snippet 3",
                             "language": "powershell",
-                            "code": "# First run: restore NuGet packages (pulls WuicCore + deps from nuget.org, ~30 s)\r\ndotnet restore\r\n\r\n# Start dev with hot reload\r\n$env:ASPNETCORE_ENVIRONMENT = 'Development'\r\ndotnet watch run\r\n\r\n# Or one-shot start (no hot reload)\r\ndotnet run"
+                            "code": "# First run: restore NuGet packages (pulls WuicCore + deps from nuget.org, ~30 s)\ndotnet restore\n\n# Start dev with hot reload\n$env:ASPNETCORE_ENVIRONMENT = 'Development'\ndotnet watch run\n\n# Or one-shot start (no hot reload)\ndotnet run"
                         },
                         {
                             "id": "code_4",
                             "title": "Snippet 4",
                             "language": "powershell",
-                            "code": "cd wwwroot\r\n\r\n# First run: restore npm dependencies (pulls wuic-framework-lib from npm registry, ~2 min)\r\nnpm install\r\n\r\n# Start dev server\r\nnpm run serve:dev"
+                            "code": "cd wwwroot\n\n# First run: restore npm dependencies (pulls wuic-framework-lib from npm registry, ~2 min)\nnpm install\n\n# Start dev server\nnpm run serve:dev"
                         },
                         {
                             "id": "code_5",
                             "title": "Snippet 5",
                             "language": "html",
-                            "code": "<wuic-data-source [hardcodedRoute]=\"'cities'\"></wuic-data-source>\r\n<wuic-data-repeater [hardcodedAction]=\"'list'\"></wuic-data-repeater>"
+                            "code": "<wuic-data-source [hardcodedRoute]=\"'cities'\"></wuic-data-source>\n<wuic-data-repeater [hardcodedAction]=\"'list'\"></wuic-data-repeater>"
+                        },
+                        {
+                            "id": "code_6",
+                            "title": "Snippet 6",
+                            "language": "bash",
+                            "code": "curl -s http://localhost:5000/api/Meta/LicenseStatus"
                         }
                     ]
                 }
@@ -7926,18 +7954,22 @@ const frameworkDocsContent = {
             "toc": [
                 {
                     "id": "sec_1",
-                    "title": "When to Use It"
+                    "title": "With a tutorial package there is nothing to scaffold"
                 },
                 {
                     "id": "sec_2",
-                    "title": "Behavior with firstRun=true"
+                    "title": "When to Use It"
                 },
                 {
                     "id": "sec_3",
-                    "title": "Typical Operations"
+                    "title": "Behavior with firstRun=true"
                 },
                 {
                     "id": "sec_4",
+                    "title": "Typical Operations"
+                },
+                {
+                    "id": "sec_5",
                     "title": "After Provisioning"
                 }
             ],
@@ -7945,7 +7977,7 @@ const frameworkDocsContent = {
                 {
                     "id": "overview",
                     "title": "Overview",
-                    "html": "<h1>Initial Scaffolding</h1><p>This page describes the initial bootstrap when <code>AppSettings.firstRun = true</code>.</p><h2>When to Use It</h2><ul><li>New installation (metadata/data DB not yet ready).</li><li>Local environment to realign with initial setup.</li><li>First launch after deploy where you want to force the guided provisioning procedure.</li></ul><h2>Behavior with firstRun=true</h2><ul><li>The <code>GET /api/Meta/FirstRunStatus</code> endpoint exposes <code>firstRun: true</code>.</li><li>At login, the first run flow appears (e.g., <code>Update</code> action on the screen).</li><li>The setup applies base configurations (connections, runtime settings, metadata bootstrap).</li></ul><h2>Typical Operations</h2><ul><li>Verify <code>AppSettings.firstRun</code> is <code>true</code> in <code>appsettings.{Environment}.json</code> of the host you are running.</li><li>Start the application and complete the initial scaffolding procedure from the UI.</li><li>Check that connections and main parameters are consistent (<code>dbms</code>, <code>DataDBName</code>, <code>ConnectionStrings</code>).</li></ul><h2>After Provisioning</h2><ul><li>The setup procedure sets <code>firstRun</code> to <code>false</code> to avoid re-executions on each start.</li><li>Perform a standard login and validate access to the main routes.</li></ul>",
+                    "html": "<h1>Initial Scaffolding</h1><p>This page describes the initial bootstrap when <code>AppSettings.firstRun = true</code>.</p><h2>With a tutorial package there is nothing to scaffold</h2><p>The scaffolding this page is about — reading the tables of a database and registering them in</p><p><code>_metadati__tabelle</code> / <code>_metadati__colonne</code> — applies <strong>only</strong> to the &quot;Existing database&quot; mode of</p><p>the first-run wizard: that is where the *Scaffold the tables of the selected database</p><p>automatically* checkbox lives.</p><p>In <strong>tutorial</strong> packages that checkbox does not exist. The metadata database arrives already</p><p>populated (routes, columns, menu, translations, sample dashboards) and the wizard only restores</p><p>it and creates the admin user. Seeing ready-made routes right after the first start is therefore</p><p>not the result of scaffolding: it is the content of the tutorial.</p><table><thead><tr><th>Wizard mode</th><th>What happens to the metadata</th></tr></thead><tbody><tr><td>Tutorial WideWorldImporters</td><td>Metadata already built, restored from the package. No scaffolding at all.</td></tr><tr><td>Existing database, checkbox off</td><td>An empty metadata database: you register the routes yourself, by hand or later from the Scaffolding page.</td></tr><tr><td>Existing database, checkbox on</td><td>At the end of the installation every table of the chosen database is registered as a route.</td></tr></tbody></table><p>The rest of this page applies to the last two rows of that table.</p><h2>When to Use It</h2><ul><li>New installation (metadata/data DB not yet ready).</li><li>Local environment to realign with initial setup.</li><li>First launch after deploy where you want to force the guided provisioning procedure.</li></ul><h2>Behavior with firstRun=true</h2><ul><li>The <code>GET /api/Meta/FirstRunStatus</code> endpoint exposes <code>firstRun: true</code>.</li><li>At login, the first run flow appears (e.g., <code>Update</code> action on the screen).</li><li>The setup applies base configurations (connections, runtime settings, metadata bootstrap).</li></ul><h2>Typical Operations</h2><ul><li>Verify <code>AppSettings.firstRun</code> is <code>true</code> in <code>appsettings.{Environment}.json</code> of the host you are running.</li><li>Start the application and complete the initial scaffolding procedure from the UI.</li><li>Check that connections and main parameters are consistent (<code>dbms</code>, <code>DataDBName</code>, <code>ConnectionStrings</code>).</li></ul><h2>After Provisioning</h2><ul><li>The setup procedure sets <code>firstRun</code> to <code>false</code> to avoid re-executions on each start.</li><li>Perform a standard login and validate access to the main routes.</li></ul>",
                     "codeSamples": []
                 }
             ],
@@ -8004,7 +8036,7 @@ const frameworkDocsContent = {
                 {
                     "id": "overview",
                     "title": "Overview",
-                    "html": "<h1>Licensing</h1><p>This page explains licensing from the end user&#39;s perspective: what is needed, how to obtain the license, and how to apply it.</p><h2>How to obtain a license</h2><p>Review plans, included features per tier (Developer / Professional / Software House) and purchase on the public site:</p><ul><li><a href=\"https://wuic-framework.com/pricing\" target=\"_blank\" rel=\"noopener noreferrer\">WUIC pricing and plans — wuic-framework.com/pricing</a></li><li><a href=\"mailto:licensing@wuic-framework.com\">Contact sales</a> — no license is needed to evaluate: without one the framework runs in Trial mode (20 records per query)</li><li><a href=\"https://wuic-framework.com\" target=\"_blank\" rel=\"noopener noreferrer\">WUIC homepage</a></li></ul><p>After purchase you will receive an email with <code>license-payload</code> + <code>license-signature</code> to install as described in the &quot;End User Procedure&quot; below.</p><h2>How It Works</h2><ul><li>The license is valid only if:</li><li>correct signature.</li><li><code>machineFingerprint</code> of the current server is present in the <code>machineFingerprints</code> list of the signed payload.</li><li>If the license is not valid, data reading (<code>getFlatRecordData</code>) is limited to a maximum of 20 records. Additionally, the host hook <code>customizeSelect</code> is bypassed (not invoked).</li></ul><h2>Where to Find the machineFingerprint</h2><p>Backend endpoint:</p><ul><li><code>GET /api/Meta/LicenseStatus</code> → field <code>machineFingerprint</code> (always available, even without a license).</li><li>During the first run it is also exposed by <code>GET /api/Meta/FirstRunStatus</code>.</li></ul><p>Note: the local file <code>installation.id</code> is no longer used by licensing.</p><h2>End User Procedure</h2><p>1. Retrieve <code>machineFingerprint</code> from your host.</p><p>2. Send the value to the vendor/licensor.</p><p>3. Receive the license values:</p><ul><li><code>license-payload</code></li><li><code>license-signature</code></li><li><code>license-public-key-pem</code> (if required by your installation)</li></ul><p>4. Enter the values in the <code>appsettings.{Environment}.json</code> file of the running host, <code>AppSettings</code> section.</p><p>5. Restart the backend.</p><p>6. Verify license status from API:</p><ul><li><code>GET /api/Meta/LicenseStatus</code></li><li>expected: <code>licenseValid = true</code>.</li></ul><h2>Multi-Machine License</h2><p>A single license can authorize multiple machines by including multiple values in <code>machineFingerprints</code>.</p><h2>Quick Troubleshooting</h2><ul><li><code>licenseReason = invalid_signature</code>:</li><li>payload/signature are not consistent with each other or the public key is different.</li><li><code>licenseReason = machine_fingerprint_not_authorized</code>:</li><li>the current machine&#39;s fingerprint is not present in the received license.</li><li><code>licenseReason = machine_fingerprint_missing</code>:</li><li>the runtime cannot calculate the local fingerprint.</li><li><code>licenseReason = license_expired</code>:</li><li>the license has expired, request renewal.</li></ul>",
+                    "html": "<h1>Licensing</h1><p>This page explains licensing from the end user&#39;s perspective: what is needed, how to obtain the license, and how to apply it.</p><h2>How to obtain a license</h2><p>Review plans, included features per tier (Developer / Professional / Software House) and purchase on the public site:</p><ul><li><a href=\"https://wuic-framework.com/pricing\" target=\"_blank\" rel=\"noopener noreferrer\">WUIC pricing and plans — wuic-framework.com/pricing</a></li><li><a href=\"mailto:licensing@wuic-framework.com\">Contact sales</a> — no license is needed to evaluate: without one the framework runs in Trial mode (20 records per query)</li><li><a href=\"https://wuic-framework.com\" target=\"_blank\" rel=\"noopener noreferrer\">WUIC homepage</a></li></ul><p>After purchase you will receive an email with <code>license-payload</code> + <code>license-signature</code> to install as described in the &quot;End User Procedure&quot; below.</p><h2>How It Works</h2><ul><li>The license is valid only if:</li><li>correct signature.</li><li><code>machineFingerprint</code> of the current server is present in the <code>machineFingerprints</code> list of the signed payload.</li><li>If the license is not valid, data reading (<code>getFlatRecordData</code>) is limited to a maximum of 20 records. Additionally, the host hook <code>customizeSelect</code> is bypassed (not invoked).</li></ul><h2>Where to Find the machineFingerprint</h2><p>Backend endpoint:</p><ul><li><code>GET /api/Meta/LicenseStatus</code> → field <code>machineFingerprint</code> (always available, even without a license).</li><li>During the first run it is also exposed by <code>GET /api/Meta/FirstRunStatus</code>.</li></ul><p>Note: the local file <code>installation.id</code> is no longer used by licensing.</p><h2>End User Procedure</h2><p>1. Retrieve <code>machineFingerprint</code> from your host.</p><p>2. Send the value to the vendor/licensor.</p><p>3. Receive the license values:</p><ul><li><code>license-payload</code></li><li><code>license-signature</code></li><li><code>license-public-key-pem</code> (if required by your installation)</li></ul><p>4. Paste the values from the UI: <strong>Administration &gt; AppSettings Editor</strong>, <strong>License</strong> section</p><p>   (fields <code>License email</code>, <code>License payload</code>, <code>License signature</code>, <code>Public key (PEM)</code>), then</p><p>   save. Alternatively you can write them by hand in the <code>AppSettings</code> section of the running</p><p>   host&#39;s <code>appsettings.{Environment}.json</code>.</p><p>5. Verify the license status:</p><ul><li>from the API: <code>GET /api/Meta/LicenseStatus</code>, expected <code>licenseValid = true</code>;</li><li>or from the page itself, which re-reads the license right after saving.</li></ul><p><strong>No backend restart is needed when you go through the editor.</strong> Saving <code>license-payload</code> /</p><p><code>license-signature</code> from the AppSettings Editor makes the backend refresh the validation</p><p>service on its own, and the license applies from the next request. A restart is only needed in</p><p>the other case, when the values are written by hand in the file: that one is read at startup.</p><h2>Multi-Machine License</h2><p>A single license can authorize multiple machines by including multiple values in <code>machineFingerprints</code>.</p><h2>Quick Troubleshooting</h2><ul><li><code>licenseReason = invalid_signature</code>:</li><li>payload/signature are not consistent with each other or the public key is different.</li><li><code>licenseReason = machine_fingerprint_not_authorized</code>:</li><li>the current machine&#39;s fingerprint is not present in the received license.</li><li><code>licenseReason = machine_fingerprint_missing</code>:</li><li>the runtime cannot calculate the local fingerprint.</li><li><code>licenseReason = license_expired</code>:</li><li>the license has expired, request renewal.</li></ul>",
                     "codeSamples": []
                 }
             ],
@@ -8679,42 +8711,46 @@ const frameworkDocsContent = {
                 },
                 {
                     "id": "sec_2",
-                    "title": "Screenshot Reference (User Manual)"
+                    "title": "What the toolbar shows by default"
                 },
                 {
                     "id": "sec_3",
-                    "title": "Inline Editing Metadata"
+                    "title": "Screenshot Reference (User Manual)"
                 },
                 {
                     "id": "sec_4",
-                    "title": "Toolbar Export/Import"
+                    "title": "Inline Editing Metadata"
                 },
                 {
                     "id": "sec_5",
-                    "title": "Metadata Config"
+                    "title": "Toolbar Export/Import"
                 },
                 {
                     "id": "sec_6",
-                    "title": "md_props_bag: toolbar"
+                    "title": "Metadata Config"
                 },
                 {
                     "id": "sec_7",
-                    "title": "md_props_bag: archetypes.list"
+                    "title": "md_props_bag: toolbar"
                 },
                 {
                     "id": "sec_8",
-                    "title": "Paging: md_pagesize and md_page_size_choice"
+                    "title": "md_props_bag: archetypes.list"
                 },
                 {
                     "id": "sec_9",
-                    "title": "Forced Virtualization on High Page Size"
+                    "title": "Paging: md_pagesize and md_page_size_choice"
                 },
                 {
                     "id": "sec_10",
-                    "title": "Events and Subscriptions (Host)"
+                    "title": "Forced Virtualization on High Page Size"
                 },
                 {
                     "id": "sec_11",
+                    "title": "Events and Subscriptions (Host)"
+                },
+                {
+                    "id": "sec_12",
                     "title": "`rowCustomSelect` — actual signature (gotcha)"
                 }
             ],
@@ -8722,7 +8758,7 @@ const frameworkDocsContent = {
                 {
                     "id": "overview",
                     "title": "Overview",
-                    "html": "<h1>List Grid</h1><p>Main component for tabular lists with filters, sorting, server-side paging, and row actions.</p><h2>Use Cases</h2><ul><li>Enterprise tabular CRUD.</li><li>Operational reports with multi-column filters.</li><li>Very large datasets with <code>cursorMode</code>.</li></ul><h2>Screenshot Reference (User Manual)</h2><ul><li><code>manual__grid__01.png</code>: <code>inline cell edit</code> mode in list-grid.</li><li><code>manual__grid__02.png</code>: <code>inline edit</code> (row-level) mode in list-grid.</li></ul><h2>Inline Editing Metadata</h2><p>Configuration in the table metadata <code>md_props_bag</code>:</p><ul><li><code>md_inline_edit</code></li></ul><p>  - Enables inline row editing in list-grid (editable cells in row context, without opening a popup).</p><p>  - Useful when you want to maintain the table UX with quick editing per record.</p><ul><li><code>md_inline_cell_edit</code></li></ul><p>  - Enables &quot;cell-by-cell&quot; inline editing (focus on the individual cell).</p><p>  - Note: in legacy configurations it may appear as <code>md_inline_cell_editing</code>; the runtime behavior is the same.</p><p>  - <strong>Runtime promotion</strong>: when <code>md_inline_cell_edit</code> is <code>true</code>, the component forces</p><p>    <code>md_inline_edit = true</code> at runtime regardless of the DB value.</p><p>    Both UX modes need the action column visible, so they are mutually</p><p>    non-exclusive at the rendering level.</p><ul><li><code>md_batch_save</code></li></ul><p>  - Enables batch saving of pending changes (<code>Save changes</code> / <code>Cancel changes</code>).</p><p>  - When used with inline-cell, changes remain pending until explicit save.</p><p>  - <strong>Prerequisite</strong>: <code>md_batch_save</code> takes effect <strong>only</strong> if <code>md_inline_cell_edit</code> is <code>true</code>.</p><p>    With <code>md_inline_cell_edit:false</code> the flag is ignored at runtime and the</p><p>    &quot;Save changes / Cancel changes&quot; buttons are not rendered.</p><h3>Valid Combinations</h3><table><thead><tr><th><code>md_inline_edit</code></th><th><code>md_inline_cell_edit</code></th><th><code>md_batch_save</code></th><th>Runtime Result</th></tr></thead><tbody><tr><td><code>true</code></td><td><code>false</code></td><td>any</td><td>Row-level inline edit with pencil. <code>md_batch_save</code> ignored.</td></tr><tr><td><code>false</code></td><td><code>true</code></td><td><code>false</code></td><td>Cell-by-cell autosave on blur. <code>md_inline_edit</code> forced to <code>true</code> at runtime.</td></tr><tr><td><code>false</code></td><td><code>true</code></td><td><code>true</code></td><td>Cell-by-cell with pending buffer + <code>Save / Cancel changes</code> toolbar.</td></tr><tr><td><code>false</code></td><td><code>false</code></td><td>any</td><td>No inline editing. <code>md_batch_save</code> ignored.</td></tr></tbody></table><p>Row-level inline edit example:</p><p>Snippet 1:</p><p>Cell-by-cell with batch save example:</p><p>Snippet 2:</p><h2>Toolbar Export/Import</h2><ul><li>Export XLS:</li></ul><p>  - Shows a progress dialog with real-time percentage;</p><p>  - Actions: <code>Continue in background</code>, <code>Cancel task</code>, <code>Stop and download partial</code>;</p><p>  - In background creates a notification with progress; click reopens the dialog.</p><ul><li>Import XLS/XLSX (if <code>md_importable = true</code>):</li></ul><p>  - Progress dialog after confirmation;</p><p>  - Actions: <code>Continue in background</code>, <code>Cancel import (rollback)</code>, <code>Stop and partial commit</code>;</p><p>  - At the end of import creates a summary notification that navigates to the route.</p><h2>Metadata Config</h2><p>Key settings in <code>md_props_bag</code> and column metadata.</p><p>Snippet 3:</p><h2>md_props_bag: toolbar</h2><p>Opt-in flags that hide blocks of the list-grid toolbar (<code>caption-bar</code>). All under <code>md_props_bag.toolbar.*</code> (parsed at runtime as <code>tableMetadata.extraProps.toolbar</code>).</p><p>Snippet 4:</p><ul><li><code>hideManageState</code> (boolean, default <code>false</code>): hides in the <strong>caption-right</strong> the &quot;Manage state&quot; button (bookmark icon) + the saved-states <code>&lt;select&gt;</code>. Useful for hardcoded / demo routes where the saved-state feature (persistence per <code>user_id</code> + route via <code>MetaService</code>) doesn&#39;t make sense — e.g. Pattern 3 pure OData without registered route metadata.</li><li><code>hideBatchActions</code> (boolean, default <code>false</code>): hides in the <strong>caption-left</strong> the &quot;Save changes&quot; (<code>pi-save</code>) + &quot;Discard changes&quot; (<code>pi-times</code>) buttons + the changes count indicator (<code>grid-changes-indicator</code>, pencil badge + count). Generated by the framework when <code>md_inline_cell_editing</code> + <code>md_batch_save</code> are active. Designed for <strong>nested grids inside a parametric-dialog</strong>: the parent&#39;s save/cancel persists master + rows in one shot via the framework batch save, and the duplicate buttons on the nested grid confuse the UX.</li></ul><p>Example nested rows in custom edit-form (runtime patch):</p><p>Snippet 5:</p><p>TS type in <a href=\"../api/wuic-framework-lib.metadatitabella.html\">`metadati_tabella.ts`</a> (<code>extraProps.toolbar</code> property). The flags do NOT disable the underlying <code>md_batch_save</code> logic (changes are still tracked); they only remove the toolbar UI — the actual save flows through the parent.</p><h2>md_props_bag: archetypes.list</h2><p>The component reads <code>md_props_bag.archetypes.list</code>.</p><p>Snippet 6:</p><ul><li><code>proportionalColwidth</code>:</li><li>type: boolean (with tolerant parser)</li><li>accepted values: <code>true</code>, <code>false</code>, <code>1</code>, <code>0</code>, <code>&quot;true&quot;</code>, <code>&quot;false&quot;</code>, <code>&quot;1&quot;</code>, <code>&quot;0&quot;</code></li><li>runtime default: <code>true</code> when absent or empty</li><li>effect: distributes column widths proportionally (instead of px) when no user-persisted widths exist.</li></ul><ul><li><code>virtualize</code>:</li><li>type: <code>boolean</code> or <code>object</code></li><li>accepted values:</li><li><code>true</code>/<code>false</code>, <code>1</code>/<code>0</code>, <code>&quot;true&quot;</code>/<code>&quot;false&quot;</code>, <code>&quot;1&quot;</code>/<code>&quot;0&quot;</code></li><li>object with <code>enabled</code> (optional) and <code>itemSize</code> (optional)</li><li>runtime default: disabled (<code>false</code>) when absent</li><li><code>enabled</code>:</li><li>default: <code>true</code> if the <code>virtualize</code> node is an object without <code>enabled</code>, otherwise tolerant parser</li><li>effect: enables <code>virtualScroll</code> on <code>p-table</code></li><li><code>itemSize</code>:</li><li>default: <code>44</code></li><li>effect: sets <code>virtualScrollItemSize</code> (virtual row height in px)</li></ul><ul><li><code>advancedFilter</code>:</li><li>type: boolean (with tolerant parser)</li><li>runtime default: <code>false</code></li><li>effect:</li><li>when <code>true</code>, the grid hides column filter icons (<code>p-columnFilter</code>) and uses the <code>wuic-filter-bar</code> above the table (at <code>data-repeater</code>/<code>bounded-repeater</code> level) to apply filters.</li></ul><p>Operational note:</p><ul><li>The <code>md_props_bag</code> suggest in the metadata editor also exposes the checkable <code>archetypes.list.advancedFilter</code> node.</li></ul><h2>Paging: md_pagesize and md_page_size_choice</h2><p>The grid uses <code>md_pagesize</code> as the default page size and <code>md_page_size_choice</code> as the list of selectable values in the paginator.</p><p>Runtime rules:</p><ul><li>If <code>md_pagesize</code> is greater than the maximum value present in <code>md_page_size_choice</code>, the framework automatically adds <code>md_pagesize</code> to the options list;</li><li>The list is normalized (valid numbers, deduplication, ascending sort).</li></ul><p>Example:</p><ul><li><code>md_pagesize = 200</code></li><li><code>md_page_size_choice = &quot;10,25,50,100&quot;</code></li><li>runtime result: <code>10,25,50,100,200</code></li></ul><h2>Forced Virtualization on High Page Size</h2><p>When the user selects in the paginator a <code>pageSize &gt;= 1000</code>:</p><ul><li>virtualization is automatically forced even if <code>md_props_bag.archetypes.list.virtualize</code> is absent or disabled;</li><li><code>virtualScrollItemSize</code> is forced to the default value <code>44</code>.</li></ul><p>This behavior protects the table rendering on very large pages.</p><h2>Events and Subscriptions (Host)</h2><p><code>wuic-list-grid</code> exposes runtime events useful for intercepting the render cycle and p-table callbacks on the host project side.</p><p>Available events:</p><ul><li><code>onAfterRender</code>: emitted at the end of grid data binding (<code>rows</code>, <code>totalRecords</code>, <code>metaInfo</code>, <code>datasource</code>).</li><li><code>onBeforeRowRender</code>: emitted before the logical rendering of a single row; supports cancel via <code>event.cancelRender()</code>.</li><li><code>onAfterRowRender</code>: emitted after the logical rendering of a single row.</li><li><code>onPaging</code>: emitted on paging events (<code>p-table onPage</code>).</li><li><code>onSorting</code>: emitted on sorting events (<code>p-table onSort</code>).</li><li><code>onFiltering</code>: emitted on filtering events (<code>p-table onFilter</code>).</li><li><code>onPTableSelectionChange</code>: emitted on row selection change.</li><li><code>onPTableRowExpand</code>: emitted on row expand.</li><li><code>onPTableRowCollapse</code>: emitted on row collapse.</li><li><code>onPTableColumnResize</code>: emitted on column resize.</li><li><code>onPTableColumnReorder</code>: emitted on column reorder.</li></ul><h3>Example 1: Direct Binding in Template</h3><p>Snippet 7:</p><h3>Example 2: Subscribe via ViewChild</h3><p>Snippet 8:</p><h2><code>rowCustomSelect</code> — actual signature (gotcha)</h2><p><code>&lt;wuic-list-grid&gt;</code> accepts a <code>[rowCustomSelect]</code> input to hook into row selection (opening a &quot;pick a document&quot; dialog, master-detail flow, etc.). The TypeScript signature declared in <a href=\"../../src/lib/component/list-grid/list-grid.component.ts#L140\">list-grid.component.ts:140</a> reads:</p><p>Snippet 9:</p><p><strong>However at runtime the callback is invoked with arguments reversed</strong> — the framework calls <code>rowCustomSelect($event, rowData, dt)</code> (see <a href=\"../../src/lib/component/dynamic-template/dynamic-template.component.ts#L447\">dynamic-template.component.ts:447</a> and <a href=\"../../src/lib/component/dynamic-template/dynamic-card-template.component.ts#L205\">dynamic-card-template.component.ts:205</a>).</p><p>Symptom of wrong arg order: <code>rowData?.id</code> is undefined → early-return guard in your handler → the callback returns silently and your dialog/action never fires. No console error.</p><p>Correct form (matches runtime invocation):</p><p>Snippet 10:</p><p>Template usage:</p><p>Snippet 11:</p><p>&gt; Note: tests in <code>designer.component.spec.ts</code> (e.g. line 512) invoke the callback with <code>({currentTarget: rowCell}, {id: 42}, null)</code>, confirming the <code>($event, rowData, dt)</code> order. If the framework eventually aligns the declared signature, this page will be updated as well.</p>",
+                    "html": "<h1>List Grid</h1><p>Main component for tabular lists with filters, sorting, server-side paging, and row actions.</p><h2>Use Cases</h2><ul><li>Enterprise tabular CRUD.</li><li>Operational reports with multi-column filters.</li><li>Very large datasets with <code>cursorMode</code>.</li></ul><h2>What the toolbar shows by default</h2><p>When you open a freshly scaffolded route, the caption bar sits above the grid. On the left:</p><table><thead><tr><th>Button</th><th>When it appears</th></tr></thead><tbody><tr><td><strong>Refresh</strong></td><td>always, unless <code>md_hide_refresh</code></td></tr><tr><td><strong>Add</strong></td><td>with <code>md_insertable</code></td></tr><tr><td><strong>Actions</strong></td><td>if the table has custom actions</td></tr><tr><td>Import / Export</td><td>always; the import branch only with <code>md_importable</code></td></tr><tr><td><strong>Reports</strong></td><td>if at least one report is bound to the route</td></tr><tr><td><strong>Save changes</strong> / <strong>Discard changes</strong></td><td>only with <code>md_inline_cell_edit</code> <strong>and</strong> <code>md_batch_save</code></td></tr></tbody></table><p>On the right: <strong>Manage state</strong> (preceded by the saved-states dropdown, when there are any),</p><p><strong>Clear filters</strong> when filters live on the columns, and <strong>Performance</strong> if the inspector is</p><p>enabled on the route.</p><p>&gt; The captions quoted further down this page <strong>are not on that screen</strong>, and that is not a</p><p>&gt; defect: the export/import ones (<em>Continue in background</em>, <em>Cancel task</em>, *Stop and download</p><p>&gt; partial<em>, </em>Cancel import (rollback)<em>, </em>Stop and commit partial*) live in the progress dialog,</p><p>&gt; which only exists while an export or import is running; <em>Save changes</em> and <em>Discard changes</em></p><p>&gt; only appear with the two flags above. They belong to moments other than first opening the</p><p>&gt; list.</p><h2>Screenshot Reference (User Manual)</h2><ul><li><code>manual__grid__01.png</code>: <code>inline cell edit</code> mode in list-grid.</li><li><code>manual__grid__02.png</code>: <code>inline edit</code> (row-level) mode in list-grid.</li></ul><h2>Inline Editing Metadata</h2><p>Configuration in the table metadata <code>md_props_bag</code>:</p><ul><li><code>md_inline_edit</code></li></ul><p>  - Enables inline row editing in list-grid (editable cells in row context, without opening a popup).</p><p>  - Useful when you want to maintain the table UX with quick editing per record.</p><ul><li><code>md_inline_cell_edit</code></li></ul><p>  - Enables &quot;cell-by-cell&quot; inline editing (focus on the individual cell).</p><p>  - Note: in legacy configurations it may appear as <code>md_inline_cell_editing</code>; the runtime behavior is the same.</p><p>  - <strong>Runtime promotion</strong>: when <code>md_inline_cell_edit</code> is <code>true</code>, the component forces</p><p>    <code>md_inline_edit = true</code> at runtime regardless of the DB value.</p><p>    Both UX modes need the action column visible, so they are mutually</p><p>    non-exclusive at the rendering level.</p><ul><li><code>md_batch_save</code></li></ul><p>  - Enables batch saving of pending changes (<code>Save changes</code> / <code>Cancel changes</code>).</p><p>  - When used with inline-cell, changes remain pending until explicit save.</p><p>  - <strong>Prerequisite</strong>: <code>md_batch_save</code> takes effect <strong>only</strong> if <code>md_inline_cell_edit</code> is <code>true</code>.</p><p>    With <code>md_inline_cell_edit:false</code> the flag is ignored at runtime and the</p><p>    &quot;Save changes / Cancel changes&quot; buttons are not rendered.</p><h3>Valid Combinations</h3><table><thead><tr><th><code>md_inline_edit</code></th><th><code>md_inline_cell_edit</code></th><th><code>md_batch_save</code></th><th>Runtime Result</th></tr></thead><tbody><tr><td><code>true</code></td><td><code>false</code></td><td>any</td><td>Row-level inline edit with pencil. <code>md_batch_save</code> ignored.</td></tr><tr><td><code>false</code></td><td><code>true</code></td><td><code>false</code></td><td>Cell-by-cell autosave on blur. <code>md_inline_edit</code> forced to <code>true</code> at runtime.</td></tr><tr><td><code>false</code></td><td><code>true</code></td><td><code>true</code></td><td>Cell-by-cell with pending buffer + <code>Save / Cancel changes</code> toolbar.</td></tr><tr><td><code>false</code></td><td><code>false</code></td><td>any</td><td>No inline editing. <code>md_batch_save</code> ignored.</td></tr></tbody></table><p>Row-level inline edit example:</p><p>Snippet 1:</p><p>Cell-by-cell with batch save example:</p><p>Snippet 2:</p><h2>Toolbar Export/Import</h2><ul><li>Export XLS:</li></ul><p>  - Shows a progress dialog with real-time percentage;</p><p>  - Actions: <code>Continue in background</code>, <code>Cancel task</code>, <code>Stop and download partial</code>;</p><p>  - In background creates a notification with progress; click reopens the dialog.</p><ul><li>Import XLS/XLSX (if <code>md_importable = true</code>):</li></ul><p>  - Progress dialog after confirmation;</p><p>  - Actions: <code>Continue in background</code>, <code>Cancel import (rollback)</code>, <code>Stop and partial commit</code>;</p><p>  - At the end of import creates a summary notification that navigates to the route.</p><h2>Metadata Config</h2><p>Key settings in <code>md_props_bag</code> and column metadata.</p><p>Snippet 3:</p><h2>md_props_bag: toolbar</h2><p>Opt-in flags that hide blocks of the list-grid toolbar (<code>caption-bar</code>). All under <code>md_props_bag.toolbar.*</code> (parsed at runtime as <code>tableMetadata.extraProps.toolbar</code>).</p><p>Snippet 4:</p><ul><li><code>hideManageState</code> (boolean, default <code>false</code>): hides in the <strong>caption-right</strong> the &quot;Manage state&quot; button (bookmark icon) + the saved-states <code>&lt;select&gt;</code>. Useful for hardcoded / demo routes where the saved-state feature (persistence per <code>user_id</code> + route via <code>MetaService</code>) doesn&#39;t make sense — e.g. Pattern 3 pure OData without registered route metadata.</li><li><code>hideBatchActions</code> (boolean, default <code>false</code>): hides in the <strong>caption-left</strong> the &quot;Save changes&quot; (<code>pi-save</code>) + &quot;Discard changes&quot; (<code>pi-times</code>) buttons + the changes count indicator (<code>grid-changes-indicator</code>, pencil badge + count). Generated by the framework when <code>md_inline_cell_editing</code> + <code>md_batch_save</code> are active. Designed for <strong>nested grids inside a parametric-dialog</strong>: the parent&#39;s save/cancel persists master + rows in one shot via the framework batch save, and the duplicate buttons on the nested grid confuse the UX.</li></ul><p>Example nested rows in custom edit-form (runtime patch):</p><p>Snippet 5:</p><p>TS type in <a href=\"../api/wuic-framework-lib.metadatitabella.html\">`metadati_tabella.ts`</a> (<code>extraProps.toolbar</code> property). The flags do NOT disable the underlying <code>md_batch_save</code> logic (changes are still tracked); they only remove the toolbar UI — the actual save flows through the parent.</p><h2>md_props_bag: archetypes.list</h2><p>The component reads <code>md_props_bag.archetypes.list</code>.</p><p>Snippet 6:</p><ul><li><code>proportionalColwidth</code>:</li><li>type: boolean (with tolerant parser)</li><li>accepted values: <code>true</code>, <code>false</code>, <code>1</code>, <code>0</code>, <code>&quot;true&quot;</code>, <code>&quot;false&quot;</code>, <code>&quot;1&quot;</code>, <code>&quot;0&quot;</code></li><li>runtime default: <code>true</code> when absent or empty</li><li>effect: distributes column widths proportionally (instead of px) when no user-persisted widths exist.</li></ul><ul><li><code>virtualize</code>:</li><li>type: <code>boolean</code> or <code>object</code></li><li>accepted values:</li><li><code>true</code>/<code>false</code>, <code>1</code>/<code>0</code>, <code>&quot;true&quot;</code>/<code>&quot;false&quot;</code>, <code>&quot;1&quot;</code>/<code>&quot;0&quot;</code></li><li>object with <code>enabled</code> (optional) and <code>itemSize</code> (optional)</li><li>runtime default: disabled (<code>false</code>) when absent</li><li><code>enabled</code>:</li><li>default: <code>true</code> if the <code>virtualize</code> node is an object without <code>enabled</code>, otherwise tolerant parser</li><li>effect: enables <code>virtualScroll</code> on <code>p-table</code></li><li><code>itemSize</code>:</li><li>default: <code>44</code></li><li>effect: sets <code>virtualScrollItemSize</code> (virtual row height in px)</li></ul><ul><li><code>advancedFilter</code>:</li><li>type: boolean (with tolerant parser)</li><li>runtime default: <code>false</code></li><li>effect:</li><li>when <code>true</code>, the grid hides column filter icons (<code>p-columnFilter</code>) and uses the <code>wuic-filter-bar</code> above the table (at <code>data-repeater</code>/<code>bounded-repeater</code> level) to apply filters.</li></ul><p>Operational note:</p><ul><li>The <code>md_props_bag</code> suggest in the metadata editor also exposes the checkable <code>archetypes.list.advancedFilter</code> node.</li></ul><h2>Paging: md_pagesize and md_page_size_choice</h2><p>The grid uses <code>md_pagesize</code> as the default page size and <code>md_page_size_choice</code> as the list of selectable values in the paginator.</p><p>Runtime rules:</p><ul><li>If <code>md_pagesize</code> is greater than the maximum value present in <code>md_page_size_choice</code>, the framework automatically adds <code>md_pagesize</code> to the options list;</li><li>The list is normalized (valid numbers, deduplication, ascending sort).</li></ul><p>Example:</p><ul><li><code>md_pagesize = 200</code></li><li><code>md_page_size_choice = &quot;10,25,50,100&quot;</code></li><li>runtime result: <code>10,25,50,100,200</code></li></ul><h2>Forced Virtualization on High Page Size</h2><p>When the user selects in the paginator a <code>pageSize &gt;= 1000</code>:</p><ul><li>virtualization is automatically forced even if <code>md_props_bag.archetypes.list.virtualize</code> is absent or disabled;</li><li><code>virtualScrollItemSize</code> is forced to the default value <code>44</code>.</li></ul><p>This behavior protects the table rendering on very large pages.</p><h2>Events and Subscriptions (Host)</h2><p><code>wuic-list-grid</code> exposes runtime events useful for intercepting the render cycle and p-table callbacks on the host project side.</p><p>Available events:</p><ul><li><code>onAfterRender</code>: emitted at the end of grid data binding (<code>rows</code>, <code>totalRecords</code>, <code>metaInfo</code>, <code>datasource</code>).</li><li><code>onBeforeRowRender</code>: emitted before the logical rendering of a single row; supports cancel via <code>event.cancelRender()</code>.</li><li><code>onAfterRowRender</code>: emitted after the logical rendering of a single row.</li><li><code>onPaging</code>: emitted on paging events (<code>p-table onPage</code>).</li><li><code>onSorting</code>: emitted on sorting events (<code>p-table onSort</code>).</li><li><code>onFiltering</code>: emitted on filtering events (<code>p-table onFilter</code>).</li><li><code>onPTableSelectionChange</code>: emitted on row selection change.</li><li><code>onPTableRowExpand</code>: emitted on row expand.</li><li><code>onPTableRowCollapse</code>: emitted on row collapse.</li><li><code>onPTableColumnResize</code>: emitted on column resize.</li><li><code>onPTableColumnReorder</code>: emitted on column reorder.</li></ul><h3>Example 1: Direct Binding in Template</h3><p>Snippet 7:</p><h3>Example 2: Subscribe via ViewChild</h3><p>Snippet 8:</p><h2><code>rowCustomSelect</code> — actual signature (gotcha)</h2><p><code>&lt;wuic-list-grid&gt;</code> accepts a <code>[rowCustomSelect]</code> input to hook into row selection (opening a &quot;pick a document&quot; dialog, master-detail flow, etc.). The TypeScript signature declared in <a href=\"../../src/lib/component/list-grid/list-grid.component.ts#L140\">list-grid.component.ts:140</a> reads:</p><p>Snippet 9:</p><p><strong>However at runtime the callback is invoked with arguments reversed</strong> — the framework calls <code>rowCustomSelect($event, rowData, dt)</code> (see <a href=\"../../src/lib/component/dynamic-template/dynamic-template.component.ts#L447\">dynamic-template.component.ts:447</a> and <a href=\"../../src/lib/component/dynamic-template/dynamic-card-template.component.ts#L205\">dynamic-card-template.component.ts:205</a>).</p><p>Symptom of wrong arg order: <code>rowData?.id</code> is undefined → early-return guard in your handler → the callback returns silently and your dialog/action never fires. No console error.</p><p>Correct form (matches runtime invocation):</p><p>Snippet 10:</p><p>Template usage:</p><p>Snippet 11:</p><p>&gt; Note: tests in <code>designer.component.spec.ts</code> (e.g. line 512) invoke the callback with <code>({currentTarget: rowCell}, {id: 42}, null)</code>, confirming the <code>($event, rowData, dt)</code> order. If the framework eventually aligns the declared signature, this page will be updated as well.</p>",
                     "codeSamples": [
                         {
                             "id": "code_1",
@@ -10448,7 +10484,7 @@ const frameworkDocsContent = {
                 {
                     "id": "overview",
                     "title": "Overview",
-                    "html": "<h1>Designer</h1><p>Visual editor for metadata-driven dashboards on route <code>#/cities/dashboard</code>.</p><h2>Scope</h2><ul><li>Board composition via drag-and-drop of nodes and UI blocks.</li><li>Layout and styling driven by <code>boardcontent</code> and table/column metadata.</li><li>Property panel editing without hardcoding in runtime components.</li></ul><h2>Designer Palette</h2><ul><li><code>Datasource</code>: metadata data source (<code>route</code>, filters, sort, paging).</li><li><code>DataRepeater</code>: list/card view connected to a datasource.</li><li><code>Dynamic Template</code>: dynamic template rendering with metadata-driven inputs.</li><li><code>Action/Button</code>: user actions attached to records and callbacks.</li><li><code>Container/Layout</code>: structural blocks for columns, rows, and wrappers.</li></ul><h2>Main Features</h2><ul><li>Drag-and-drop nodes onto the canvas with persistence in <code>boardcontent</code>.</li><li>Contextual property panel with inputs consistent with the selected components.</li><li>Binding between nodes (<code>datasource -&gt; repeater/template</code>) with minimal validation.</li><li>Integrated runtime preview and layout realignment.</li><li>Pending changes management with guard before exit.</li></ul><h2>Element context menu</h2><p>Right-click on a canvas element, a breadcrumb item at the bottom or a node in the hierarchy tree shows a context menu with three items:</p><ul><li><strong>Edit properties</strong> (pi-cog) — selects the element as the &quot;current tool&quot; and shows its property panel on the right; equivalent to clicking in the tree. Useful to edit properties of nested elements without hunting for them in the hierarchy.</li><li><strong>Rename</strong> (breadcrumb only) — opens a dialog to rename the <code>displayName</code>.</li><li><strong>Remove</strong> — deletes the element from the board.</li></ul><h2>Recommended Operational Flow</h2><ul><li>Open the target dashboard route.</li><li>Insert/connect nodes from the palette.</li><li>Configure essential <code>inputs</code> (e.g., <code>route</code>, <code>action</code>, <code>datasource</code>).</li><li>Save and validate the result at runtime.</li></ul><h2>Operational Notes</h2><ul><li>For specific dashboard fixes, prefer <code>boardcontent</code> patches instead of global changes.</li><li>Avoid duplicate properties between <code>inputs</code> and inconsistent inline styles.</li><li>Always verify that datasources have a populated <code>inputs.route</code>.</li></ul>",
+                    "html": "<h1>Designer</h1><p>Visual editor for metadata-driven dashboards on route <code>#/cities/dashboard</code>.</p><h2>Scope</h2><ul><li>Board composition via drag-and-drop of nodes and UI blocks.</li><li>Layout and styling driven by <code>boardcontent</code> and table/column metadata.</li><li>Property panel editing without hardcoding in runtime components.</li></ul><h2>Designer Palette</h2><p>The palette is split into three groups. The names below are the ones you read in the palette,</p><p>uppercase exactly as the designer writes them.</p><p><strong>HTML</strong> — the markup building blocks:</p><table><thead><tr><th>Tool</th><th>What it is for</th></tr></thead><tbody><tr><td><code>TABLE</code></td><td>a grid of cells. <code>TR</code> and <code>TD</code> exist as tools but are not draggable: the table creates them</td></tr><tr><td><code>DIV</code></td><td>free-form container, the structural block you use most</td></tr><tr><td><code>SPAN</code>, <code>LABEL</code>, <code>Hx</code></td><td>databound text; <code>Hx</code> picks the level from h1 to h6</td></tr><tr><td><code>ANCHOR</code>, <code>IMG</code>, <code>IMAGE</code>, <code>IFRAME</code></td><td>links, images, external content</td></tr><tr><td><code>UL</code></td><td>list</td></tr><tr><td><code>BUTTON</code></td><td>button with a callback</td></tr><tr><td><code>INPUT</code>, <code>TEXTAREA</code>, <code>CHECKBOX</code>, <code>SELECT</code>, <code>MULTISELECT</code>, <code>DATE</code></td><td>input fields</td></tr><tr><td><code>KPI</code></td><td>a single highlighted value</td></tr><tr><td><code>SEPARATOR</code>, <code>HR</code></td><td>separators</td></tr></tbody></table><p><strong>DATA</strong> — the nodes wired to the backend:</p><table><thead><tr><th>Tool</th><th>What it is for</th></tr></thead><tbody><tr><td><code>DATASOURCE</code></td><td>metadata data source (<code>route</code>, filters, sort, paging)</td></tr><tr><td><code>DATAREPEATER</code></td><td>list/card view connected to a datasource</td></tr><tr><td><code>FILTERBAR</code></td><td>filter bar above the repeater</td></tr><tr><td><code>PAGER</code></td><td>paginator</td></tr></tbody></table><p><strong>CONTAINER</strong> — the layouts:</p><table><thead><tr><th>Tool</th><th>What it is for</th></tr></thead><tbody><tr><td><code>TABVIEW</code> + <code>TABPANEL</code></td><td>tabs</td></tr><tr><td><code>SPLITTER</code> + <code>SPLITTER-AREA</code></td><td>resizable panes</td></tr><tr><td><code>ACCORDION</code> + <code>ACCORDION-AREA</code></td><td>accordion sections</td></tr></tbody></table><p>Two names you will look for in vain: <strong>there is no &quot;Dynamic Template&quot; tool</strong> — the dynamic</p><p>template is what the <code>DATAREPEATER</code> renders, you configure it from its properties and you never</p><p>drag it; and <strong>&quot;Container&quot; / &quot;Layout&quot; are the group name</strong>, not selectable entries.</p><p>On top of these come the custom tools registered by the host project</p><p>(<code>MetadataProviderService.customDesignerTools</code>), which appear at the end under the group they</p><p>declare.</p><h2>Main Features</h2><ul><li>Drag-and-drop nodes onto the canvas with persistence in <code>boardcontent</code>.</li><li>Contextual property panel with inputs consistent with the selected components.</li><li>Binding between nodes (<code>datasource -&gt; repeater/template</code>) with minimal validation.</li><li>Integrated runtime preview and layout realignment.</li><li>Pending changes management with guard before exit.</li></ul><h2>Element context menu</h2><p>Right-click on a canvas element, a breadcrumb item at the bottom or a node in the hierarchy tree shows a context menu with three items:</p><ul><li><strong>Edit properties</strong> (pi-cog) — selects the element as the &quot;current tool&quot; and shows its property panel on the right; equivalent to clicking in the tree. Useful to edit properties of nested elements without hunting for them in the hierarchy.</li><li><strong>Rename</strong> (breadcrumb only) — opens a dialog to rename the <code>displayName</code>.</li><li><strong>Remove</strong> — deletes the element from the board.</li></ul><h2>Recommended Operational Flow</h2><ul><li>Open the target dashboard route.</li><li>Insert/connect nodes from the palette.</li><li>Configure essential <code>inputs</code> (e.g., <code>route</code>, <code>action</code>, <code>datasource</code>).</li><li>Save and validate the result at runtime.</li></ul><h2>Operational Notes</h2><ul><li>For specific dashboard fixes, prefer <code>boardcontent</code> patches instead of global changes.</li><li>Avoid duplicate properties between <code>inputs</code> and inconsistent inline styles.</li><li>Always verify that datasources have a populated <code>inputs.route</code>.</li></ul>",
                     "codeSamples": []
                 }
             ],
@@ -14563,13 +14599,17 @@ const frameworkDocsContent = {
                 {
                     "id": "sec_4",
                     "title": "Quick Start — premier composant"
+                },
+                {
+                    "id": "sec_5",
+                    "title": "Les premieres listes affichent 20 enregistrements : c'est le mode Trial"
                 }
             ],
             "sections": [
                 {
                     "id": "overview",
                     "title": "Overview",
-                    "html": "<h1>Panorama du Framework</h1><p>WUIC Framework est une plateforme pilotee par metadata pour creer des interfaces metier de maniere rapide et coherente.</p><h2>Contenu</h2><ul><li>DataSource et DataRepeater pour orchestrer les donnees et le rendu.</li><li>Archetypes visuels (list, map, scheduler, chart, carousel).</li><li>Designer runtime pour les dashboards et les templates dynamiques.</li><li>Workflow designer/runner pour les processus operationnels.</li><li>RAG Chatbot pour interroger la codebase en langage naturel.</li><li>Multi-SGBD : SQL Server, MySQL, PostgreSQL et Oracle via des providers drop-in (<code>dbms</code> : <code>mssql</code> | <code>mysql</code> | <code>postgresql</code> | <code>oracle</code>).</li></ul><h2>First Steps — Demarrage de l&#39;environnement dev</h2><p>La stack WUIC est composee de plusieurs services. Demarrez-les dans l&#39;ordre indique.</p><h3>Prerequis</h3><table><thead><tr><th>Element</th><th>Verification</th><th>Notes</th></tr></thead><tbody><tr><td>.NET 10 SDK</td><td><code>dotnet --version</code></td><td>Hosting Bundle pour IIS en production</td></tr><tr><td>Node.js 22 LTS</td><td><code>node --version</code></td><td>La 22 est la version avec laquelle le paquet est teste ; avec npm 10.9.x l&#39;installation passe grace au <code>package-lock.json</code> inclus</td></tr><tr><td>PowerShell 5.1+</td><td><code>$PSVersionTable.PSVersion</code></td><td>Le Windows PowerShell livre avec Windows suffit : <code>rename-project.ps1</code> et les scripts <code>llm-workspace/</code> fonctionnent aussi sur 5.1. PowerShell 7 est recommande, pas requis</td></tr><tr><td>SQL Server 2019+</td><td><code>sqlcmd -S localhost\\sqlexpress -E -C -Q &quot;SELECT 1&quot;</code></td><td>S&#39;il manque, <strong>la ligne unique l&#39;installe elle-meme</strong> (SQL Server Express, ou le moteur choisi avec <code>-Dbms</code>) ; pas sur Windows Server, voir l&#39;encadre ci-dessous. 2019 suffit pour les packages sans <code>.bak</code> ; le tutoriel <code>.bak</code> est une sauvegarde SQL Server 2022 et exige <strong>2022 ou plus recent</strong></td></tr><tr><td>Linux (installeur <code>install.sh</code>)</td><td><code>lsb_release -ds</code></td><td><strong>Ubuntu 22.04 ou 24.04 LTS</strong> (24.04 recommandee) : ce sont les seules versions d&#39;Ubuntu supportees par Microsoft pour SQL Server, la <strong>26.04 n&#39;est pas supportee</strong> (<a href=\"https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-setup?view=sql-server-ver17\" target=\"_blank\" rel=\"noopener noreferrer\">Supported platforms</a>). Meme recommandation avec MySQL, PostgreSQL et Oracle, car l&#39;installeur est teste sur ces versions</td></tr><tr><td>GPU NVIDIA (CUDA 12.x + cuDNN 9)</td><td><code>nvidia-smi</code></td><td>Optionnel : accelere le RAG Chatbot (sans GPU il tourne sur CPU)</td></tr></tbody></table><p>&gt; <strong>Sur Windows Server la base de donnees doit etre installee avant.</strong> La ligne unique recupere</p><p>&gt; les composants manquants via <code>winget</code>, absent sur Windows Server : sans une instance deja</p><p>&gt; joignable, l&#39;installation s&#39;arrete avec `No SQL Server instance reachable and winget is</p><p>&gt; missing`. Installe donc le moteur avant de lancer la ligne - SQL Server doit etre **2019 ou</p><p>&gt; superieur<strong> (Express suffit ; </strong>2022 ou superieur** pour le tutoriel <code>.bak</code>), et une 2017</p><p>&gt; n&#39;est pas acceptee. Si l&#39;instance n&#39;est pas celle par defaut, passe-la avec</p><p>&gt; <code>-SqlServer &#39;localhost\\NOMINSTANCE&#39;</code>. Cela vaut pour tous les moteurs, pas seulement SQL Server.</p><h3>1. Telecharger le template de projet</h3><p>Sous Windows, une seule ligne PowerShell fait tout : elle telecharge le paquet, verifie le SDK .NET 10</p><p>et Node.js 22 (en installant ce qui manque), execute <code>dotnet restore</code> et <code>npm install</code>,</p><p>et installe l&#39;extension WUIC Assistant dans VS Code.</p><p>Snippet 1:</p><p>Options utiles sur la meme ligne : <code>-Dbms mysql</code> (ou <code>postgres</code>, <code>oracle</code>) pour un moteur</p><p>autre que SQL Server — l&#39;installeur l&#39;installe et le configure lui-meme — et <code>-WithTutorial</code></p><p>pour telecharger aussi la base de donnees d&#39;exemple.</p><p>Quand c&#39;est termine, le dernier ecran est deja votre liste de taches :</p><p>Snippet 2:</p><p>La chaine de connexion est prete a l&#39;emploi : au premier demarrage le wizard ne demande rien</p><p>d&#39;autre. Avec <code>-Dbms mysql</code> ou <code>-Dbms postgres</code> cette ligne change en consequence et porte en</p><p>elle l&#39;utilisateur et le mot de passe, parce que le mot de passe du superutilisateur est</p><p><strong>genere par l&#39;installeur</strong> ; ce meme mot de passe est enregistre dans <code>wuic-secrets.json</code>, a</p><p>cote de l&#39;installation, et c&#39;est le seul endroit ou il reste ecrit.</p><p>Le chemin manuel reste valable, sur n&#39;importe quel systeme :</p><p>Partez du paquet <code>WuicTest-src-*.zip</code> (lien dans la section <strong>Download</strong> du site).</p><p>Extrayez-le dans un dossier de travail, ex. <code>C:\\dev\\WuicTest</code> (les fichiers vont directement</p><p>a la racine, PAS dans un sous-dossier <code>src/</code>). Le paquet contient :</p><ul><li><code>WuicTest.csproj</code> → projet host avec <code>&lt;PackageReference Include=&quot;WuicCore&quot; Version=&quot;...&quot; /&gt;</code></li><li><code>wwwroot/</code> → app Angular avec <code>package.json</code> qui reference <code>wuic-framework-lib</code> depuis le registre npm</li><li><code>appsettings.json</code> preconfigure en mode <code>firstRun = &quot;true&quot;</code> avec placeholders <code>__SET_*__</code></li><li><code>appsettings-samples/</code> → 6 templates prets (<code>mssql</code>/<code>mysql</code>, firstRun/post-firstRun, <code>Development</code>)</li></ul><p>&gt; <strong>Pas besoin de cloner le repository du framework</strong> : <code>WuicCore</code> arrive comme paquet NuGet</p><p>&gt; depuis <code>nuget.org</code> et <code>wuic-framework-lib</code> comme paquet npm depuis le registre npm. Le source</p><p>&gt; du framework n&#39;est necessaire que si vous voulez le modifier — typiquement pas votre cas.</p><p>&gt; <strong>npm 10.9.x et les paquets anterieurs a la 1.7.1</strong> : ces paquets ne contiennent pas de</p><p>&gt; <code>package-lock.json</code>, et sans lock npm 10.9.x (la version installee par Node 22 LTS) s&#39;arrete avec</p><p>&gt; <code>Cannot read properties of null (reading &#39;edgesOut&#39;)</code> pendant la resolution des peers.</p><p>&gt; Telechargez le lock publie a cote de la release —</p><p>&gt; <code>https://wuic-framework.com/downloads/locks/&lt;nom-du-zip&gt;.package-lock.json</code> — placez-le dans</p><p>&gt; <code>wwwroot/</code> et relancez <code>npm install</code>. La ligne unique <code>-Src</code> le fait pour vous.</p><h3>2. Base de donnees</h3><p>Il faut une instance du moteur joignable. <strong>Avec la ligne unique, rien a faire</strong> : elle</p><p>installe et configure l&#39;instance, et la chaine de connexion a coller dans le wizard est la</p><p>derniere chose qu&#39;elle affiche. Sur le chemin manuel, l&#39;instance doit deja exister.</p><p>Connexions dans <code>appsettings.json</code> :</p><ul><li><code>MetaDataSQLConnection</code> — DB metadata (menu, tables, colonnes, board, utilisateurs)</li><li><code>DataSQLConnection</code> — DB donnees applicatives</li></ul><p>S&#39;il s&#39;agit de la premiere installation (<code>AppSettings.firstRun = &quot;true&quot;</code> dans le template),</p><p>le wizard de scaffolding au premier demarrage cree le schema metadata et peuple le DB donnees.</p><p>Voir la page <em>Scaffolding initial</em> pour le flux guide.</p><h3>3. Backend (.NET)</h3><p>Depuis la racine du dossier extrait (ex. <code>C:\\dev\\WuicTest</code>) :</p><p>Snippet 3:</p><p>Le backend expose les API sur <code>http://localhost:5000</code>.</p><h3>4. Frontend (Angular)</h3><p>Dans un second shell, depuis le sous-dossier <code>wwwroot/</code> :</p><p>Snippet 4:</p><p>Le frontend est disponible sur <code>http://localhost:4200</code>.</p><p>Login par defaut (post-firstRun) : <code>admin</code> / <code>admin</code>.</p><h3>5. RAG Chatbot (optionnel)</h3><p>Le RAG Chatbot (<code>Administration &gt; RAG Chat</code>) tourne <strong>dans le backend .NET</strong> :</p><p>le moteur de retrieval (<code>rag-engine/WuicRagEngine.dll</code>, ONNX Runtime</p><p>in-process) est charge par le backend quand <code>AppSettings.rag-use-dotnet-engine</code></p><p>vaut <code>&quot;true&quot;</code> (valeur par defaut des packages de release). **Pas de Python, pas</p><p>de venv, aucun serveur separe a demarrer.**</p><p>A la <strong>premiere</strong> ouverture du chatbot (ou a la fin du first-run) le backend</p><p>telecharge seul les modeles ONNX (<code>bge-m3</code> + reranker), le tokenizer et</p><p>l&#39;index (~4,5 Go) depuis <code>rag-engine-models-url</code> (par defaut</p><p><code>https://wuic-framework.com/rag-models</code>) dans <code>rag-engine/artifacts/</code>. Une</p><p>connexion internet n&#39;est necessaire qu&#39;une seule fois ; le telechargement</p><p>tourne en arriere-plan (1-5 min) et une notification in-app arrive au debut</p><p>et a la fin. Entre-temps le composant affiche l&#39;etat <strong>RAG offline</strong> et le</p><p>reste de l&#39;application fonctionne normalement.</p><p>Cles <code>AppSettings</code> pertinentes (toutes avec des valeurs par defaut pretes) :</p><ul><li><code>rag-use-dotnet-engine</code> = <code>true</code> — active le moteur .NET (<code>false</code> = fallback Python, voir ci-dessous)</li><li><code>rag-engine-device</code> = <code>auto</code> — <code>auto</code> | <code>cuda</code> | <code>cpu</code> : avec GPU NVIDIA (CUDA 12.x + cuDNN 9) ~1 s/requete, sur CPU ~15-25 s/requete</li><li><code>rag-engine-profile</code> = <code>release</code> — <code>release</code> = sources du framework en signature seulement ; <code>internal</code> = index integral</li><li><code>rag-engine-models-url</code> — source du telechargement au premier demarrage</li><li><code>rag-engine-cuda-path</code> = (vide) — dossier des DLL CUDA/cuDNN si elles ne sont pas installees au niveau systeme</li></ul><p>Pour le chat avec LLM, renseignez <code>rag-llm-provider</code> + <code>rag-llm-api-key</code></p><p>(Claude via Anthropic, ou un modele local via Ollama avec <code>rag-llm-base-url</code>).</p><p>Sans provider, seul le mode retrieval (recherche de snippets) fonctionne.</p><p>Detail des cles sur la page <em>AppSettings</em>.</p><p>&gt; L&#39;ancien stack Python (<code>scripts/rag-setup.ps1</code> + <code>rag_server.py</code> sur</p><p>&gt; <code>127.0.0.1:8765</code>) n&#39;est utilisable qu&#39;en fallback avec</p><p>&gt; <code>rag-use-dotnet-engine = &quot;false&quot;</code> et n&#39;est pas inclus dans les packages de release.</p><h2>Recapitulatif des services</h2><table><thead><tr><th>Service</th><th>Port</th><th>Obligatoire</th><th>Commande rapide</th></tr></thead><tbody><tr><td>SQL Server</td><td>1433</td><td>oui</td><td>(service Windows)</td></tr><tr><td>Backend .NET</td><td>5000</td><td>oui</td><td><code>dotnet watch ... run</code></td></tr><tr><td>Frontend Angular</td><td>4200</td><td>oui</td><td><code>npm run serve:dev</code></td></tr><tr><td>Engine RAG .NET (ONNX)</td><td>in-process</td><td>non</td><td>charge par le backend au premier chat</td></tr></tbody></table><h2>Quick Start — premier composant</h2><p>1. Configurez l&#39;endpoint AsmxProxy.</p><p>2. Definissez la route metadata et les colonnes.</p><p>3. Montez <code>wuic-data-source</code> + <code>wuic-data-repeater</code>.</p><p>Snippet 5:</p>",
+                    "html": "<h1>Panorama du Framework</h1><p>WUIC Framework est une plateforme pilotee par metadata pour creer des interfaces metier de maniere rapide et coherente.</p><h2>Contenu</h2><ul><li>DataSource et DataRepeater pour orchestrer les donnees et le rendu.</li><li>Archetypes visuels (list, map, scheduler, chart, carousel).</li><li>Designer runtime pour les dashboards et les templates dynamiques.</li><li>Workflow designer/runner pour les processus operationnels.</li><li>RAG Chatbot pour interroger la codebase en langage naturel.</li><li>Multi-SGBD : SQL Server, MySQL, PostgreSQL et Oracle via des providers drop-in (<code>dbms</code> : <code>mssql</code> | <code>mysql</code> | <code>postgresql</code> | <code>oracle</code>).</li></ul><h2>First Steps — Demarrage de l&#39;environnement dev</h2><p>La stack WUIC est composee de plusieurs services. Demarrez-les dans l&#39;ordre indique.</p><h3>Prerequis</h3><table><thead><tr><th>Element</th><th>Verification</th><th>Notes</th></tr></thead><tbody><tr><td>.NET 10 SDK</td><td><code>dotnet --version</code></td><td>Hosting Bundle pour IIS en production</td></tr><tr><td>Node.js 22 LTS</td><td><code>node --version</code></td><td>La 22 est la version avec laquelle le paquet est teste ; avec npm 10.9.x l&#39;installation passe grace au <code>package-lock.json</code> inclus</td></tr><tr><td>PowerShell 5.1+</td><td><code>$PSVersionTable.PSVersion</code></td><td>Le Windows PowerShell livre avec Windows suffit : <code>rename-project.ps1</code> et les scripts <code>llm-workspace/</code> fonctionnent aussi sur 5.1. PowerShell 7 est recommande, pas requis</td></tr><tr><td>SQL Server 2019+</td><td><code>sqlcmd -S localhost\\sqlexpress -E -C -Q &quot;SELECT 1&quot;</code></td><td>S&#39;il manque, <strong>la ligne unique l&#39;installe elle-meme</strong> (SQL Server Express, ou le moteur choisi avec <code>-Dbms</code>) ; pas sur Windows Server, voir l&#39;encadre ci-dessous. 2019 suffit pour les packages sans <code>.bak</code> ; le tutoriel <code>.bak</code> est une sauvegarde SQL Server 2022 et exige <strong>2022 ou plus recent</strong></td></tr><tr><td>Linux (installeur <code>install.sh</code>)</td><td><code>lsb_release -ds</code></td><td><strong>Ubuntu 22.04 ou 24.04 LTS</strong> (24.04 recommandee) : ce sont les seules versions d&#39;Ubuntu supportees par Microsoft pour SQL Server, la <strong>26.04 n&#39;est pas supportee</strong> (<a href=\"https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-setup?view=sql-server-ver17\" target=\"_blank\" rel=\"noopener noreferrer\">Supported platforms</a>). Meme recommandation avec MySQL, PostgreSQL et Oracle, car l&#39;installeur est teste sur ces versions</td></tr><tr><td>GPU NVIDIA (CUDA 12.x + cuDNN 9)</td><td><code>nvidia-smi</code></td><td>Optionnel : accelere le RAG Chatbot (sans GPU il tourne sur CPU)</td></tr></tbody></table><p>&gt; <strong>Sur Windows Server la base de donnees doit etre installee avant.</strong> La ligne unique recupere</p><p>&gt; les composants manquants via <code>winget</code>, absent sur Windows Server : sans une instance deja</p><p>&gt; joignable, l&#39;installation s&#39;arrete avec `No SQL Server instance reachable and winget is</p><p>&gt; missing`. Installe donc le moteur avant de lancer la ligne - SQL Server doit etre **2019 ou</p><p>&gt; superieur<strong> (Express suffit ; </strong>2022 ou superieur** pour le tutoriel <code>.bak</code>), et une 2017</p><p>&gt; n&#39;est pas acceptee. Si l&#39;instance n&#39;est pas celle par defaut, passe-la avec</p><p>&gt; <code>-SqlServer &#39;localhost\\NOMINSTANCE&#39;</code>. Cela vaut pour tous les moteurs, pas seulement SQL Server.</p><h3>1. Telecharger le template de projet</h3><p>Sous Windows, une seule ligne PowerShell fait tout : elle telecharge le paquet, verifie le SDK .NET 10</p><p>et Node.js 22 (en installant ce qui manque), execute <code>dotnet restore</code> et <code>npm install</code>,</p><p>et installe l&#39;extension WUIC Assistant dans VS Code.</p><p>Snippet 1:</p><p>Options utiles sur la meme ligne : <code>-Dbms mysql</code> (ou <code>postgres</code>, <code>oracle</code>) pour un moteur</p><p>autre que SQL Server — l&#39;installeur l&#39;installe et le configure lui-meme — et <code>-WithTutorial</code></p><p>pour telecharger aussi la base de donnees d&#39;exemple.</p><p>Quand c&#39;est termine, le dernier ecran est deja votre liste de taches :</p><p>Snippet 2:</p><p>La chaine de connexion est prete a l&#39;emploi : au premier demarrage le wizard ne demande rien</p><p>d&#39;autre. Avec <code>-Dbms mysql</code> ou <code>-Dbms postgres</code> cette ligne change en consequence et porte en</p><p>elle l&#39;utilisateur et le mot de passe, parce que le mot de passe du superutilisateur est</p><p><strong>genere par l&#39;installeur</strong> ; ce meme mot de passe est enregistre dans <code>wuic-secrets.json</code>, a</p><p>cote de l&#39;installation, et c&#39;est le seul endroit ou il reste ecrit.</p><p>Le chemin manuel reste valable, sur n&#39;importe quel systeme :</p><p>Partez du paquet <code>WuicTest-src-*.zip</code> (lien dans la section <strong>Download</strong> du site).</p><p>Extrayez-le dans un dossier de travail, ex. <code>C:\\dev\\WuicTest</code> (les fichiers vont directement</p><p>a la racine, PAS dans un sous-dossier <code>src/</code>). Le paquet contient :</p><ul><li><code>WuicTest.csproj</code> → projet host avec <code>&lt;PackageReference Include=&quot;WuicCore&quot; Version=&quot;...&quot; /&gt;</code></li><li><code>wwwroot/</code> → app Angular avec <code>package.json</code> qui reference <code>wuic-framework-lib</code> depuis le registre npm</li><li><code>appsettings.json</code> preconfigure en mode <code>firstRun = &quot;true&quot;</code> avec placeholders <code>__SET_*__</code></li><li><code>appsettings-samples/</code> → 6 templates prets (<code>mssql</code>/<code>mysql</code>, firstRun/post-firstRun, <code>Development</code>)</li></ul><p>&gt; <strong>Pas besoin de cloner le repository du framework</strong> : <code>WuicCore</code> arrive comme paquet NuGet</p><p>&gt; depuis <code>nuget.org</code> et <code>wuic-framework-lib</code> comme paquet npm depuis le registre npm. Le source</p><p>&gt; du framework n&#39;est necessaire que si vous voulez le modifier — typiquement pas votre cas.</p><p>&gt; <strong>npm 10.9.x et les paquets anterieurs a la 1.7.1</strong> : ces paquets ne contiennent pas de</p><p>&gt; <code>package-lock.json</code>, et sans lock npm 10.9.x (la version installee par Node 22 LTS) s&#39;arrete avec</p><p>&gt; <code>Cannot read properties of null (reading &#39;edgesOut&#39;)</code> pendant la resolution des peers.</p><p>&gt; Telechargez le lock publie a cote de la release —</p><p>&gt; <code>https://wuic-framework.com/downloads/locks/&lt;nom-du-zip&gt;.package-lock.json</code> — placez-le dans</p><p>&gt; <code>wwwroot/</code> et relancez <code>npm install</code>. La ligne unique <code>-Src</code> le fait pour vous.</p><h3>2. Base de donnees</h3><p>Il faut une instance du moteur joignable. <strong>Avec la ligne unique, rien a faire</strong> : elle</p><p>installe et configure l&#39;instance, et la chaine de connexion a coller dans le wizard est la</p><p>derniere chose qu&#39;elle affiche. Sur le chemin manuel, l&#39;instance doit deja exister.</p><p>Connexions dans <code>appsettings.json</code> :</p><ul><li><code>MetaDataSQLConnection</code> — DB metadata (menu, tables, colonnes, board, utilisateurs)</li><li><code>DataSQLConnection</code> — DB donnees applicatives</li></ul><p>S&#39;il s&#39;agit de la premiere installation (<code>AppSettings.firstRun = &quot;true&quot;</code> dans le template),</p><p>le wizard de scaffolding au premier demarrage cree le schema metadata et peuple le DB donnees.</p><p>Voir la page <em>Scaffolding initial</em> pour le flux guide.</p><p>#### Ce que demande le wizard de premier demarrage</p><p>Au premier demarrage l&#39;application n&#39;affiche pas le formulaire de connexion mais la page</p><p><strong>Configuration initiale du projet</strong>. On la remplit une seule fois : a la fin <code>firstRun</code> passe</p><p>a <code>false</code> et la page ne revient plus.</p><ul><li><strong>Mode d&#39;installation</strong> — deux entrees : <strong>Base existante</strong>, qui enregistre une base a vous,</li></ul><p>  et <strong>Tutorial WideWorldImporters</strong>, qui installe la base d&#39;exemple. La seconde n&#39;apparait que</p><p>  si le paquet embarque le tutoriel (<code>tutorialAvailable</code>) : dans les paquets sans tutoriel la</p><p>  liste deroulante n&#39;existe pas et le mode est &quot;Base existante&quot;.</p><ul><li><strong>SGBD</strong> — le moteur. En le changeant, la chaine de connexion ci-dessous est reecrite dans la</li></ul><p>  forme du provider choisi.</p><ul><li><strong>DataSQLConnection</strong> — la chaine vers la base de donnees, et le champ dont depend tout le</li></ul><p>  reste : tant que vous n&#39;avez pas appuye sur <strong>Tester la connexion et charger les bases</strong>, la</p><p>  liste des bases reste desactivee. Le test valide les identifiants, liste les bases du serveur</p><p>  et, sur SQL Server, corrige lui-meme les parametres de certificat</p><p>  (<code>Encrypt=False;TrustServerCertificate=True</code>) en vous le signalant. <code>Integrated Security</code> ne</p><p>  vaut que sur SQL Server : les autres moteurs exigent un utilisateur et un mot de passe.</p><ul><li><strong>Base de donnees</strong> et <strong>Nom de la base de metadonnees</strong> — la premiere se choisit dans la</li></ul><p>  liste chargee par le test (en mode tutoriel c&#39;est un champ libre, <code>WideWorldImporters</code> par</p><p>  defaut) ; la seconde est le nom de la base de metadonnees a creer (<code>metadataDB</code> par defaut,</p><p>  <code>MetadataCRM</code> en mode tutoriel). Si cette base existe deja, le wizard demande confirmation</p><p>  avant de la recreer.</p><ul><li><strong>Generer automatiquement les metadonnees des tables</strong> (uniquement en &quot;Base existante&quot;) —</li></ul><p>  remplit <code>_metadati__tabelle</code> / <code>_metadati__colonne</code> a partir de toutes les tables de la base</p><p>  choisie. C&#39;est ce qui allonge le plus le provisioning sur une base comptant beaucoup de</p><p>  tables.</p><ul><li><strong>Utilisateur administrateur initial</strong> — nom d&#39;utilisateur (<code>admin</code> par defaut), mot de passe</li></ul><p>  (4 caracteres minimum) et langue. Il n&#39;y a pas de mot de passe par defaut : celui saisi ici</p><p>  est le seul qui ouvrira la premiere session. La langue choisie est appliquee a</p><p>  l&#39;administrateur et a cette page elle-meme.</p><ul><li><strong>RAG Chatbot</strong> — uniquement la cle Anthropic, facultative. Rien a installer : voir l&#39;etape 5.</li></ul><p>Une fois <strong>Confirmer et creer la base de metadonnees</strong> presse, le provisioning se deroule seul,</p><p>avec une barre de progression et le nombre de lots traites. Duree mesuree sur les installations</p><p>de test : <strong>30 s - 2 min</strong> en mode tutoriel, <strong>1-4 min</strong> sur une base existante avec la</p><p>generation automatique activee. A la fin, la page laisse place au formulaire de connexion.</p><h3>3. Backend (.NET)</h3><p>Depuis la racine du dossier extrait (ex. <code>C:\\dev\\WuicTest</code>) :</p><p>Snippet 3:</p><p>Le backend expose les API sur <code>http://localhost:5000</code>.</p><h3>4. Frontend (Angular)</h3><p>Dans un second shell, depuis le sous-dossier <code>wwwroot/</code> :</p><p>Snippet 4:</p><p>Le frontend est disponible sur <code>http://localhost:4200</code>.</p><p>Les identifiants sont ceux de l&#39;administrateur choisi dans le wizard de premier demarrage :</p><p>le nom d&#39;utilisateur est <code>admin</code> si vous ne l&#39;avez pas change, et le mot de passe est celui que</p><p>vous avez saisi (il n&#39;y a pas de mot de passe par defaut).</p><h3>5. RAG Chatbot (optionnel)</h3><p>Le RAG Chatbot (<code>Administration &gt; RAG Chat</code>) tourne <strong>dans le backend .NET</strong> :</p><p>le moteur de retrieval (<code>rag-engine/WuicRagEngine.dll</code>, ONNX Runtime</p><p>in-process) est charge par le backend quand <code>AppSettings.rag-use-dotnet-engine</code></p><p>vaut <code>&quot;true&quot;</code> (valeur par defaut des packages de release). **Pas de Python, pas</p><p>de venv, aucun serveur separe a demarrer.**</p><p>A la <strong>premiere</strong> ouverture du chatbot (ou a la fin du first-run) le backend</p><p>telecharge seul les modeles ONNX (<code>bge-m3</code> + reranker), le tokenizer et</p><p>l&#39;index (~4,5 Go) depuis <code>rag-engine-models-url</code> (par defaut</p><p><code>https://wuic-framework.com/rag-models</code>) dans <code>rag-engine/artifacts/</code>. Une</p><p>connexion internet n&#39;est necessaire qu&#39;une seule fois ; le telechargement</p><p>tourne en arriere-plan (1-5 min) et une notification in-app arrive au debut</p><p>et a la fin. Entre-temps le composant affiche l&#39;etat <strong>RAG offline</strong> et le</p><p>reste de l&#39;application fonctionne normalement.</p><p>Cles <code>AppSettings</code> pertinentes (toutes avec des valeurs par defaut pretes) :</p><ul><li><code>rag-use-dotnet-engine</code> = <code>true</code> — active le moteur .NET (<code>false</code> = fallback Python, voir ci-dessous)</li><li><code>rag-engine-device</code> = <code>auto</code> — <code>auto</code> | <code>cuda</code> | <code>cpu</code> : avec GPU NVIDIA (CUDA 12.x + cuDNN 9) ~1 s/requete, sur CPU ~15-25 s/requete</li><li><code>rag-engine-profile</code> = <code>release</code> — <code>release</code> = sources du framework en signature seulement ; <code>internal</code> = index integral</li><li><code>rag-engine-models-url</code> — source du telechargement au premier demarrage</li><li><code>rag-engine-cuda-path</code> = (vide) — dossier des DLL CUDA/cuDNN si elles ne sont pas installees au niveau systeme</li></ul><p>Pour le chat avec LLM, renseignez <code>rag-llm-provider</code> + <code>rag-llm-api-key</code></p><p>(Claude via Anthropic, ou un modele local via Ollama avec <code>rag-llm-base-url</code>).</p><p>Sans provider, seul le mode retrieval (recherche de snippets) fonctionne.</p><p>Detail des cles sur la page <em>AppSettings</em>.</p><p>&gt; L&#39;ancien stack Python (<code>scripts/rag-setup.ps1</code> + <code>rag_server.py</code> sur</p><p>&gt; <code>127.0.0.1:8765</code>) n&#39;est utilisable qu&#39;en fallback avec</p><p>&gt; <code>rag-use-dotnet-engine = &quot;false&quot;</code> et n&#39;est pas inclus dans les packages de release.</p><h2>Recapitulatif des services</h2><table><thead><tr><th>Service</th><th>Port</th><th>Obligatoire</th><th>Commande rapide</th></tr></thead><tbody><tr><td>SQL Server</td><td>1433</td><td>oui</td><td>(service Windows)</td></tr><tr><td>Backend .NET</td><td>5000</td><td>oui</td><td><code>dotnet watch ... run</code></td></tr><tr><td>Frontend Angular</td><td>4200</td><td>oui</td><td><code>npm run serve:dev</code></td></tr><tr><td>Engine RAG .NET (ONNX)</td><td>in-process</td><td>non</td><td>charge par le backend au premier chat</td></tr></tbody></table><h2>Quick Start — premier composant</h2><p>1. Configurez l&#39;endpoint AsmxProxy.</p><p>2. Definissez la route metadata et les colonnes.</p><p>3. Montez <code>wuic-data-source</code> + <code>wuic-data-repeater</code>.</p><p>Snippet 5:</p><h2>Les premieres listes affichent 20 enregistrements : c&#39;est le mode Trial</h2><p>Une installation neuve fonctionne <strong>sans licence</strong>, donc en mode Trial, et dans ce mode</p><p><strong>chaque requete est limitee a 20 enregistrements</strong>. Ce n&#39;est ni une anomalie ni une limite</p><p>de la base de donnees : une liste qui affiche &quot;20 sur 20&quot; sur une table de plusieurs milliers</p><p>de lignes tourne tout simplement sans licence.</p><p>Comment le confirmer en une seconde :</p><p>Snippet 6:</p><p><code>licenseValid: false</code> confirme le mode Trial, et <code>licenseReason</code> en donne la raison</p><p>(<code>invalid_signature</code>, <code>license_expired</code>, <code>machine_fingerprint_not_authorized</code>, ...).</p><p>Comment en sortir : on colle la licence depuis <strong>Administration &gt; Editeur AppSettings</strong>, onglet</p><p>Licensing, et elle prend effet immediatement - aucun redemarrage du backend n&#39;est necessaire.</p><p>Les details, y compris les limites que le mode Trial impose au-dela du nombre</p><p>d&#39;enregistrements, se trouvent sur la page <a href=\"licensing.md\">Licensing</a>.</p>",
                     "codeSamples": [
                         {
                             "id": "code_1",
@@ -14581,25 +14621,31 @@ const frameworkDocsContent = {
                             "id": "code_2",
                             "title": "Snippet 2",
                             "language": "text",
-                            "code": "Developer workspace ready: C:\\Users\\<user>\\AppData\\Local\\WUIC\\app\r\n\r\n  code \"C:\\Users\\<user>\\AppData\\Local\\WUIC\\app\\WuicTest.code-workspace\"\r\n  then F5 > 'Fullstack: WuicTest + Chrome' (backend http://localhost:5000, frontend http://localhost:4200)\r\n\r\nFirst start opens the first-run wizard: paste this connection string (Windows authentication)\r\n  Data Source=localhost\\SQLEXPRESS;Integrated Security=SSPI;Initial Catalog=WuicData;Encrypt=False;TrustServerCertificate=True\r\nRename the project: .\\rename-project.ps1 -Name MyApp"
+                            "code": "Developer workspace ready: C:\\Users\\<user>\\AppData\\Local\\WUIC\\app\n\n  code \"C:\\Users\\<user>\\AppData\\Local\\WUIC\\app\\WuicTest.code-workspace\"\n  then F5 > 'Fullstack: WuicTest + Chrome' (backend http://localhost:5000, frontend http://localhost:4200)\n\nFirst start opens the first-run wizard: paste this connection string (Windows authentication)\n  Data Source=localhost\\SQLEXPRESS;Integrated Security=SSPI;Initial Catalog=WuicData;Encrypt=False;TrustServerCertificate=True\nRename the project: .\\rename-project.ps1 -Name MyApp"
                         },
                         {
                             "id": "code_3",
                             "title": "Snippet 3",
                             "language": "powershell",
-                            "code": "# Premiere fois : restore des paquets NuGet (pulls WuicCore + deps depuis nuget.org, ~30 s)\r\ndotnet restore\r\n\r\n# Demarrage dev avec hot reload\r\n$env:ASPNETCORE_ENVIRONMENT = 'Development'\r\ndotnet watch run\r\n\r\n# Ou demarrage one-shot (sans hot reload)\r\ndotnet run"
+                            "code": "# Premiere fois : restore des paquets NuGet (pulls WuicCore + deps depuis nuget.org, ~30 s)\ndotnet restore\n\n# Demarrage dev avec hot reload\n$env:ASPNETCORE_ENVIRONMENT = 'Development'\ndotnet watch run\n\n# Ou demarrage one-shot (sans hot reload)\ndotnet run"
                         },
                         {
                             "id": "code_4",
                             "title": "Snippet 4",
                             "language": "powershell",
-                            "code": "cd wwwroot\r\n\r\n# Premiere fois : restore des dependances npm (pulls wuic-framework-lib depuis npm registry, ~2 min)\r\nnpm install\r\n\r\n# Demarrage dev server\r\nnpm run serve:dev"
+                            "code": "cd wwwroot\n\n# Premiere fois : restore des dependances npm (pulls wuic-framework-lib depuis npm registry, ~2 min)\nnpm install\n\n# Demarrage dev server\nnpm run serve:dev"
                         },
                         {
                             "id": "code_5",
                             "title": "Snippet 5",
                             "language": "html",
-                            "code": "<wuic-data-source [hardcodedRoute]=\"'cities'\"></wuic-data-source>\r\n<wuic-data-repeater [hardcodedAction]=\"'list'\"></wuic-data-repeater>"
+                            "code": "<wuic-data-source [hardcodedRoute]=\"'cities'\"></wuic-data-source>\n<wuic-data-repeater [hardcodedAction]=\"'list'\"></wuic-data-repeater>"
+                        },
+                        {
+                            "id": "code_6",
+                            "title": "Snippet 6",
+                            "language": "bash",
+                            "code": "curl -s http://localhost:5000/api/Meta/LicenseStatus"
                         }
                     ]
                 }
@@ -14634,18 +14680,22 @@ const frameworkDocsContent = {
             "toc": [
                 {
                     "id": "sec_1",
-                    "title": "Quand l'utiliser"
+                    "title": "Avec un paquet tutoriel il n'y a rien a scaffolder"
                 },
                 {
                     "id": "sec_2",
-                    "title": "Comportement avec firstRun=true"
+                    "title": "Quand l'utiliser"
                 },
                 {
                     "id": "sec_3",
-                    "title": "Operations typiques"
+                    "title": "Comportement avec firstRun=true"
                 },
                 {
                     "id": "sec_4",
+                    "title": "Operations typiques"
+                },
+                {
+                    "id": "sec_5",
                     "title": "Apres le provisionnement"
                 }
             ],
@@ -14653,7 +14703,7 @@ const frameworkDocsContent = {
                 {
                     "id": "overview",
                     "title": "Overview",
-                    "html": "<h1>Scaffolding initial</h1><p>Cette page decrit le bootstrap initial lorsque <code>AppSettings.firstRun = true</code>.</p><h2>Quand l&#39;utiliser</h2><ul><li>Nouvelle installation (base de donnees metadata/donnees pas encore prete).</li><li>Environnement local a realigner avec le setup initial.</li><li>Premier demarrage apres un deploiement ou vous souhaitez forcer la procedure guidee de provisionnement.</li></ul><h2>Comportement avec firstRun=true</h2><ul><li>L&#39;endpoint <code>GET /api/Meta/FirstRunStatus</code> expose <code>firstRun: true</code>.</li><li>Au login apparait le flux de premier demarrage (ex. action <code>Aggiorna</code> dans l&#39;ecran).</li><li>Le setup applique les configurations de base (connexions, parametres runtime, bootstrap metadata).</li></ul><h2>Operations typiques</h2><ul><li>Verifier que <code>AppSettings.firstRun</code> est a <code>true</code> dans <code>appsettings.{Environment}.json</code> de l&#39;hote que vous executez.</li><li>Demarrer l&#39;application et completer la procedure de scaffolding initial depuis l&#39;interface.</li><li>Controler que les connexions et parametres principaux sont coherents (<code>dbms</code>, <code>DataDBName</code>, <code>ConnectionStrings</code>).</li></ul><h2>Apres le provisionnement</h2><ul><li>La procedure de setup met <code>firstRun</code> a <code>false</code> pour eviter les re-executions a chaque demarrage.</li><li>Effectuer un login standard et valider l&#39;acces aux routes principales.</li></ul>",
+                    "html": "<h1>Scaffolding initial</h1><p>Cette page decrit le bootstrap initial lorsque <code>AppSettings.firstRun = true</code>.</p><h2>Avec un paquet tutoriel il n&#39;y a rien a scaffolder</h2><p>Le scaffolding dont parle cette page — lire les tables d&#39;une base et les enregistrer dans</p><p><code>_metadati__tabelle</code> / <code>_metadati__colonne</code> — ne concerne <strong>que</strong> le mode &quot;Base existante&quot; du</p><p>wizard de premier demarrage : c&#39;est la que se trouve la case *Generer automatiquement les</p><p>metadonnees des tables de la base choisie*.</p><p>Dans les paquets <strong>tutoriel</strong> cette case n&#39;existe pas. La base de metadonnees arrive deja</p><p>remplie (routes, colonnes, menu, traductions, tableaux de bord d&#39;exemple) et le wizard se</p><p>contente de la restaurer et de creer l&#39;utilisateur administrateur. Voir des routes toutes</p><p>pretes juste apres le premier demarrage n&#39;est donc pas le resultat d&#39;un scaffolding : c&#39;est le</p><p>contenu du tutoriel.</p><table><thead><tr><th>Mode du wizard</th><th>Ce qui arrive aux metadonnees</th></tr></thead><tbody><tr><td>Tutorial WideWorldImporters</td><td>Metadonnees deja construites, restaurees depuis le paquet. Aucun scaffolding.</td></tr><tr><td>Base existante, case decochee</td><td>Base de metadonnees vide : les routes s&#39;enregistrent a la main, ou plus tard depuis la page Scaffolding.</td></tr><tr><td>Base existante, case cochee</td><td>En fin d&#39;installation, chaque table de la base choisie est enregistree comme route.</td></tr></tbody></table><p>Le reste de cette page concerne les deux dernieres lignes de ce tableau.</p><h2>Quand l&#39;utiliser</h2><ul><li>Nouvelle installation (base de donnees metadata/donnees pas encore prete).</li><li>Environnement local a realigner avec le setup initial.</li><li>Premier demarrage apres un deploiement ou vous souhaitez forcer la procedure guidee de provisionnement.</li></ul><h2>Comportement avec firstRun=true</h2><ul><li>L&#39;endpoint <code>GET /api/Meta/FirstRunStatus</code> expose <code>firstRun: true</code>.</li><li>Au login apparait le flux de premier demarrage (ex. action <code>Aggiorna</code> dans l&#39;ecran).</li><li>Le setup applique les configurations de base (connexions, parametres runtime, bootstrap metadata).</li></ul><h2>Operations typiques</h2><ul><li>Verifier que <code>AppSettings.firstRun</code> est a <code>true</code> dans <code>appsettings.{Environment}.json</code> de l&#39;hote que vous executez.</li><li>Demarrer l&#39;application et completer la procedure de scaffolding initial depuis l&#39;interface.</li><li>Controler que les connexions et parametres principaux sont coherents (<code>dbms</code>, <code>DataDBName</code>, <code>ConnectionStrings</code>).</li></ul><h2>Apres le provisionnement</h2><ul><li>La procedure de setup met <code>firstRun</code> a <code>false</code> pour eviter les re-executions a chaque demarrage.</li><li>Effectuer un login standard et valider l&#39;acces aux routes principales.</li></ul>",
                     "codeSamples": []
                 }
             ],
@@ -14712,7 +14762,7 @@ const frameworkDocsContent = {
                 {
                     "id": "overview",
                     "title": "Overview",
-                    "html": "<h1>Licensing</h1><p>Cette page explique le licensing du point de vue de l&#39;utilisateur final : ce qui est necessaire, comment obtenir la licence et comment l&#39;appliquer.</p><h2>Comment obtenir une licence</h2><p>Consultez les plans, les fonctionnalites incluses par niveau (Developer / Professional / Software House) et procedez a l&#39;achat sur le site public :</p><ul><li><a href=\"https://wuic-framework.com/pricing\" target=\"_blank\" rel=\"noopener noreferrer\">Tarifs et plans WUIC — wuic-framework.com/pricing</a></li><li><a href=\"mailto:licensing@wuic-framework.com\">Contact commercial</a> — aucune licence n&#39;est requise pour evaluer : sans licence le framework tourne en mode Trial (20 enregistrements par requete)</li><li><a href=\"https://wuic-framework.com\" target=\"_blank\" rel=\"noopener noreferrer\">Page d&#39;accueil WUIC</a></li></ul><p>Apres l&#39;achat, vous recevrez un email avec <code>license-payload</code> + <code>license-signature</code> a installer comme decrit dans la &quot;Procedure utilisateur final&quot; ci-dessous.</p><h2>Comment ca fonctionne</h2><ul><li>La licence n&#39;est valide que si :</li><li>la signature est correcte.</li><li>le <code>machineFingerprint</code> du serveur courant est present dans la liste <code>machineFingerprints</code> du payload signe.</li><li>Si la licence n&#39;est pas valide, la lecture des donnees (<code>getFlatRecordData</code>) est limitee a un maximum de 20 enregistrements. De plus, le hook hote <code>customizeSelect</code> est contourne (non invoque).</li></ul><h2>Ou trouver le machineFingerprint</h2><p>Endpoint backend :</p><ul><li><code>GET /api/Meta/LicenseStatus</code> → champ <code>machineFingerprint</code> (toujours disponible, meme sans licence).</li><li>Pendant le first-run, <code>GET /api/Meta/FirstRunStatus</code> l&#39;expose aussi.</li></ul><p>Note : le fichier local <code>installation.id</code> n&#39;est plus utilise par le licensing.</p><h2>Procedure utilisateur final</h2><p>1. Recuperez le <code>machineFingerprint</code> de votre hote.</p><p>2. Envoyez la valeur au fournisseur/licencieur.</p><p>3. Recevez les valeurs de licence :</p><ul><li><code>license-payload</code></li><li><code>license-signature</code></li><li><code>license-public-key-pem</code> (si prevu par votre installation)</li></ul><p>4. Inserez les valeurs dans le fichier <code>appsettings.{Environment}.json</code> de l&#39;hote en execution, section <code>AppSettings</code>.</p><p>5. Redemarrez le backend.</p><p>6. Verifiez le statut de la licence via l&#39;API :</p><ul><li><code>GET /api/Meta/LicenseStatus</code></li><li>attendu : <code>licenseValid = true</code>.</li></ul><h2>Licence multi-machine</h2><p>Une seule licence peut autoriser plusieurs machines en incluant plusieurs valeurs dans <code>machineFingerprints</code>.</p><h2>Depannage rapide</h2><ul><li><code>licenseReason = invalid_signature</code> :</li><li>payload/signature non coherents entre eux ou cle publique differente.</li><li><code>licenseReason = machine_fingerprint_not_authorized</code> :</li><li>le fingerprint de la machine courante n&#39;est pas present dans la licence recue.</li><li><code>licenseReason = machine_fingerprint_missing</code> :</li><li>le runtime ne parvient pas a calculer le fingerprint local.</li><li><code>licenseReason = license_expired</code> :</li><li>la licence a expire, demandez un renouvellement.</li></ul>",
+                    "html": "<h1>Licensing</h1><p>Cette page explique le licensing du point de vue de l&#39;utilisateur final : ce qui est necessaire, comment obtenir la licence et comment l&#39;appliquer.</p><h2>Comment obtenir une licence</h2><p>Consultez les plans, les fonctionnalites incluses par niveau (Developer / Professional / Software House) et procedez a l&#39;achat sur le site public :</p><ul><li><a href=\"https://wuic-framework.com/pricing\" target=\"_blank\" rel=\"noopener noreferrer\">Tarifs et plans WUIC — wuic-framework.com/pricing</a></li><li><a href=\"mailto:licensing@wuic-framework.com\">Contact commercial</a> — aucune licence n&#39;est requise pour evaluer : sans licence le framework tourne en mode Trial (20 enregistrements par requete)</li><li><a href=\"https://wuic-framework.com\" target=\"_blank\" rel=\"noopener noreferrer\">Page d&#39;accueil WUIC</a></li></ul><p>Apres l&#39;achat, vous recevrez un email avec <code>license-payload</code> + <code>license-signature</code> a installer comme decrit dans la &quot;Procedure utilisateur final&quot; ci-dessous.</p><h2>Comment ca fonctionne</h2><ul><li>La licence n&#39;est valide que si :</li><li>la signature est correcte.</li><li>le <code>machineFingerprint</code> du serveur courant est present dans la liste <code>machineFingerprints</code> du payload signe.</li><li>Si la licence n&#39;est pas valide, la lecture des donnees (<code>getFlatRecordData</code>) est limitee a un maximum de 20 enregistrements. De plus, le hook hote <code>customizeSelect</code> est contourne (non invoque).</li></ul><h2>Ou trouver le machineFingerprint</h2><p>Endpoint backend :</p><ul><li><code>GET /api/Meta/LicenseStatus</code> → champ <code>machineFingerprint</code> (toujours disponible, meme sans licence).</li><li>Pendant le first-run, <code>GET /api/Meta/FirstRunStatus</code> l&#39;expose aussi.</li></ul><p>Note : le fichier local <code>installation.id</code> n&#39;est plus utilise par le licensing.</p><h2>Procedure utilisateur final</h2><p>1. Recuperez le <code>machineFingerprint</code> de votre hote.</p><p>2. Envoyez la valeur au fournisseur/licencieur.</p><p>3. Recevez les valeurs de licence :</p><ul><li><code>license-payload</code></li><li><code>license-signature</code></li><li><code>license-public-key-pem</code> (si prevu par votre installation)</li></ul><p>4. Collez les valeurs depuis l&#39;interface : <strong>Administration &gt; Editeur AppSettings</strong>, section</p><p>   <strong>License</strong> (champs <code>License email</code>, <code>License payload</code>, <code>License signature</code>,</p><p>   <code>Public key (PEM)</code>), puis enregistrez. On peut aussi les ecrire a la main dans la section</p><p>   <code>AppSettings</code> du fichier <code>appsettings.{Environment}.json</code> de l&#39;hote en cours d&#39;execution.</p><p>5. Verifiez le statut de la licence :</p><ul><li>via l&#39;API : <code>GET /api/Meta/LicenseStatus</code>, attendu <code>licenseValid = true</code> ;</li><li>ou depuis la page elle-meme, qui relit la licence juste apres l&#39;enregistrement.</li></ul><p><strong>Aucun redemarrage du backend n&#39;est necessaire si vous passez par l&#39;editeur.</strong> En enregistrant</p><p><code>license-payload</code> / <code>license-signature</code> depuis l&#39;Editeur AppSettings, le backend recharge</p><p>lui-meme le service de validation et la licence s&#39;applique des la requete suivante. Le</p><p>redemarrage n&#39;est requis que dans l&#39;autre cas, quand les valeurs sont ecrites a la main dans le</p><p>fichier : celui-ci est relu au demarrage.</p><h2>Licence multi-machine</h2><p>Une seule licence peut autoriser plusieurs machines en incluant plusieurs valeurs dans <code>machineFingerprints</code>.</p><h2>Depannage rapide</h2><ul><li><code>licenseReason = invalid_signature</code> :</li><li>payload/signature non coherents entre eux ou cle publique differente.</li><li><code>licenseReason = machine_fingerprint_not_authorized</code> :</li><li>le fingerprint de la machine courante n&#39;est pas present dans la licence recue.</li><li><code>licenseReason = machine_fingerprint_missing</code> :</li><li>le runtime ne parvient pas a calculer le fingerprint local.</li><li><code>licenseReason = license_expired</code> :</li><li>la licence a expire, demandez un renouvellement.</li></ul>",
                     "codeSamples": []
                 }
             ],
@@ -15387,42 +15437,46 @@ const frameworkDocsContent = {
                 },
                 {
                     "id": "sec_2",
-                    "title": "Reference de capture d'ecran (manuel utilisateur)"
+                    "title": "Ce que la toolbar affiche par defaut"
                 },
                 {
                     "id": "sec_3",
-                    "title": "Metadonnees inline editing"
+                    "title": "Reference de capture d'ecran (manuel utilisateur)"
                 },
                 {
                     "id": "sec_4",
-                    "title": "Barre d'outils export/import"
+                    "title": "Metadonnees inline editing"
                 },
                 {
                     "id": "sec_5",
-                    "title": "Config metadata"
+                    "title": "Barre d'outils export/import"
                 },
                 {
                     "id": "sec_6",
-                    "title": "md_props_bag: toolbar"
+                    "title": "Config metadata"
                 },
                 {
                     "id": "sec_7",
-                    "title": "md_props_bag: archetypes.list"
+                    "title": "md_props_bag: toolbar"
                 },
                 {
                     "id": "sec_8",
-                    "title": "Pagination : md_pagesize et md_page_size_choice"
+                    "title": "md_props_bag: archetypes.list"
                 },
                 {
                     "id": "sec_9",
-                    "title": "Activation forcee de la virtualisation sur une taille de page elevee"
+                    "title": "Pagination : md_pagesize et md_page_size_choice"
                 },
                 {
                     "id": "sec_10",
-                    "title": "Evenements et subscriptions (host)"
+                    "title": "Activation forcee de la virtualisation sur une taille de page elevee"
                 },
                 {
                     "id": "sec_11",
+                    "title": "Evenements et subscriptions (host)"
+                },
+                {
+                    "id": "sec_12",
                     "title": "`rowCustomSelect` — signature reelle (piege)"
                 }
             ],
@@ -15430,7 +15484,7 @@ const frameworkDocsContent = {
                 {
                     "id": "overview",
                     "title": "Overview",
-                    "html": "<h1>List Grid</h1><p>Composant principal pour les listes tabulaires avec filtres, tri, pagination cote serveur et actions sur les lignes.</p><h2>Cas d&#39;utilisation</h2><ul><li>CRUD tabulaires enterprise.</li><li>Rapports operationnels avec filtres multi-colonnes.</li><li>Jeux de donnees tres volumineux avec <code>cursorMode</code>.</li></ul><h2>Reference de capture d&#39;ecran (manuel utilisateur)</h2><ul><li><code>manual__grid__01.png</code> : mode <code>inline cell edit</code> dans list-grid.</li><li><code>manual__grid__02.png</code> : mode <code>inline edit</code> (au niveau ligne) dans list-grid.</li></ul><h2>Metadonnees inline editing</h2><p>Configuration dans le <code>md_props_bag</code> de la table metadata :</p><ul><li><code>md_inline_edit</code></li></ul><p>  - active l&#39;edition inline de la ligne dans list-grid (cellules editables dans le contexte de la ligne, sans ouverture de popup).</p><p>  - utile lorsque vous souhaitez conserver l&#39;UX tabulaire avec une edition rapide par enregistrement.</p><ul><li><code>md_inline_cell_edit</code></li></ul><p>  - active l&#39;edition inline &quot;cellule par cellule&quot; (focus sur la cellule individuelle).</p><p>  - note : dans les configurations legacy, il peut apparaitre sous le nom <code>md_inline_cell_editing</code> ; le comportement runtime est le meme.</p><p>  - <strong>promotion runtime</strong> : lorsque <code>md_inline_cell_edit</code> est <code>true</code>, le composant force</p><p>    a runtime egalement <code>md_inline_edit = true</code> independamment de la valeur en DB.</p><p>    Les deux UX necessitent que la colonne d&#39;actions soit visible, elles sont donc mutuellement</p><p>    non exclusives au niveau du rendu.</p><ul><li><code>md_batch_save</code></li></ul><p>  - active la sauvegarde batch des modifications en attente (<code>Save changes</code> / <code>Cancel changes</code>).</p><p>  - si utilise conjointement avec inline-cell, les modifications restent en attente jusqu&#39;a la sauvegarde explicite.</p><p>  - <strong>prerequis</strong> : <code>md_batch_save</code> n&#39;a d&#39;effet <strong>que</strong> si <code>md_inline_cell_edit</code> est <code>true</code>.</p><p>    Avec <code>md_inline_cell_edit:false</code>, le flag est ignore a runtime et les boutons</p><p>    &quot;Sauvegarder les modifications / Annuler les modifications&quot; ne sont pas affiches.</p><h3>Combinaisons valides</h3><table><thead><tr><th><code>md_inline_edit</code></th><th><code>md_inline_cell_edit</code></th><th><code>md_batch_save</code></th><th>Resultat runtime</th></tr></thead><tbody><tr><td><code>true</code></td><td><code>false</code></td><td>quelconque</td><td>Edition inline au niveau ligne avec crayon. <code>md_batch_save</code> ignore.</td></tr><tr><td><code>false</code></td><td><code>true</code></td><td><code>false</code></td><td>Autosave cellule par cellule au blur. <code>md_inline_edit</code> force a <code>true</code> a runtime.</td></tr><tr><td><code>false</code></td><td><code>true</code></td><td><code>true</code></td><td>Cellule par cellule avec buffer en attente + barre d&#39;outils <code>Sauvegarder / Annuler les modifications</code>.</td></tr><tr><td><code>false</code></td><td><code>false</code></td><td>quelconque</td><td>Aucune edition inline. <code>md_batch_save</code> ignore.</td></tr></tbody></table><p>Exemple edition inline au niveau ligne :</p><p>Snippet 1:</p><p>Exemple cellule par cellule avec sauvegarde batch :</p><p>Snippet 2:</p><h2>Barre d&#39;outils export/import</h2><ul><li>Export XLS :</li></ul><p>  - affiche une boite de dialogue de progression avec pourcentage en temps reel ;</p><p>  - actions : <code>Continuer en arriere-plan</code>, <code>Annuler la tache</code>, <code>Interrompre et telecharger le partiel</code> ;</p><p>  - en arriere-plan, cree une notification avec progression ; un clic rouvre la boite de dialogue.</p><ul><li>Import XLS/XLSX (si <code>md_importable = true</code>) :</li></ul><p>  - boite de dialogue de progression apres la confirmation ;</p><p>  - actions : <code>Continuer en arriere-plan</code>, <code>Annuler l&#39;import (rollback)</code>, <code>Arreter et commit partiel</code> ;</p><p>  - a la fin de l&#39;import, cree une notification recapitulative qui redirige vers la route.</p><h2>Config metadata</h2><p>Parametres cles dans <code>md_props_bag</code> et metadonnees de colonnes.</p><p>Snippet 3:</p><h2>md_props_bag: toolbar</h2><p>Flags opt-in qui masquent des blocs de la barre d&#39;outils de la list-grid (<code>caption-bar</code>). Tous sous <code>md_props_bag.toolbar.*</code> (parse au runtime comme <code>tableMetadata.extraProps.toolbar</code>).</p><p>Snippet 4:</p><ul><li><code>hideManageState</code> (boolean, defaut <code>false</code>) : masque dans la <strong>caption-right</strong> le bouton &quot;Gestion etat&quot; (icone bookmark) + le <code>&lt;select&gt;</code> des etats enregistres. Utile pour les routes hardcoded / demo ou la fonctionnalite saved-state (persistance par <code>user_id</code> + route via <code>MetaService</code>) n&#39;a pas de sens — par ex. Pattern 3 pur OData sans route metadata enregistree.</li><li><code>hideBatchActions</code> (boolean, defaut <code>false</code>) : masque dans la <strong>caption-left</strong> les boutons &quot;Enregistrer les modifications&quot; (<code>pi-save</code>) + &quot;Annuler les modifications&quot; (<code>pi-times</code>) + l&#39;indicateur de comptage des changements (<code>grid-changes-indicator</code>, badge pencil + count). Generes par le framework quand <code>md_inline_cell_editing</code> + <code>md_batch_save</code> sont actifs. Concu pour les <strong>grids imbriquees dans un parametric-dialog</strong> : le save/cancel du parent persiste le master + les lignes en un seul coup via le batch save framework, et les boutons en double sur la grid imbriquee perturbent l&#39;UX.</li></ul><p>Exemple de lignes imbriquees dans un edit-form custom (patch runtime) :</p><p>Snippet 5:</p><p>Type TS dans <a href=\"../api/wuic-framework-lib.metadatitabella.html\">`metadati_tabella.ts`</a> (propriete <code>extraProps.toolbar</code>). Les flags ne desactivent PAS la logique <code>md_batch_save</code> sous-jacente (les changements restent traces) ; ils suppriment uniquement l&#39;UI de la barre d&#39;outils — le save effectif passe par le flux du parent.</p><h2>md_props_bag: archetypes.list</h2><p>Le composant lit <code>md_props_bag.archetypes.list</code>.</p><p>Snippet 6:</p><ul><li><code>proportionalColwidth</code> :</li><li>type : boolean (avec parser tolerant)</li><li>valeurs acceptees : <code>true</code>, <code>false</code>, <code>1</code>, <code>0</code>, <code>&quot;true&quot;</code>, <code>&quot;false&quot;</code>, <code>&quot;1&quot;</code>, <code>&quot;0&quot;</code></li><li>valeur par defaut runtime : <code>true</code> lorsqu&#39;absent ou vide</li><li>effet : distribue les largeurs de colonnes en pourcentage (au lieu de px) lorsqu&#39;il n&#39;y a pas de largeurs utilisateur persistees.</li></ul><ul><li><code>virtualize</code> :</li><li>type : <code>boolean</code> ou <code>object</code></li><li>valeurs acceptees :</li><li><code>true</code>/<code>false</code>, <code>1</code>/<code>0</code>, <code>&quot;true&quot;</code>/<code>&quot;false&quot;</code>, <code>&quot;1&quot;</code>/<code>&quot;0&quot;</code></li><li>object avec <code>enabled</code> (optionnel) et <code>itemSize</code> (optionnel)</li><li>valeur par defaut runtime : desactive (<code>false</code>) lorsqu&#39;absent</li><li><code>enabled</code> :</li><li>par defaut : <code>true</code> si le noeud <code>virtualize</code> est un objet sans <code>enabled</code>, sinon parser tolerant</li><li>effet : active <code>virtualScroll</code> sur <code>p-table</code></li><li><code>itemSize</code> :</li><li>par defaut : <code>44</code></li><li>effet : definit <code>virtualScrollItemSize</code> (hauteur de la ligne virtuelle en px)</li></ul><ul><li><code>advancedFilter</code> :</li><li>type : boolean (avec parser tolerant)</li><li>valeur par defaut runtime : <code>false</code></li><li>effet :</li><li>lorsque <code>true</code>, la grille masque les icones de filtre de colonne (<code>p-columnFilter</code>) et utilise la <code>wuic-filter-bar</code> au-dessus de la table (au niveau <code>data-repeater</code>/<code>bounded-repeater</code>) pour appliquer les filtres.</li></ul><p>Note operationnelle :</p><ul><li>le suggest <code>md_props_bag</code> dans le metadata editor expose egalement le noeud cochable <code>archetypes.list.advancedFilter</code>.</li></ul><h2>Pagination : md_pagesize et md_page_size_choice</h2><p>La grille utilise <code>md_pagesize</code> comme taille de page par defaut et <code>md_page_size_choice</code> comme liste de valeurs selectionnables dans le paginateur.</p><p>Regles runtime :</p><ul><li>si <code>md_pagesize</code> est superieur a la valeur maximale presente dans <code>md_page_size_choice</code>, le framework ajoute automatiquement <code>md_pagesize</code> a la liste d&#39;options ;</li><li>la liste est normalisee (nombres valides, deduplication, tri croissant).</li></ul><p>Exemple :</p><ul><li><code>md_pagesize = 200</code></li><li><code>md_page_size_choice = &quot;10,25,50,100&quot;</code></li><li>resultat runtime : <code>10,25,50,100,200</code></li></ul><h2>Activation forcee de la virtualisation sur une taille de page elevee</h2><p>Lorsque l&#39;utilisateur selectionne dans le paginateur une valeur <code>pageSize &gt;= 1000</code> :</p><ul><li>la virtualisation est forcee automatiquement meme si <code>md_props_bag.archetypes.list.virtualize</code> est absent ou desactive ;</li><li><code>virtualScrollItemSize</code> est force a la valeur par defaut <code>44</code>.</li></ul><p>Ce comportement protege le rendu de la table sur des pages tres volumineuses.</p><h2>Evenements et subscriptions (host)</h2><p><code>wuic-list-grid</code> expose des evenements runtime utiles pour intercepter le cycle de rendu et les callbacks p-table cote projet host.</p><p>Evenements disponibles :</p><ul><li><code>onAfterRender</code> : emis a la fin du binding des donnees de la grille (<code>rows</code>, <code>totalRecords</code>, <code>metaInfo</code>, <code>datasource</code>).</li><li><code>onBeforeRowRender</code> : emis avant le rendu logique de la ligne individuelle ; supporte l&#39;annulation via <code>event.cancelRender()</code>.</li><li><code>onAfterRowRender</code> : emis apres le rendu logique de la ligne individuelle.</li><li><code>onPaging</code> : emis sur les evenements de pagination (<code>p-table onPage</code>).</li><li><code>onSorting</code> : emis sur les evenements de tri (<code>p-table onSort</code>).</li><li><code>onFiltering</code> : emis sur les evenements de filtrage (<code>p-table onFilter</code>).</li><li><code>onPTableSelectionChange</code> : emis lors du changement de selection des lignes.</li><li><code>onPTableRowExpand</code> : emis lors de l&#39;expansion d&#39;une ligne.</li><li><code>onPTableRowCollapse</code> : emis lors de la reduction d&#39;une ligne.</li><li><code>onPTableColumnResize</code> : emis lors du redimensionnement d&#39;une colonne.</li><li><code>onPTableColumnReorder</code> : emis lors de la reorganisation des colonnes.</li></ul><h3>Exemple 1 : binding direct dans le template</h3><p>Snippet 7:</p><h3>Exemple 2 : subscribe via ViewChild</h3><p>Snippet 8:</p><h2><code>rowCustomSelect</code> — signature reelle (piege)</h2><p><code>&lt;wuic-list-grid&gt;</code> accepte une entree <code>[rowCustomSelect]</code> pour intercepter la selection d&#39;une ligne (ouverture d&#39;une dialog &quot;choisir un document&quot;, flux master-detail, etc.). La signature TypeScript declaree dans <a href=\"../../src/lib/component/list-grid/list-grid.component.ts#L140\">list-grid.component.ts:140</a> est :</p><p>Snippet 9:</p><p><strong>Mais au runtime la callback est invoquee avec les arguments inverses</strong> — le framework appelle <code>rowCustomSelect($event, rowData, dt)</code> (voir <a href=\"../../src/lib/component/dynamic-template/dynamic-template.component.ts#L447\">dynamic-template.component.ts:447</a> et <a href=\"../../src/lib/component/dynamic-template/dynamic-card-template.component.ts#L205\">dynamic-card-template.component.ts:205</a>).</p><p>Symptome en cas d&#39;ordre incorrect : <code>rowData?.id</code> est undefined → guard precoce dans votre handler → la callback retourne silencieusement et votre dialog/action ne demarre pas. Aucune erreur en console.</p><p>Forme correcte (alignee a l&#39;invocation runtime) :</p><p>Snippet 10:</p><p>Utilisation dans le template :</p><p>Snippet 11:</p><p>&gt; Note : les tests dans <code>designer.component.spec.ts</code> (par ex. ligne 512) invoquent la callback avec <code>({currentTarget: rowCell}, {id: 42}, null)</code>, confirmant l&#39;ordre <code>($event, rowData, dt)</code>. Si le framework finit par aligner la signature declaree, cette page sera mise a jour.</p>",
+                    "html": "<h1>List Grid</h1><p>Composant principal pour les listes tabulaires avec filtres, tri, pagination cote serveur et actions sur les lignes.</p><h2>Cas d&#39;utilisation</h2><ul><li>CRUD tabulaires enterprise.</li><li>Rapports operationnels avec filtres multi-colonnes.</li><li>Jeux de donnees tres volumineux avec <code>cursorMode</code>.</li></ul><h2>Ce que la toolbar affiche par defaut</h2><p>En ouvrant une route fraichement scaffoldee, la caption-bar se trouve au-dessus de la grille.</p><p>A gauche :</p><table><thead><tr><th>Bouton</th><th>Quand il apparait</th></tr></thead><tbody><tr><td><strong>Actualiser</strong></td><td>toujours, sauf <code>md_hide_refresh</code></td></tr><tr><td><strong>Ajouter</strong></td><td>avec <code>md_insertable</code></td></tr><tr><td><strong>Actes</strong></td><td>si la table a des actions custom</td></tr><tr><td>Import / Export</td><td>toujours ; la branche import seulement avec <code>md_importable</code></td></tr><tr><td><strong>Rapports</strong></td><td>si au moins un rapport est associe a la route</td></tr><tr><td><strong>Enregistrer les modifications</strong> / <strong>Annuler les modifications</strong></td><td>seulement avec <code>md_inline_cell_edit</code> <strong>et</strong> <code>md_batch_save</code></td></tr></tbody></table><p>A droite : <strong>Gerer l&#39;etat</strong> (precede de la liste des etats sauvegardes, s&#39;il y en a),</p><p><strong>Effacer les filtres</strong> quand les filtres sont sur les colonnes, et <strong>Performance</strong> si</p><p>l&#39;inspector est active sur la route.</p><p>&gt; Les libelles cites plus bas dans cette page <strong>ne sont pas sur cet ecran</strong>, et ce n&#39;est pas un</p><p>&gt; defaut : ceux de l&#39;export/import (<em>Continuer en arriere-plan</em>, <em>Annuler la tache</em>, *Arreter et</p><p>&gt; telecharger partiel<em>, </em>Annuler l&#39;import (rollback)<em>, </em>Arreter et valider partiel*) vivent dans</p><p>&gt; la boite de progression, qui n&#39;existe que pendant un export ou un import ; *Enregistrer les</p><p>&gt; modifications<em> et </em>Annuler les modifications* n&#39;apparaissent qu&#39;avec les deux flags ci-dessus.</p><p>&gt; Ils appartiennent a d&#39;autres moments que la premiere ouverture de la liste.</p><h2>Reference de capture d&#39;ecran (manuel utilisateur)</h2><ul><li><code>manual__grid__01.png</code> : mode <code>inline cell edit</code> dans list-grid.</li><li><code>manual__grid__02.png</code> : mode <code>inline edit</code> (au niveau ligne) dans list-grid.</li></ul><h2>Metadonnees inline editing</h2><p>Configuration dans le <code>md_props_bag</code> de la table metadata :</p><ul><li><code>md_inline_edit</code></li></ul><p>  - active l&#39;edition inline de la ligne dans list-grid (cellules editables dans le contexte de la ligne, sans ouverture de popup).</p><p>  - utile lorsque vous souhaitez conserver l&#39;UX tabulaire avec une edition rapide par enregistrement.</p><ul><li><code>md_inline_cell_edit</code></li></ul><p>  - active l&#39;edition inline &quot;cellule par cellule&quot; (focus sur la cellule individuelle).</p><p>  - note : dans les configurations legacy, il peut apparaitre sous le nom <code>md_inline_cell_editing</code> ; le comportement runtime est le meme.</p><p>  - <strong>promotion runtime</strong> : lorsque <code>md_inline_cell_edit</code> est <code>true</code>, le composant force</p><p>    a runtime egalement <code>md_inline_edit = true</code> independamment de la valeur en DB.</p><p>    Les deux UX necessitent que la colonne d&#39;actions soit visible, elles sont donc mutuellement</p><p>    non exclusives au niveau du rendu.</p><ul><li><code>md_batch_save</code></li></ul><p>  - active la sauvegarde batch des modifications en attente (<code>Save changes</code> / <code>Cancel changes</code>).</p><p>  - si utilise conjointement avec inline-cell, les modifications restent en attente jusqu&#39;a la sauvegarde explicite.</p><p>  - <strong>prerequis</strong> : <code>md_batch_save</code> n&#39;a d&#39;effet <strong>que</strong> si <code>md_inline_cell_edit</code> est <code>true</code>.</p><p>    Avec <code>md_inline_cell_edit:false</code>, le flag est ignore a runtime et les boutons</p><p>    &quot;Sauvegarder les modifications / Annuler les modifications&quot; ne sont pas affiches.</p><h3>Combinaisons valides</h3><table><thead><tr><th><code>md_inline_edit</code></th><th><code>md_inline_cell_edit</code></th><th><code>md_batch_save</code></th><th>Resultat runtime</th></tr></thead><tbody><tr><td><code>true</code></td><td><code>false</code></td><td>quelconque</td><td>Edition inline au niveau ligne avec crayon. <code>md_batch_save</code> ignore.</td></tr><tr><td><code>false</code></td><td><code>true</code></td><td><code>false</code></td><td>Autosave cellule par cellule au blur. <code>md_inline_edit</code> force a <code>true</code> a runtime.</td></tr><tr><td><code>false</code></td><td><code>true</code></td><td><code>true</code></td><td>Cellule par cellule avec buffer en attente + barre d&#39;outils <code>Sauvegarder / Annuler les modifications</code>.</td></tr><tr><td><code>false</code></td><td><code>false</code></td><td>quelconque</td><td>Aucune edition inline. <code>md_batch_save</code> ignore.</td></tr></tbody></table><p>Exemple edition inline au niveau ligne :</p><p>Snippet 1:</p><p>Exemple cellule par cellule avec sauvegarde batch :</p><p>Snippet 2:</p><h2>Barre d&#39;outils export/import</h2><ul><li>Export XLS :</li></ul><p>  - affiche une boite de dialogue de progression avec pourcentage en temps reel ;</p><p>  - actions : <code>Continuer en arriere-plan</code>, <code>Annuler la tache</code>, <code>Interrompre et telecharger le partiel</code> ;</p><p>  - en arriere-plan, cree une notification avec progression ; un clic rouvre la boite de dialogue.</p><ul><li>Import XLS/XLSX (si <code>md_importable = true</code>) :</li></ul><p>  - boite de dialogue de progression apres la confirmation ;</p><p>  - actions : <code>Continuer en arriere-plan</code>, <code>Annuler l&#39;import (rollback)</code>, <code>Arreter et commit partiel</code> ;</p><p>  - a la fin de l&#39;import, cree une notification recapitulative qui redirige vers la route.</p><h2>Config metadata</h2><p>Parametres cles dans <code>md_props_bag</code> et metadonnees de colonnes.</p><p>Snippet 3:</p><h2>md_props_bag: toolbar</h2><p>Flags opt-in qui masquent des blocs de la barre d&#39;outils de la list-grid (<code>caption-bar</code>). Tous sous <code>md_props_bag.toolbar.*</code> (parse au runtime comme <code>tableMetadata.extraProps.toolbar</code>).</p><p>Snippet 4:</p><ul><li><code>hideManageState</code> (boolean, defaut <code>false</code>) : masque dans la <strong>caption-right</strong> le bouton &quot;Gestion etat&quot; (icone bookmark) + le <code>&lt;select&gt;</code> des etats enregistres. Utile pour les routes hardcoded / demo ou la fonctionnalite saved-state (persistance par <code>user_id</code> + route via <code>MetaService</code>) n&#39;a pas de sens — par ex. Pattern 3 pur OData sans route metadata enregistree.</li><li><code>hideBatchActions</code> (boolean, defaut <code>false</code>) : masque dans la <strong>caption-left</strong> les boutons &quot;Enregistrer les modifications&quot; (<code>pi-save</code>) + &quot;Annuler les modifications&quot; (<code>pi-times</code>) + l&#39;indicateur de comptage des changements (<code>grid-changes-indicator</code>, badge pencil + count). Generes par le framework quand <code>md_inline_cell_editing</code> + <code>md_batch_save</code> sont actifs. Concu pour les <strong>grids imbriquees dans un parametric-dialog</strong> : le save/cancel du parent persiste le master + les lignes en un seul coup via le batch save framework, et les boutons en double sur la grid imbriquee perturbent l&#39;UX.</li></ul><p>Exemple de lignes imbriquees dans un edit-form custom (patch runtime) :</p><p>Snippet 5:</p><p>Type TS dans <a href=\"../api/wuic-framework-lib.metadatitabella.html\">`metadati_tabella.ts`</a> (propriete <code>extraProps.toolbar</code>). Les flags ne desactivent PAS la logique <code>md_batch_save</code> sous-jacente (les changements restent traces) ; ils suppriment uniquement l&#39;UI de la barre d&#39;outils — le save effectif passe par le flux du parent.</p><h2>md_props_bag: archetypes.list</h2><p>Le composant lit <code>md_props_bag.archetypes.list</code>.</p><p>Snippet 6:</p><ul><li><code>proportionalColwidth</code> :</li><li>type : boolean (avec parser tolerant)</li><li>valeurs acceptees : <code>true</code>, <code>false</code>, <code>1</code>, <code>0</code>, <code>&quot;true&quot;</code>, <code>&quot;false&quot;</code>, <code>&quot;1&quot;</code>, <code>&quot;0&quot;</code></li><li>valeur par defaut runtime : <code>true</code> lorsqu&#39;absent ou vide</li><li>effet : distribue les largeurs de colonnes en pourcentage (au lieu de px) lorsqu&#39;il n&#39;y a pas de largeurs utilisateur persistees.</li></ul><ul><li><code>virtualize</code> :</li><li>type : <code>boolean</code> ou <code>object</code></li><li>valeurs acceptees :</li><li><code>true</code>/<code>false</code>, <code>1</code>/<code>0</code>, <code>&quot;true&quot;</code>/<code>&quot;false&quot;</code>, <code>&quot;1&quot;</code>/<code>&quot;0&quot;</code></li><li>object avec <code>enabled</code> (optionnel) et <code>itemSize</code> (optionnel)</li><li>valeur par defaut runtime : desactive (<code>false</code>) lorsqu&#39;absent</li><li><code>enabled</code> :</li><li>par defaut : <code>true</code> si le noeud <code>virtualize</code> est un objet sans <code>enabled</code>, sinon parser tolerant</li><li>effet : active <code>virtualScroll</code> sur <code>p-table</code></li><li><code>itemSize</code> :</li><li>par defaut : <code>44</code></li><li>effet : definit <code>virtualScrollItemSize</code> (hauteur de la ligne virtuelle en px)</li></ul><ul><li><code>advancedFilter</code> :</li><li>type : boolean (avec parser tolerant)</li><li>valeur par defaut runtime : <code>false</code></li><li>effet :</li><li>lorsque <code>true</code>, la grille masque les icones de filtre de colonne (<code>p-columnFilter</code>) et utilise la <code>wuic-filter-bar</code> au-dessus de la table (au niveau <code>data-repeater</code>/<code>bounded-repeater</code>) pour appliquer les filtres.</li></ul><p>Note operationnelle :</p><ul><li>le suggest <code>md_props_bag</code> dans le metadata editor expose egalement le noeud cochable <code>archetypes.list.advancedFilter</code>.</li></ul><h2>Pagination : md_pagesize et md_page_size_choice</h2><p>La grille utilise <code>md_pagesize</code> comme taille de page par defaut et <code>md_page_size_choice</code> comme liste de valeurs selectionnables dans le paginateur.</p><p>Regles runtime :</p><ul><li>si <code>md_pagesize</code> est superieur a la valeur maximale presente dans <code>md_page_size_choice</code>, le framework ajoute automatiquement <code>md_pagesize</code> a la liste d&#39;options ;</li><li>la liste est normalisee (nombres valides, deduplication, tri croissant).</li></ul><p>Exemple :</p><ul><li><code>md_pagesize = 200</code></li><li><code>md_page_size_choice = &quot;10,25,50,100&quot;</code></li><li>resultat runtime : <code>10,25,50,100,200</code></li></ul><h2>Activation forcee de la virtualisation sur une taille de page elevee</h2><p>Lorsque l&#39;utilisateur selectionne dans le paginateur une valeur <code>pageSize &gt;= 1000</code> :</p><ul><li>la virtualisation est forcee automatiquement meme si <code>md_props_bag.archetypes.list.virtualize</code> est absent ou desactive ;</li><li><code>virtualScrollItemSize</code> est force a la valeur par defaut <code>44</code>.</li></ul><p>Ce comportement protege le rendu de la table sur des pages tres volumineuses.</p><h2>Evenements et subscriptions (host)</h2><p><code>wuic-list-grid</code> expose des evenements runtime utiles pour intercepter le cycle de rendu et les callbacks p-table cote projet host.</p><p>Evenements disponibles :</p><ul><li><code>onAfterRender</code> : emis a la fin du binding des donnees de la grille (<code>rows</code>, <code>totalRecords</code>, <code>metaInfo</code>, <code>datasource</code>).</li><li><code>onBeforeRowRender</code> : emis avant le rendu logique de la ligne individuelle ; supporte l&#39;annulation via <code>event.cancelRender()</code>.</li><li><code>onAfterRowRender</code> : emis apres le rendu logique de la ligne individuelle.</li><li><code>onPaging</code> : emis sur les evenements de pagination (<code>p-table onPage</code>).</li><li><code>onSorting</code> : emis sur les evenements de tri (<code>p-table onSort</code>).</li><li><code>onFiltering</code> : emis sur les evenements de filtrage (<code>p-table onFilter</code>).</li><li><code>onPTableSelectionChange</code> : emis lors du changement de selection des lignes.</li><li><code>onPTableRowExpand</code> : emis lors de l&#39;expansion d&#39;une ligne.</li><li><code>onPTableRowCollapse</code> : emis lors de la reduction d&#39;une ligne.</li><li><code>onPTableColumnResize</code> : emis lors du redimensionnement d&#39;une colonne.</li><li><code>onPTableColumnReorder</code> : emis lors de la reorganisation des colonnes.</li></ul><h3>Exemple 1 : binding direct dans le template</h3><p>Snippet 7:</p><h3>Exemple 2 : subscribe via ViewChild</h3><p>Snippet 8:</p><h2><code>rowCustomSelect</code> — signature reelle (piege)</h2><p><code>&lt;wuic-list-grid&gt;</code> accepte une entree <code>[rowCustomSelect]</code> pour intercepter la selection d&#39;une ligne (ouverture d&#39;une dialog &quot;choisir un document&quot;, flux master-detail, etc.). La signature TypeScript declaree dans <a href=\"../../src/lib/component/list-grid/list-grid.component.ts#L140\">list-grid.component.ts:140</a> est :</p><p>Snippet 9:</p><p><strong>Mais au runtime la callback est invoquee avec les arguments inverses</strong> — le framework appelle <code>rowCustomSelect($event, rowData, dt)</code> (voir <a href=\"../../src/lib/component/dynamic-template/dynamic-template.component.ts#L447\">dynamic-template.component.ts:447</a> et <a href=\"../../src/lib/component/dynamic-template/dynamic-card-template.component.ts#L205\">dynamic-card-template.component.ts:205</a>).</p><p>Symptome en cas d&#39;ordre incorrect : <code>rowData?.id</code> est undefined → guard precoce dans votre handler → la callback retourne silencieusement et votre dialog/action ne demarre pas. Aucune erreur en console.</p><p>Forme correcte (alignee a l&#39;invocation runtime) :</p><p>Snippet 10:</p><p>Utilisation dans le template :</p><p>Snippet 11:</p><p>&gt; Note : les tests dans <code>designer.component.spec.ts</code> (par ex. ligne 512) invoquent la callback avec <code>({currentTarget: rowCell}, {id: 42}, null)</code>, confirmant l&#39;ordre <code>($event, rowData, dt)</code>. Si le framework finit par aligner la signature declaree, cette page sera mise a jour.</p>",
                     "codeSamples": [
                         {
                             "id": "code_1",
@@ -17156,7 +17210,7 @@ const frameworkDocsContent = {
                 {
                     "id": "overview",
                     "title": "Overview",
-                    "html": "<h1>Designer</h1><p>Editeur visuel pour les dashboards pilotes par metadata sur la route <code>#/cities/dashboard</code>.</p><h2>Scope</h2><ul><li>Composition de board par glisser-deposer de noeuds et blocs UI.</li><li>Mise en page et styles pilotes par <code>boardcontent</code> et metadata table/colonne.</li><li>Edition via le panneau de proprietes sans codage en dur dans les composants runtime.</li></ul><h2>Palette Designer</h2><ul><li><code>Datasource</code> : source de donnees metadata (<code>route</code>, filtres, tri, pagination).</li><li><code>DataRepeater</code> : visualisation liste/carte liee a une datasource.</li><li><code>Dynamic Template</code> : rendu de template dynamique avec inputs pilotes par metadata.</li><li><code>Action/Button</code> : actions utilisateur liees aux enregistrements et callbacks.</li><li><code>Container/Layout</code> : blocs structurels pour colonnes, lignes et wrappers.</li></ul><h2>Fonctionnalites principales</h2><ul><li>Glisser-deposer de noeuds sur le canvas avec persistance dans le <code>boardcontent</code>.</li><li>Panneau de proprietes contextuel avec des inputs coherents aux composants selectionnes.</li><li>Liaison entre noeuds (<code>datasource -&gt; repeater/template</code>) avec validation minimale.</li><li>Apercu runtime integre et realignement de la mise en page.</li><li>Gestion des modifications en attente avec guard avant la sortie.</li></ul><h2>Menu contextuel des elements</h2><p>Le clic droit sur un element du canvas, sur un element du fil d&#39;Ariane en bas ou sur un noeud de l&#39;arbre de hierarchie affiche un menu contextuel avec trois entrees :</p><ul><li><strong>Modifier les proprietes</strong> (pi-cog) - selectionne l&#39;element comme &quot;current tool&quot; et affiche son panneau de proprietes a droite ; equivalent au clic dans l&#39;arbre. Utile pour editer les proprietes d&#39;elements imbriques sans devoir les chercher dans la hierarchie.</li><li><strong>Renommer</strong> (uniquement fil d&#39;Ariane) - ouvre une boite de dialogue pour renommer le <code>displayName</code>.</li><li><strong>Supprimer</strong> - retire l&#39;element du board.</li></ul><h2>Flux operationnel conseille</h2><ul><li>Ouvrir la route dashboard cible.</li><li>Inserer/relier les noeuds depuis la palette.</li><li>Configurer les <code>inputs</code> essentiels (ex. <code>route</code>, <code>action</code>, <code>datasource</code>).</li><li>Sauvegarder et valider le resultat en runtime.</li></ul><h2>Notes operationnelles</h2><ul><li>Pour les correctifs specifiques a un dashboard, privilegier la patch du <code>boardcontent</code> plutot que des modifications globales.</li><li>Eviter les proprietes dupliquees entre <code>inputs</code> et le style inline incoherent.</li><li>Toujours verifier que les datasources ont <code>inputs.route</code> renseignee.</li></ul>",
+                    "html": "<h1>Designer</h1><p>Editeur visuel pour les dashboards pilotes par metadata sur la route <code>#/cities/dashboard</code>.</p><h2>Scope</h2><ul><li>Composition de board par glisser-deposer de noeuds et blocs UI.</li><li>Mise en page et styles pilotes par <code>boardcontent</code> et metadata table/colonne.</li><li>Edition via le panneau de proprietes sans codage en dur dans les composants runtime.</li></ul><h2>Palette Designer</h2><p>La palette est divisee en trois groupes. Les noms ci-dessous sont ceux que vous lisez dans la</p><p>palette, en majuscules comme le designer les ecrit.</p><p><strong>HTML</strong> — les briques de balisage :</p><table><thead><tr><th>Tool</th><th>A quoi ca sert</th></tr></thead><tbody><tr><td><code>TABLE</code></td><td>grille de cellules. <code>TR</code> et <code>TD</code> existent comme tools mais ne se glissent pas : c&#39;est la table qui les cree</td></tr><tr><td><code>DIV</code></td><td>conteneur libre, le bloc structurel le plus utilise</td></tr><tr><td><code>SPAN</code>, <code>LABEL</code>, <code>Hx</code></td><td>texte databound ; <code>Hx</code> choisit le niveau de h1 a h6</td></tr><tr><td><code>ANCHOR</code>, <code>IMG</code>, <code>IMAGE</code>, <code>IFRAME</code></td><td>liens, images, contenu externe</td></tr><tr><td><code>UL</code></td><td>liste</td></tr><tr><td><code>BUTTON</code></td><td>bouton avec callback</td></tr><tr><td><code>INPUT</code>, <code>TEXTAREA</code>, <code>CHECKBOX</code>, <code>SELECT</code>, <code>MULTISELECT</code>, <code>DATE</code></td><td>champs de saisie</td></tr><tr><td><code>KPI</code></td><td>une valeur unique mise en avant</td></tr><tr><td><code>SEPARATOR</code>, <code>HR</code></td><td>separateurs</td></tr></tbody></table><p><strong>DATA</strong> — les noeuds relies au backend :</p><table><thead><tr><th>Tool</th><th>A quoi ca sert</th></tr></thead><tbody><tr><td><code>DATASOURCE</code></td><td>source de donnees metadata (<code>route</code>, filtres, tri, pagination)</td></tr><tr><td><code>DATAREPEATER</code></td><td>visualisation liste/carte liee a une datasource</td></tr><tr><td><code>FILTERBAR</code></td><td>barre de filtres au-dessus du repeater</td></tr><tr><td><code>PAGER</code></td><td>paginateur</td></tr></tbody></table><p><strong>CONTAINER</strong> — les mises en page :</p><table><thead><tr><th>Tool</th><th>A quoi ca sert</th></tr></thead><tbody><tr><td><code>TABVIEW</code> + <code>TABPANEL</code></td><td>onglets</td></tr><tr><td><code>SPLITTER</code> + <code>SPLITTER-AREA</code></td><td>panneaux redimensionnables</td></tr><tr><td><code>ACCORDION</code> + <code>ACCORDION-AREA</code></td><td>sections en accordeon</td></tr></tbody></table><p>Deux noms que l&#39;on cherche en vain : <strong>il n&#39;existe aucun tool &quot;Dynamic Template&quot;</strong> — le template</p><p>dynamique est ce que le <code>DATAREPEATER</code> rend, il se configure depuis ses proprietes et ne se</p><p>glisse pas ; et <strong>&quot;Container&quot; / &quot;Layout&quot; sont le nom du groupe</strong>, pas des entrees selectionnables.</p><p>S&#39;y ajoutent les tools custom enregistres par le projet hote</p><p>(<code>MetadataProviderService.customDesignerTools</code>), qui apparaissent en fin de liste sous le groupe</p><p>qu&#39;ils declarent.</p><h2>Fonctionnalites principales</h2><ul><li>Glisser-deposer de noeuds sur le canvas avec persistance dans le <code>boardcontent</code>.</li><li>Panneau de proprietes contextuel avec des inputs coherents aux composants selectionnes.</li><li>Liaison entre noeuds (<code>datasource -&gt; repeater/template</code>) avec validation minimale.</li><li>Apercu runtime integre et realignement de la mise en page.</li><li>Gestion des modifications en attente avec guard avant la sortie.</li></ul><h2>Menu contextuel des elements</h2><p>Le clic droit sur un element du canvas, sur un element du fil d&#39;Ariane en bas ou sur un noeud de l&#39;arbre de hierarchie affiche un menu contextuel avec trois entrees :</p><ul><li><strong>Modifier les proprietes</strong> (pi-cog) - selectionne l&#39;element comme &quot;current tool&quot; et affiche son panneau de proprietes a droite ; equivalent au clic dans l&#39;arbre. Utile pour editer les proprietes d&#39;elements imbriques sans devoir les chercher dans la hierarchie.</li><li><strong>Renommer</strong> (uniquement fil d&#39;Ariane) - ouvre une boite de dialogue pour renommer le <code>displayName</code>.</li><li><strong>Supprimer</strong> - retire l&#39;element du board.</li></ul><h2>Flux operationnel conseille</h2><ul><li>Ouvrir la route dashboard cible.</li><li>Inserer/relier les noeuds depuis la palette.</li><li>Configurer les <code>inputs</code> essentiels (ex. <code>route</code>, <code>action</code>, <code>datasource</code>).</li><li>Sauvegarder et valider le resultat en runtime.</li></ul><h2>Notes operationnelles</h2><ul><li>Pour les correctifs specifiques a un dashboard, privilegier la patch du <code>boardcontent</code> plutot que des modifications globales.</li><li>Eviter les proprietes dupliquees entre <code>inputs</code> et le style inline incoherent.</li><li>Toujours verifier que les datasources ont <code>inputs.route</code> renseignee.</li></ul>",
                     "codeSamples": []
                 }
             ],
@@ -21271,13 +21325,17 @@ const frameworkDocsContent = {
                 {
                     "id": "sec_4",
                     "title": "Quick Start — primer componente"
+                },
+                {
+                    "id": "sec_5",
+                    "title": "Las primeras listas muestran 20 registros: es el modo Trial"
                 }
             ],
             "sections": [
                 {
                     "id": "overview",
                     "title": "Overview",
-                    "html": "<h1>Panorámica del Framework</h1><p>WUIC Framework es una plataforma metadata-driven para crear interfaces de negocio de forma rápida y coherente.</p><h2>Qué incluye</h2><ul><li>DataSource y DataRepeater para orquestar datos y renderizado.</li><li>Archetypes visuales (list, map, scheduler, chart, carousel).</li><li>Designer runtime para dashboards y templates dinámicos.</li><li>Workflow designer/runner para procesos operativos.</li><li>RAG Chatbot para consultar la codebase en lenguaje natural.</li><li>Multi-SGBD: SQL Server, MySQL, PostgreSQL y Oracle mediante providers drop-in (<code>dbms</code>: <code>mssql</code> | <code>mysql</code> | <code>postgresql</code> | <code>oracle</code>).</li></ul><h2>First Steps — Arranque del entorno dev</h2><p>El stack WUIC está compuesto por varios servicios. Arráncalos en el orden indicado.</p><h3>Prerrequisitos</h3><table><thead><tr><th>Qué</th><th>Verificación</th><th>Notas</th></tr></thead><tbody><tr><td>.NET 10 SDK</td><td><code>dotnet --version</code></td><td>Hosting Bundle para IIS en producción</td></tr><tr><td>Node.js 22 LTS</td><td><code>node --version</code></td><td>La 22 es la version con la que se prueba el paquete; con npm 10.9.x la instalacion funciona gracias al <code>package-lock.json</code> incluido</td></tr><tr><td>PowerShell 5.1+</td><td><code>$PSVersionTable.PSVersion</code></td><td>El Windows PowerShell preinstalado es suficiente: <code>rename-project.ps1</code> y los scripts <code>llm-workspace/</code> tambien funcionan en 5.1. PowerShell 7 es recomendable, no obligatorio</td></tr><tr><td>SQL Server 2019+</td><td><code>sqlcmd -S localhost\\sqlexpress -E -C -Q &quot;SELECT 1&quot;</code></td><td>Si falta, <strong>la línea única lo instala por su cuenta</strong> (SQL Server Express, o el motor elegido con <code>-Dbms</code>); en Windows Server no, ver el recuadro de abajo. 2019 basta para los paquetes sin <code>.bak</code>; el tutorial <code>.bak</code> es una copia de SQL Server 2022 y requiere <strong>2022 o superior</strong></td></tr><tr><td>Linux (instalador <code>install.sh</code>)</td><td><code>lsb_release -ds</code></td><td><strong>Ubuntu 22.04 o 24.04 LTS</strong> (24.04 recomendada): son las unicas versiones de Ubuntu que Microsoft soporta para SQL Server, la <strong>26.04 no esta soportada</strong> (<a href=\"https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-setup?view=sql-server-ver17\" target=\"_blank\" rel=\"noopener noreferrer\">Supported platforms</a>). Misma recomendacion con MySQL, PostgreSQL y Oracle, porque el instalador esta probado en esas versiones</td></tr><tr><td>GPU NVIDIA (CUDA 12.x + cuDNN 9)</td><td><code>nvidia-smi</code></td><td>Opcional: acelera el RAG Chatbot (sin GPU funciona en CPU)</td></tr></tbody></table><p>&gt; <strong>En Windows Server la base de datos debe instalarse antes.</strong> La linea unica obtiene los</p><p>&gt; componentes que faltan mediante <code>winget</code>, que no esta presente en Windows Server: sin una</p><p>&gt; instancia ya accesible la instalacion se detiene con `No SQL Server instance reachable and</p><p>&gt; winget is missing`. Instala el motor antes de ejecutar la linea - SQL Server debe ser **2019 o</p><p>&gt; superior<strong> (Express es suficiente; </strong>2022 o superior** para el tutorial <code>.bak</code>), y una 2017 no</p><p>&gt; se acepta. Si la instancia no es la predeterminada, pasala con</p><p>&gt; <code>-SqlServer &#39;localhost\\NOMBREINSTANCIA&#39;</code>. Vale para todos los motores, no solo SQL Server.</p><h3>1. Descarga el template de proyecto</h3><p>En Windows una sola linea de PowerShell lo hace todo: descarga el paquete, comprueba el SDK de .NET 10</p><p>y Node.js 22 (instalando lo que falte), ejecuta <code>dotnet restore</code> y <code>npm install</code>,</p><p>e instala la extension WUIC Assistant en VS Code.</p><p>Snippet 1:</p><p>Opciones útiles en la misma línea: <code>-Dbms mysql</code> (o <code>postgres</code>, <code>oracle</code>) para un motor</p><p>distinto de SQL Server — el instalador lo instala y lo configura él mismo — y <code>-WithTutorial</code></p><p>para descargar también la base de datos de ejemplo.</p><p>Cuando termina, la última pantalla ya es tu lista de tareas:</p><p>Snippet 2:</p><p>La cadena de conexión ya está lista: en el primer arranque el wizard no pide nada más. Con</p><p><code>-Dbms mysql</code> o <code>-Dbms postgres</code> esa línea cambia en consecuencia y lleva dentro usuario y</p><p>contraseña, porque la contraseña del superusuario <strong>la genera el instalador</strong>; esa misma</p><p>contraseña se guarda en <code>wuic-secrets.json</code>, junto a la instalación, y es el único sitio donde</p><p>queda escrita.</p><p>La via manual sigue siendo valida, en cualquier sistema:</p><p>Parte del paquete <code>WuicTest-src-*.zip</code> (enlace en la sección <strong>Download</strong> del sitio).</p><p>Extráelo en una carpeta de trabajo, p. ej. <code>C:\\dev\\WuicTest</code> (los archivos van directamente</p><p>en la raíz, NO dentro de una subcarpeta <code>src/</code>). El paquete contiene:</p><ul><li><code>WuicTest.csproj</code> → proyecto host con <code>&lt;PackageReference Include=&quot;WuicCore&quot; Version=&quot;...&quot; /&gt;</code></li><li><code>wwwroot/</code> → app Angular cuyo <code>package.json</code> referencia <code>wuic-framework-lib</code> desde el registry npm</li><li><code>appsettings.json</code> preconfigurado en modo <code>firstRun = &quot;true&quot;</code> con placeholders <code>__SET_*__</code></li><li><code>appsettings-samples/</code> → 6 templates listos (<code>mssql</code>/<code>mysql</code>, firstRun/post-firstRun, <code>Development</code>)</li></ul><p>&gt; <strong>No hace falta clonar el repositorio del framework</strong>: <code>WuicCore</code> llega como paquete NuGet</p><p>&gt; desde <code>nuget.org</code> y <code>wuic-framework-lib</code> como paquete npm desde el registry npm. El código</p><p>&gt; fuente del framework solo se necesita si quieres modificarlo — típicamente no es tu caso.</p><p>&gt; <strong>npm 10.9.x y los paquetes anteriores a 1.7.1</strong>: esos paquetes no incluyen <code>package-lock.json</code>, y</p><p>&gt; sin lock npm 10.9.x (la version que instala Node 22 LTS) se detiene con</p><p>&gt; <code>Cannot read properties of null (reading &#39;edgesOut&#39;)</code> al resolver las dependencias peer.</p><p>&gt; Descarga el lock publicado junto a la release —</p><p>&gt; <code>https://wuic-framework.com/downloads/locks/&lt;nombre-del-zip&gt;.package-lock.json</code> — colocalo en</p><p>&gt; <code>wwwroot/</code> y ejecuta <code>npm install</code> otra vez. La linea unica <code>-Src</code> lo hace por ti.</p><h3>2. Database</h3><p>Hace falta una instancia del motor accesible. <strong>Con la línea única no hay nada que hacer</strong>:</p><p>la instala y la configura ella, y la cadena de conexión que hay que pegar en el wizard es lo</p><p>último que imprime. En la vía manual la instancia debe existir ya.</p><p>Conexiones en <code>appsettings.json</code>:</p><ul><li><code>MetaDataSQLConnection</code> — DB metadata (menú, tablas, columnas, boards, usuarios)</li><li><code>DataSQLConnection</code> — DB datos de la aplicación</li></ul><p>Si es la primera instalación (<code>AppSettings.firstRun = &quot;true&quot;</code> en el template),</p><p>el wizard de scaffolding en el primer arranque crea el esquema metadata y puebla el DB datos.</p><p>Ver la página <em>Scaffolding inicial</em> para el flujo guiado.</p><h3>3. Backend (.NET)</h3><p>Desde la raíz de la carpeta extraída (p. ej. <code>C:\\dev\\WuicTest</code>):</p><p>Snippet 3:</p><p>El backend expone las API en <code>http://localhost:5000</code>.</p><h3>4. Frontend (Angular)</h3><p>En una segunda shell, desde la subcarpeta <code>wwwroot/</code>:</p><p>Snippet 4:</p><p>El frontend está disponible en <code>http://localhost:4200</code>.</p><p>Login por defecto (post-firstRun): <code>admin</code> / <code>admin</code>.</p><h3>5. RAG Chatbot (opcional)</h3><p>El RAG Chatbot (<code>Administración &gt; RAG Chat</code>) se ejecuta **dentro del backend</p><p>.NET**: el motor de retrieval (<code>rag-engine/WuicRagEngine.dll</code>, ONNX Runtime</p><p>in-process) lo carga el backend cuando <code>AppSettings.rag-use-dotnet-engine</code> es</p><p><code>&quot;true&quot;</code> (valor por defecto en los paquetes de release). **Sin Python, sin</p><p>venv, ningún servidor separado que arrancar.**</p><p>La <strong>primera</strong> vez que se abre el chatbot (o al final del first-run) el</p><p>backend descarga por sí solo los modelos ONNX (<code>bge-m3</code> + reranker), el</p><p>tokenizer y el índice (~4,5 GB) desde <code>rag-engine-models-url</code> (por defecto</p><p><code>https://wuic-framework.com/rag-models</code>) en <code>rag-engine/artifacts/</code>. Solo hace</p><p>falta conexión a internet una vez; la descarga corre en segundo plano (1-5 min)</p><p>y llega una notificación in-app al inicio y al final. Mientras tanto el</p><p>componente muestra el estado <strong>RAG offline</strong> y el resto de la aplicación</p><p>funciona con normalidad.</p><p>Claves <code>AppSettings</code> relevantes (todas con valores por defecto listos):</p><ul><li><code>rag-use-dotnet-engine</code> = <code>true</code> — activa el motor .NET (<code>false</code> = fallback Python, ver abajo)</li><li><code>rag-engine-device</code> = <code>auto</code> — <code>auto</code> | <code>cuda</code> | <code>cpu</code>: con GPU NVIDIA (CUDA 12.x + cuDNN 9) ~1 s/consulta, en CPU ~15-25 s/consulta</li><li><code>rag-engine-profile</code> = <code>release</code> — <code>release</code> = fuentes del framework solo como firma; <code>internal</code> = índice completo</li><li><code>rag-engine-models-url</code> — origen de la descarga en el primer arranque</li><li><code>rag-engine-cuda-path</code> = (vacío) — carpeta de las DLL CUDA/cuDNN si no están instaladas a nivel de sistema</li></ul><p>Para el chat con LLM configura <code>rag-llm-provider</code> + <code>rag-llm-api-key</code> (Claude</p><p>vía Anthropic, o un modelo local vía Ollama con <code>rag-llm-base-url</code>). Sin</p><p>provider solo funciona la modalidad retrieval (búsqueda de snippets). Detalle</p><p>de las claves en la página <em>AppSettings</em>.</p><p>&gt; El stack histórico Python (<code>scripts/rag-setup.ps1</code> + <code>rag_server.py</code> en</p><p>&gt; <code>127.0.0.1:8765</code>) solo puede usarse como fallback con</p><p>&gt; <code>rag-use-dotnet-engine = &quot;false&quot;</code> y no se incluye en los paquetes de release.</p><h2>Resumen de servicios</h2><table><thead><tr><th>Servicio</th><th>Puerto</th><th>Obligatorio</th><th>Comando rápido</th></tr></thead><tbody><tr><td>SQL Server</td><td>1433</td><td>sí</td><td>(servicio Windows)</td></tr><tr><td>Backend .NET</td><td>5000</td><td>sí</td><td><code>dotnet watch ... run</code></td></tr><tr><td>Frontend Angular</td><td>4200</td><td>sí</td><td><code>npm run serve:dev</code></td></tr><tr><td>Engine RAG .NET (ONNX)</td><td>in-process</td><td>no</td><td>cargado por el backend en el primer chat</td></tr></tbody></table><h2>Quick Start — primer componente</h2><p>1. Configura el endpoint AsmxProxy.</p><p>2. Define route metadata y columnas.</p><p>3. Monta <code>wuic-data-source</code> + <code>wuic-data-repeater</code>.</p><p>Snippet 5:</p>",
+                    "html": "<h1>Panorámica del Framework</h1><p>WUIC Framework es una plataforma metadata-driven para crear interfaces de negocio de forma rápida y coherente.</p><h2>Qué incluye</h2><ul><li>DataSource y DataRepeater para orquestar datos y renderizado.</li><li>Archetypes visuales (list, map, scheduler, chart, carousel).</li><li>Designer runtime para dashboards y templates dinámicos.</li><li>Workflow designer/runner para procesos operativos.</li><li>RAG Chatbot para consultar la codebase en lenguaje natural.</li><li>Multi-SGBD: SQL Server, MySQL, PostgreSQL y Oracle mediante providers drop-in (<code>dbms</code>: <code>mssql</code> | <code>mysql</code> | <code>postgresql</code> | <code>oracle</code>).</li></ul><h2>First Steps — Arranque del entorno dev</h2><p>El stack WUIC está compuesto por varios servicios. Arráncalos en el orden indicado.</p><h3>Prerrequisitos</h3><table><thead><tr><th>Qué</th><th>Verificación</th><th>Notas</th></tr></thead><tbody><tr><td>.NET 10 SDK</td><td><code>dotnet --version</code></td><td>Hosting Bundle para IIS en producción</td></tr><tr><td>Node.js 22 LTS</td><td><code>node --version</code></td><td>La 22 es la version con la que se prueba el paquete; con npm 10.9.x la instalacion funciona gracias al <code>package-lock.json</code> incluido</td></tr><tr><td>PowerShell 5.1+</td><td><code>$PSVersionTable.PSVersion</code></td><td>El Windows PowerShell preinstalado es suficiente: <code>rename-project.ps1</code> y los scripts <code>llm-workspace/</code> tambien funcionan en 5.1. PowerShell 7 es recomendable, no obligatorio</td></tr><tr><td>SQL Server 2019+</td><td><code>sqlcmd -S localhost\\sqlexpress -E -C -Q &quot;SELECT 1&quot;</code></td><td>Si falta, <strong>la línea única lo instala por su cuenta</strong> (SQL Server Express, o el motor elegido con <code>-Dbms</code>); en Windows Server no, ver el recuadro de abajo. 2019 basta para los paquetes sin <code>.bak</code>; el tutorial <code>.bak</code> es una copia de SQL Server 2022 y requiere <strong>2022 o superior</strong></td></tr><tr><td>Linux (instalador <code>install.sh</code>)</td><td><code>lsb_release -ds</code></td><td><strong>Ubuntu 22.04 o 24.04 LTS</strong> (24.04 recomendada): son las unicas versiones de Ubuntu que Microsoft soporta para SQL Server, la <strong>26.04 no esta soportada</strong> (<a href=\"https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-setup?view=sql-server-ver17\" target=\"_blank\" rel=\"noopener noreferrer\">Supported platforms</a>). Misma recomendacion con MySQL, PostgreSQL y Oracle, porque el instalador esta probado en esas versiones</td></tr><tr><td>GPU NVIDIA (CUDA 12.x + cuDNN 9)</td><td><code>nvidia-smi</code></td><td>Opcional: acelera el RAG Chatbot (sin GPU funciona en CPU)</td></tr></tbody></table><p>&gt; <strong>En Windows Server la base de datos debe instalarse antes.</strong> La linea unica obtiene los</p><p>&gt; componentes que faltan mediante <code>winget</code>, que no esta presente en Windows Server: sin una</p><p>&gt; instancia ya accesible la instalacion se detiene con `No SQL Server instance reachable and</p><p>&gt; winget is missing`. Instala el motor antes de ejecutar la linea - SQL Server debe ser **2019 o</p><p>&gt; superior<strong> (Express es suficiente; </strong>2022 o superior** para el tutorial <code>.bak</code>), y una 2017 no</p><p>&gt; se acepta. Si la instancia no es la predeterminada, pasala con</p><p>&gt; <code>-SqlServer &#39;localhost\\NOMBREINSTANCIA&#39;</code>. Vale para todos los motores, no solo SQL Server.</p><h3>1. Descarga el template de proyecto</h3><p>En Windows una sola linea de PowerShell lo hace todo: descarga el paquete, comprueba el SDK de .NET 10</p><p>y Node.js 22 (instalando lo que falte), ejecuta <code>dotnet restore</code> y <code>npm install</code>,</p><p>e instala la extension WUIC Assistant en VS Code.</p><p>Snippet 1:</p><p>Opciones útiles en la misma línea: <code>-Dbms mysql</code> (o <code>postgres</code>, <code>oracle</code>) para un motor</p><p>distinto de SQL Server — el instalador lo instala y lo configura él mismo — y <code>-WithTutorial</code></p><p>para descargar también la base de datos de ejemplo.</p><p>Cuando termina, la última pantalla ya es tu lista de tareas:</p><p>Snippet 2:</p><p>La cadena de conexión ya está lista: en el primer arranque el wizard no pide nada más. Con</p><p><code>-Dbms mysql</code> o <code>-Dbms postgres</code> esa línea cambia en consecuencia y lleva dentro usuario y</p><p>contraseña, porque la contraseña del superusuario <strong>la genera el instalador</strong>; esa misma</p><p>contraseña se guarda en <code>wuic-secrets.json</code>, junto a la instalación, y es el único sitio donde</p><p>queda escrita.</p><p>La via manual sigue siendo valida, en cualquier sistema:</p><p>Parte del paquete <code>WuicTest-src-*.zip</code> (enlace en la sección <strong>Download</strong> del sitio).</p><p>Extráelo en una carpeta de trabajo, p. ej. <code>C:\\dev\\WuicTest</code> (los archivos van directamente</p><p>en la raíz, NO dentro de una subcarpeta <code>src/</code>). El paquete contiene:</p><ul><li><code>WuicTest.csproj</code> → proyecto host con <code>&lt;PackageReference Include=&quot;WuicCore&quot; Version=&quot;...&quot; /&gt;</code></li><li><code>wwwroot/</code> → app Angular cuyo <code>package.json</code> referencia <code>wuic-framework-lib</code> desde el registry npm</li><li><code>appsettings.json</code> preconfigurado en modo <code>firstRun = &quot;true&quot;</code> con placeholders <code>__SET_*__</code></li><li><code>appsettings-samples/</code> → 6 templates listos (<code>mssql</code>/<code>mysql</code>, firstRun/post-firstRun, <code>Development</code>)</li></ul><p>&gt; <strong>No hace falta clonar el repositorio del framework</strong>: <code>WuicCore</code> llega como paquete NuGet</p><p>&gt; desde <code>nuget.org</code> y <code>wuic-framework-lib</code> como paquete npm desde el registry npm. El código</p><p>&gt; fuente del framework solo se necesita si quieres modificarlo — típicamente no es tu caso.</p><p>&gt; <strong>npm 10.9.x y los paquetes anteriores a 1.7.1</strong>: esos paquetes no incluyen <code>package-lock.json</code>, y</p><p>&gt; sin lock npm 10.9.x (la version que instala Node 22 LTS) se detiene con</p><p>&gt; <code>Cannot read properties of null (reading &#39;edgesOut&#39;)</code> al resolver las dependencias peer.</p><p>&gt; Descarga el lock publicado junto a la release —</p><p>&gt; <code>https://wuic-framework.com/downloads/locks/&lt;nombre-del-zip&gt;.package-lock.json</code> — colocalo en</p><p>&gt; <code>wwwroot/</code> y ejecuta <code>npm install</code> otra vez. La linea unica <code>-Src</code> lo hace por ti.</p><h3>2. Database</h3><p>Hace falta una instancia del motor accesible. <strong>Con la línea única no hay nada que hacer</strong>:</p><p>la instala y la configura ella, y la cadena de conexión que hay que pegar en el wizard es lo</p><p>último que imprime. En la vía manual la instancia debe existir ya.</p><p>Conexiones en <code>appsettings.json</code>:</p><ul><li><code>MetaDataSQLConnection</code> — DB metadata (menú, tablas, columnas, boards, usuarios)</li><li><code>DataSQLConnection</code> — DB datos de la aplicación</li></ul><p>Si es la primera instalación (<code>AppSettings.firstRun = &quot;true&quot;</code> en el template),</p><p>el wizard de scaffolding en el primer arranque crea el esquema metadata y puebla el DB datos.</p><p>Ver la página <em>Scaffolding inicial</em> para el flujo guiado.</p><p>#### Qué pide el asistente de primer arranque</p><p>En el primer arranque la aplicación no muestra el formulario de acceso sino la página</p><p><strong>Configuración inicial del proyecto</strong>. Se rellena una sola vez: al terminar <code>firstRun</code> pasa a</p><p><code>false</code> y la página no vuelve a aparecer.</p><ul><li><strong>Modo de instalación</strong> — dos entradas: <strong>Base de datos existente</strong>, que registra una base de</li></ul><p>  datos tuya, y <strong>Tutorial WideWorldImporters</strong>, que instala la base de ejemplo. La segunda solo</p><p>  aparece si el paquete trae el tutorial (<code>tutorialAvailable</code>): en los paquetes sin tutorial el</p><p>  desplegable no se muestra y el modo es &quot;Base de datos existente&quot;.</p><ul><li><strong>SGBD</strong> — el motor. Al cambiarlo, la cadena de conexión de abajo se reescribe con la forma</li></ul><p>  del proveedor elegido.</p><ul><li><strong>DataSQLConnection</strong> — la cadena hacia la base de datos, y el campo del que depende todo lo</li></ul><p>  demás: hasta que no pulses <strong>Probar conexión y cargar bases de datos</strong> la lista de bases</p><p>  permanece deshabilitada. La prueba valida las credenciales, enumera las bases del servidor y,</p><p>  en SQL Server, corrige por su cuenta los parámetros de certificado</p><p>  (<code>Encrypt=False;TrustServerCertificate=True</code>) avisándote. <code>Integrated Security</code> solo vale en</p><p>  SQL Server: los demás motores necesitan usuario y contraseña.</p><ul><li><strong>Base de datos</strong> y <strong>Nombre de la base de metadatos</strong> — la primera se elige de la lista que</li></ul><p>  cargó la prueba (en modo tutorial es un campo libre, <code>WideWorldImporters</code> por defecto); la</p><p>  segunda es el nombre de la base de metadatos a crear (<code>metadataDB</code> por defecto, <code>MetadataCRM</code></p><p>  en modo tutorial). Si esa base ya existe, el asistente pide confirmación antes de recrearla.</p><ul><li><strong>Generar automáticamente los metadatos de las tablas</strong> (solo en &quot;Base de datos existente&quot;) —</li></ul><p>  rellena <code>_metadati__tabelle</code> / <code>_metadati__colonne</code> a partir de todas las tablas de la base</p><p>  elegida. Es lo que más alarga el aprovisionamiento en bases con muchas tablas.</p><ul><li><strong>Usuario admin inicial</strong> — nombre de usuario (<code>admin</code> por defecto), contraseña (mínimo 4</li></ul><p>  caracteres) e idioma. No hay contraseña predeterminada: la que escribas aquí es la única con</p><p>  la que entrarás en el primer acceso. El idioma elegido se aplica al usuario admin y a esta</p><p>  misma página.</p><ul><li><strong>RAG Chatbot</strong> — solo la clave de Anthropic, opcional. Nada que instalar: ver el paso 5.</li></ul><p>Al pulsar <strong>Confirmar y crear la base de metadatos</strong> el aprovisionamiento continúa solo, con una</p><p>barra de progreso y el número de lotes procesados. Cuánto dura, medido en las instalaciones de</p><p>prueba: <strong>30 s - 2 min</strong> en modo tutorial, <strong>1-4 min</strong> sobre una base existente con el scaffold</p><p>automático activado. Al terminar, la página deja paso al formulario de acceso.</p><h3>3. Backend (.NET)</h3><p>Desde la raíz de la carpeta extraída (p. ej. <code>C:\\dev\\WuicTest</code>):</p><p>Snippet 3:</p><p>El backend expone las API en <code>http://localhost:5000</code>.</p><h3>4. Frontend (Angular)</h3><p>En una segunda shell, desde la subcarpeta <code>wwwroot/</code>:</p><p>Snippet 4:</p><p>El frontend está disponible en <code>http://localhost:4200</code>.</p><p>Las credenciales son las del usuario admin elegido en el asistente de primer arranque: el</p><p>nombre de usuario es <code>admin</code> si no lo cambiaste, y la contraseña es la que escribiste (no hay</p><p>contraseña predeterminada).</p><h3>5. RAG Chatbot (opcional)</h3><p>El RAG Chatbot (<code>Administración &gt; RAG Chat</code>) se ejecuta **dentro del backend</p><p>.NET**: el motor de retrieval (<code>rag-engine/WuicRagEngine.dll</code>, ONNX Runtime</p><p>in-process) lo carga el backend cuando <code>AppSettings.rag-use-dotnet-engine</code> es</p><p><code>&quot;true&quot;</code> (valor por defecto en los paquetes de release). **Sin Python, sin</p><p>venv, ningún servidor separado que arrancar.**</p><p>La <strong>primera</strong> vez que se abre el chatbot (o al final del first-run) el</p><p>backend descarga por sí solo los modelos ONNX (<code>bge-m3</code> + reranker), el</p><p>tokenizer y el índice (~4,5 GB) desde <code>rag-engine-models-url</code> (por defecto</p><p><code>https://wuic-framework.com/rag-models</code>) en <code>rag-engine/artifacts/</code>. Solo hace</p><p>falta conexión a internet una vez; la descarga corre en segundo plano (1-5 min)</p><p>y llega una notificación in-app al inicio y al final. Mientras tanto el</p><p>componente muestra el estado <strong>RAG offline</strong> y el resto de la aplicación</p><p>funciona con normalidad.</p><p>Claves <code>AppSettings</code> relevantes (todas con valores por defecto listos):</p><ul><li><code>rag-use-dotnet-engine</code> = <code>true</code> — activa el motor .NET (<code>false</code> = fallback Python, ver abajo)</li><li><code>rag-engine-device</code> = <code>auto</code> — <code>auto</code> | <code>cuda</code> | <code>cpu</code>: con GPU NVIDIA (CUDA 12.x + cuDNN 9) ~1 s/consulta, en CPU ~15-25 s/consulta</li><li><code>rag-engine-profile</code> = <code>release</code> — <code>release</code> = fuentes del framework solo como firma; <code>internal</code> = índice completo</li><li><code>rag-engine-models-url</code> — origen de la descarga en el primer arranque</li><li><code>rag-engine-cuda-path</code> = (vacío) — carpeta de las DLL CUDA/cuDNN si no están instaladas a nivel de sistema</li></ul><p>Para el chat con LLM configura <code>rag-llm-provider</code> + <code>rag-llm-api-key</code> (Claude</p><p>vía Anthropic, o un modelo local vía Ollama con <code>rag-llm-base-url</code>). Sin</p><p>provider solo funciona la modalidad retrieval (búsqueda de snippets). Detalle</p><p>de las claves en la página <em>AppSettings</em>.</p><p>&gt; El stack histórico Python (<code>scripts/rag-setup.ps1</code> + <code>rag_server.py</code> en</p><p>&gt; <code>127.0.0.1:8765</code>) solo puede usarse como fallback con</p><p>&gt; <code>rag-use-dotnet-engine = &quot;false&quot;</code> y no se incluye en los paquetes de release.</p><h2>Resumen de servicios</h2><table><thead><tr><th>Servicio</th><th>Puerto</th><th>Obligatorio</th><th>Comando rápido</th></tr></thead><tbody><tr><td>SQL Server</td><td>1433</td><td>sí</td><td>(servicio Windows)</td></tr><tr><td>Backend .NET</td><td>5000</td><td>sí</td><td><code>dotnet watch ... run</code></td></tr><tr><td>Frontend Angular</td><td>4200</td><td>sí</td><td><code>npm run serve:dev</code></td></tr><tr><td>Engine RAG .NET (ONNX)</td><td>in-process</td><td>no</td><td>cargado por el backend en el primer chat</td></tr></tbody></table><h2>Quick Start — primer componente</h2><p>1. Configura el endpoint AsmxProxy.</p><p>2. Define route metadata y columnas.</p><p>3. Monta <code>wuic-data-source</code> + <code>wuic-data-repeater</code>.</p><p>Snippet 5:</p><h2>Las primeras listas muestran 20 registros: es el modo Trial</h2><p>Una instalacion recien hecha funciona <strong>sin licencia</strong>, es decir, en modo Trial, y en ese</p><p>modo <strong>cada consulta esta limitada a 20 registros</strong>. No es un error ni un limite de la base</p><p>de datos: una lista que indica &quot;20 de 20&quot; sobre una tabla con miles de filas simplemente</p><p>esta funcionando sin licencia.</p><p>Como confirmarlo en un segundo:</p><p>Snippet 6:</p><p><code>licenseValid: false</code> confirma el modo Trial, y <code>licenseReason</code> dice por que</p><p>(<code>invalid_signature</code>, <code>license_expired</code>, <code>machine_fingerprint_not_authorized</code>, ...).</p><p>Como salir: se pega la licencia desde <strong>Administracion &gt; Editor AppSettings</strong>, pestana Licensing,</p><p>y tiene efecto de inmediato: no hace falta reiniciar el backend. Los detalles, incluidos los</p><p>limites que el modo Trial impone mas alla del numero de registros, estan en la pagina</p><p><a href=\"licensing.md\">Licensing</a>.</p>",
                     "codeSamples": [
                         {
                             "id": "code_1",
@@ -21289,25 +21347,31 @@ const frameworkDocsContent = {
                             "id": "code_2",
                             "title": "Snippet 2",
                             "language": "text",
-                            "code": "Developer workspace ready: C:\\Users\\<user>\\AppData\\Local\\WUIC\\app\r\n\r\n  code \"C:\\Users\\<user>\\AppData\\Local\\WUIC\\app\\WuicTest.code-workspace\"\r\n  then F5 > 'Fullstack: WuicTest + Chrome' (backend http://localhost:5000, frontend http://localhost:4200)\r\n\r\nFirst start opens the first-run wizard: paste this connection string (Windows authentication)\r\n  Data Source=localhost\\SQLEXPRESS;Integrated Security=SSPI;Initial Catalog=WuicData;Encrypt=False;TrustServerCertificate=True\r\nRename the project: .\\rename-project.ps1 -Name MyApp"
+                            "code": "Developer workspace ready: C:\\Users\\<user>\\AppData\\Local\\WUIC\\app\n\n  code \"C:\\Users\\<user>\\AppData\\Local\\WUIC\\app\\WuicTest.code-workspace\"\n  then F5 > 'Fullstack: WuicTest + Chrome' (backend http://localhost:5000, frontend http://localhost:4200)\n\nFirst start opens the first-run wizard: paste this connection string (Windows authentication)\n  Data Source=localhost\\SQLEXPRESS;Integrated Security=SSPI;Initial Catalog=WuicData;Encrypt=False;TrustServerCertificate=True\nRename the project: .\\rename-project.ps1 -Name MyApp"
                         },
                         {
                             "id": "code_3",
                             "title": "Snippet 3",
                             "language": "powershell",
-                            "code": "# Primera vez: restore paquetes NuGet (pulls WuicCore + deps desde nuget.org, ~30 s)\r\ndotnet restore\r\n\r\n# Arranque dev con hot reload\r\n$env:ASPNETCORE_ENVIRONMENT = 'Development'\r\ndotnet watch run\r\n\r\n# O arranque one-shot (sin hot reload)\r\ndotnet run"
+                            "code": "# Primera vez: restore paquetes NuGet (pulls WuicCore + deps desde nuget.org, ~30 s)\ndotnet restore\n\n# Arranque dev con hot reload\n$env:ASPNETCORE_ENVIRONMENT = 'Development'\ndotnet watch run\n\n# O arranque one-shot (sin hot reload)\ndotnet run"
                         },
                         {
                             "id": "code_4",
                             "title": "Snippet 4",
                             "language": "powershell",
-                            "code": "cd wwwroot\r\n\r\n# Primera vez: restore dependencias npm (pulls wuic-framework-lib desde npm registry, ~2 min)\r\nnpm install\r\n\r\n# Arranque dev server\r\nnpm run serve:dev"
+                            "code": "cd wwwroot\n\n# Primera vez: restore dependencias npm (pulls wuic-framework-lib desde npm registry, ~2 min)\nnpm install\n\n# Arranque dev server\nnpm run serve:dev"
                         },
                         {
                             "id": "code_5",
                             "title": "Snippet 5",
                             "language": "html",
-                            "code": "<wuic-data-source [hardcodedRoute]=\"'cities'\"></wuic-data-source>\r\n<wuic-data-repeater [hardcodedAction]=\"'list'\"></wuic-data-repeater>"
+                            "code": "<wuic-data-source [hardcodedRoute]=\"'cities'\"></wuic-data-source>\n<wuic-data-repeater [hardcodedAction]=\"'list'\"></wuic-data-repeater>"
+                        },
+                        {
+                            "id": "code_6",
+                            "title": "Snippet 6",
+                            "language": "bash",
+                            "code": "curl -s http://localhost:5000/api/Meta/LicenseStatus"
                         }
                     ]
                 }
@@ -21342,18 +21406,22 @@ const frameworkDocsContent = {
             "toc": [
                 {
                     "id": "sec_1",
-                    "title": "Cuándo usarlo"
+                    "title": "Con un paquete tutorial no hay nada que scaffoldar"
                 },
                 {
                     "id": "sec_2",
-                    "title": "Comportamiento con firstRun=true"
+                    "title": "Cuándo usarlo"
                 },
                 {
                     "id": "sec_3",
-                    "title": "Operaciones típicas"
+                    "title": "Comportamiento con firstRun=true"
                 },
                 {
                     "id": "sec_4",
+                    "title": "Operaciones típicas"
+                },
+                {
+                    "id": "sec_5",
                     "title": "Después del provisioning"
                 }
             ],
@@ -21361,7 +21429,7 @@ const frameworkDocsContent = {
                 {
                     "id": "overview",
                     "title": "Overview",
-                    "html": "<h1>Scaffolding inicial</h1><p>Esta página describe el bootstrap inicial cuando <code>AppSettings.firstRun = true</code>.</p><h2>Cuándo usarlo</h2><ul><li>Nueva instalación (DB metadata/datos aún no preparados).</li><li>Entorno local a realinear con la configuración inicial.</li><li>Primer arranque después del deploy donde se quiere forzar el procedimiento guiado de provisioning.</li></ul><h2>Comportamiento con firstRun=true</h2><ul><li>El endpoint <code>GET /api/Meta/FirstRunStatus</code> expone <code>firstRun: true</code>.</li><li>En el login aparece el flujo de primer arranque (por ejemplo, la acción <code>Aggiorna</code> en la pantalla).</li><li>El setup aplica las configuraciones base (conexiones, ajustes runtime, bootstrap metadata).</li></ul><h2>Operaciones típicas</h2><ul><li>Verifica que <code>AppSettings.firstRun</code> esté a <code>true</code> en <code>appsettings.{Environment}.json</code> del host que estás ejecutando.</li><li>Arranca la aplicación y completa el procedimiento de scaffolding inicial desde la UI.</li><li>Comprueba que las conexiones y los parámetros principales sean coherentes (<code>dbms</code>, <code>DataDBName</code>, <code>ConnectionStrings</code>).</li></ul><h2>Después del provisioning</h2><ul><li>El procedimiento de setup pone <code>firstRun</code> a <code>false</code> para evitar reejecuciones en cada arranque.</li><li>Realiza login estándar y valida el acceso a las routes principales.</li></ul>",
+                    "html": "<h1>Scaffolding inicial</h1><p>Esta página describe el bootstrap inicial cuando <code>AppSettings.firstRun = true</code>.</p><h2>Con un paquete tutorial no hay nada que scaffoldar</h2><p>El scaffolding del que habla esta página — leer las tablas de una base de datos y registrarlas</p><p>en <code>_metadati__tabelle</code> / <code>_metadati__colonne</code> — afecta <strong>solo</strong> al modo &quot;Base de datos</p><p>existente&quot; del asistente de primer arranque: ahí es donde aparece la casilla *Generar</p><p>automáticamente los metadatos de las tablas de la base elegida*.</p><p>En los paquetes <strong>tutorial</strong> esa casilla no existe. La base de metadatos llega ya poblada</p><p>(rutas, columnas, menú, traducciones, cuadros de mando de ejemplo) y el asistente se limita a</p><p>restaurarla y a crear el usuario admin. Ver rutas ya listas justo después del primer arranque no</p><p>es, por tanto, resultado de un scaffolding: es el contenido del tutorial.</p><table><thead><tr><th>Modo del asistente</th><th>Qué pasa con los metadatos</th></tr></thead><tbody><tr><td>Tutorial WideWorldImporters</td><td>Metadatos ya construidos, restaurados desde el paquete. Ningún scaffolding.</td></tr><tr><td>Base existente, casilla apagada</td><td>Base de metadatos vacía: las rutas se registran a mano, o después desde la página Scaffolding.</td></tr><tr><td>Base existente, casilla encendida</td><td>Al final de la instalación cada tabla de la base elegida se registra como ruta.</td></tr></tbody></table><p>El resto de esta página se aplica a las dos últimas filas de esa tabla.</p><h2>Cuándo usarlo</h2><ul><li>Nueva instalación (DB metadata/datos aún no preparados).</li><li>Entorno local a realinear con la configuración inicial.</li><li>Primer arranque después del deploy donde se quiere forzar el procedimiento guiado de provisioning.</li></ul><h2>Comportamiento con firstRun=true</h2><ul><li>El endpoint <code>GET /api/Meta/FirstRunStatus</code> expone <code>firstRun: true</code>.</li><li>En el login aparece el flujo de primer arranque (por ejemplo, la acción <code>Aggiorna</code> en la pantalla).</li><li>El setup aplica las configuraciones base (conexiones, ajustes runtime, bootstrap metadata).</li></ul><h2>Operaciones típicas</h2><ul><li>Verifica que <code>AppSettings.firstRun</code> esté a <code>true</code> en <code>appsettings.{Environment}.json</code> del host que estás ejecutando.</li><li>Arranca la aplicación y completa el procedimiento de scaffolding inicial desde la UI.</li><li>Comprueba que las conexiones y los parámetros principales sean coherentes (<code>dbms</code>, <code>DataDBName</code>, <code>ConnectionStrings</code>).</li></ul><h2>Después del provisioning</h2><ul><li>El procedimiento de setup pone <code>firstRun</code> a <code>false</code> para evitar reejecuciones en cada arranque.</li><li>Realiza login estándar y valida el acceso a las routes principales.</li></ul>",
                     "codeSamples": []
                 }
             ],
@@ -21420,7 +21488,7 @@ const frameworkDocsContent = {
                 {
                     "id": "overview",
                     "title": "Overview",
-                    "html": "<h1>Licensing</h1><p>Esta página explica el licenciamiento desde el punto de vista del usuario final: qué se necesita, cómo obtener la licencia y cómo aplicarla.</p><h2>Cómo obtener una licencia</h2><p>Consulta los planes, las funcionalidades incluidas por nivel (Developer / Professional / Software House) y procede a la compra en el sitio público:</p><ul><li><a href=\"https://wuic-framework.com/pricing\" target=\"_blank\" rel=\"noopener noreferrer\">Precios y planes WUIC — wuic-framework.com/pricing</a></li><li><a href=\"mailto:licensing@wuic-framework.com\">Contacto comercial</a> — no hace falta licencia para evaluar: sin licencia el framework funciona en modo Trial (20 registros por consulta)</li><li><a href=\"https://wuic-framework.com\" target=\"_blank\" rel=\"noopener noreferrer\">Página principal WUIC</a></li></ul><p>Tras la compra recibirás un correo con <code>license-payload</code> + <code>license-signature</code> para instalar como se describe en el &quot;Procedimiento del usuario final&quot; a continuación.</p><h2>Cómo funciona</h2><ul><li>La licencia es válida solo si:</li><li>firma correcta.</li><li><code>machineFingerprint</code> del servidor actual presente en la lista <code>machineFingerprints</code> del payload firmado.</li><li>Si la licencia no es válida, la lectura de datos (<code>getFlatRecordData</code>) se limita a un máximo de 20 registros. Además, el hook host <code>customizeSelect</code> se omite (no se invoca).</li></ul><h2>Dónde encontrar el machineFingerprint</h2><p>Endpoint backend:</p><ul><li><code>GET /api/Meta/LicenseStatus</code> → campo <code>machineFingerprint</code> (siempre disponible, incluso sin licencia).</li><li>Durante el first-run también lo expone <code>GET /api/Meta/FirstRunStatus</code>.</li></ul><p>Nota: el archivo local <code>installation.id</code> ya no se usa para el licenciamiento.</p><h2>Procedimiento para el usuario final</h2><p>1. Recupera <code>machineFingerprint</code> desde tu host.</p><p>2. Envía el valor al proveedor/licenciante.</p><p>3. Recibe los valores de licencia:</p><ul><li><code>license-payload</code></li><li><code>license-signature</code></li><li><code>license-public-key-pem</code> (si lo requiere tu instalación)</li></ul><p>4. Inserta los valores en el archivo <code>appsettings.{Environment}.json</code> del host en ejecución, sección <code>AppSettings</code>.</p><p>5. Reinicia el backend.</p><p>6. Verifica el estado de la licencia desde la API:</p><ul><li><code>GET /api/Meta/LicenseStatus</code></li><li>esperado: <code>licenseValid = true</code>.</li></ul><h2>Licencia multi-máquina</h2><p>Una única licencia puede autorizar múltiples máquinas incluyendo varios valores en <code>machineFingerprints</code>.</p><h2>Solución rápida de problemas</h2><ul><li><code>licenseReason = invalid_signature</code>:</li><li>payload/firma no coherentes entre sí o public key diferente.</li><li><code>licenseReason = machine_fingerprint_not_authorized</code>:</li><li>el fingerprint de la máquina actual no está presente en la licencia recibida.</li><li><code>licenseReason = machine_fingerprint_missing</code>:</li><li>el runtime no puede calcular el fingerprint local.</li><li><code>licenseReason = license_expired</code>:</li><li>la licencia ha expirado, solicita la renovación.</li></ul>",
+                    "html": "<h1>Licensing</h1><p>Esta página explica el licenciamiento desde el punto de vista del usuario final: qué se necesita, cómo obtener la licencia y cómo aplicarla.</p><h2>Cómo obtener una licencia</h2><p>Consulta los planes, las funcionalidades incluidas por nivel (Developer / Professional / Software House) y procede a la compra en el sitio público:</p><ul><li><a href=\"https://wuic-framework.com/pricing\" target=\"_blank\" rel=\"noopener noreferrer\">Precios y planes WUIC — wuic-framework.com/pricing</a></li><li><a href=\"mailto:licensing@wuic-framework.com\">Contacto comercial</a> — no hace falta licencia para evaluar: sin licencia el framework funciona en modo Trial (20 registros por consulta)</li><li><a href=\"https://wuic-framework.com\" target=\"_blank\" rel=\"noopener noreferrer\">Página principal WUIC</a></li></ul><p>Tras la compra recibirás un correo con <code>license-payload</code> + <code>license-signature</code> para instalar como se describe en el &quot;Procedimiento del usuario final&quot; a continuación.</p><h2>Cómo funciona</h2><ul><li>La licencia es válida solo si:</li><li>firma correcta.</li><li><code>machineFingerprint</code> del servidor actual presente en la lista <code>machineFingerprints</code> del payload firmado.</li><li>Si la licencia no es válida, la lectura de datos (<code>getFlatRecordData</code>) se limita a un máximo de 20 registros. Además, el hook host <code>customizeSelect</code> se omite (no se invoca).</li></ul><h2>Dónde encontrar el machineFingerprint</h2><p>Endpoint backend:</p><ul><li><code>GET /api/Meta/LicenseStatus</code> → campo <code>machineFingerprint</code> (siempre disponible, incluso sin licencia).</li><li>Durante el first-run también lo expone <code>GET /api/Meta/FirstRunStatus</code>.</li></ul><p>Nota: el archivo local <code>installation.id</code> ya no se usa para el licenciamiento.</p><h2>Procedimiento para el usuario final</h2><p>1. Recupera <code>machineFingerprint</code> desde tu host.</p><p>2. Envía el valor al proveedor/licenciante.</p><p>3. Recibe los valores de licencia:</p><ul><li><code>license-payload</code></li><li><code>license-signature</code></li><li><code>license-public-key-pem</code> (si lo requiere tu instalación)</li></ul><p>4. Pega los valores desde la interfaz: <strong>Administracion &gt; Editor AppSettings</strong>, sección</p><p>   <strong>License</strong> (campos <code>License email</code>, <code>License payload</code>, <code>License signature</code>,</p><p>   <code>Public key (PEM)</code>), y guarda. También se pueden escribir a mano en la sección</p><p>   <code>AppSettings</code> del archivo <code>appsettings.{Environment}.json</code> del host en ejecución.</p><p>5. Verifica el estado de la licencia:</p><ul><li>desde la API: <code>GET /api/Meta/LicenseStatus</code>, esperado <code>licenseValid = true</code>;</li><li>o desde la propia página, que vuelve a leer la licencia justo después de guardar.</li></ul><p><strong>No hace falta reiniciar el backend si pasas por el editor.</strong> Al guardar <code>license-payload</code> /</p><p><code>license-signature</code> desde el Editor AppSettings el backend recarga por su cuenta el servicio de</p><p>validación, y la licencia vale desde la siguiente petición. El reinicio solo se necesita en el</p><p>otro caso, cuando los valores se escriben a mano en el archivo: ese se lee al arrancar.</p><h2>Licencia multi-máquina</h2><p>Una única licencia puede autorizar múltiples máquinas incluyendo varios valores en <code>machineFingerprints</code>.</p><h2>Solución rápida de problemas</h2><ul><li><code>licenseReason = invalid_signature</code>:</li><li>payload/firma no coherentes entre sí o public key diferente.</li><li><code>licenseReason = machine_fingerprint_not_authorized</code>:</li><li>el fingerprint de la máquina actual no está presente en la licencia recibida.</li><li><code>licenseReason = machine_fingerprint_missing</code>:</li><li>el runtime no puede calcular el fingerprint local.</li><li><code>licenseReason = license_expired</code>:</li><li>la licencia ha expirado, solicita la renovación.</li></ul>",
                     "codeSamples": []
                 }
             ],
@@ -22095,42 +22163,46 @@ const frameworkDocsContent = {
                 },
                 {
                     "id": "sec_2",
-                    "title": "Screenshot de referencia (manual de usuario)"
+                    "title": "Qué muestra la toolbar por defecto"
                 },
                 {
                     "id": "sec_3",
-                    "title": "Metadatos de inline editing"
+                    "title": "Screenshot de referencia (manual de usuario)"
                 },
                 {
                     "id": "sec_4",
-                    "title": "Toolbar export/import"
+                    "title": "Metadatos de inline editing"
                 },
                 {
                     "id": "sec_5",
-                    "title": "Config metadata"
+                    "title": "Toolbar export/import"
                 },
                 {
                     "id": "sec_6",
-                    "title": "md_props_bag: toolbar"
+                    "title": "Config metadata"
                 },
                 {
                     "id": "sec_7",
-                    "title": "md_props_bag: archetypes.list"
+                    "title": "md_props_bag: toolbar"
                 },
                 {
                     "id": "sec_8",
-                    "title": "Paging: md_pagesize y md_page_size_choice"
+                    "title": "md_props_bag: archetypes.list"
                 },
                 {
                     "id": "sec_9",
-                    "title": "Forzado de virtualización en page size alto"
+                    "title": "Paging: md_pagesize y md_page_size_choice"
                 },
                 {
                     "id": "sec_10",
-                    "title": "Eventos y subscriptions (host)"
+                    "title": "Forzado de virtualización en page size alto"
                 },
                 {
                     "id": "sec_11",
+                    "title": "Eventos y subscriptions (host)"
+                },
+                {
+                    "id": "sec_12",
                     "title": "`rowCustomSelect` — firma real (gotcha)"
                 }
             ],
@@ -22138,7 +22210,7 @@ const frameworkDocsContent = {
                 {
                     "id": "overview",
                     "title": "Overview",
-                    "html": "<h1>List Grid</h1><p>Componente principal para listas tabulares con filtros, sorting, paging server-side y acciones de fila.</p><h2>Casos de uso</h2><ul><li>CRUD tabulares enterprise.</li><li>Informes operativos con filtros multi-columna.</li><li>Datasets muy grandes con <code>cursorMode</code>.</li></ul><h2>Screenshot de referencia (manual de usuario)</h2><ul><li><code>manual__grid__01.png</code>: modalidad <code>inline cell edit</code> en list-grid.</li><li><code>manual__grid__02.png</code>: modalidad <code>inline edit</code> (row-level) en list-grid.</li></ul><h2>Metadatos de inline editing</h2><p>Configuración en el <code>md_props_bag</code> de la tabla metadata:</p><ul><li><code>md_inline_edit</code></li></ul><p>  - habilita el editing inline de la fila en list-grid (celdas editables en contexto de fila, sin apertura de popup).</p><p>  - útil cuando se quiere mantener la UX de tabla con edición rápida por registro.</p><ul><li><code>md_inline_cell_edit</code></li></ul><p>  - habilita el editing inline &quot;celda por celda&quot; (foco en la celda individual).</p><p>  - nota: en configuraciones legacy puede aparecer como <code>md_inline_cell_editing</code>; el comportamiento runtime es el mismo.</p><p>  - <strong>promoción runtime</strong>: cuando <code>md_inline_cell_edit</code> es <code>true</code>, el componente fuerza</p><p>    en runtime también <code>md_inline_edit = true</code> independientemente del valor en DB.</p><p>    Ambas UX necesitan la action column visible, por lo que son mutuamente</p><p>    no-exclusivas a nivel de renderizado.</p><ul><li><code>md_batch_save</code></li></ul><p>  - habilita el guardado batch de los cambios pendientes (<code>Save changes</code> / <code>Cancel changes</code>).</p><p>  - si se usa junto con inline-cell, los cambios quedan pending hasta el guardado explícito.</p><p>  - <strong>prerequisito</strong>: <code>md_batch_save</code> tiene efecto <strong>solo</strong> si <code>md_inline_cell_edit</code> es <code>true</code>.</p><p>    Con <code>md_inline_cell_edit:false</code> el flag se ignora en runtime y los botones</p><p>    &quot;Guardar cambios / Cancelar cambios&quot; no se renderizan.</p><h3>Combinaciones válidas</h3><table><thead><tr><th><code>md_inline_edit</code></th><th><code>md_inline_cell_edit</code></th><th><code>md_batch_save</code></th><th>Resultado runtime</th></tr></thead><tbody><tr><td><code>true</code></td><td><code>false</code></td><td>cualquiera</td><td>Inline edit a nivel de fila con pencil. <code>md_batch_save</code> ignorado.</td></tr><tr><td><code>false</code></td><td><code>true</code></td><td><code>false</code></td><td>Cell-by-cell autosave on blur. <code>md_inline_edit</code> forzado a <code>true</code> en runtime.</td></tr><tr><td><code>false</code></td><td><code>true</code></td><td><code>true</code></td><td>Cell-by-cell con buffer pending + toolbar <code>Guardar / Cancelar cambios</code>.</td></tr><tr><td><code>false</code></td><td><code>false</code></td><td>cualquiera</td><td>Sin inline editing. <code>md_batch_save</code> ignorado.</td></tr></tbody></table><p>Ejemplo row-level inline edit:</p><p>Snippet 1:</p><p>Ejemplo cell-by-cell con batch save:</p><p>Snippet 2:</p><h2>Toolbar export/import</h2><ul><li>Export XLS:</li></ul><p>  - muestra diálogo de progreso con porcentaje en tiempo real;</p><p>  - acciones: <code>Continuar en background</code>, <code>Cancelar tarea</code>, <code>Interrumpir y descargar parcial</code>;</p><p>  - en background crea una notificación con progreso; el clic reabre el diálogo.</p><ul><li>Import XLS/XLSX (si <code>md_importable = true</code>):</li></ul><p>  - diálogo de progreso tras la confirmación;</p><p>  - acciones: <code>Continuar en background</code>, <code>Cancelar import (rollback)</code>, <code>Detener y commit parcial</code>;</p><p>  - al finalizar el import crea una notificación de resumen que lleva a la route.</p><h2>Config metadata</h2><p>Ajustes clave en <code>md_props_bag</code> y metadatos de columna.</p><p>Snippet 3:</p><h2>md_props_bag: toolbar</h2><p>Flags opt-in que ocultan bloques de la toolbar de la list-grid (<code>caption-bar</code>). Todos bajo <code>md_props_bag.toolbar.*</code> (parseado en runtime como <code>tableMetadata.extraProps.toolbar</code>).</p><p>Snippet 4:</p><ul><li><code>hideManageState</code> (boolean, default <code>false</code>): oculta en la <strong>caption-right</strong> el botón &quot;Gestionar estado&quot; (icono bookmark) + el <code>&lt;select&gt;</code> de estados guardados. Útil para rutas hardcoded / demo donde el feature saved-state (persistencia por <code>user_id</code> + ruta vía <code>MetaService</code>) no tiene sentido — p. ej. Pattern 3 puro OData sin route metadata registrada.</li><li><code>hideBatchActions</code> (boolean, default <code>false</code>): oculta en la <strong>caption-left</strong> los botones &quot;Guardar cambios&quot; (<code>pi-save</code>) + &quot;Descartar cambios&quot; (<code>pi-times</code>) + el indicador de conteo de changes (<code>grid-changes-indicator</code>, badge pencil + count). Generados por el framework cuando <code>md_inline_cell_editing</code> + <code>md_batch_save</code> están activos. Diseñado para <strong>nested grids dentro de un parametric-dialog</strong>: el save/cancel del padre persiste master + filas en un golpe vía batch save framework, y los botones duplicados en la nested grid confunden la UX.</li></ul><p>Ejemplo nested rows en custom edit-form (runtime patch):</p><p>Snippet 5:</p><p>Tipo TS en <a href=\"../api/wuic-framework-lib.metadatitabella.html\">`metadati_tabella.ts`</a> (propiedad <code>extraProps.toolbar</code>). Los flags NO deshabilitan la lógica <code>md_batch_save</code> subyacente (los changes siguen siendo trackeados); solo eliminan la UI de la toolbar — el save efectivo pasa por el flujo del padre.</p><h2>md_props_bag: archetypes.list</h2><p>El componente lee <code>md_props_bag.archetypes.list</code>.</p><p>Snippet 6:</p><ul><li><code>proportionalColwidth</code>:</li><li>tipo: boolean (con parser tolerante)</li><li>valores aceptados: <code>true</code>, <code>false</code>, <code>1</code>, <code>0</code>, <code>&quot;true&quot;</code>, <code>&quot;false&quot;</code>, <code>&quot;1&quot;</code>, <code>&quot;0&quot;</code></li><li>default runtime: <code>true</code> cuando ausente o vacío</li><li>efecto: distribuye los anchos de columna en porcentaje (en lugar de px) cuando no hay anchos de usuario persistidos.</li></ul><ul><li><code>virtualize</code>:</li><li>tipo: <code>boolean</code> o <code>object</code></li><li>valores aceptados:</li><li><code>true</code>/<code>false</code>, <code>1</code>/<code>0</code>, <code>&quot;true&quot;</code>/<code>&quot;false&quot;</code>, <code>&quot;1&quot;</code>/<code>&quot;0&quot;</code></li><li>object con <code>enabled</code> (opcional) y <code>itemSize</code> (opcional)</li><li>default runtime: deshabilitado (<code>false</code>) cuando ausente</li><li><code>enabled</code>:</li><li>default: <code>true</code> si el nodo <code>virtualize</code> es un object sin <code>enabled</code>, de lo contrario parser tolerante</li><li>efecto: habilita <code>virtualScroll</code> en <code>p-table</code></li><li><code>itemSize</code>:</li><li>default: <code>44</code></li><li>efecto: establece <code>virtualScrollItemSize</code> (altura de fila virtual en px)</li></ul><ul><li><code>advancedFilter</code>:</li><li>tipo: boolean (con parser tolerante)</li><li>default runtime: <code>false</code></li><li>efecto:</li><li>cuando <code>true</code>, la grilla oculta los iconos de filtro de columna (<code>p-columnFilter</code>) y usa la <code>wuic-filter-bar</code> sobre la tabla (a nivel <code>data-repeater</code>/<code>bounded-repeater</code>) para aplicar los filtros.</li></ul><p>Nota operativa:</p><ul><li>el suggest <code>md_props_bag</code> en el metadata editor expone también el nodo checkeable <code>archetypes.list.advancedFilter</code>.</li></ul><h2>Paging: md_pagesize y md_page_size_choice</h2><p>La grilla usa <code>md_pagesize</code> como tamaño de página por defecto y <code>md_page_size_choice</code> como lista de valores seleccionables en el paginador.</p><p>Reglas runtime:</p><ul><li>si <code>md_pagesize</code> es mayor que el valor máximo presente en <code>md_page_size_choice</code>, el framework agrega automáticamente <code>md_pagesize</code> a la lista de opciones;</li><li>la lista se normaliza (números válidos, deduplicación, orden ascendente).</li></ul><p>Ejemplo:</p><ul><li><code>md_pagesize = 200</code></li><li><code>md_page_size_choice = &quot;10,25,50,100&quot;</code></li><li>resultado runtime: <code>10,25,50,100,200</code></li></ul><h2>Forzado de virtualización en page size alto</h2><p>Cuando el usuario selecciona en el paginador un valor <code>pageSize &gt;= 1000</code>:</p><ul><li>la virtualización se fuerza automáticamente aunque <code>md_props_bag.archetypes.list.virtualize</code> esté ausente o deshabilitado;</li><li><code>virtualScrollItemSize</code> se fuerza al valor predeterminado <code>44</code>.</li></ul><p>Este comportamiento protege el rendimiento de la tabla en páginas muy grandes.</p><h2>Eventos y subscriptions (host)</h2><p><code>wuic-list-grid</code> expone eventos runtime útiles para interceptar el ciclo de render y callbacks de p-table en el proyecto host.</p><p>Eventos disponibles:</p><ul><li><code>onAfterRender</code>: emitido al finalizar el binding de datos de la grilla (<code>rows</code>, <code>totalRecords</code>, <code>metaInfo</code>, <code>datasource</code>).</li><li><code>onBeforeRowRender</code>: emitido antes del renderizado lógico de la fila individual; soporta cancelación mediante <code>event.cancelRender()</code>.</li><li><code>onAfterRowRender</code>: emitido después del renderizado lógico de la fila individual.</li><li><code>onPaging</code>: emitido en los eventos de paging (<code>p-table onPage</code>).</li><li><code>onSorting</code>: emitido en los eventos de sorting (<code>p-table onSort</code>).</li><li><code>onFiltering</code>: emitido en los eventos de filtering (<code>p-table onFilter</code>).</li><li><code>onPTableSelectionChange</code>: emitido al cambiar la selección de filas.</li><li><code>onPTableRowExpand</code>: emitido al expandir una fila.</li><li><code>onPTableRowCollapse</code>: emitido al colapsar una fila.</li><li><code>onPTableColumnResize</code>: emitido al redimensionar una columna.</li><li><code>onPTableColumnReorder</code>: emitido al reordenar columnas.</li></ul><h3>Ejemplo 1: binding directo en el template</h3><p>Snippet 7:</p><h3>Ejemplo 2: subscribe vía ViewChild</h3><p>Snippet 8:</p><h2><code>rowCustomSelect</code> — firma real (gotcha)</h2><p><code>&lt;wuic-list-grid&gt;</code> acepta una entrada <code>[rowCustomSelect]</code> para interceptar la seleccion de una fila (apertura de un dialog &quot;elige un documento&quot;, flujo master-detail, etc.). La firma TypeScript declarada en <a href=\"../../src/lib/component/list-grid/list-grid.component.ts#L140\">list-grid.component.ts:140</a> es:</p><p>Snippet 9:</p><p><strong>Pero en runtime la callback se invoca con argumentos invertidos</strong> — el framework llama <code>rowCustomSelect($event, rowData, dt)</code> (ver <a href=\"../../src/lib/component/dynamic-template/dynamic-template.component.ts#L447\">dynamic-template.component.ts:447</a> y <a href=\"../../src/lib/component/dynamic-template/dynamic-card-template.component.ts#L205\">dynamic-card-template.component.ts:205</a>).</p><p>Sintoma cuando el orden es erroneo: <code>rowData?.id</code> es undefined → guard temprano en tu handler → la callback retorna silenciosamente y tu dialog/accion no arranca. Ningun error en consola.</p><p>Forma correcta (alineada con la invocacion runtime):</p><p>Snippet 10:</p><p>Uso en el template:</p><p>Snippet 11:</p><p>&gt; Nota: los tests en <code>designer.component.spec.ts</code> (p. ej. linea 512) invocan la callback con <code>({currentTarget: rowCell}, {id: 42}, null)</code>, confirmando el orden <code>($event, rowData, dt)</code>. Si en el futuro el framework alinea la firma declarada, esta pagina se actualizara.</p>",
+                    "html": "<h1>List Grid</h1><p>Componente principal para listas tabulares con filtros, sorting, paging server-side y acciones de fila.</p><h2>Casos de uso</h2><ul><li>CRUD tabulares enterprise.</li><li>Informes operativos con filtros multi-columna.</li><li>Datasets muy grandes con <code>cursorMode</code>.</li></ul><h2>Qué muestra la toolbar por defecto</h2><p>Al abrir una ruta recién scaffoldada, la caption-bar está encima de la rejilla. A la izquierda:</p><table><thead><tr><th>Botón</th><th>Cuándo aparece</th></tr></thead><tbody><tr><td><strong>Actualizar</strong></td><td>siempre, salvo <code>md_hide_refresh</code></td></tr><tr><td><strong>Agregar</strong></td><td>con <code>md_insertable</code></td></tr><tr><td><strong>Comportamiento</strong></td><td>si la tabla tiene acciones personalizadas</td></tr><tr><td>Import / Export</td><td>siempre; la rama de import solo con <code>md_importable</code></td></tr><tr><td><strong>Informes</strong></td><td>si hay al menos un informe asociado a la ruta</td></tr><tr><td><strong>Guardar cambios</strong> / <strong>Descartar cambios</strong></td><td>solo con <code>md_inline_cell_edit</code> <strong>y</strong> <code>md_batch_save</code></td></tr></tbody></table><p>A la derecha: <strong>Gestionar estado</strong> (precedido por el desplegable de estados guardados, si los</p><p>hay), <strong>Limpiar filtros</strong> cuando los filtros están en las columnas, y <strong>Rendimiento</strong> si el</p><p>inspector está habilitado en la ruta.</p><p>&gt; Las etiquetas citadas más abajo en esta página <strong>no están en esa pantalla</strong>, y no es un</p><p>&gt; defecto: las de export/import (<em>Continuar en segundo plano</em>, <em>Cancelar tarea</em>, *Detener y</p><p>&gt; descargar parcial<em>, </em>Cancelar import (rollback)<em>, </em>Detener y confirmar parcial*) viven en el</p><p>&gt; diálogo de progreso, que solo existe mientras un export o un import está en curso; *Guardar</p><p>&gt; cambios<em> y </em>Descartar cambios* solo aparecen con los dos flags de arriba. Pertenecen a</p><p>&gt; momentos distintos de la primera apertura de la lista.</p><h2>Screenshot de referencia (manual de usuario)</h2><ul><li><code>manual__grid__01.png</code>: modalidad <code>inline cell edit</code> en list-grid.</li><li><code>manual__grid__02.png</code>: modalidad <code>inline edit</code> (row-level) en list-grid.</li></ul><h2>Metadatos de inline editing</h2><p>Configuración en el <code>md_props_bag</code> de la tabla metadata:</p><ul><li><code>md_inline_edit</code></li></ul><p>  - habilita el editing inline de la fila en list-grid (celdas editables en contexto de fila, sin apertura de popup).</p><p>  - útil cuando se quiere mantener la UX de tabla con edición rápida por registro.</p><ul><li><code>md_inline_cell_edit</code></li></ul><p>  - habilita el editing inline &quot;celda por celda&quot; (foco en la celda individual).</p><p>  - nota: en configuraciones legacy puede aparecer como <code>md_inline_cell_editing</code>; el comportamiento runtime es el mismo.</p><p>  - <strong>promoción runtime</strong>: cuando <code>md_inline_cell_edit</code> es <code>true</code>, el componente fuerza</p><p>    en runtime también <code>md_inline_edit = true</code> independientemente del valor en DB.</p><p>    Ambas UX necesitan la action column visible, por lo que son mutuamente</p><p>    no-exclusivas a nivel de renderizado.</p><ul><li><code>md_batch_save</code></li></ul><p>  - habilita el guardado batch de los cambios pendientes (<code>Save changes</code> / <code>Cancel changes</code>).</p><p>  - si se usa junto con inline-cell, los cambios quedan pending hasta el guardado explícito.</p><p>  - <strong>prerequisito</strong>: <code>md_batch_save</code> tiene efecto <strong>solo</strong> si <code>md_inline_cell_edit</code> es <code>true</code>.</p><p>    Con <code>md_inline_cell_edit:false</code> el flag se ignora en runtime y los botones</p><p>    &quot;Guardar cambios / Cancelar cambios&quot; no se renderizan.</p><h3>Combinaciones válidas</h3><table><thead><tr><th><code>md_inline_edit</code></th><th><code>md_inline_cell_edit</code></th><th><code>md_batch_save</code></th><th>Resultado runtime</th></tr></thead><tbody><tr><td><code>true</code></td><td><code>false</code></td><td>cualquiera</td><td>Inline edit a nivel de fila con pencil. <code>md_batch_save</code> ignorado.</td></tr><tr><td><code>false</code></td><td><code>true</code></td><td><code>false</code></td><td>Cell-by-cell autosave on blur. <code>md_inline_edit</code> forzado a <code>true</code> en runtime.</td></tr><tr><td><code>false</code></td><td><code>true</code></td><td><code>true</code></td><td>Cell-by-cell con buffer pending + toolbar <code>Guardar / Cancelar cambios</code>.</td></tr><tr><td><code>false</code></td><td><code>false</code></td><td>cualquiera</td><td>Sin inline editing. <code>md_batch_save</code> ignorado.</td></tr></tbody></table><p>Ejemplo row-level inline edit:</p><p>Snippet 1:</p><p>Ejemplo cell-by-cell con batch save:</p><p>Snippet 2:</p><h2>Toolbar export/import</h2><ul><li>Export XLS:</li></ul><p>  - muestra diálogo de progreso con porcentaje en tiempo real;</p><p>  - acciones: <code>Continuar en background</code>, <code>Cancelar tarea</code>, <code>Interrumpir y descargar parcial</code>;</p><p>  - en background crea una notificación con progreso; el clic reabre el diálogo.</p><ul><li>Import XLS/XLSX (si <code>md_importable = true</code>):</li></ul><p>  - diálogo de progreso tras la confirmación;</p><p>  - acciones: <code>Continuar en background</code>, <code>Cancelar import (rollback)</code>, <code>Detener y commit parcial</code>;</p><p>  - al finalizar el import crea una notificación de resumen que lleva a la route.</p><h2>Config metadata</h2><p>Ajustes clave en <code>md_props_bag</code> y metadatos de columna.</p><p>Snippet 3:</p><h2>md_props_bag: toolbar</h2><p>Flags opt-in que ocultan bloques de la toolbar de la list-grid (<code>caption-bar</code>). Todos bajo <code>md_props_bag.toolbar.*</code> (parseado en runtime como <code>tableMetadata.extraProps.toolbar</code>).</p><p>Snippet 4:</p><ul><li><code>hideManageState</code> (boolean, default <code>false</code>): oculta en la <strong>caption-right</strong> el botón &quot;Gestionar estado&quot; (icono bookmark) + el <code>&lt;select&gt;</code> de estados guardados. Útil para rutas hardcoded / demo donde el feature saved-state (persistencia por <code>user_id</code> + ruta vía <code>MetaService</code>) no tiene sentido — p. ej. Pattern 3 puro OData sin route metadata registrada.</li><li><code>hideBatchActions</code> (boolean, default <code>false</code>): oculta en la <strong>caption-left</strong> los botones &quot;Guardar cambios&quot; (<code>pi-save</code>) + &quot;Descartar cambios&quot; (<code>pi-times</code>) + el indicador de conteo de changes (<code>grid-changes-indicator</code>, badge pencil + count). Generados por el framework cuando <code>md_inline_cell_editing</code> + <code>md_batch_save</code> están activos. Diseñado para <strong>nested grids dentro de un parametric-dialog</strong>: el save/cancel del padre persiste master + filas en un golpe vía batch save framework, y los botones duplicados en la nested grid confunden la UX.</li></ul><p>Ejemplo nested rows en custom edit-form (runtime patch):</p><p>Snippet 5:</p><p>Tipo TS en <a href=\"../api/wuic-framework-lib.metadatitabella.html\">`metadati_tabella.ts`</a> (propiedad <code>extraProps.toolbar</code>). Los flags NO deshabilitan la lógica <code>md_batch_save</code> subyacente (los changes siguen siendo trackeados); solo eliminan la UI de la toolbar — el save efectivo pasa por el flujo del padre.</p><h2>md_props_bag: archetypes.list</h2><p>El componente lee <code>md_props_bag.archetypes.list</code>.</p><p>Snippet 6:</p><ul><li><code>proportionalColwidth</code>:</li><li>tipo: boolean (con parser tolerante)</li><li>valores aceptados: <code>true</code>, <code>false</code>, <code>1</code>, <code>0</code>, <code>&quot;true&quot;</code>, <code>&quot;false&quot;</code>, <code>&quot;1&quot;</code>, <code>&quot;0&quot;</code></li><li>default runtime: <code>true</code> cuando ausente o vacío</li><li>efecto: distribuye los anchos de columna en porcentaje (en lugar de px) cuando no hay anchos de usuario persistidos.</li></ul><ul><li><code>virtualize</code>:</li><li>tipo: <code>boolean</code> o <code>object</code></li><li>valores aceptados:</li><li><code>true</code>/<code>false</code>, <code>1</code>/<code>0</code>, <code>&quot;true&quot;</code>/<code>&quot;false&quot;</code>, <code>&quot;1&quot;</code>/<code>&quot;0&quot;</code></li><li>object con <code>enabled</code> (opcional) y <code>itemSize</code> (opcional)</li><li>default runtime: deshabilitado (<code>false</code>) cuando ausente</li><li><code>enabled</code>:</li><li>default: <code>true</code> si el nodo <code>virtualize</code> es un object sin <code>enabled</code>, de lo contrario parser tolerante</li><li>efecto: habilita <code>virtualScroll</code> en <code>p-table</code></li><li><code>itemSize</code>:</li><li>default: <code>44</code></li><li>efecto: establece <code>virtualScrollItemSize</code> (altura de fila virtual en px)</li></ul><ul><li><code>advancedFilter</code>:</li><li>tipo: boolean (con parser tolerante)</li><li>default runtime: <code>false</code></li><li>efecto:</li><li>cuando <code>true</code>, la grilla oculta los iconos de filtro de columna (<code>p-columnFilter</code>) y usa la <code>wuic-filter-bar</code> sobre la tabla (a nivel <code>data-repeater</code>/<code>bounded-repeater</code>) para aplicar los filtros.</li></ul><p>Nota operativa:</p><ul><li>el suggest <code>md_props_bag</code> en el metadata editor expone también el nodo checkeable <code>archetypes.list.advancedFilter</code>.</li></ul><h2>Paging: md_pagesize y md_page_size_choice</h2><p>La grilla usa <code>md_pagesize</code> como tamaño de página por defecto y <code>md_page_size_choice</code> como lista de valores seleccionables en el paginador.</p><p>Reglas runtime:</p><ul><li>si <code>md_pagesize</code> es mayor que el valor máximo presente en <code>md_page_size_choice</code>, el framework agrega automáticamente <code>md_pagesize</code> a la lista de opciones;</li><li>la lista se normaliza (números válidos, deduplicación, orden ascendente).</li></ul><p>Ejemplo:</p><ul><li><code>md_pagesize = 200</code></li><li><code>md_page_size_choice = &quot;10,25,50,100&quot;</code></li><li>resultado runtime: <code>10,25,50,100,200</code></li></ul><h2>Forzado de virtualización en page size alto</h2><p>Cuando el usuario selecciona en el paginador un valor <code>pageSize &gt;= 1000</code>:</p><ul><li>la virtualización se fuerza automáticamente aunque <code>md_props_bag.archetypes.list.virtualize</code> esté ausente o deshabilitado;</li><li><code>virtualScrollItemSize</code> se fuerza al valor predeterminado <code>44</code>.</li></ul><p>Este comportamiento protege el rendimiento de la tabla en páginas muy grandes.</p><h2>Eventos y subscriptions (host)</h2><p><code>wuic-list-grid</code> expone eventos runtime útiles para interceptar el ciclo de render y callbacks de p-table en el proyecto host.</p><p>Eventos disponibles:</p><ul><li><code>onAfterRender</code>: emitido al finalizar el binding de datos de la grilla (<code>rows</code>, <code>totalRecords</code>, <code>metaInfo</code>, <code>datasource</code>).</li><li><code>onBeforeRowRender</code>: emitido antes del renderizado lógico de la fila individual; soporta cancelación mediante <code>event.cancelRender()</code>.</li><li><code>onAfterRowRender</code>: emitido después del renderizado lógico de la fila individual.</li><li><code>onPaging</code>: emitido en los eventos de paging (<code>p-table onPage</code>).</li><li><code>onSorting</code>: emitido en los eventos de sorting (<code>p-table onSort</code>).</li><li><code>onFiltering</code>: emitido en los eventos de filtering (<code>p-table onFilter</code>).</li><li><code>onPTableSelectionChange</code>: emitido al cambiar la selección de filas.</li><li><code>onPTableRowExpand</code>: emitido al expandir una fila.</li><li><code>onPTableRowCollapse</code>: emitido al colapsar una fila.</li><li><code>onPTableColumnResize</code>: emitido al redimensionar una columna.</li><li><code>onPTableColumnReorder</code>: emitido al reordenar columnas.</li></ul><h3>Ejemplo 1: binding directo en el template</h3><p>Snippet 7:</p><h3>Ejemplo 2: subscribe vía ViewChild</h3><p>Snippet 8:</p><h2><code>rowCustomSelect</code> — firma real (gotcha)</h2><p><code>&lt;wuic-list-grid&gt;</code> acepta una entrada <code>[rowCustomSelect]</code> para interceptar la seleccion de una fila (apertura de un dialog &quot;elige un documento&quot;, flujo master-detail, etc.). La firma TypeScript declarada en <a href=\"../../src/lib/component/list-grid/list-grid.component.ts#L140\">list-grid.component.ts:140</a> es:</p><p>Snippet 9:</p><p><strong>Pero en runtime la callback se invoca con argumentos invertidos</strong> — el framework llama <code>rowCustomSelect($event, rowData, dt)</code> (ver <a href=\"../../src/lib/component/dynamic-template/dynamic-template.component.ts#L447\">dynamic-template.component.ts:447</a> y <a href=\"../../src/lib/component/dynamic-template/dynamic-card-template.component.ts#L205\">dynamic-card-template.component.ts:205</a>).</p><p>Sintoma cuando el orden es erroneo: <code>rowData?.id</code> es undefined → guard temprano en tu handler → la callback retorna silenciosamente y tu dialog/accion no arranca. Ningun error en consola.</p><p>Forma correcta (alineada con la invocacion runtime):</p><p>Snippet 10:</p><p>Uso en el template:</p><p>Snippet 11:</p><p>&gt; Nota: los tests en <code>designer.component.spec.ts</code> (p. ej. linea 512) invocan la callback con <code>({currentTarget: rowCell}, {id: 42}, null)</code>, confirmando el orden <code>($event, rowData, dt)</code>. Si en el futuro el framework alinea la firma declarada, esta pagina se actualizara.</p>",
                     "codeSamples": [
                         {
                             "id": "code_1",
@@ -23864,7 +23936,7 @@ const frameworkDocsContent = {
                 {
                     "id": "overview",
                     "title": "Overview",
-                    "html": "<h1>Designer</h1><p>Editor visual para dashboards metadata-driven en la route <code>#/cities/dashboard</code>.</p><h2>Scope</h2><ul><li>Composición de boards mediante drag-and-drop de nodos y bloques UI.</li><li>Layout y estilos controlados por <code>boardcontent</code> y metadata de tabla/columna.</li><li>Edición en el panel de propiedades sin hardcode en los componentes runtime.</li></ul><h2>Palette Designer</h2><ul><li><code>Datasource</code>: fuente de datos metadata (<code>route</code>, filtros, orden, paginación).</li><li><code>DataRepeater</code>: visualización de lista/tarjeta vinculada a un datasource.</li><li><code>Dynamic Template</code>: renderizado de plantilla dinámica con inputs metadata-driven.</li><li><code>Action/Button</code>: acciones de usuario vinculadas a registros y callbacks.</li><li><code>Container/Layout</code>: bloques estructurales para columnas, filas y wrappers.</li></ul><h2>Funcionalidades principales</h2><ul><li>Drag-and-drop de nodos sobre el canvas con persistencia en el <code>boardcontent</code>.</li><li>Panel de propiedades contextual con inputs coherentes con los componentes seleccionados.</li><li>Binding entre nodos (<code>datasource -&gt; repeater/template</code>) con validación mínima.</li><li>Preview runtime integrada y realineamiento de layout.</li><li>Gestión de cambios pendientes con guard antes de salir.</li></ul><h2>Menú contextual de los elementos</h2><p>Clic derecho sobre un elemento del canvas, sobre un elemento del breadcrumb inferior o sobre un nodo del árbol de jerarquía muestra un menú contextual con tres opciones:</p><ul><li><strong>Editar propiedades</strong> (pi-cog) — selecciona el elemento como &quot;current tool&quot; y muestra su panel de propiedades a la derecha; equivalente al clic en el árbol. Útil para editar propiedades de elementos anidados sin tener que buscarlos en la jerarquía.</li><li><strong>Renombrar</strong> (solo breadcrumb) — abre un diálogo para renombrar el <code>displayName</code>.</li><li><strong>Eliminar</strong> — borra el elemento del board.</li></ul><h2>Flujo operativo recomendado</h2><ul><li>Abrir la route del dashboard objetivo.</li><li>Insertar/vincular nodos desde la palette.</li><li>Configurar los <code>inputs</code> esenciales (ej. <code>route</code>, <code>action</code>, <code>datasource</code>).</li><li>Guardar y validar el resultado en runtime.</li></ul><h2>Notas operativas</h2><ul><li>Para correcciones específicas del dashboard, privilegiar patches del <code>boardcontent</code> en lugar de modificaciones globales.</li><li>Evitar propiedades duplicadas entre <code>inputs</code> y estilos inline no coherentes.</li><li>Verificar siempre que los datasources tengan <code>inputs.route</code> valorizada.</li></ul>",
+                    "html": "<h1>Designer</h1><p>Editor visual para dashboards metadata-driven en la route <code>#/cities/dashboard</code>.</p><h2>Scope</h2><ul><li>Composición de boards mediante drag-and-drop de nodos y bloques UI.</li><li>Layout y estilos controlados por <code>boardcontent</code> y metadata de tabla/columna.</li><li>Edición en el panel de propiedades sin hardcode en los componentes runtime.</li></ul><h2>Palette Designer</h2><p>La paleta está dividida en tres grupos. Los nombres de abajo son los que se leen en la paleta,</p><p>en mayúsculas tal como los escribe el designer.</p><p><strong>HTML</strong> — los ladrillos de marcado:</p><table><thead><tr><th>Tool</th><th>Para qué sirve</th></tr></thead><tbody><tr><td><code>TABLE</code></td><td>rejilla de celdas. <code>TR</code> y <code>TD</code> existen como tools pero no se arrastran: los crea la tabla</td></tr><tr><td><code>DIV</code></td><td>contenedor libre, el bloque estructural más usado</td></tr><tr><td><code>SPAN</code>, <code>LABEL</code>, <code>Hx</code></td><td>texto databound; <code>Hx</code> elige el nivel de h1 a h6</td></tr><tr><td><code>ANCHOR</code>, <code>IMG</code>, <code>IMAGE</code>, <code>IFRAME</code></td><td>enlaces, imágenes, contenido externo</td></tr><tr><td><code>UL</code></td><td>lista</td></tr><tr><td><code>BUTTON</code></td><td>botón con callback</td></tr><tr><td><code>INPUT</code>, <code>TEXTAREA</code>, <code>CHECKBOX</code>, <code>SELECT</code>, <code>MULTISELECT</code>, <code>DATE</code></td><td>campos de entrada</td></tr><tr><td><code>KPI</code></td><td>un único valor destacado</td></tr><tr><td><code>SEPARATOR</code>, <code>HR</code></td><td>separadores</td></tr></tbody></table><p><strong>DATA</strong> — los nodos conectados al backend:</p><table><thead><tr><th>Tool</th><th>Para qué sirve</th></tr></thead><tbody><tr><td><code>DATASOURCE</code></td><td>fuente de datos metadata (<code>route</code>, filtros, orden, paginación)</td></tr><tr><td><code>DATAREPEATER</code></td><td>visualización de lista/tarjeta vinculada a un datasource</td></tr><tr><td><code>FILTERBAR</code></td><td>barra de filtros sobre el repeater</td></tr><tr><td><code>PAGER</code></td><td>paginador</td></tr></tbody></table><p><strong>CONTAINER</strong> — los layouts:</p><table><thead><tr><th>Tool</th><th>Para qué sirve</th></tr></thead><tbody><tr><td><code>TABVIEW</code> + <code>TABPANEL</code></td><td>pestañas</td></tr><tr><td><code>SPLITTER</code> + <code>SPLITTER-AREA</code></td><td>paneles redimensionables</td></tr><tr><td><code>ACCORDION</code> + <code>ACCORDION-AREA</code></td><td>secciones en acordeón</td></tr></tbody></table><p>Dos nombres que se buscan en vano: <strong>no existe ningún tool &quot;Dynamic Template&quot;</strong> — la plantilla</p><p>dinámica es lo que renderiza el <code>DATAREPEATER</code>, se configura desde sus propiedades y no se</p><p>arrastra; y <strong>&quot;Container&quot; / &quot;Layout&quot; son el nombre del grupo</strong>, no entradas seleccionables.</p><p>A estos se suman los tools personalizados registrados por el proyecto anfitrión</p><p>(<code>MetadataProviderService.customDesignerTools</code>), que aparecen al final bajo el grupo que</p><p>declaran.</p><h2>Funcionalidades principales</h2><ul><li>Drag-and-drop de nodos sobre el canvas con persistencia en el <code>boardcontent</code>.</li><li>Panel de propiedades contextual con inputs coherentes con los componentes seleccionados.</li><li>Binding entre nodos (<code>datasource -&gt; repeater/template</code>) con validación mínima.</li><li>Preview runtime integrada y realineamiento de layout.</li><li>Gestión de cambios pendientes con guard antes de salir.</li></ul><h2>Menú contextual de los elementos</h2><p>Clic derecho sobre un elemento del canvas, sobre un elemento del breadcrumb inferior o sobre un nodo del árbol de jerarquía muestra un menú contextual con tres opciones:</p><ul><li><strong>Editar propiedades</strong> (pi-cog) — selecciona el elemento como &quot;current tool&quot; y muestra su panel de propiedades a la derecha; equivalente al clic en el árbol. Útil para editar propiedades de elementos anidados sin tener que buscarlos en la jerarquía.</li><li><strong>Renombrar</strong> (solo breadcrumb) — abre un diálogo para renombrar el <code>displayName</code>.</li><li><strong>Eliminar</strong> — borra el elemento del board.</li></ul><h2>Flujo operativo recomendado</h2><ul><li>Abrir la route del dashboard objetivo.</li><li>Insertar/vincular nodos desde la palette.</li><li>Configurar los <code>inputs</code> esenciales (ej. <code>route</code>, <code>action</code>, <code>datasource</code>).</li><li>Guardar y validar el resultado en runtime.</li></ul><h2>Notas operativas</h2><ul><li>Para correcciones específicas del dashboard, privilegiar patches del <code>boardcontent</code> en lugar de modificaciones globales.</li><li>Evitar propiedades duplicadas entre <code>inputs</code> y estilos inline no coherentes.</li><li>Verificar siempre que los datasources tengan <code>inputs.route</code> valorizada.</li></ul>",
                     "codeSamples": []
                 }
             ],
@@ -27979,13 +28051,17 @@ const frameworkDocsContent = {
                 {
                     "id": "sec_4",
                     "title": "Quick Start — erste Komponente"
+                },
+                {
+                    "id": "sec_5",
+                    "title": "Die ersten Listen zeigen 20 Datensaetze: das ist der Trial-Modus"
                 }
             ],
             "sections": [
                 {
                     "id": "overview",
                     "title": "Overview",
-                    "html": "<h1>Framework-Uebersicht</h1><p>WUIC Framework ist eine metadata-gesteuerte Plattform zum schnellen und konsistenten Erstellen von Business-Oberflaechen.</p><h2>Was ist enthalten</h2><ul><li>DataSource und DataRepeater zur Orchestrierung von Daten und Rendering.</li><li>Visuelle Archetypes (list, map, scheduler, chart, carousel).</li><li>Runtime-Designer fuer Dashboards und dynamische Templates.</li><li>Workflow-Designer/Runner fuer operative Prozesse.</li><li>RAG Chatbot zum Abfragen der Codebasis in natuerlicher Sprache.</li><li>Multi-DBMS: SQL Server, MySQL, PostgreSQL und Oracle ueber Drop-in-Provider (<code>dbms</code>: <code>mssql</code> | <code>mysql</code> | <code>postgresql</code> | <code>oracle</code>).</li></ul><h2>First Steps — Dev-Umgebung starten</h2><p>Der WUIC-Stack besteht aus mehreren Diensten. Starte sie in der angegebenen Reihenfolge.</p><h3>Voraussetzungen</h3><table><thead><tr><th>Was</th><th>Verifikation</th><th>Hinweise</th></tr></thead><tbody><tr><td>.NET 10 SDK</td><td><code>dotnet --version</code></td><td>Hosting Bundle fuer IIS in Produktion</td></tr><tr><td>Node.js 22 LTS</td><td><code>node --version</code></td><td>Mit 22 wird das Paket getestet; unter npm 10.9.x gelingt die Installation dank der mitgelieferten <code>package-lock.json</code></td></tr><tr><td>PowerShell 5.1+</td><td><code>$PSVersionTable.PSVersion</code></td><td>Die vorinstallierte Windows PowerShell genuegt: <code>rename-project.ps1</code> und die <code>llm-workspace/</code>-Skripte laufen auch unter 5.1. PowerShell 7 wird empfohlen, ist nicht erforderlich</td></tr><tr><td>SQL Server 2019+</td><td><code>sqlcmd -S localhost\\sqlexpress -E -C -Q &quot;SELECT 1&quot;</code></td><td>Fehlt er, <strong>installiert ihn der Einzeiler selbst</strong> (SQL Server Express, oder die mit <code>-Dbms</code> gewaehlte Engine); auf Windows Server nicht, siehe Kasten unten. 2019 reicht fuer die Pakete ohne <code>.bak</code>; das <code>.bak</code>-Tutorial ist ein SQL Server 2022-Backup und benoetigt <strong>2022 oder neuer</strong></td></tr><tr><td>Linux (Installer <code>install.sh</code>)</td><td><code>lsb_release -ds</code></td><td><strong>Ubuntu 22.04 oder 24.04 LTS</strong> (24.04 empfohlen): nur diese Ubuntu-Versionen werden von Microsoft fuer SQL Server unterstuetzt, die <strong>26.04 wird nicht unterstuetzt</strong> (<a href=\"https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-setup?view=sql-server-ver17\" target=\"_blank\" rel=\"noopener noreferrer\">Supported platforms</a>). Gleiche Empfehlung mit MySQL, PostgreSQL und Oracle, da der Installer auf diesen Versionen getestet ist</td></tr><tr><td>NVIDIA-GPU (CUDA 12.x + cuDNN 9)</td><td><code>nvidia-smi</code></td><td>Optional: beschleunigt den RAG Chatbot (ohne GPU laeuft er auf CPU)</td></tr></tbody></table><p>&gt; <strong>Auf Windows Server muss die Datenbank vorher installiert werden.</strong> Der Einzeiler beschafft</p><p>&gt; fehlende Komponenten ueber <code>winget</code>, das auf Windows Server nicht vorhanden ist: ohne eine</p><p>&gt; bereits erreichbare Instanz bricht die Installation mit `No SQL Server instance reachable and</p><p>&gt; winget is missing` ab. Installiere die Engine also vor dem Ausfuehren der Zeile - SQL Server</p><p>&gt; muss <strong>2019 oder neuer</strong> sein (Express genuegt; <strong>2022 oder neuer</strong> fuer das <code>.bak</code>-Tutorial),</p><p>&gt; eine 2017 wird nicht akzeptiert. Ist es nicht die Standardinstanz, uebergib sie mit</p><p>&gt; <code>-SqlServer &#39;localhost\\INSTANZNAME&#39;</code>. Das gilt fuer alle Engines, nicht nur SQL Server.</p><h3>1. Projekt-Template herunterladen</h3><p>Unter Windows erledigt eine PowerShell-Zeile alles: sie laedt das Paket, prueft .NET SDK 10</p><p>und Node.js 22 (und installiert, was fehlt), fuehrt <code>dotnet restore</code> und <code>npm install</code> aus</p><p>und installiert die Erweiterung WUIC Assistant in VS Code.</p><p>Snippet 1:</p><p>Nuetzliche Optionen auf derselben Zeile: <code>-Dbms mysql</code> (oder <code>postgres</code>, <code>oracle</code>) fuer eine</p><p>andere Engine als SQL Server — der Installer installiert und konfiguriert sie selbst — und</p><p><code>-WithTutorial</code>, um auch die Beispieldatenbank herunterzuladen.</p><p>Wenn er fertig ist, ist der letzte Bildschirm bereits die Aufgabenliste:</p><p>Snippet 2:</p><p>Die Verbindungszeichenfolge ist fertig: beim ersten Start fragt der Wizard nach nichts</p><p>weiterem. Mit <code>-Dbms mysql</code> oder <code>-Dbms postgres</code> aendert sich diese Zeile entsprechend und</p><p>traegt Benutzer und Passwort in sich, denn das Superuser-Passwort <strong>erzeugt der Installer</strong>;</p><p>dasselbe Passwort wird in <code>wuic-secrets.json</code> neben der Installation gespeichert, und das ist</p><p>der einzige Ort, an dem es geschrieben bleibt.</p><p>Der manuelle Weg bleibt gueltig, auf jedem System:</p><p>Starten Sie mit dem Paket <code>WuicTest-src-*.zip</code> (Link im <strong>Download</strong>-Bereich der Website).</p><p>Entpacken Sie es in einen Arbeitsordner, z.B. <code>C:\\dev\\WuicTest</code> (die Dateien kommen direkt</p><p>in den Root, NICHT in einen <code>src/</code>-Unterordner). Das Paket enthaelt:</p><ul><li><code>WuicTest.csproj</code> → Host-Projekt mit <code>&lt;PackageReference Include=&quot;WuicCore&quot; Version=&quot;...&quot; /&gt;</code></li><li><code>wwwroot/</code> → Angular-App, deren <code>package.json</code> <code>wuic-framework-lib</code> aus der npm-Registry referenziert</li><li><code>appsettings.json</code> vorkonfiguriert im <code>firstRun = &quot;true&quot;</code>-Modus mit <code>__SET_*__</code>-Platzhaltern</li><li><code>appsettings-samples/</code> → 6 fertige Templates (<code>mssql</code>/<code>mysql</code>, firstRun/post-firstRun, <code>Development</code>)</li></ul><p>&gt; <strong>Kein Klonen des Framework-Repositories noetig</strong>: <code>WuicCore</code> kommt als NuGet-Paket von</p><p>&gt; <code>nuget.org</code> und <code>wuic-framework-lib</code> als npm-Paket aus der npm-Registry. Der Framework-</p><p>&gt; Quellcode wird nur benoetigt, wenn Sie ihn modifizieren wollen — typischerweise nicht Ihr Fall.</p><p>&gt; <strong>npm 10.9.x und Pakete aelter als 1.7.1</strong>: diese Pakete enthalten keine <code>package-lock.json</code>, und</p><p>&gt; ohne Lock bricht npm 10.9.x (die Version, die Node 22 LTS mitbringt) mit</p><p>&gt; <code>Cannot read properties of null (reading &#39;edgesOut&#39;)</code> bei der Peer-Aufloesung ab.</p><p>&gt; Laden Sie den neben der Release veroeffentlichten Lock herunter —</p><p>&gt; <code>https://wuic-framework.com/downloads/locks/&lt;zip-name&gt;.package-lock.json</code> — legen Sie ihn in</p><p>&gt; <code>wwwroot/</code> und starten Sie <code>npm install</code> erneut. Der <code>-Src</code>-Einzeiler erledigt das selbst.</p><h3>2. Datenbank</h3><p>Es braucht eine erreichbare Instanz der Engine. <strong>Mit dem Einzeiler ist nichts zu tun</strong>: er</p><p>installiert und konfiguriert die Instanz, und die Verbindungszeichenfolge zum Einfuegen in den</p><p>Wizard ist das Letzte, was er ausgibt. Auf dem manuellen Weg muss die Instanz bereits</p><p>vorhanden sein.</p><p>Verbindungen in <code>appsettings.json</code>:</p><ul><li><code>MetaDataSQLConnection</code> — Metadata-DB (Menue, Tabellen, Spalten, Board, Benutzer)</li><li><code>DataSQLConnection</code> — Anwendungsdaten-DB</li></ul><p>Bei Erstinstallation (<code>AppSettings.firstRun = &quot;true&quot;</code> im Template) erstellt der Scaffolding-</p><p>Wizard beim ersten Start das Metadata-Schema und befuellt die Daten-DB.</p><p>Siehe Seite <em>Initial Scaffolding</em> fuer den gefuehrten Flow.</p><h3>3. Backend (.NET)</h3><p>Aus dem Root des entpackten Ordners (z.B. <code>C:\\dev\\WuicTest</code>):</p><p>Snippet 3:</p><p>Das Backend stellt die APIs auf <code>http://localhost:5000</code> bereit.</p><h3>4. Frontend (Angular)</h3><p>In einer zweiten Shell, aus dem Unterordner <code>wwwroot/</code>:</p><p>Snippet 4:</p><p>Das Frontend ist auf <code>http://localhost:4200</code> verfuegbar.</p><p>Standard-Login (post-firstRun): <code>admin</code> / <code>admin</code>.</p><h3>5. RAG Chatbot (optional)</h3><p>Der RAG Chatbot (<code>Amministrazione &gt; RAG Chat</code>) laeuft <strong>im .NET-Backend</strong>: die</p><p>Retrieval-Engine (<code>rag-engine/WuicRagEngine.dll</code>, ONNX Runtime in-process) wird</p><p>vom Backend geladen, wenn <code>AppSettings.rag-use-dotnet-engine</code> auf <code>&quot;true&quot;</code></p><p>steht (Default in den Release-Paketen). **Kein Python, keine venv, kein</p><p>separater Server, der gestartet werden muss.**</p><p>Beim <strong>ersten</strong> Oeffnen des Chatbots (oder am Ende des First-Run) laedt das</p><p>Backend selbststaendig die ONNX-Modelle (<code>bge-m3</code> + Reranker), den Tokenizer</p><p>und den Index (~4,5 GB) von <code>rag-engine-models-url</code> (Default</p><p><code>https://wuic-framework.com/rag-models</code>) nach <code>rag-engine/artifacts/</code>. Eine</p><p>Internetverbindung wird nur einmal benoetigt; der Download laeuft im</p><p>Hintergrund (1-5 Min.) und eine In-App-Benachrichtigung erscheint zu Beginn</p><p>und am Ende. Solange zeigt die Komponente den Status <strong>RAG offline</strong>, der Rest</p><p>der Anwendung funktioniert normal.</p><p>Relevante <code>AppSettings</code>-Schluessel (alle mit fertigen Defaults):</p><ul><li><code>rag-use-dotnet-engine</code> = <code>true</code> — aktiviert die .NET-Engine (<code>false</code> = Python-Fallback, siehe unten)</li><li><code>rag-engine-device</code> = <code>auto</code> — <code>auto</code> | <code>cuda</code> | <code>cpu</code>: mit NVIDIA-GPU (CUDA 12.x + cuDNN 9) ~1 s/Abfrage, auf CPU ~15-25 s/Abfrage</li><li><code>rag-engine-profile</code> = <code>release</code> — <code>release</code> = Framework-Quellen nur als Signatur; <code>internal</code> = vollstaendiger Index</li><li><code>rag-engine-models-url</code> — Download-Quelle beim ersten Start</li><li><code>rag-engine-cuda-path</code> = (leer) — Ordner der CUDA/cuDNN-DLLs, falls nicht systemweit installiert</li></ul><p>Fuer den Chat mit LLM <code>rag-llm-provider</code> + <code>rag-llm-api-key</code> setzen (Claude</p><p>via Anthropic oder ein lokales Modell via Ollama mit <code>rag-llm-base-url</code>). Ohne</p><p>Provider funktioniert nur der Retrieval-Modus (Snippet-Suche). Details zu den</p><p>Schluesseln auf der Seite <em>AppSettings</em>.</p><p>&gt; Der historische Python-Stack (<code>scripts/rag-setup.ps1</code> + <code>rag_server.py</code> auf</p><p>&gt; <code>127.0.0.1:8765</code>) ist nur als Fallback mit <code>rag-use-dotnet-engine = &quot;false&quot;</code></p><p>&gt; nutzbar und ist in den Release-Paketen nicht enthalten.</p><h2>Dienste-Zusammenfassung</h2><table><thead><tr><th>Dienst</th><th>Port</th><th>Erforderlich</th><th>Schnellbefehl</th></tr></thead><tbody><tr><td>SQL Server</td><td>1433</td><td>ja</td><td>(Windows-Dienst)</td></tr><tr><td>Backend .NET</td><td>5000</td><td>ja</td><td><code>dotnet watch ... run</code></td></tr><tr><td>Frontend Angular</td><td>4200</td><td>ja</td><td><code>npm run serve:dev</code></td></tr><tr><td>RAG-Engine .NET (ONNX)</td><td>in-process</td><td>nein</td><td>wird vom Backend beim ersten Chat geladen</td></tr></tbody></table><h2>Quick Start — erste Komponente</h2><p>1. AsmxProxy-Endpoint konfigurieren.</p><p>2. Route-Metadata und Spalten definieren.</p><p>3. <code>wuic-data-source</code> + <code>wuic-data-repeater</code> montieren.</p><p>Snippet 5:</p>",
+                    "html": "<h1>Framework-Uebersicht</h1><p>WUIC Framework ist eine metadata-gesteuerte Plattform zum schnellen und konsistenten Erstellen von Business-Oberflaechen.</p><h2>Was ist enthalten</h2><ul><li>DataSource und DataRepeater zur Orchestrierung von Daten und Rendering.</li><li>Visuelle Archetypes (list, map, scheduler, chart, carousel).</li><li>Runtime-Designer fuer Dashboards und dynamische Templates.</li><li>Workflow-Designer/Runner fuer operative Prozesse.</li><li>RAG Chatbot zum Abfragen der Codebasis in natuerlicher Sprache.</li><li>Multi-DBMS: SQL Server, MySQL, PostgreSQL und Oracle ueber Drop-in-Provider (<code>dbms</code>: <code>mssql</code> | <code>mysql</code> | <code>postgresql</code> | <code>oracle</code>).</li></ul><h2>First Steps — Dev-Umgebung starten</h2><p>Der WUIC-Stack besteht aus mehreren Diensten. Starte sie in der angegebenen Reihenfolge.</p><h3>Voraussetzungen</h3><table><thead><tr><th>Was</th><th>Verifikation</th><th>Hinweise</th></tr></thead><tbody><tr><td>.NET 10 SDK</td><td><code>dotnet --version</code></td><td>Hosting Bundle fuer IIS in Produktion</td></tr><tr><td>Node.js 22 LTS</td><td><code>node --version</code></td><td>Mit 22 wird das Paket getestet; unter npm 10.9.x gelingt die Installation dank der mitgelieferten <code>package-lock.json</code></td></tr><tr><td>PowerShell 5.1+</td><td><code>$PSVersionTable.PSVersion</code></td><td>Die vorinstallierte Windows PowerShell genuegt: <code>rename-project.ps1</code> und die <code>llm-workspace/</code>-Skripte laufen auch unter 5.1. PowerShell 7 wird empfohlen, ist nicht erforderlich</td></tr><tr><td>SQL Server 2019+</td><td><code>sqlcmd -S localhost\\sqlexpress -E -C -Q &quot;SELECT 1&quot;</code></td><td>Fehlt er, <strong>installiert ihn der Einzeiler selbst</strong> (SQL Server Express, oder die mit <code>-Dbms</code> gewaehlte Engine); auf Windows Server nicht, siehe Kasten unten. 2019 reicht fuer die Pakete ohne <code>.bak</code>; das <code>.bak</code>-Tutorial ist ein SQL Server 2022-Backup und benoetigt <strong>2022 oder neuer</strong></td></tr><tr><td>Linux (Installer <code>install.sh</code>)</td><td><code>lsb_release -ds</code></td><td><strong>Ubuntu 22.04 oder 24.04 LTS</strong> (24.04 empfohlen): nur diese Ubuntu-Versionen werden von Microsoft fuer SQL Server unterstuetzt, die <strong>26.04 wird nicht unterstuetzt</strong> (<a href=\"https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-setup?view=sql-server-ver17\" target=\"_blank\" rel=\"noopener noreferrer\">Supported platforms</a>). Gleiche Empfehlung mit MySQL, PostgreSQL und Oracle, da der Installer auf diesen Versionen getestet ist</td></tr><tr><td>NVIDIA-GPU (CUDA 12.x + cuDNN 9)</td><td><code>nvidia-smi</code></td><td>Optional: beschleunigt den RAG Chatbot (ohne GPU laeuft er auf CPU)</td></tr></tbody></table><p>&gt; <strong>Auf Windows Server muss die Datenbank vorher installiert werden.</strong> Der Einzeiler beschafft</p><p>&gt; fehlende Komponenten ueber <code>winget</code>, das auf Windows Server nicht vorhanden ist: ohne eine</p><p>&gt; bereits erreichbare Instanz bricht die Installation mit `No SQL Server instance reachable and</p><p>&gt; winget is missing` ab. Installiere die Engine also vor dem Ausfuehren der Zeile - SQL Server</p><p>&gt; muss <strong>2019 oder neuer</strong> sein (Express genuegt; <strong>2022 oder neuer</strong> fuer das <code>.bak</code>-Tutorial),</p><p>&gt; eine 2017 wird nicht akzeptiert. Ist es nicht die Standardinstanz, uebergib sie mit</p><p>&gt; <code>-SqlServer &#39;localhost\\INSTANZNAME&#39;</code>. Das gilt fuer alle Engines, nicht nur SQL Server.</p><h3>1. Projekt-Template herunterladen</h3><p>Unter Windows erledigt eine PowerShell-Zeile alles: sie laedt das Paket, prueft .NET SDK 10</p><p>und Node.js 22 (und installiert, was fehlt), fuehrt <code>dotnet restore</code> und <code>npm install</code> aus</p><p>und installiert die Erweiterung WUIC Assistant in VS Code.</p><p>Snippet 1:</p><p>Nuetzliche Optionen auf derselben Zeile: <code>-Dbms mysql</code> (oder <code>postgres</code>, <code>oracle</code>) fuer eine</p><p>andere Engine als SQL Server — der Installer installiert und konfiguriert sie selbst — und</p><p><code>-WithTutorial</code>, um auch die Beispieldatenbank herunterzuladen.</p><p>Wenn er fertig ist, ist der letzte Bildschirm bereits die Aufgabenliste:</p><p>Snippet 2:</p><p>Die Verbindungszeichenfolge ist fertig: beim ersten Start fragt der Wizard nach nichts</p><p>weiterem. Mit <code>-Dbms mysql</code> oder <code>-Dbms postgres</code> aendert sich diese Zeile entsprechend und</p><p>traegt Benutzer und Passwort in sich, denn das Superuser-Passwort <strong>erzeugt der Installer</strong>;</p><p>dasselbe Passwort wird in <code>wuic-secrets.json</code> neben der Installation gespeichert, und das ist</p><p>der einzige Ort, an dem es geschrieben bleibt.</p><p>Der manuelle Weg bleibt gueltig, auf jedem System:</p><p>Starten Sie mit dem Paket <code>WuicTest-src-*.zip</code> (Link im <strong>Download</strong>-Bereich der Website).</p><p>Entpacken Sie es in einen Arbeitsordner, z.B. <code>C:\\dev\\WuicTest</code> (die Dateien kommen direkt</p><p>in den Root, NICHT in einen <code>src/</code>-Unterordner). Das Paket enthaelt:</p><ul><li><code>WuicTest.csproj</code> → Host-Projekt mit <code>&lt;PackageReference Include=&quot;WuicCore&quot; Version=&quot;...&quot; /&gt;</code></li><li><code>wwwroot/</code> → Angular-App, deren <code>package.json</code> <code>wuic-framework-lib</code> aus der npm-Registry referenziert</li><li><code>appsettings.json</code> vorkonfiguriert im <code>firstRun = &quot;true&quot;</code>-Modus mit <code>__SET_*__</code>-Platzhaltern</li><li><code>appsettings-samples/</code> → 6 fertige Templates (<code>mssql</code>/<code>mysql</code>, firstRun/post-firstRun, <code>Development</code>)</li></ul><p>&gt; <strong>Kein Klonen des Framework-Repositories noetig</strong>: <code>WuicCore</code> kommt als NuGet-Paket von</p><p>&gt; <code>nuget.org</code> und <code>wuic-framework-lib</code> als npm-Paket aus der npm-Registry. Der Framework-</p><p>&gt; Quellcode wird nur benoetigt, wenn Sie ihn modifizieren wollen — typischerweise nicht Ihr Fall.</p><p>&gt; <strong>npm 10.9.x und Pakete aelter als 1.7.1</strong>: diese Pakete enthalten keine <code>package-lock.json</code>, und</p><p>&gt; ohne Lock bricht npm 10.9.x (die Version, die Node 22 LTS mitbringt) mit</p><p>&gt; <code>Cannot read properties of null (reading &#39;edgesOut&#39;)</code> bei der Peer-Aufloesung ab.</p><p>&gt; Laden Sie den neben der Release veroeffentlichten Lock herunter —</p><p>&gt; <code>https://wuic-framework.com/downloads/locks/&lt;zip-name&gt;.package-lock.json</code> — legen Sie ihn in</p><p>&gt; <code>wwwroot/</code> und starten Sie <code>npm install</code> erneut. Der <code>-Src</code>-Einzeiler erledigt das selbst.</p><h3>2. Datenbank</h3><p>Es braucht eine erreichbare Instanz der Engine. <strong>Mit dem Einzeiler ist nichts zu tun</strong>: er</p><p>installiert und konfiguriert die Instanz, und die Verbindungszeichenfolge zum Einfuegen in den</p><p>Wizard ist das Letzte, was er ausgibt. Auf dem manuellen Weg muss die Instanz bereits</p><p>vorhanden sein.</p><p>Verbindungen in <code>appsettings.json</code>:</p><ul><li><code>MetaDataSQLConnection</code> — Metadata-DB (Menue, Tabellen, Spalten, Board, Benutzer)</li><li><code>DataSQLConnection</code> — Anwendungsdaten-DB</li></ul><p>Bei Erstinstallation (<code>AppSettings.firstRun = &quot;true&quot;</code> im Template) erstellt der Scaffolding-</p><p>Wizard beim ersten Start das Metadata-Schema und befuellt die Daten-DB.</p><p>Siehe Seite <em>Initial Scaffolding</em> fuer den gefuehrten Flow.</p><p>#### Was der First-Run-Wizard abfragt</p><p>Beim ersten Start zeigt die Anwendung nicht das Login, sondern die Seite **Initiale</p><p>Projektkonfiguration**. Sie wird genau einmal ausgefuellt: danach steht <code>firstRun</code> auf <code>false</code></p><p>und die Seite erscheint nicht wieder.</p><ul><li><strong>Setup-Modus</strong> — zwei Eintraege: <strong>Bestehende Datenbank</strong>, die eine eigene Datenbank</li></ul><p>  registriert, und <strong>Tutorial WideWorldImporters</strong>, das die Beispieldatenbank installiert. Der</p><p>  zweite erscheint nur, wenn das Paket das Tutorial mitbringt (<code>tutorialAvailable</code>): in Paketen</p><p>  ohne Tutorial gibt es die Auswahl gar nicht, und der Modus ist &quot;Bestehende Datenbank&quot;.</p><ul><li><strong>DBMS</strong> — die Engine. Beim Wechsel wird die Verbindungszeichenfolge darunter in der Form des</li></ul><p>  gewaehlten Providers neu geschrieben.</p><ul><li><strong>DataSQLConnection</strong> — die Zeichenfolge zur Daten-DB und das Feld, von dem alles Weitere</li></ul><p>  abhaengt: bis <strong>Verbindung testen und Datenbanken laden</strong> gedrueckt wurde, bleibt die</p><p>  Datenbankliste deaktiviert. Der Test prueft die Zugangsdaten, listet die Datenbanken des</p><p>  Servers und korrigiert auf SQL Server selbsttaetig die Zertifikatsparameter</p><p>  (<code>Encrypt=False;TrustServerCertificate=True</code>) und sagt es Ihnen. <code>Integrated Security</code> gilt</p><p>  nur auf SQL Server: die anderen Engines brauchen Benutzer und Passwort.</p><ul><li><strong>Daten-Datenbank</strong> und <strong>Name der Metadaten-DB</strong> — die erste wird aus der vom Test geladenen</li></ul><p>  Liste gewaehlt (im Tutorial-Modus ist es ein freies Textfeld, Standard <code>WideWorldImporters</code>);</p><p>  die zweite ist der Name der anzulegenden Metadaten-DB (Standard <code>metadataDB</code>, im</p><p>  Tutorial-Modus <code>MetadataCRM</code>). Existiert diese Datenbank bereits, fragt der Wizard vor dem</p><p>  Neuanlegen nach.</p><ul><li><strong>Tabellen automatisch scaffolden</strong> (nur bei &quot;Bestehende Datenbank&quot;) — befuellt</li></ul><p>  <code>_metadati__tabelle</code> / <code>_metadati__colonne</code> aus allen Tabellen der gewaehlten Datenbank. Das</p><p>  verlaengert das Provisioning bei Datenbanken mit vielen Tabellen am staerksten.</p><ul><li><strong>Initialer Admin-Benutzer</strong> — Benutzername (Standard <code>admin</code>), Passwort (mindestens 4</li></ul><p>  Zeichen) und Sprache. Es gibt kein Standardpasswort: das hier eingegebene ist das einzige, mit</p><p>  dem die erste Anmeldung gelingt. Die gewaehlte Sprache gilt fuer den Admin-Benutzer und fuer</p><p>  diese Seite selbst.</p><ul><li><strong>RAG Chatbot</strong> — nur der Anthropic-Schluessel, optional. Nichts zu installieren: siehe</li></ul><p>  Schritt 5.</p><p>Nach <strong>Bestaetigen und Metadaten-DB erzeugen</strong> laeuft das Provisioning selbstaendig weiter, mit</p><p>Fortschrittsbalken und der Zahl verarbeiteter Batches. Dauer, gemessen auf den</p><p>Test-Installationen: <strong>30 s - 2 min</strong> im Tutorial-Modus, <strong>1-4 min</strong> auf einer bestehenden</p><p>Datenbank mit aktiviertem automatischem Scaffolding. Am Ende weicht die Seite dem Login-Formular.</p><h3>3. Backend (.NET)</h3><p>Aus dem Root des entpackten Ordners (z.B. <code>C:\\dev\\WuicTest</code>):</p><p>Snippet 3:</p><p>Das Backend stellt die APIs auf <code>http://localhost:5000</code> bereit.</p><h3>4. Frontend (Angular)</h3><p>In einer zweiten Shell, aus dem Unterordner <code>wwwroot/</code>:</p><p>Snippet 4:</p><p>Das Frontend ist auf <code>http://localhost:4200</code> verfuegbar.</p><p>Die Zugangsdaten sind die des im First-Run-Wizard gewaehlten Admin-Benutzers: der</p><p>Benutzername ist <code>admin</code>, sofern nicht geaendert, und das Passwort ist das selbst gesetzte (ein</p><p>Standardpasswort gibt es nicht).</p><h3>5. RAG Chatbot (optional)</h3><p>Der RAG Chatbot (<code>Amministrazione &gt; RAG Chat</code>) laeuft <strong>im .NET-Backend</strong>: die</p><p>Retrieval-Engine (<code>rag-engine/WuicRagEngine.dll</code>, ONNX Runtime in-process) wird</p><p>vom Backend geladen, wenn <code>AppSettings.rag-use-dotnet-engine</code> auf <code>&quot;true&quot;</code></p><p>steht (Default in den Release-Paketen). **Kein Python, keine venv, kein</p><p>separater Server, der gestartet werden muss.**</p><p>Beim <strong>ersten</strong> Oeffnen des Chatbots (oder am Ende des First-Run) laedt das</p><p>Backend selbststaendig die ONNX-Modelle (<code>bge-m3</code> + Reranker), den Tokenizer</p><p>und den Index (~4,5 GB) von <code>rag-engine-models-url</code> (Default</p><p><code>https://wuic-framework.com/rag-models</code>) nach <code>rag-engine/artifacts/</code>. Eine</p><p>Internetverbindung wird nur einmal benoetigt; der Download laeuft im</p><p>Hintergrund (1-5 Min.) und eine In-App-Benachrichtigung erscheint zu Beginn</p><p>und am Ende. Solange zeigt die Komponente den Status <strong>RAG offline</strong>, der Rest</p><p>der Anwendung funktioniert normal.</p><p>Relevante <code>AppSettings</code>-Schluessel (alle mit fertigen Defaults):</p><ul><li><code>rag-use-dotnet-engine</code> = <code>true</code> — aktiviert die .NET-Engine (<code>false</code> = Python-Fallback, siehe unten)</li><li><code>rag-engine-device</code> = <code>auto</code> — <code>auto</code> | <code>cuda</code> | <code>cpu</code>: mit NVIDIA-GPU (CUDA 12.x + cuDNN 9) ~1 s/Abfrage, auf CPU ~15-25 s/Abfrage</li><li><code>rag-engine-profile</code> = <code>release</code> — <code>release</code> = Framework-Quellen nur als Signatur; <code>internal</code> = vollstaendiger Index</li><li><code>rag-engine-models-url</code> — Download-Quelle beim ersten Start</li><li><code>rag-engine-cuda-path</code> = (leer) — Ordner der CUDA/cuDNN-DLLs, falls nicht systemweit installiert</li></ul><p>Fuer den Chat mit LLM <code>rag-llm-provider</code> + <code>rag-llm-api-key</code> setzen (Claude</p><p>via Anthropic oder ein lokales Modell via Ollama mit <code>rag-llm-base-url</code>). Ohne</p><p>Provider funktioniert nur der Retrieval-Modus (Snippet-Suche). Details zu den</p><p>Schluesseln auf der Seite <em>AppSettings</em>.</p><p>&gt; Der historische Python-Stack (<code>scripts/rag-setup.ps1</code> + <code>rag_server.py</code> auf</p><p>&gt; <code>127.0.0.1:8765</code>) ist nur als Fallback mit <code>rag-use-dotnet-engine = &quot;false&quot;</code></p><p>&gt; nutzbar und ist in den Release-Paketen nicht enthalten.</p><h2>Dienste-Zusammenfassung</h2><table><thead><tr><th>Dienst</th><th>Port</th><th>Erforderlich</th><th>Schnellbefehl</th></tr></thead><tbody><tr><td>SQL Server</td><td>1433</td><td>ja</td><td>(Windows-Dienst)</td></tr><tr><td>Backend .NET</td><td>5000</td><td>ja</td><td><code>dotnet watch ... run</code></td></tr><tr><td>Frontend Angular</td><td>4200</td><td>ja</td><td><code>npm run serve:dev</code></td></tr><tr><td>RAG-Engine .NET (ONNX)</td><td>in-process</td><td>nein</td><td>wird vom Backend beim ersten Chat geladen</td></tr></tbody></table><h2>Quick Start — erste Komponente</h2><p>1. AsmxProxy-Endpoint konfigurieren.</p><p>2. Route-Metadata und Spalten definieren.</p><p>3. <code>wuic-data-source</code> + <code>wuic-data-repeater</code> montieren.</p><p>Snippet 5:</p><h2>Die ersten Listen zeigen 20 Datensaetze: das ist der Trial-Modus</h2><p>Eine frische Installation laeuft <strong>ohne Lizenz</strong>, also im Trial-Modus, und in diesem Modus</p><p>ist <strong>jede Abfrage auf 20 Datensaetze begrenzt</strong>. Das ist weder ein Fehler noch eine Grenze</p><p>der Datenbank: Eine Liste, die bei einer Tabelle mit Tausenden von Zeilen &quot;20 von 20&quot;</p><p>anzeigt, laeuft schlicht ohne Lizenz.</p><p>So laesst es sich in einer Sekunde bestaetigen:</p><p>Snippet 6:</p><p><code>licenseValid: false</code> bestaetigt den Trial-Modus, und <code>licenseReason</code> nennt den Grund</p><p>(<code>invalid_signature</code>, <code>license_expired</code>, <code>machine_fingerprint_not_authorized</code>, ...).</p><p>So kommt man heraus: Die Lizenz unter <strong>Verwaltung &gt; AppSettings-Editor</strong>, Reiter Licensing,</p><p>einfuegen - sie gilt sofort, ein Neustart des Backends ist nicht noetig. Die Details,</p><p>einschliesslich der Grenzen, die der Trial ueber die Datensatzzahl hinaus setzt, stehen auf</p><p>der Seite <a href=\"licensing.md\">Licensing</a>.</p>",
                     "codeSamples": [
                         {
                             "id": "code_1",
@@ -27997,25 +28073,31 @@ const frameworkDocsContent = {
                             "id": "code_2",
                             "title": "Snippet 2",
                             "language": "text",
-                            "code": "Developer workspace ready: C:\\Users\\<user>\\AppData\\Local\\WUIC\\app\r\n\r\n  code \"C:\\Users\\<user>\\AppData\\Local\\WUIC\\app\\WuicTest.code-workspace\"\r\n  then F5 > 'Fullstack: WuicTest + Chrome' (backend http://localhost:5000, frontend http://localhost:4200)\r\n\r\nFirst start opens the first-run wizard: paste this connection string (Windows authentication)\r\n  Data Source=localhost\\SQLEXPRESS;Integrated Security=SSPI;Initial Catalog=WuicData;Encrypt=False;TrustServerCertificate=True\r\nRename the project: .\\rename-project.ps1 -Name MyApp"
+                            "code": "Developer workspace ready: C:\\Users\\<user>\\AppData\\Local\\WUIC\\app\n\n  code \"C:\\Users\\<user>\\AppData\\Local\\WUIC\\app\\WuicTest.code-workspace\"\n  then F5 > 'Fullstack: WuicTest + Chrome' (backend http://localhost:5000, frontend http://localhost:4200)\n\nFirst start opens the first-run wizard: paste this connection string (Windows authentication)\n  Data Source=localhost\\SQLEXPRESS;Integrated Security=SSPI;Initial Catalog=WuicData;Encrypt=False;TrustServerCertificate=True\nRename the project: .\\rename-project.ps1 -Name MyApp"
                         },
                         {
                             "id": "code_3",
                             "title": "Snippet 3",
                             "language": "powershell",
-                            "code": "# Erstes Mal: NuGet-Pakete wiederherstellen (holt WuicCore + deps von nuget.org, ~30 s)\r\ndotnet restore\r\n\r\n# Dev-Start mit Hot Reload\r\n$env:ASPNETCORE_ENVIRONMENT = 'Development'\r\ndotnet watch run\r\n\r\n# Oder One-Shot-Start (ohne Hot Reload)\r\ndotnet run"
+                            "code": "# Erstes Mal: NuGet-Pakete wiederherstellen (holt WuicCore + deps von nuget.org, ~30 s)\ndotnet restore\n\n# Dev-Start mit Hot Reload\n$env:ASPNETCORE_ENVIRONMENT = 'Development'\ndotnet watch run\n\n# Oder One-Shot-Start (ohne Hot Reload)\ndotnet run"
                         },
                         {
                             "id": "code_4",
                             "title": "Snippet 4",
                             "language": "powershell",
-                            "code": "cd wwwroot\r\n\r\n# Erstes Mal: npm-Abhaengigkeiten wiederherstellen (holt wuic-framework-lib aus npm-Registry, ~2 Min.)\r\nnpm install\r\n\r\n# Dev-Server starten\r\nnpm run serve:dev"
+                            "code": "cd wwwroot\n\n# Erstes Mal: npm-Abhaengigkeiten wiederherstellen (holt wuic-framework-lib aus npm-Registry, ~2 Min.)\nnpm install\n\n# Dev-Server starten\nnpm run serve:dev"
                         },
                         {
                             "id": "code_5",
                             "title": "Snippet 5",
                             "language": "html",
-                            "code": "<wuic-data-source [hardcodedRoute]=\"'cities'\"></wuic-data-source>\r\n<wuic-data-repeater [hardcodedAction]=\"'list'\"></wuic-data-repeater>"
+                            "code": "<wuic-data-source [hardcodedRoute]=\"'cities'\"></wuic-data-source>\n<wuic-data-repeater [hardcodedAction]=\"'list'\"></wuic-data-repeater>"
+                        },
+                        {
+                            "id": "code_6",
+                            "title": "Snippet 6",
+                            "language": "bash",
+                            "code": "curl -s http://localhost:5000/api/Meta/LicenseStatus"
                         }
                     ]
                 }
@@ -28050,18 +28132,22 @@ const frameworkDocsContent = {
             "toc": [
                 {
                     "id": "sec_1",
-                    "title": "Wann verwenden"
+                    "title": "Mit einem Tutorial-Paket gibt es nichts zu scaffolden"
                 },
                 {
                     "id": "sec_2",
-                    "title": "Verhalten bei firstRun=true"
+                    "title": "Wann verwenden"
                 },
                 {
                     "id": "sec_3",
-                    "title": "Typische Vorgaenge"
+                    "title": "Verhalten bei firstRun=true"
                 },
                 {
                     "id": "sec_4",
+                    "title": "Typische Vorgaenge"
+                },
+                {
+                    "id": "sec_5",
                     "title": "Nach dem Provisioning"
                 }
             ],
@@ -28069,7 +28155,7 @@ const frameworkDocsContent = {
                 {
                     "id": "overview",
                     "title": "Overview",
-                    "html": "<h1>Initiales Scaffolding</h1><p>Diese Seite beschreibt den initialen Bootstrap, wenn <code>AppSettings.firstRun = true</code>.</p><h2>Wann verwenden</h2><ul><li>Neuinstallation (Metadata-/Daten-DB noch nicht bereit).</li><li>Lokale Umgebung, die mit dem initialen Setup neu ausgerichtet werden soll.</li><li>Erster Start nach einem Deploy, bei dem die gefuehrte Provisioning-Prozedur erzwungen werden soll.</li></ul><h2>Verhalten bei firstRun=true</h2><ul><li>Der Endpoint <code>GET /api/Meta/FirstRunStatus</code> gibt <code>firstRun: true</code> zurueck.</li><li>Beim Login erscheint der Erststart-Flow (z.B. Aktion <code>Aktualisieren</code> im Screen).</li><li>Das Setup wendet die Basiskonfigurationen an (Verbindungen, Runtime-Einstellungen, Metadata-Bootstrap).</li></ul><h2>Typische Vorgaenge</h2><ul><li>Pruefen, dass <code>AppSettings.firstRun</code> auf <code>true</code> in <code>appsettings.{Environment}.json</code> des ausgefuehrten Hosts steht.</li><li>Anwendung starten und die initiale Scaffolding-Prozedur ueber die UI abschliessen.</li><li>Sicherstellen, dass Verbindungen und Hauptparameter konsistent sind (<code>dbms</code>, <code>DataDBName</code>, <code>ConnectionStrings</code>).</li></ul><h2>Nach dem Provisioning</h2><ul><li>Die Setup-Prozedur setzt <code>firstRun</code> auf <code>false</code>, um eine erneute Ausfuehrung bei jedem Start zu vermeiden.</li><li>Standard-Login durchfuehren und den Zugriff auf die Hauptrouten validieren.</li></ul>",
+                    "html": "<h1>Initiales Scaffolding</h1><p>Diese Seite beschreibt den initialen Bootstrap, wenn <code>AppSettings.firstRun = true</code>.</p><h2>Mit einem Tutorial-Paket gibt es nichts zu scaffolden</h2><p>Das Scaffolding, um das es auf dieser Seite geht — die Tabellen einer Datenbank lesen und in</p><p><code>_metadati__tabelle</code> / <code>_metadati__colonne</code> registrieren — betrifft <strong>nur</strong> den Modus</p><p>&quot;Bestehende Datenbank&quot; des First-Run-Wizards: dort steht die Checkbox *Tabellen der gewaehlten</p><p>Datenbank automatisch scaffolden*.</p><p>In <strong>Tutorial</strong>-Paketen gibt es diese Checkbox nicht. Die Metadaten-DB kommt bereits befuellt</p><p>(Routen, Spalten, Menue, Uebersetzungen, Beispiel-Dashboards), und der Wizard stellt sie nur</p><p>wieder her und legt den Admin-Benutzer an. Fertige Routen direkt nach dem ersten Start sind also</p><p>nicht das Ergebnis eines Scaffoldings, sondern der Inhalt des Tutorials.</p><table><thead><tr><th>Wizard-Modus</th><th>Was mit den Metadaten passiert</th></tr></thead><tbody><tr><td>Tutorial WideWorldImporters</td><td>Metadaten bereits fertig, aus dem Paket wiederhergestellt. Kein Scaffolding.</td></tr><tr><td>Bestehende Datenbank, Checkbox aus</td><td>Leere Metadaten-DB: die Routen werden selbst registriert, von Hand oder spaeter ueber die Seite Scaffolding.</td></tr><tr><td>Bestehende Datenbank, Checkbox an</td><td>Am Ende der Installation wird jede Tabelle der gewaehlten Datenbank als Route registriert.</td></tr></tbody></table><p>Der Rest dieser Seite gilt fuer die letzten beiden Zeilen dieser Tabelle.</p><h2>Wann verwenden</h2><ul><li>Neuinstallation (Metadata-/Daten-DB noch nicht bereit).</li><li>Lokale Umgebung, die mit dem initialen Setup neu ausgerichtet werden soll.</li><li>Erster Start nach einem Deploy, bei dem die gefuehrte Provisioning-Prozedur erzwungen werden soll.</li></ul><h2>Verhalten bei firstRun=true</h2><ul><li>Der Endpoint <code>GET /api/Meta/FirstRunStatus</code> gibt <code>firstRun: true</code> zurueck.</li><li>Beim Login erscheint der Erststart-Flow (z.B. Aktion <code>Aktualisieren</code> im Screen).</li><li>Das Setup wendet die Basiskonfigurationen an (Verbindungen, Runtime-Einstellungen, Metadata-Bootstrap).</li></ul><h2>Typische Vorgaenge</h2><ul><li>Pruefen, dass <code>AppSettings.firstRun</code> auf <code>true</code> in <code>appsettings.{Environment}.json</code> des ausgefuehrten Hosts steht.</li><li>Anwendung starten und die initiale Scaffolding-Prozedur ueber die UI abschliessen.</li><li>Sicherstellen, dass Verbindungen und Hauptparameter konsistent sind (<code>dbms</code>, <code>DataDBName</code>, <code>ConnectionStrings</code>).</li></ul><h2>Nach dem Provisioning</h2><ul><li>Die Setup-Prozedur setzt <code>firstRun</code> auf <code>false</code>, um eine erneute Ausfuehrung bei jedem Start zu vermeiden.</li><li>Standard-Login durchfuehren und den Zugriff auf die Hauptrouten validieren.</li></ul>",
                     "codeSamples": []
                 }
             ],
@@ -28128,7 +28214,7 @@ const frameworkDocsContent = {
                 {
                     "id": "overview",
                     "title": "Overview",
-                    "html": "<h1>Lizenzierung</h1><p>Diese Seite erklaert die Lizenzierung aus der Sicht des Endbenutzers: was benoetigt wird, wie man die Lizenz erhaelt und wie man sie anwendet.</p><h2>Wie erhalte ich eine Lizenz</h2><p>Schauen Sie sich die Plaene, die enthaltenen Funktionen pro Stufe (Developer / Professional / Software House) an und kaufen Sie auf der oeffentlichen Website:</p><ul><li><a href=\"https://wuic-framework.com/pricing\" target=\"_blank\" rel=\"noopener noreferrer\">WUIC Preise und Plaene — wuic-framework.com/pricing</a></li><li><a href=\"mailto:licensing@wuic-framework.com\">Vertriebskontakt</a> — zum Evaluieren ist keine Lizenz noetig: ohne Lizenz laeuft das Framework im Trial-Modus (20 Datensaetze pro Abfrage)</li><li><a href=\"https://wuic-framework.com\" target=\"_blank\" rel=\"noopener noreferrer\">WUIC Startseite</a></li></ul><p>Nach dem Kauf erhalten Sie eine E-Mail mit <code>license-payload</code> + <code>license-signature</code>, die Sie wie im Abschnitt &quot;Endbenutzer-Verfahren&quot; unten beschrieben installieren.</p><h2>Funktionsweise</h2><ul><li>Die Lizenz ist nur gueltig, wenn:</li><li>Korrekte Signatur.</li><li><code>machineFingerprint</code> des aktuellen Servers in der Liste <code>machineFingerprints</code> des signierten Payloads vorhanden ist.</li><li>Wenn die Lizenz nicht gueltig ist, wird das Lesen von Daten (<code>getFlatRecordData</code>) auf maximal 20 Datensaetze beschraenkt. Zusaetzlich wird der Host-Hook <code>customizeSelect</code> umgangen (nicht aufgerufen).</li></ul><h2>Wo finde ich den machineFingerprint</h2><p>Backend-Endpunkt:</p><ul><li><code>GET /api/Meta/LicenseStatus</code> → Feld <code>machineFingerprint</code> (immer verfuegbar, auch ohne Lizenz).</li><li>Waehrend des First-Run liefert es auch <code>GET /api/Meta/FirstRunStatus</code>.</li></ul><p>Hinweis: Die lokale Datei <code>installation.id</code> wird nicht mehr fuer die Lizenzierung verwendet.</p><h2>Vorgehensweise fuer den Endbenutzer</h2><p>1. Rufen Sie <code>machineFingerprint</code> von Ihrem Host ab.</p><p>2. Senden Sie den Wert an den Anbieter/Lizenzgeber.</p><p>3. Erhalten Sie die Lizenzwerte:</p><ul><li><code>license-payload</code></li><li><code>license-signature</code></li><li><code>license-public-key-pem</code> (falls fuer Ihre Installation vorgesehen)</li></ul><p>4. Tragen Sie die Werte in die Datei <code>appsettings.{Environment}.json</code> des laufenden Hosts ein, Abschnitt <code>AppSettings</code>.</p><p>5. Starten Sie das Backend neu.</p><p>6. Ueberpruefen Sie den Lizenzstatus ueber die API:</p><ul><li><code>GET /api/Meta/LicenseStatus</code></li><li>Erwartet: <code>licenseValid = true</code>.</li></ul><h2>Multi-Maschinen-Lizenz</h2><p>Eine einzelne Lizenz kann mehrere Maschinen autorisieren, indem mehrere Werte in <code>machineFingerprints</code> aufgenommen werden.</p><h2>Schnelle Fehlerbehebung</h2><ul><li><code>licenseReason = invalid_signature</code>:</li><li>Payload/Signatur stimmen nicht ueberein oder der oeffentliche Schluessel ist abweichend.</li><li><code>licenseReason = machine_fingerprint_not_authorized</code>:</li><li>Der Fingerprint der aktuellen Maschine ist nicht in der erhaltenen Lizenz enthalten.</li><li><code>licenseReason = machine_fingerprint_missing</code>:</li><li>Die Laufzeitumgebung kann den lokalen Fingerprint nicht berechnen.</li><li><code>licenseReason = license_expired</code>:</li><li>Die Lizenz ist abgelaufen, fordern Sie eine Erneuerung an.</li></ul>",
+                    "html": "<h1>Lizenzierung</h1><p>Diese Seite erklaert die Lizenzierung aus der Sicht des Endbenutzers: was benoetigt wird, wie man die Lizenz erhaelt und wie man sie anwendet.</p><h2>Wie erhalte ich eine Lizenz</h2><p>Schauen Sie sich die Plaene, die enthaltenen Funktionen pro Stufe (Developer / Professional / Software House) an und kaufen Sie auf der oeffentlichen Website:</p><ul><li><a href=\"https://wuic-framework.com/pricing\" target=\"_blank\" rel=\"noopener noreferrer\">WUIC Preise und Plaene — wuic-framework.com/pricing</a></li><li><a href=\"mailto:licensing@wuic-framework.com\">Vertriebskontakt</a> — zum Evaluieren ist keine Lizenz noetig: ohne Lizenz laeuft das Framework im Trial-Modus (20 Datensaetze pro Abfrage)</li><li><a href=\"https://wuic-framework.com\" target=\"_blank\" rel=\"noopener noreferrer\">WUIC Startseite</a></li></ul><p>Nach dem Kauf erhalten Sie eine E-Mail mit <code>license-payload</code> + <code>license-signature</code>, die Sie wie im Abschnitt &quot;Endbenutzer-Verfahren&quot; unten beschrieben installieren.</p><h2>Funktionsweise</h2><ul><li>Die Lizenz ist nur gueltig, wenn:</li><li>Korrekte Signatur.</li><li><code>machineFingerprint</code> des aktuellen Servers in der Liste <code>machineFingerprints</code> des signierten Payloads vorhanden ist.</li><li>Wenn die Lizenz nicht gueltig ist, wird das Lesen von Daten (<code>getFlatRecordData</code>) auf maximal 20 Datensaetze beschraenkt. Zusaetzlich wird der Host-Hook <code>customizeSelect</code> umgangen (nicht aufgerufen).</li></ul><h2>Wo finde ich den machineFingerprint</h2><p>Backend-Endpunkt:</p><ul><li><code>GET /api/Meta/LicenseStatus</code> → Feld <code>machineFingerprint</code> (immer verfuegbar, auch ohne Lizenz).</li><li>Waehrend des First-Run liefert es auch <code>GET /api/Meta/FirstRunStatus</code>.</li></ul><p>Hinweis: Die lokale Datei <code>installation.id</code> wird nicht mehr fuer die Lizenzierung verwendet.</p><h2>Vorgehensweise fuer den Endbenutzer</h2><p>1. Rufen Sie <code>machineFingerprint</code> von Ihrem Host ab.</p><p>2. Senden Sie den Wert an den Anbieter/Lizenzgeber.</p><p>3. Erhalten Sie die Lizenzwerte:</p><ul><li><code>license-payload</code></li><li><code>license-signature</code></li><li><code>license-public-key-pem</code> (falls fuer Ihre Installation vorgesehen)</li></ul><p>4. Fuegen Sie die Werte ueber die Oberflaeche ein: <strong>Verwaltung &gt; AppSettings-Editor</strong>,</p><p>   Abschnitt <strong>License</strong> (Felder <code>License email</code>, <code>License payload</code>, <code>License signature</code>,</p><p>   <code>Public key (PEM)</code>), dann speichern. Alternativ koennen sie von Hand im Abschnitt</p><p>   <code>AppSettings</code> der Datei <code>appsettings.{Environment}.json</code> des laufenden Hosts stehen.</p><p>5. Ueberpruefen Sie den Lizenzstatus:</p><ul><li>ueber die API: <code>GET /api/Meta/LicenseStatus</code>, erwartet <code>licenseValid = true</code>;</li><li>oder auf der Seite selbst, die die Lizenz direkt nach dem Speichern neu einliest.</li></ul><p><strong>Ein Neustart des Backends ist nicht noetig, wenn Sie den Editor benutzen.</strong> Beim Speichern von</p><p><code>license-payload</code> / <code>license-signature</code> im AppSettings-Editor laedt das Backend den</p><p>Validierungsdienst selbst neu, und die Lizenz gilt ab der naechsten Anfrage. Ein Neustart ist nur</p><p>im anderen Fall noetig, wenn die Werte von Hand in die Datei geschrieben werden: die wird beim</p><p>Start gelesen.</p><h2>Multi-Maschinen-Lizenz</h2><p>Eine einzelne Lizenz kann mehrere Maschinen autorisieren, indem mehrere Werte in <code>machineFingerprints</code> aufgenommen werden.</p><h2>Schnelle Fehlerbehebung</h2><ul><li><code>licenseReason = invalid_signature</code>:</li><li>Payload/Signatur stimmen nicht ueberein oder der oeffentliche Schluessel ist abweichend.</li><li><code>licenseReason = machine_fingerprint_not_authorized</code>:</li><li>Der Fingerprint der aktuellen Maschine ist nicht in der erhaltenen Lizenz enthalten.</li><li><code>licenseReason = machine_fingerprint_missing</code>:</li><li>Die Laufzeitumgebung kann den lokalen Fingerprint nicht berechnen.</li><li><code>licenseReason = license_expired</code>:</li><li>Die Lizenz ist abgelaufen, fordern Sie eine Erneuerung an.</li></ul>",
                     "codeSamples": []
                 }
             ],
@@ -28803,42 +28889,46 @@ const frameworkDocsContent = {
                 },
                 {
                     "id": "sec_2",
-                    "title": "Screenshot-Referenz (Benutzerhandbuch)"
+                    "title": "Was die Toolbar standardmaessig zeigt"
                 },
                 {
                     "id": "sec_3",
-                    "title": "Metadaten Inline-Editing"
+                    "title": "Screenshot-Referenz (Benutzerhandbuch)"
                 },
                 {
                     "id": "sec_4",
-                    "title": "Toolbar Export/Import"
+                    "title": "Metadaten Inline-Editing"
                 },
                 {
                     "id": "sec_5",
-                    "title": "Config Metadata"
+                    "title": "Toolbar Export/Import"
                 },
                 {
                     "id": "sec_6",
-                    "title": "md_props_bag: toolbar"
+                    "title": "Config Metadata"
                 },
                 {
                     "id": "sec_7",
-                    "title": "md_props_bag: archetypes.list"
+                    "title": "md_props_bag: toolbar"
                 },
                 {
                     "id": "sec_8",
-                    "title": "Paging: md_pagesize und md_page_size_choice"
+                    "title": "md_props_bag: archetypes.list"
                 },
                 {
                     "id": "sec_9",
-                    "title": "Erzwungene Virtualisierung bei hoher Seitengroesse"
+                    "title": "Paging: md_pagesize und md_page_size_choice"
                 },
                 {
                     "id": "sec_10",
-                    "title": "Events und Subscriptions (Host)"
+                    "title": "Erzwungene Virtualisierung bei hoher Seitengroesse"
                 },
                 {
                     "id": "sec_11",
+                    "title": "Events und Subscriptions (Host)"
+                },
+                {
+                    "id": "sec_12",
                     "title": "`rowCustomSelect` — tatsachliche Signatur (Falle)"
                 }
             ],
@@ -28846,7 +28936,7 @@ const frameworkDocsContent = {
                 {
                     "id": "overview",
                     "title": "Overview",
-                    "html": "<h1>List Grid</h1><p>Hauptkomponente fuer tabellarische Listen mit Filtern, Sortierung, serverseitigem Paging und Zeilenaktionen.</p><h2>Anwendungsfaelle</h2><ul><li>Enterprise-CRUD-Tabellen.</li><li>Operative Reports mit Multi-Spalten-Filtern.</li><li>Sehr grosse Datasets mit <code>cursorMode</code>.</li></ul><h2>Screenshot-Referenz (Benutzerhandbuch)</h2><ul><li><code>manual__grid__01.png</code>: Modus <code>inline cell edit</code> im List-Grid.</li><li><code>manual__grid__02.png</code>: Modus <code>inline edit</code> (Row-Level) im List-Grid.</li></ul><h2>Metadaten Inline-Editing</h2><p>Konfiguration im <code>md_props_bag</code> der Tabellen-Metadata:</p><ul><li><code>md_inline_edit</code></li></ul><p>  - aktiviert das Inline-Editing der Zeile im List-Grid (editierbare Zellen im Zeilenkontext, ohne Popup-Oeffnung).</p><p>  - nuetzlich wenn die Tabellen-UX mit schnellem Editing pro Datensatz beibehalten werden soll.</p><ul><li><code>md_inline_cell_edit</code></li></ul><p>  - aktiviert das Inline-Editing &quot;Zelle fuer Zelle&quot; (Fokus auf einzelne Zelle).</p><p>  - Hinweis: in Legacy-Konfigurationen kann dies als <code>md_inline_cell_editing</code> erscheinen; das Runtime-Verhalten ist identisch.</p><p>  - <strong>Runtime-Promotion</strong>: wenn <code>md_inline_cell_edit</code> <code>true</code> ist, erzwingt die Komponente</p><p>    zur Laufzeit auch <code>md_inline_edit = true</code>, unabhaengig vom DB-Wert.</p><p>    Beide UX benoetigen die sichtbare Action-Spalte, daher sind sie auf Rendering-Ebene</p><p>    nicht gegenseitig ausschliessend.</p><ul><li><code>md_batch_save</code></li></ul><p>  - aktiviert das Batch-Speichern der ausstehenden Aenderungen (<code>Save changes</code> / <code>Cancel changes</code>).</p><p>  - bei Verwendung zusammen mit Inline-Cell bleiben die Aenderungen ausstehend bis zum expliziten Speichern.</p><p>  - <strong>Voraussetzung</strong>: <code>md_batch_save</code> wirkt <strong>nur</strong> wenn <code>md_inline_cell_edit</code> <code>true</code> ist.</p><p>    Mit <code>md_inline_cell_edit:false</code> wird das Flag zur Laufzeit ignoriert und die Buttons</p><p>    &quot;Aenderungen speichern / Aenderungen verwerfen&quot; werden nicht gerendert.</p><h3>Gueltige Kombinationen</h3><table><thead><tr><th><code>md_inline_edit</code></th><th><code>md_inline_cell_edit</code></th><th><code>md_batch_save</code></th><th>Runtime-Ergebnis</th></tr></thead><tbody><tr><td><code>true</code></td><td><code>false</code></td><td>beliebig</td><td>Row-Level Inline-Edit mit Pencil. <code>md_batch_save</code> ignoriert.</td></tr><tr><td><code>false</code></td><td><code>true</code></td><td><code>false</code></td><td>Zelle-fuer-Zelle Autosave bei Blur. <code>md_inline_edit</code> wird zur Laufzeit auf <code>true</code> erzwungen.</td></tr><tr><td><code>false</code></td><td><code>true</code></td><td><code>true</code></td><td>Zelle-fuer-Zelle mit Pending-Buffer + Toolbar <code>Speichern / Aenderungen verwerfen</code>.</td></tr><tr><td><code>false</code></td><td><code>false</code></td><td>beliebig</td><td>Kein Inline-Editing. <code>md_batch_save</code> ignoriert.</td></tr></tbody></table><p>Beispiel Row-Level Inline-Edit:</p><p>Snippet 1:</p><p>Beispiel Zelle-fuer-Zelle mit Batch-Save:</p><p>Snippet 2:</p><h2>Toolbar Export/Import</h2><ul><li>Export XLS:</li></ul><p>  - zeigt Fortschrittsdialog mit Echtzeit-Prozentsatz;</p><p>  - Aktionen: <code>Im Hintergrund fortsetzen</code>, <code>Task abbrechen</code>, <code>Unterbrechen und teilweise herunterladen</code>;</p><p>  - im Hintergrund wird eine Benachrichtigung mit Fortschritt erstellt; Klick oeffnet den Dialog erneut.</p><ul><li>Import XLS/XLSX (wenn <code>md_importable = true</code>):</li></ul><p>  - Fortschrittsdialog nach Bestaetigung;</p><p>  - Aktionen: <code>Im Hintergrund fortsetzen</code>, <code>Import abbrechen (Rollback)</code>, <code>Stop und teilweise Commit</code>;</p><p>  - nach Import-Ende wird eine Zusammenfassungs-Benachrichtigung erstellt, die zur Route fuehrt.</p><h2>Config Metadata</h2><p>Schluessel-Einstellungen in <code>md_props_bag</code> und Spalten-Metadaten.</p><p>Snippet 3:</p><h2>md_props_bag: toolbar</h2><p>Opt-in-Flags, die Bloecke der list-grid Toolbar (<code>caption-bar</code>) ausblenden. Alle unter <code>md_props_bag.toolbar.*</code> (zur Laufzeit als <code>tableMetadata.extraProps.toolbar</code> geparst).</p><p>Snippet 4:</p><ul><li><code>hideManageState</code> (boolean, default <code>false</code>): blendet in der <strong>caption-right</strong> den Button &quot;Status verwalten&quot; (Bookmark-Icon) + das <code>&lt;select&gt;</code> der gespeicherten Zustaende aus. Nuetzlich fuer hardcoded / Demo-Routes, bei denen das Saved-State-Feature (Persistenz pro <code>user_id</code> + Route via <code>MetaService</code>) keinen Sinn ergibt — z.B. Pattern 3 reines OData ohne registrierte Route-Metadaten.</li><li><code>hideBatchActions</code> (boolean, default <code>false</code>): blendet in der <strong>caption-left</strong> die Buttons &quot;Aenderungen speichern&quot; (<code>pi-save</code>) + &quot;Aenderungen verwerfen&quot; (<code>pi-times</code>) + den Aenderungs-Zaehler-Indikator (<code>grid-changes-indicator</code>, Pencil-Badge + Count) aus. Vom Framework generiert, wenn <code>md_inline_cell_editing</code> + <code>md_batch_save</code> aktiv sind. Konzipiert fuer <strong>verschachtelte Grids in einem parametric-dialog</strong>: Save/Cancel des Parents persistiert Master + Zeilen in einem Schritt via Framework Batch Save, und die Duplikat-Buttons auf der nested Grid verwirren die UX.</li></ul><p>Beispiel nested rows in custom edit-form (Runtime-Patch):</p><p>Snippet 5:</p><p>TS-Typ in <a href=\"../api/wuic-framework-lib.metadatitabella.html\">`metadati_tabella.ts`</a> (<code>extraProps.toolbar</code> Property). Die Flags deaktivieren NICHT die zugrundeliegende <code>md_batch_save</code>-Logik (Aenderungen werden weiterhin getrackt); sie entfernen nur die Toolbar-UI — der eigentliche Save laeuft ueber den Parent-Flow.</p><h2>md_props_bag: archetypes.list</h2><p>Die Komponente liest <code>md_props_bag.archetypes.list</code>.</p><p>Snippet 6:</p><ul><li><code>proportionalColwidth</code>:</li><li>Typ: boolean (mit tolerantem Parser)</li><li>akzeptierte Werte: <code>true</code>, <code>false</code>, <code>1</code>, <code>0</code>, <code>&quot;true&quot;</code>, <code>&quot;false&quot;</code>, <code>&quot;1&quot;</code>, <code>&quot;0&quot;</code></li><li>Runtime-Default: <code>true</code> wenn absent oder leer</li><li>Effekt: verteilt die Spaltenbreiten prozentual (anstelle von px), wenn keine vom Benutzer persistierten Breiten vorhanden sind.</li></ul><ul><li><code>virtualize</code>:</li><li>Typ: <code>boolean</code> oder <code>object</code></li><li>akzeptierte Werte:</li><li><code>true</code>/<code>false</code>, <code>1</code>/<code>0</code>, <code>&quot;true&quot;</code>/<code>&quot;false&quot;</code>, <code>&quot;1&quot;</code>/<code>&quot;0&quot;</code></li><li>Object mit <code>enabled</code> (optional) und <code>itemSize</code> (optional)</li><li>Runtime-Default: deaktiviert (<code>false</code>) wenn absent</li><li><code>enabled</code>:</li><li>Default: <code>true</code> wenn der <code>virtualize</code>-Knoten ein Object ohne <code>enabled</code> ist, sonst toleranter Parser</li><li>Effekt: aktiviert <code>virtualScroll</code> auf <code>p-table</code></li><li><code>itemSize</code>:</li><li>Default: <code>44</code></li><li>Effekt: setzt <code>virtualScrollItemSize</code> (virtuelle Zeilenhoehe in px)</li></ul><ul><li><code>advancedFilter</code>:</li><li>Typ: boolean (mit tolerantem Parser)</li><li>Runtime-Default: <code>false</code></li><li>Effekt:</li><li>wenn <code>true</code>, blendet das Grid die Spalten-Filter-Icons (<code>p-columnFilter</code>) aus und verwendet die <code>wuic-filter-bar</code> ueber der Tabelle (auf <code>data-repeater</code>/<code>bounded-repeater</code>-Ebene), um die Filter anzuwenden.</li></ul><p>Betriebshinweis:</p><ul><li>der <code>md_props_bag</code>-Suggest im Metadata-Editor stellt auch den checkbaren Knoten <code>archetypes.list.advancedFilter</code> bereit.</li></ul><h2>Paging: md_pagesize und md_page_size_choice</h2><p>Das Grid verwendet <code>md_pagesize</code> als Standard-Seitengroesse und <code>md_page_size_choice</code> als Liste der im Paginator auswaehlbaren Werte.</p><p>Runtime-Regeln:</p><ul><li>wenn <code>md_pagesize</code> groesser als der maximale Wert in <code>md_page_size_choice</code> ist, fuegt das Framework <code>md_pagesize</code> automatisch zur Optionsliste hinzu;</li><li>die Liste wird normalisiert (gueltige Zahlen, Deduplizierung, aufsteigende Sortierung).</li></ul><p>Beispiel:</p><ul><li><code>md_pagesize = 200</code></li><li><code>md_page_size_choice = &quot;10,25,50,100&quot;</code></li><li>Runtime-Ergebnis: <code>10,25,50,100,200</code></li></ul><h2>Erzwungene Virtualisierung bei hoher Seitengroesse</h2><p>Wenn der Benutzer im Paginator einen Wert <code>pageSize &gt;= 1000</code> auswaehlt:</p><ul><li>wird die Virtualisierung automatisch erzwungen, auch wenn <code>md_props_bag.archetypes.list.virtualize</code> absent oder deaktiviert ist;</li><li><code>virtualScrollItemSize</code> wird auf den Standardwert <code>44</code> gesetzt.</li></ul><p>Dieses Verhalten schuetzt das Rendering der Tabelle bei sehr grossen Seiten.</p><h2>Events und Subscriptions (Host)</h2><p><code>wuic-list-grid</code> stellt Runtime-Events bereit, die nuetzlich sind, um den Render-Zyklus und die p-table-Callbacks auf der Host-Projektseite zu intercepten.</p><p>Verfuegbare Events:</p><ul><li><code>onAfterRender</code>: wird am Ende des Datenbindings des Grids emittiert (<code>rows</code>, <code>totalRecords</code>, <code>metaInfo</code>, <code>datasource</code>).</li><li><code>onBeforeRowRender</code>: wird vor dem logischen Rendering der einzelnen Zeile emittiert; unterstuetzt Cancel via <code>event.cancelRender()</code>.</li><li><code>onAfterRowRender</code>: wird nach dem logischen Rendering der einzelnen Zeile emittiert.</li><li><code>onPaging</code>: wird bei Paging-Events emittiert (<code>p-table onPage</code>).</li><li><code>onSorting</code>: wird bei Sorting-Events emittiert (<code>p-table onSort</code>).</li><li><code>onFiltering</code>: wird bei Filtering-Events emittiert (<code>p-table onFilter</code>).</li><li><code>onPTableSelectionChange</code>: wird bei Aenderung der Zeilenauswahl emittiert.</li><li><code>onPTableRowExpand</code>: wird beim Expandieren einer Zeile emittiert.</li><li><code>onPTableRowCollapse</code>: wird beim Collapsen einer Zeile emittiert.</li><li><code>onPTableColumnResize</code>: wird beim Spalten-Resize emittiert.</li><li><code>onPTableColumnReorder</code>: wird beim Spalten-Reorder emittiert.</li></ul><h3>Beispiel 1: direktes Binding im Template</h3><p>Snippet 7:</p><h3>Beispiel 2: Subscribe via ViewChild</h3><p>Snippet 8:</p><h2><code>rowCustomSelect</code> — tatsachliche Signatur (Falle)</h2><p><code>&lt;wuic-list-grid&gt;</code> akzeptiert ein <code>[rowCustomSelect]</code>-Input zum Abfangen der Zeilenauswahl (Offnen eines &quot;Dokument auswahlen&quot;-Dialogs, Master-Detail-Flow, etc.). Die TypeScript-Signatur in <a href=\"../../src/lib/component/list-grid/list-grid.component.ts#L140\">list-grid.component.ts:140</a> lautet:</p><p>Snippet 9:</p><p><strong>Zur Laufzeit wird der Callback jedoch mit umgekehrten Argumenten aufgerufen</strong> — das Framework ruft <code>rowCustomSelect($event, rowData, dt)</code> auf (siehe <a href=\"../../src/lib/component/dynamic-template/dynamic-template.component.ts#L447\">dynamic-template.component.ts:447</a> und <a href=\"../../src/lib/component/dynamic-template/dynamic-card-template.component.ts#L205\">dynamic-card-template.component.ts:205</a>).</p><p>Symptom bei falscher Reihenfolge: <code>rowData?.id</code> ist undefined → fruhzeitiger Guard im Handler → der Callback kehrt stillschweigend zuruck und der Dialog/die Aktion startet nicht. Kein Konsolenfehler.</p><p>Korrekte Form (auf Laufzeit-Invocation abgestimmt):</p><p>Snippet 10:</p><p>Verwendung im Template:</p><p>Snippet 11:</p><p>&gt; Hinweis: Die Tests in <code>designer.component.spec.ts</code> (z.B. Zeile 512) rufen den Callback mit <code>({currentTarget: rowCell}, {id: 42}, null)</code> auf und bestatigen die Reihenfolge <code>($event, rowData, dt)</code>. Sollte das Framework die deklarierte Signatur kunftig angleichen, wird auch diese Seite aktualisiert.</p>",
+                    "html": "<h1>List Grid</h1><p>Hauptkomponente fuer tabellarische Listen mit Filtern, Sortierung, serverseitigem Paging und Zeilenaktionen.</p><h2>Anwendungsfaelle</h2><ul><li>Enterprise-CRUD-Tabellen.</li><li>Operative Reports mit Multi-Spalten-Filtern.</li><li>Sehr grosse Datasets mit <code>cursorMode</code>.</li></ul><h2>Was die Toolbar standardmaessig zeigt</h2><p>Beim Oeffnen einer frisch gescaffoldeten Route sitzt die Caption-Bar ueber dem Grid. Links:</p><table><thead><tr><th>Schaltflaeche</th><th>Wann sie erscheint</th></tr></thead><tbody><tr><td><strong>Aktualisieren</strong></td><td>immer, ausser bei <code>md_hide_refresh</code></td></tr><tr><td><strong>Hinzufuegen</strong></td><td>mit <code>md_insertable</code></td></tr><tr><td><strong>Aktionen</strong></td><td>wenn die Tabelle Custom Actions hat</td></tr><tr><td>Import / Export</td><td>immer; der Import-Zweig nur mit <code>md_importable</code></td></tr><tr><td><strong>Berichte</strong></td><td>wenn der Route mindestens ein Report zugeordnet ist</td></tr><tr><td><strong>Aenderungen speichern</strong> / <strong>Aenderungen verwerfen</strong></td><td>nur mit <code>md_inline_cell_edit</code> <strong>und</strong> <code>md_batch_save</code></td></tr></tbody></table><p>Rechts: <strong>Status verwalten</strong> (davor die Auswahl der gespeicherten Zustaende, falls vorhanden),</p><p><strong>Filter loeschen</strong>, wenn die Filter auf den Spalten sitzen, und <strong>Performance</strong>, wenn der</p><p>Inspector fuer die Route aktiviert ist.</p><p>&gt; Die weiter unten auf dieser Seite zitierten Beschriftungen **stehen nicht auf diesem</p><p>&gt; Bildschirm*<em>, und das ist kein Fehler: die von Export/Import (</em>Im Hintergrund fortfahren*,</p><p>&gt; <em>Task abbrechen</em>, <em>Stoppen und teilweise herunterladen</em>, <em>Import abbrechen (Rollback)</em>,</p><p>&gt; <em>Stoppen und teilweise committen</em>) leben im Fortschrittsdialog, den es nur waehrend eines</p><p>&gt; laufenden Exports oder Imports gibt; <em>Aenderungen speichern</em> und <em>Aenderungen verwerfen</em></p><p>&gt; erscheinen nur mit den beiden Flags oben. Sie gehoeren zu anderen Momenten als dem ersten</p><p>&gt; Oeffnen der Liste.</p><h2>Screenshot-Referenz (Benutzerhandbuch)</h2><ul><li><code>manual__grid__01.png</code>: Modus <code>inline cell edit</code> im List-Grid.</li><li><code>manual__grid__02.png</code>: Modus <code>inline edit</code> (Row-Level) im List-Grid.</li></ul><h2>Metadaten Inline-Editing</h2><p>Konfiguration im <code>md_props_bag</code> der Tabellen-Metadata:</p><ul><li><code>md_inline_edit</code></li></ul><p>  - aktiviert das Inline-Editing der Zeile im List-Grid (editierbare Zellen im Zeilenkontext, ohne Popup-Oeffnung).</p><p>  - nuetzlich wenn die Tabellen-UX mit schnellem Editing pro Datensatz beibehalten werden soll.</p><ul><li><code>md_inline_cell_edit</code></li></ul><p>  - aktiviert das Inline-Editing &quot;Zelle fuer Zelle&quot; (Fokus auf einzelne Zelle).</p><p>  - Hinweis: in Legacy-Konfigurationen kann dies als <code>md_inline_cell_editing</code> erscheinen; das Runtime-Verhalten ist identisch.</p><p>  - <strong>Runtime-Promotion</strong>: wenn <code>md_inline_cell_edit</code> <code>true</code> ist, erzwingt die Komponente</p><p>    zur Laufzeit auch <code>md_inline_edit = true</code>, unabhaengig vom DB-Wert.</p><p>    Beide UX benoetigen die sichtbare Action-Spalte, daher sind sie auf Rendering-Ebene</p><p>    nicht gegenseitig ausschliessend.</p><ul><li><code>md_batch_save</code></li></ul><p>  - aktiviert das Batch-Speichern der ausstehenden Aenderungen (<code>Save changes</code> / <code>Cancel changes</code>).</p><p>  - bei Verwendung zusammen mit Inline-Cell bleiben die Aenderungen ausstehend bis zum expliziten Speichern.</p><p>  - <strong>Voraussetzung</strong>: <code>md_batch_save</code> wirkt <strong>nur</strong> wenn <code>md_inline_cell_edit</code> <code>true</code> ist.</p><p>    Mit <code>md_inline_cell_edit:false</code> wird das Flag zur Laufzeit ignoriert und die Buttons</p><p>    &quot;Aenderungen speichern / Aenderungen verwerfen&quot; werden nicht gerendert.</p><h3>Gueltige Kombinationen</h3><table><thead><tr><th><code>md_inline_edit</code></th><th><code>md_inline_cell_edit</code></th><th><code>md_batch_save</code></th><th>Runtime-Ergebnis</th></tr></thead><tbody><tr><td><code>true</code></td><td><code>false</code></td><td>beliebig</td><td>Row-Level Inline-Edit mit Pencil. <code>md_batch_save</code> ignoriert.</td></tr><tr><td><code>false</code></td><td><code>true</code></td><td><code>false</code></td><td>Zelle-fuer-Zelle Autosave bei Blur. <code>md_inline_edit</code> wird zur Laufzeit auf <code>true</code> erzwungen.</td></tr><tr><td><code>false</code></td><td><code>true</code></td><td><code>true</code></td><td>Zelle-fuer-Zelle mit Pending-Buffer + Toolbar <code>Speichern / Aenderungen verwerfen</code>.</td></tr><tr><td><code>false</code></td><td><code>false</code></td><td>beliebig</td><td>Kein Inline-Editing. <code>md_batch_save</code> ignoriert.</td></tr></tbody></table><p>Beispiel Row-Level Inline-Edit:</p><p>Snippet 1:</p><p>Beispiel Zelle-fuer-Zelle mit Batch-Save:</p><p>Snippet 2:</p><h2>Toolbar Export/Import</h2><ul><li>Export XLS:</li></ul><p>  - zeigt Fortschrittsdialog mit Echtzeit-Prozentsatz;</p><p>  - Aktionen: <code>Im Hintergrund fortsetzen</code>, <code>Task abbrechen</code>, <code>Unterbrechen und teilweise herunterladen</code>;</p><p>  - im Hintergrund wird eine Benachrichtigung mit Fortschritt erstellt; Klick oeffnet den Dialog erneut.</p><ul><li>Import XLS/XLSX (wenn <code>md_importable = true</code>):</li></ul><p>  - Fortschrittsdialog nach Bestaetigung;</p><p>  - Aktionen: <code>Im Hintergrund fortsetzen</code>, <code>Import abbrechen (Rollback)</code>, <code>Stop und teilweise Commit</code>;</p><p>  - nach Import-Ende wird eine Zusammenfassungs-Benachrichtigung erstellt, die zur Route fuehrt.</p><h2>Config Metadata</h2><p>Schluessel-Einstellungen in <code>md_props_bag</code> und Spalten-Metadaten.</p><p>Snippet 3:</p><h2>md_props_bag: toolbar</h2><p>Opt-in-Flags, die Bloecke der list-grid Toolbar (<code>caption-bar</code>) ausblenden. Alle unter <code>md_props_bag.toolbar.*</code> (zur Laufzeit als <code>tableMetadata.extraProps.toolbar</code> geparst).</p><p>Snippet 4:</p><ul><li><code>hideManageState</code> (boolean, default <code>false</code>): blendet in der <strong>caption-right</strong> den Button &quot;Status verwalten&quot; (Bookmark-Icon) + das <code>&lt;select&gt;</code> der gespeicherten Zustaende aus. Nuetzlich fuer hardcoded / Demo-Routes, bei denen das Saved-State-Feature (Persistenz pro <code>user_id</code> + Route via <code>MetaService</code>) keinen Sinn ergibt — z.B. Pattern 3 reines OData ohne registrierte Route-Metadaten.</li><li><code>hideBatchActions</code> (boolean, default <code>false</code>): blendet in der <strong>caption-left</strong> die Buttons &quot;Aenderungen speichern&quot; (<code>pi-save</code>) + &quot;Aenderungen verwerfen&quot; (<code>pi-times</code>) + den Aenderungs-Zaehler-Indikator (<code>grid-changes-indicator</code>, Pencil-Badge + Count) aus. Vom Framework generiert, wenn <code>md_inline_cell_editing</code> + <code>md_batch_save</code> aktiv sind. Konzipiert fuer <strong>verschachtelte Grids in einem parametric-dialog</strong>: Save/Cancel des Parents persistiert Master + Zeilen in einem Schritt via Framework Batch Save, und die Duplikat-Buttons auf der nested Grid verwirren die UX.</li></ul><p>Beispiel nested rows in custom edit-form (Runtime-Patch):</p><p>Snippet 5:</p><p>TS-Typ in <a href=\"../api/wuic-framework-lib.metadatitabella.html\">`metadati_tabella.ts`</a> (<code>extraProps.toolbar</code> Property). Die Flags deaktivieren NICHT die zugrundeliegende <code>md_batch_save</code>-Logik (Aenderungen werden weiterhin getrackt); sie entfernen nur die Toolbar-UI — der eigentliche Save laeuft ueber den Parent-Flow.</p><h2>md_props_bag: archetypes.list</h2><p>Die Komponente liest <code>md_props_bag.archetypes.list</code>.</p><p>Snippet 6:</p><ul><li><code>proportionalColwidth</code>:</li><li>Typ: boolean (mit tolerantem Parser)</li><li>akzeptierte Werte: <code>true</code>, <code>false</code>, <code>1</code>, <code>0</code>, <code>&quot;true&quot;</code>, <code>&quot;false&quot;</code>, <code>&quot;1&quot;</code>, <code>&quot;0&quot;</code></li><li>Runtime-Default: <code>true</code> wenn absent oder leer</li><li>Effekt: verteilt die Spaltenbreiten prozentual (anstelle von px), wenn keine vom Benutzer persistierten Breiten vorhanden sind.</li></ul><ul><li><code>virtualize</code>:</li><li>Typ: <code>boolean</code> oder <code>object</code></li><li>akzeptierte Werte:</li><li><code>true</code>/<code>false</code>, <code>1</code>/<code>0</code>, <code>&quot;true&quot;</code>/<code>&quot;false&quot;</code>, <code>&quot;1&quot;</code>/<code>&quot;0&quot;</code></li><li>Object mit <code>enabled</code> (optional) und <code>itemSize</code> (optional)</li><li>Runtime-Default: deaktiviert (<code>false</code>) wenn absent</li><li><code>enabled</code>:</li><li>Default: <code>true</code> wenn der <code>virtualize</code>-Knoten ein Object ohne <code>enabled</code> ist, sonst toleranter Parser</li><li>Effekt: aktiviert <code>virtualScroll</code> auf <code>p-table</code></li><li><code>itemSize</code>:</li><li>Default: <code>44</code></li><li>Effekt: setzt <code>virtualScrollItemSize</code> (virtuelle Zeilenhoehe in px)</li></ul><ul><li><code>advancedFilter</code>:</li><li>Typ: boolean (mit tolerantem Parser)</li><li>Runtime-Default: <code>false</code></li><li>Effekt:</li><li>wenn <code>true</code>, blendet das Grid die Spalten-Filter-Icons (<code>p-columnFilter</code>) aus und verwendet die <code>wuic-filter-bar</code> ueber der Tabelle (auf <code>data-repeater</code>/<code>bounded-repeater</code>-Ebene), um die Filter anzuwenden.</li></ul><p>Betriebshinweis:</p><ul><li>der <code>md_props_bag</code>-Suggest im Metadata-Editor stellt auch den checkbaren Knoten <code>archetypes.list.advancedFilter</code> bereit.</li></ul><h2>Paging: md_pagesize und md_page_size_choice</h2><p>Das Grid verwendet <code>md_pagesize</code> als Standard-Seitengroesse und <code>md_page_size_choice</code> als Liste der im Paginator auswaehlbaren Werte.</p><p>Runtime-Regeln:</p><ul><li>wenn <code>md_pagesize</code> groesser als der maximale Wert in <code>md_page_size_choice</code> ist, fuegt das Framework <code>md_pagesize</code> automatisch zur Optionsliste hinzu;</li><li>die Liste wird normalisiert (gueltige Zahlen, Deduplizierung, aufsteigende Sortierung).</li></ul><p>Beispiel:</p><ul><li><code>md_pagesize = 200</code></li><li><code>md_page_size_choice = &quot;10,25,50,100&quot;</code></li><li>Runtime-Ergebnis: <code>10,25,50,100,200</code></li></ul><h2>Erzwungene Virtualisierung bei hoher Seitengroesse</h2><p>Wenn der Benutzer im Paginator einen Wert <code>pageSize &gt;= 1000</code> auswaehlt:</p><ul><li>wird die Virtualisierung automatisch erzwungen, auch wenn <code>md_props_bag.archetypes.list.virtualize</code> absent oder deaktiviert ist;</li><li><code>virtualScrollItemSize</code> wird auf den Standardwert <code>44</code> gesetzt.</li></ul><p>Dieses Verhalten schuetzt das Rendering der Tabelle bei sehr grossen Seiten.</p><h2>Events und Subscriptions (Host)</h2><p><code>wuic-list-grid</code> stellt Runtime-Events bereit, die nuetzlich sind, um den Render-Zyklus und die p-table-Callbacks auf der Host-Projektseite zu intercepten.</p><p>Verfuegbare Events:</p><ul><li><code>onAfterRender</code>: wird am Ende des Datenbindings des Grids emittiert (<code>rows</code>, <code>totalRecords</code>, <code>metaInfo</code>, <code>datasource</code>).</li><li><code>onBeforeRowRender</code>: wird vor dem logischen Rendering der einzelnen Zeile emittiert; unterstuetzt Cancel via <code>event.cancelRender()</code>.</li><li><code>onAfterRowRender</code>: wird nach dem logischen Rendering der einzelnen Zeile emittiert.</li><li><code>onPaging</code>: wird bei Paging-Events emittiert (<code>p-table onPage</code>).</li><li><code>onSorting</code>: wird bei Sorting-Events emittiert (<code>p-table onSort</code>).</li><li><code>onFiltering</code>: wird bei Filtering-Events emittiert (<code>p-table onFilter</code>).</li><li><code>onPTableSelectionChange</code>: wird bei Aenderung der Zeilenauswahl emittiert.</li><li><code>onPTableRowExpand</code>: wird beim Expandieren einer Zeile emittiert.</li><li><code>onPTableRowCollapse</code>: wird beim Collapsen einer Zeile emittiert.</li><li><code>onPTableColumnResize</code>: wird beim Spalten-Resize emittiert.</li><li><code>onPTableColumnReorder</code>: wird beim Spalten-Reorder emittiert.</li></ul><h3>Beispiel 1: direktes Binding im Template</h3><p>Snippet 7:</p><h3>Beispiel 2: Subscribe via ViewChild</h3><p>Snippet 8:</p><h2><code>rowCustomSelect</code> — tatsachliche Signatur (Falle)</h2><p><code>&lt;wuic-list-grid&gt;</code> akzeptiert ein <code>[rowCustomSelect]</code>-Input zum Abfangen der Zeilenauswahl (Offnen eines &quot;Dokument auswahlen&quot;-Dialogs, Master-Detail-Flow, etc.). Die TypeScript-Signatur in <a href=\"../../src/lib/component/list-grid/list-grid.component.ts#L140\">list-grid.component.ts:140</a> lautet:</p><p>Snippet 9:</p><p><strong>Zur Laufzeit wird der Callback jedoch mit umgekehrten Argumenten aufgerufen</strong> — das Framework ruft <code>rowCustomSelect($event, rowData, dt)</code> auf (siehe <a href=\"../../src/lib/component/dynamic-template/dynamic-template.component.ts#L447\">dynamic-template.component.ts:447</a> und <a href=\"../../src/lib/component/dynamic-template/dynamic-card-template.component.ts#L205\">dynamic-card-template.component.ts:205</a>).</p><p>Symptom bei falscher Reihenfolge: <code>rowData?.id</code> ist undefined → fruhzeitiger Guard im Handler → der Callback kehrt stillschweigend zuruck und der Dialog/die Aktion startet nicht. Kein Konsolenfehler.</p><p>Korrekte Form (auf Laufzeit-Invocation abgestimmt):</p><p>Snippet 10:</p><p>Verwendung im Template:</p><p>Snippet 11:</p><p>&gt; Hinweis: Die Tests in <code>designer.component.spec.ts</code> (z.B. Zeile 512) rufen den Callback mit <code>({currentTarget: rowCell}, {id: 42}, null)</code> auf und bestatigen die Reihenfolge <code>($event, rowData, dt)</code>. Sollte das Framework die deklarierte Signatur kunftig angleichen, wird auch diese Seite aktualisiert.</p>",
                     "codeSamples": [
                         {
                             "id": "code_1",
@@ -30572,7 +30662,7 @@ const frameworkDocsContent = {
                 {
                     "id": "overview",
                     "title": "Overview",
-                    "html": "<h1>Designer</h1><p>Visueller Editor fuer metadata-gesteuerte Dashboards auf Route <code>#/cities/dashboard</code>.</p><h2>Geltungsbereich</h2><ul><li>Board-Komposition via Drag-and-Drop von Knoten und UI-Bloecken.</li><li>Layout und Styling gesteuert durch <code>boardcontent</code> und Tabellen-/Spalten-Metadata.</li><li>Property-Panel-Editing ohne Hardcoding in den Runtime-Komponenten.</li></ul><h2>Designer-Palette</h2><ul><li><code>Datasource</code>: Metadata-Datenquelle (<code>route</code>, Filter, Sortierung, Paging).</li><li><code>DataRepeater</code>: Listen-/Karten-Visualisierung verbunden mit Datasource.</li><li><code>Dynamic Template</code>: dynamisches Template-Rendering mit metadata-gesteuerten Inputs.</li><li><code>Action/Button</code>: Benutzeraktionen verknuepft mit Datensaetzen und Callbacks.</li><li><code>Container/Layout</code>: strukturelle Bloecke fuer Spalten, Zeilen und Wrapper.</li></ul><h2>Hauptfunktionen</h2><ul><li>Drag-and-Drop von Knoten auf die Canvas mit Persistierung im <code>boardcontent</code>.</li><li>Kontextbezogenes Property-Panel mit zu den ausgewaehlten Komponenten konsistenten Inputs.</li><li>Binding zwischen Knoten (<code>datasource -&gt; repeater/template</code>) mit Minimalvalidierung.</li><li>Integrierte Runtime-Vorschau und Layout-Neuausrichtung.</li><li>Verwaltung ausstehender Aenderungen mit Guard vor dem Verlassen.</li></ul><h2>Kontextmenue der Elemente</h2><p>Rechtsklick auf ein Element der Canvas, auf einen Eintrag der unteren Breadcrumb oder auf einen Knoten im Hierarchiebaum zeigt ein Kontextmenue mit drei Eintraegen:</p><ul><li><strong>Eigenschaften bearbeiten</strong> (pi-cog) - waehlt das Element als &quot;current tool&quot; aus und zeigt sein Property-Panel rechts; entspricht dem Klick im Baum. Nuetzlich, um Eigenschaften verschachtelter Elemente zu bearbeiten, ohne sie in der Hierarchie suchen zu muessen.</li><li><strong>Umbenennen</strong> (nur Breadcrumb) - oeffnet einen Dialog zum Umbenennen des <code>displayName</code>.</li><li><strong>Entfernen</strong> - loescht das Element vom Board.</li></ul><h2>Empfohlener operativer Ablauf</h2><ul><li>Ziel-Dashboard-Route oeffnen.</li><li>Knoten aus der Palette einfuegen/verbinden.</li><li>Wesentliche <code>inputs</code> konfigurieren (z.B. <code>route</code>, <code>action</code>, <code>datasource</code>).</li><li>Speichern und Ergebnis in der Runtime validieren.</li></ul><h2>Betriebshinweise</h2><ul><li>Fuer dashboard-spezifische Fixes <code>boardcontent</code>-Patches gegenueber globalen Aenderungen bevorzugen.</li><li>Doppelte Eigenschaften zwischen <code>inputs</code> und inkonsistentem Inline-Stil vermeiden.</li><li>Immer ueberpruefen, dass Datasources eine gesetzte <code>inputs.route</code> haben.</li></ul>",
+                    "html": "<h1>Designer</h1><p>Visueller Editor fuer metadata-gesteuerte Dashboards auf Route <code>#/cities/dashboard</code>.</p><h2>Geltungsbereich</h2><ul><li>Board-Komposition via Drag-and-Drop von Knoten und UI-Bloecken.</li><li>Layout und Styling gesteuert durch <code>boardcontent</code> und Tabellen-/Spalten-Metadata.</li><li>Property-Panel-Editing ohne Hardcoding in den Runtime-Komponenten.</li></ul><h2>Designer-Palette</h2><p>Die Palette ist in drei Gruppen geteilt. Die Namen unten sind die, die in der Palette stehen —</p><p>in Grossbuchstaben, genau wie der Designer sie schreibt.</p><p><strong>HTML</strong> — die Markup-Bausteine:</p><table><thead><tr><th>Tool</th><th>Wofuer</th></tr></thead><tbody><tr><td><code>TABLE</code></td><td>Zellenraster. <code>TR</code> und <code>TD</code> gibt es als Tools, sie lassen sich aber nicht ziehen: die Tabelle erzeugt sie</td></tr><tr><td><code>DIV</code></td><td>freier Container, der meistgenutzte Strukturblock</td></tr><tr><td><code>SPAN</code>, <code>LABEL</code>, <code>Hx</code></td><td>databound Text; <code>Hx</code> waehlt die Ebene von h1 bis h6</td></tr><tr><td><code>ANCHOR</code>, <code>IMG</code>, <code>IMAGE</code>, <code>IFRAME</code></td><td>Links, Bilder, externe Inhalte</td></tr><tr><td><code>UL</code></td><td>Liste</td></tr><tr><td><code>BUTTON</code></td><td>Schaltflaeche mit Callback</td></tr><tr><td><code>INPUT</code>, <code>TEXTAREA</code>, <code>CHECKBOX</code>, <code>SELECT</code>, <code>MULTISELECT</code>, <code>DATE</code></td><td>Eingabefelder</td></tr><tr><td><code>KPI</code></td><td>einzelner hervorgehobener Wert</td></tr><tr><td><code>SEPARATOR</code>, <code>HR</code></td><td>Trenner</td></tr></tbody></table><p><strong>DATA</strong> — die mit dem Backend verbundenen Knoten:</p><table><thead><tr><th>Tool</th><th>Wofuer</th></tr></thead><tbody><tr><td><code>DATASOURCE</code></td><td>Metadata-Datenquelle (<code>route</code>, Filter, Sortierung, Paging)</td></tr><tr><td><code>DATAREPEATER</code></td><td>Listen-/Karten-Visualisierung verbunden mit einer Datasource</td></tr><tr><td><code>FILTERBAR</code></td><td>Filterleiste ueber dem Repeater</td></tr><tr><td><code>PAGER</code></td><td>Paginator</td></tr></tbody></table><p><strong>CONTAINER</strong> — die Layouts:</p><table><thead><tr><th>Tool</th><th>Wofuer</th></tr></thead><tbody><tr><td><code>TABVIEW</code> + <code>TABPANEL</code></td><td>Reiter</td></tr><tr><td><code>SPLITTER</code> + <code>SPLITTER-AREA</code></td><td>groessenveraenderbare Bereiche</td></tr><tr><td><code>ACCORDION</code> + <code>ACCORDION-AREA</code></td><td>Akkordeon-Abschnitte</td></tr></tbody></table><p>Zwei Namen, die man vergeblich sucht: <strong>ein Tool &quot;Dynamic Template&quot; gibt es nicht</strong> — das</p><p>dynamische Template ist das, was der <code>DATAREPEATER</code> rendert; es wird ueber dessen Eigenschaften</p><p>konfiguriert und nicht gezogen. Und <strong>&quot;Container&quot; / &quot;Layout&quot; sind der Gruppenname</strong>, keine</p><p>auswaehlbaren Eintraege.</p><p>Dazu kommen die vom Host-Projekt registrierten Custom-Tools</p><p>(<code>MetadataProviderService.customDesignerTools</code>), die am Ende unter der von ihnen deklarierten</p><p>Gruppe erscheinen.</p><h2>Hauptfunktionen</h2><ul><li>Drag-and-Drop von Knoten auf die Canvas mit Persistierung im <code>boardcontent</code>.</li><li>Kontextbezogenes Property-Panel mit zu den ausgewaehlten Komponenten konsistenten Inputs.</li><li>Binding zwischen Knoten (<code>datasource -&gt; repeater/template</code>) mit Minimalvalidierung.</li><li>Integrierte Runtime-Vorschau und Layout-Neuausrichtung.</li><li>Verwaltung ausstehender Aenderungen mit Guard vor dem Verlassen.</li></ul><h2>Kontextmenue der Elemente</h2><p>Rechtsklick auf ein Element der Canvas, auf einen Eintrag der unteren Breadcrumb oder auf einen Knoten im Hierarchiebaum zeigt ein Kontextmenue mit drei Eintraegen:</p><ul><li><strong>Eigenschaften bearbeiten</strong> (pi-cog) - waehlt das Element als &quot;current tool&quot; aus und zeigt sein Property-Panel rechts; entspricht dem Klick im Baum. Nuetzlich, um Eigenschaften verschachtelter Elemente zu bearbeiten, ohne sie in der Hierarchie suchen zu muessen.</li><li><strong>Umbenennen</strong> (nur Breadcrumb) - oeffnet einen Dialog zum Umbenennen des <code>displayName</code>.</li><li><strong>Entfernen</strong> - loescht das Element vom Board.</li></ul><h2>Empfohlener operativer Ablauf</h2><ul><li>Ziel-Dashboard-Route oeffnen.</li><li>Knoten aus der Palette einfuegen/verbinden.</li><li>Wesentliche <code>inputs</code> konfigurieren (z.B. <code>route</code>, <code>action</code>, <code>datasource</code>).</li><li>Speichern und Ergebnis in der Runtime validieren.</li></ul><h2>Betriebshinweise</h2><ul><li>Fuer dashboard-spezifische Fixes <code>boardcontent</code>-Patches gegenueber globalen Aenderungen bevorzugen.</li><li>Doppelte Eigenschaften zwischen <code>inputs</code> und inkonsistentem Inline-Stil vermeiden.</li><li>Immer ueberpruefen, dass Datasources eine gesetzte <code>inputs.route</code> haben.</li></ul>",
                     "codeSamples": []
                 }
             ],
@@ -35168,4 +35258,4 @@ i0.ɵɵngDeclareClassMetadata({ minVersion: "12.0.0", version: "21.2.9", ngImpor
             }] } });
 
 export { FrameworkDocsComponent };
-//# sourceMappingURL=wuic-framework-lib-framework-docs.component-Bi5Pm3vl.mjs.map
+//# sourceMappingURL=wuic-framework-lib-framework-docs.component-B2AdE4N0.mjs.map