Major
Detail
Major
Detail
#26382
Error messages "Duplicate tag name..." when starting an application in the IDE from a TL-Studio
#26405
TTypeRewriter logs warning "Unable to resolve items by external reference" also unnecessarily
#26431
Changed superclass relationship leads to changed attribute list in the form editor only after a restart
#26484
In-app template for grid and tables: Function "Verifier for use as list item" does not get component model
#26536
When rendering HTML from TLScript expressions, configured renderers are not taken into account
#26797
Transaction with user input: invisible properties of the form model cannot be assigned values (initialized)
#26885
Constraints on declarative forms with arguments from a container reference lead to errors for new elements
#26921
ClassCastException when evaluating security rules that refer to (non-structuredElement) singletons of a module.
#26922
With generated subject classes, a default provider of an attribute in a non-structure class does not get a create context
#26988
In-app documentation generator does not extract documentation for overwritten config properties
#27027
Declarative forms: SelectField disappears after upload if option list depends on mandatory property
#27042
MaintenanceJspBase should write to the log first, then to the client, instead of the other way around.
Enhancement
Major
#25881
No more automatic creation of "table types" for database tables
Until now, for TL-5 compatibility reasons, model elements are automatically created in the dynamic model for database tables. These "table types" are not part of the model configuration and therefore cannot be migrated automatically.
Furthermore, for tables for which no model is defined (e.g. Person, Group, ...) additional model elements are generated (in the module "tl.legacy.tabletypes").
Improvement
- No more automatic generation of these legacy table types. Model elements must be defined for such tables.
Code migration
- Model references to tl.legacy.tabletypes must be replaced with references to "real" model elements.
- Replacing model references:
- tl.legacy.tabletypes:PersonTable => tl.accounts:Person
- tl.tables:PersonTableInterface => tl.accounts:Person
- tl.legacy.tabletypes:GroupTable => tl.accounts:Group
- tl.legacy.tabletypes:WebFolderTable => tl.folder:WebFolder
- tl.legacy.tabletypes:DocumentTable => tl.folder:Document
- tl.legacy.tabletypes:DocumentVersionTable => tl.folder:DocumentVersion
- tl.tables:AbstractUnitTableInterface => tl.units:AbstractUnit
- tl.legacy.tabletypes:CurrencyTable => tl.units:Currency
- tl.legacy.tabletypes:UnitTable => tl.units:Unit
- tl.legacy.tabletypes:CommentTable => tl.comments:Comment
- tl.legacy.tabletypes:MetaElementTable => tl.model:TLClass
- tl.tables:FastListEltTableInterface => tl.model:TLClassifier
- tl.legacy.tabletypes:FastListEltTable => tl.model:TLClassifier
- tl.legacy.tabletypes:MetaAttributeTable => tl.model:TLStructuredTypePart
- tl.legacy.tabletypes:FastListTable => tl.model:TLEnumeration
- tl.legacy.tabletypes:AddressTable => tl.accounts:Address
- tl.legacy.tabletypes:BoundedRoleTable => tl.accounts:Role
- tl.legacy.tabletypes:MailFolderTable => tl.mail:MailFolder
- tl.legacy.tabletypes:MailTable => tl.mail:Mail
- tl.tables:UsedSkillProfileTableInterface => Resources:UsedSkillProfile
- The tag <reference-builder ... /> or <reference-builder ... ></reference-builder>.
- Search for attributes of type tl.tables:ContactTableInterface and replace with either Contacts:Contact.Person or Contacts:Contact.Company.
Data migration
If the above code changes have been made, a migration script must be created to make these changes in the database. Here you can use the script com.top_logic.element/webapp/WEB-INF/kbase/migration/tl-element/Ticket_25881_Removed_legacy_types.migration.xml as an example.
Test
Refactoring, no additional test.