` (empty, filled by the application) and `

` with the administration. An overlay of the shell (`WEB-INF/views/app.view.xml` of an application) that still names `config:reference="system-separator"` or uses `` or `` can no longer be loaded (the application answers `/view/` with HTTP 500). Adapt: - Entries placed before the system section with `config:position="before" config:reference="system-separator"` are written into the application section without these two attributes: ```xml

...

``` - A `` between own entries: put the entries before and after it into one `

` each. - A `` with label: replace it by `

` with the same label (optional `label`, `icon`) and move the entries it covered into the section. Entry ids stay unchanged. Detect: `grep -rn -e 'system-separator' -e ' ``` becomes ```xml ``` Likewise `cell-class` → `cell-role` on the column and `css-class` → `role` on `ResourceDisplayByExpression`. A script that yields further own classes besides the status class keeps those in the class property. A display with a role appears as a pill, not as coloured text. The TL-Script functions `securityGrantsRowClass` and `securityGrantsCellClass` are renamed to `securityGrantsRowRole` and `securityGrantsCellRole`, yield a role name and belong into `row-role` resp. `cell-role`. Java: `RowClassFunction` is renamed to `RowFunction` (`RowFunction.rowClass(...)`, `RowFunction.rowRole(...)`); the record `ColumnSetup` has the additional component `cellRole` after `cellClass`. Detect: `grep -rn -e 'tl-status-' -e 'securityGrantsRowClass' -e 'securityGrantsCellClass' -e 'RowClassFunction' -e 'ColumnSetup(' .` ### 4.3 Showing a unit only for one type: `` instead of `` (#30258) An `` whose `type` only serves to hide a unit for objects of other types is replaced by ```xml ``` (or complemented by it, if an access check is wanted too; its `type` is then a type all checked objects have). Detect: `grep -rn '` is ``, `` is ``. An application that overrides these views or uses the actions in own views renames them. Detect: `grep -rn -e 'invitation-code' -e 'check-invitation-code' -e 'accept-invitation' .` ### 4.6 Agents and tools at `/agent-api` (#30200) The key commands are gone. Objects are addressed with the IDs from the observation (`key` / `nodeId` / `rowId` / `value`, see the respective argument schema); the table takes `rowId` instead of `rowIndex`, `drop` expects `keys` as JSON array. Argument schemas are under `schemas` and referenced via `$ref`; there is no `params` field any more. The compact view is called `mode=actions`, `pretty=true` gives indented output. Adapt own clients, agent prompts and recorded scripts. Detect: `grep -rn -e 'agent-api' -e 'rowIndex' -e 'ByKey' -e '"params"' .` ### 4.7 Log view of the administration moved (#30059) The view `admin/system/logs.view.xml` (module `tl-layout-view`) is now `admin/monitoring/logs.view.xml`. A same-path overlay of the application (`WEB-INF/views/admin/system/logs.view.xml`) or a `` must use the new path; an overlay of the old path has no base any more. Detect: `grep -rn 'admin/system/logs' . ; find . -path '*WEB-INF/views/admin/system/logs.view.xml' -not -path '*/target/*'` --- ## 5. Java APIs and TL-Script ### 5.1 View commands without `HandlerResult` (#30151) Own `ViewCommand` implementations, `CommandModel`s, `ButtonAction`s or `@ReactCommandHandler` methods: - return type `void` instead of `HandlerResult`; `return HandlerResult.DEFAULT_RESULT;` is dropped; - `return HandlerResult.error(key)` becomes `throw new TopLogicException(key)`; `return HandlerResult.notExecutable(...)` resp. checking an `ExecutableState` becomes `throw CommandErrors.notExecutable(state)`; - a caller evaluating `command.execute(...)` catches `TopLogicException` instead of checking `isSuccess()`; - a handler answering its caller declares the answer as msgbuf message and returns it instead of `ReactCommandReply.create().put(...).toResult()`. Client code reads the answer fields as before; a failed command now answers with `success: false` and `error`. Detect: `grep -rn -e 'ViewCommand' -e 'CommandModel' -e 'ButtonAction' -e 'ReactCommandHandler' -e 'ReactCommandReply' --include=*.java . | grep -v '^.*import'` ### 5.2 Command lists and `ViewCommandModel` (#30063, #30207) - Code reading or setting the command list of a configuration of `CommandCarrierElement` or `FormElement` (`getCommands()`) gets `List` instead of `List>`. `.view.xml` files are unchanged. - `ViewCommandModel.execute(ReactContext, Object)` is now `execute(Object)`; the command runs in the context the model was created with. - The public constructors of `ViewCommandModel` and `ViewUploadCommandModel` expect the `ViewContext` as first argument. `ViewCommandModel.create(...)` / `forCommand(...)` no longer accept a `null` context. - `RowCommandColumn.RowCommand.of(...)` expects no context any more. - An own wrapper around a `ViewCommandModel` that only sets another execution context is superfluous. Detect: `grep -rn -e 'CommandCarrierElement' -e 'FormElement' -e 'ViewCommandModel' -e 'ViewUploadCommandModel' -e 'RowCommand.of' --include=*.java .` ### 5.3 Own React controls: stable object IDs for scripting (#30200) - Subclasses of `ReactControl` overriding `scriptingScalarState()` override `scriptingScalarState(ProjectionMode mode)` instead (the variant without parameter is `final`). Implementations of `ScriptingNode.scriptingState()` become `scriptingState(ProjectionMode mode)`. An object is entered into the projection with `ScriptingModelKey.putIdentity(projection, mode, objectIdentities(), ...)` instead of by its key. - A control whose commands address objects holds their IDs in an `ObjectIdIndex`, returns it from `objectIdentities()` and marks the ID arguments of its typed argument interfaces with `@DisplayedObjectId` (lists additionally with `@JsonBinding(SimpleJsonListBinding.class)`). A `recordCommand` override that only translates IDs into keys is dropped. - Removed types: `ModelKeyArguments` (constant `KEY` is now in `ScriptingModelKey`), `SelectByKeysArguments`, `SelectByNameArguments`, `DropObjectsArguments` and the `*ByKeyArguments` of table and tree. Detect: `grep -rn -e 'scriptingScalarState' -e 'scriptingState(' -e 'ModelKeyArguments' -e 'SelectByKeysArguments' -e 'SelectByNameArguments' -e 'DropObjectsArguments' -e 'ByKeyArguments' -e 'recordCommand' --include=*.java .` ### 5.4 Model value listeners (#30132) An own class implementing `com.top_logic.layout.form.ValueListener` that is configured in a model annotation `` must implement `com.top_logic.model.annotate.AttributeValueListener` instead: `valueChanged(TLFormObjectBase object, TLStructuredTypePart attribute, Object oldValue, Object newValue)` receives the edited object (form overlay) and the attribute instead of the `FormField`. Model files and `