enhancement
major
#29756
React view table: Excel export (parity with classic TableComponent) and generic download view action
#29776
TL Views: Einheitliches Drag & Drop für Tabellen, Baum-Tabellen, Bäume und Kanban-Boards mit mehreren Drop-Operationen, Drop-Positionen und Drag-Arten
#29782
Concept: Discover right for the model based security (filtered object sources, masked form fields)
#29787
React UI: Atomare Bausteine (Schaltflächen, Menü-Auslöser, Checkboxen, Eingabefelder, Chips, …) sehen überall gleich aus und lassen sich durch eine Komponentenbibliothek (z.B. Material UI) ersetzen
#29797
XML import into existing data: resolve IDs against existing objects, skip known subtrees, optional references, language and variables from the input
#29799
Form dependencies: derived fields do not follow edited values; Java script functions cannot report what they read to the ScriptTracer
#29812
TL Views: a table column declares its own comparator; enumeration columns follow the enumeration's order
#29814
TL Views: no supported way for a server-side background source (a bus listener) to push a channel value into a view; only <start-job> does it through internal API
#29816
TL Views table: a <computed-column> cannot be hidden by default (shown only through the column chooser)
#29825
Design System: column selection of the React table – grouping as one select, checkbox first, visible and hidden columns apart
#29836
Design System wave 4a: dialog, window, drawer, snackbar and notice bar read the design system package
#29840
Persistent object wrapper hierarchy: remove dead and duplicated code, move stateless behavior into interface defaults, replace class identity checks
#29849
Configuration: an encrypted property value that is not a valid encrypted value is silently "decrypted" to garbage instead of being rejected
#29854
PowerPoint-Präsentationen aus TL-Script erzeugen: deklarative Folienbausteine, Export in eine Firmenvorlage, Analyse von Vorlagen
#29858
Privileged TL-Script functions: authorize a configured script as a whole by a command group on a computed security object
major
#29580
RowSourceObserver: a disposed observer is still notified and throws NPE (_scope null) from DerivedViewChannel and GlobalModelEventForwarder
#29783
TLScriptFunctions: a script function is bound to an arbitrary overload of the same name, including a private one
#29788
Configuration: the error for an undecodable encrypted property echoes the value (e.g. a plain-text password) into the log
#29789
tl:generate-java fails on the first build after a TopLogic version change: it neither resolves the engine web fragments nor reads the project's own model sources
#29791
TL Views table: the row activation button runs the activation command without selecting its row, so commands reading the selection channel see another row (wrong breadcrumb label)
#29792
TL Views: a closed dialog (and a left tile-stack frame) stays visible for 1 s unless the application ships its own exit animation - move the demo's animations into the engine
#29800
Model patch of an existing database fails when a class gains a generalization and overrides its attributes in the same change
#29806
WrapperGenerator: every top-level class of a module with a singleton extends StructuredElement (regression of #26716)
#29807
WrapperGenerator: classifier constants of two enumerations collide, the generated factory does not compile
#29808
TL Views: the <on-submit> command of a text or number <value-input> runs on Enter only, not when the field is left with a changed value
#29810
TL Views: the selection channel of a <tree> keeps an object deleted in another view, and scripts over it fail
#29813
TL Views: a <tree> does not react to a change of an object it does not display yet, so a node that becomes a child of a shown node does not appear
#29822
CompactHistoryTask: Wartungsfenster bleibt nach dem Lauf aktiv, Task-Ende geht im Neustart der Persistenzschicht verloren
#29824
TL Views table: "Standard wiederherstellen" in the column selection drops a declared group-by (and does not restore the declared sort)
#29837
TestCompileJSPs modifies the module's source webapp and breaks concurrently running scripted tests of the same module
#29838
ClusterManager: a database connection that failed in a cluster transaction is returned to the pool and keeps failing every refetch
#29846
Changing the type of a column with content fails on Oracle (ORA-01439) and of an indexed column on MS SQL Server
#29848
ReportQueueTest.testAddJob fails sporadically: the queue thread may process the job before the test checks that it is queued
task
minor
#29790
Upgrade guide 7.11 to 8.0: add the Maven >= 3.8.9 requirement, state that 7.10.x applications can follow it, and point to it from the release notes
Follow-up to #29612 (upgrade-7.11-to-8.0.md, now part of the developer documentation in com.top_logic/src/main/java/META-INF/tl-docs/). Found while upgrading a small application from 7.10.2 to 8.0.0-alpha10 with the guide; the guide worked well otherwise.
Missing steps
- Maven >= 3.8.9. #29702 raised the requireMavenVersion enforcer rule in tl-parent-all to 3.8.9 on 2026-09-30, after the guide was written (2026-09-17); #29702 has no RequiresMigration keyword. Phase 1.1 says "No new JVM flags are needed" but does not mention the Maven version, so a build with e.g. Maven 3.8.7 (current Debian/Ubuntu package) stops at the enforcer: {{{
Rule 0: org.apache.maven.enforcer.rules.version.RequireMavenVersion failed with message: Detected Maven Version: 3.8.7 is not in the allowed range [3.8.9,). }}} Add to phase 1.1: Maven 3.8.9 or newer is required; a Maven wrapper (mvn -N wrapper:wrapper -Dmaven=3.9.x) is the project-local way if the system Maven is older.
- Java binding generation. An application that binds tl:generate-java to generate-sources cannot build after the parent bump, see #29789. Also worth a sentence: an application whose POM has no own <version> inherits the TopLogic version, so its own artifact changes coordinates with every upgrade.
Clarification
The guide states 7.11.0 as the base. 7.11.0 has no ticket with the RequiresMigration keyword, so a 7.10.x application can follow the guide unchanged (verified with 7.10.2). Say so in the introduction, otherwise 7.10.x users look for a separate 7.10 to 7.11 path.
Discoverability
The guide ships only inside the 8.0 jars (tl-docs). An application still on 7.x cannot see it via its developer documentation (list_docs of the tl-mcp server lists only the docs of the modules on its class path), and the release notes on dev.top-logic.com list only the migration tickets of the respective (alpha) release, with no cumulative view. Someone upgrading from 7.x therefore only finds it by browsing the engine repository on GitHub.
Lösung
In upgrade-7.11-to-8.0.md:
- Introduction: a 7.10.x application follows the guide unchanged, there is no separate 7.10 to 7.11 path.
- Phase 1.1: Maven 3.8.9 or newer is required (#29702), with the enforcer message and the Maven wrapper as the project-local remedy.
- Phase 1.1, POM hygiene: an application POM without an own <version> inherits the TopLogic version; declare an own version.
- Appendix A: #29702 is listed as a change without migration section.
The binding generation (#29789) is not described in the guide: #29789 is planned for 8.0.0, the target version of the guide.
Discoverability: this ticket carries RequiresMigration, so the migration section below - the pointer to the guide - appears in the release notes of the release it lands in and of 8.0.0. Nothing is shipped with 7.x.
Migration
An application is upgraded from TopLogic 7.10 or 7.11 to 8.0 following the upgrade guide upgrade-7.11-to-8.0 of the developer documentation (shipped in tl-core, readable with the read_doc tool of the tl-mcp server and in the documentation window of a React application): https://github.com/top-logic/tl-engine/blob/TL_8.0.0/com.top_logic/src/main/java/META-INF/tl-docs/upgrade-7.11-to-8.0.md
The guide covers all changes of 8.0 that require a migration step, including those whose tickets have no migration section, in the order in which they have to be done.