#28816 Reference value attributes only generate errors with SingleSelection

enhancement

critical

#29088

Model-based access rights

#29108

Lightweight UI definition layer (TL Views) based on React UI components

major

#28694

Description of model parts as formatted text (rich text)

#28708

Enable Standard Selection in (Tree) Tables and Grids via TL Script

#29102

Add com.top_logic.layout.react module for React/SSE integration

#29221

Automatic determination of possible authorization configurations

#29349

XML Parsing Functions for TL-Script via XMLImporter

#29374

TL Script: gzip()

#29389

Code Completion for Variables ($) in the TL Script Editor

#29396

Conversation display for TL Views: object list element, file chips, card panels

#29399

Info Service Notifications: Display at the bottom instead of the top, and keep them in place when hovering over them with the mouse

#29400

Introduce a first-class "operation mode" service for applications (OperationMode enum + ApplicationModeService)

minor

#29085

Re-login on session timeout instead of redirect to login page

#29089

Extend the TL Script functions log() and info() to include selectable message levels (INFO, WARN, ERROR)

#29195

Problems with HTML attributes and TL script

#29306

TL Script: dateFormat() should accept an explicit timezone to format Calendar values losslessly

#29382

Expose a public, classpath-driven overload of `Workspace.getAppPaths`

#29385

The app archetype should automatically generate a standard git-ignored local-credentials overlay (tl_config) by default

#29392

Transaction Abort on Non-2xx Response

#29398

defect

major

#29383

A dead SOCKET_APPENDER (Chainsaw, localhost:4445) in the default logging configuration can cause logging to stall and operations to abort under heavy load

#29384

The TL-Script functions `resetSequence` and `generateSequenceId` generate a different sequence ID than `SequenceDefaultProvider` (in terms of suffix and context order), so they cannot reset a provider-managed sequence with a dynamic context

#29394

Editable tables in the React UI: Generalized row-set bindings for tabular editing in forms

#29410

Attribut filename der Structured-Text-Bildablage case-sensitive (binär) speichern

#29419

Understandable save failures and form validation feedback in the React view layer

minor

#28816

Reference value attributes only generate errors with SingleSelection

#29359

Inappropriate tooltips on some main tabs

#29360

Occasional error message in the log: "mainLayout" is null.

#29361

Invalid database definition for tag

#29363

Missing validation of dialogs in GOTO statements to dialogs of invisible parents

#29380

Context-sensitive auto-numbering fails if the context and the numbered object are created within a single transaction

#29381

Double-clicking in a graphic component does not work reliably

#29390

Subtree selection ends too early if the lowest level is not included in the level filter

#29393

URL routing in the React view layer is broken: ForwardingReactContext does not delegate getRouteManager()

#29401

Images in an image drop zone cannot be copied or saved using the browser's context menu

#29402

Tree selection is lost when the view is refreshed (invalidated)

#29412

Flaky TestDynamicComponentService.testIncrementalUpdates: asserts on asynchronous WatchService event after a fixed 10ms sleep

#29416

Anzeige des Änderungslogs schlägt fehl, wenn parallel Änderungen committet werden

#29420

FlowDiagram: Fehlerfall im row-wise Sub-Grid: subGridCols=2 und subGridStartCol=1

#29426

FlowDiagram: Text in PDF-eingebettetem Diagramm ist nicht selektierbar

task

major

#29407

Security-Scan: npm-Abhängigkeiten der React-Module aktualisieren

#29408

Security-Scan: httpcore5 anheben; pdfbox-/azure-Findings bewerten

minor

#29415

Slim down the repository CLAUDE.md and consolidate developer guidance into skills and FAQ articles

defect

minor

#28816

Reference value attributes only generate errors with SingleSelection

Migration ModelSystem PersistencyLayer

If there is data in the system such that a reference-type, multi-valued (multiple) attribute points to an object that no longer exists (because it was deleted during a migration, for example), does this result in an error if exactly this one object is referenced in this attribute? (Good)

However, if multiple objects are referenced in the attribute—some of which exist and some of which do not—this does not result in an error. (Bad)

Migration

When resolving a multi-valued reference attribute, any reference to an object that no longer exists now results in a KnowledgeBaseRuntimeException (InvalidLinkException, "Dangling references to no longer existing objects"). Previously, such entries were silently ignored as long as at least one other referenced object existed.

Data sets in which objects were deleted without cleaning up the incoming references (e.g., due to a previous migration) must be cleaned up before the update; otherwise, reading the affected attributes will fail at runtime. Custom migrations that delete objects must also remove the references to those objects.