major
minor
defect
major
minor
#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
enhancement
For each database table, a tl:TLClass (table interface) is created, and all !TLClasses that store data in this table have this table set as their generalization.
This should no longer be the case.
Code Migration
- Model references to tl.tables must be replaced with references to "real" model elements.
- Replacing model references:
- tl.tables:ExternalReferenceTableInterface => Ticket:ExternalReference
- tl.legacy.tabletypes:ExternalReferenceTable => Ticket:ExternalReference
- tl.tables:ActivityTableInterface => RiskItems:Activity
- tl.tables:ApproachingCurveTableInterface => ApproachingCurveStructure:ApproachingCurveType
- tl.tables:AssignedGoalTableInterface => AssignedGoals:AssignedGoal
- tl.tables:CommitteeTableInterface => CommitteeStruct:Committee
- tl.tables:CostTypeTableInterface => costStructure:CostAreaChild
- tl.tables:CostUnitTableInterface => costStructure:CostUnit.internal
- tl.tables:DecisionMemoTableInterface => Decisions:DecisionMemo
- tl.tables:ExportTemplatePlaceholderTableInterface => posElement:ExportTemplatePlaceholder
- tl.tables:ExportTemplateTableInterface => posElement:ExportTemplate
- tl.tables:FinalReportTableInterface => FinalReports:FinalReport
- tl.tables:GovernedTaskTableInterface => GovernedObjects:GovernedTask
- tl.tables:KPGroupTableInterface => KPI:KPI.Group
- tl.tables:MeetingTableInterface => Meetings:Meetings.all
- tl.tables:MilestoneTableInterface => Milestones:Milestones.all
- tl.tables:OrgUnitTableInterface => orgStructure:OrgUnit.base
- tl.tables:ProgramTableInterface => Programs:Program
- tl.tables:ProjectResultTableInterface => FinalReports:ProjectResult
- tl.tables:ProjectTableInterface => projElement:Project
- tl.tables:ScenarioTableInterface => ScenarioStruct:Scenario.all
- tl.tables:StatusReportDetailTableInterface => StatusReports:StatusReportDetail
- tl.tables:StatusReportTableInterface => StatusReports:StatusReport
- tl.tables:SubprojectTableInterface => projElement:Subproject
- tl.tables:TagTableInterface => Tag:Tag
- tl.tables:TargetProductTableInterface => Programs:TargetProduct
- tl.tables:TemplateActivityTableInterface => projectTemplate:Activity
- tl.tables:TemplateMilestoneTableInterface => projectTemplate:projectTemplate.Milestone
- tl.tables:WorkpackageTableInterface => projElement:Workpackage
- tl.tables:ObjectTableInterface => tl.model:TLObject or, better yet, something more specific
- References to other classes in "tl.tables" must be replaced with appropriate alternatives. The conservative approach to migration would be to identify which TLClasses write to the corresponding table (and its derived tables) and select the common supertype.
- If model files from the database were overwritten, changes must be applied there as well.
Data Migration
If the above code changes were made in separate model files, a migration script must be created to apply these changes to the database. For guidance, you can refer to the script at, for example: /com.top_logic.project.pos/webapp/WEB-INF/kbase/migration/tl-pos/Ticket_26398_remove_table_interfaces.migration.xml.
Test
Refactoring No test.