major
nice-to-have
minor
#25217
Layout-Export führt zu invaliden Komponenten-Referenzen bei Referenzierung einer bestehenden Komponente
#25327
Modell-Editor: Falsche Kompositionsmarker, wenn Container-Typ in Diagramm von Content-Typ gezogen wird
defect
major
#25210
Modell-Referenzen in Konfigurationen müssen über Namen realisiert sein, falsche Abhängigkeiten in TestComponentConfiguration und Layout-Build-Tooling
DynamicComponentService: Layouts may refer to other typed layout definitions.
Dependencies on the ModelService must be removed. It is not acceptable to have to start the application with its model for the build tooling (layout overlay processing). Parameters of the typed configuration must not contain any references to model elements. This applies in particular to form configurations.
Test
- Configure the form with ` formTable ` in-app.
- Export the layout to the IDE.
- CallTestComponentConfiguration.
The issue is the resolution of the `typeSpec` argument, which specifies the target type for the form.
Code Migration
If in-app forms already exist:
- Search for <formTable, <foreign-objects, and com.top_logic.layout.formeditor.parts.ForeignAttributeTemplateProvider in *.bpml, *.bpmn, and *.xml files
- In the found tag, replace the typeSpec attribute with type.
- This migration is intended only for workspace configurations, not for forms in an existing database. Forms in the database are migrated automatically.
- Alternatively, the workspace migration can also be performed automatically using a shell command: find */webapp/WEB-INF/layouts -name \*.xml -print0 | xargs -0 -n 1 -I{} xsltproc -o "{}" com.top_logic/webapp/WEB-INF/kbase/migration/tl/Ticket_25210_Model_references_in_form_definitions.migration.xsl "{}" followed by normalization of the layouts.