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
A historical reference can only point to one object at a time. To do this, you have to select the "Historic storage".
It would be better to have a "versioning" classification for a reference - such as "multiple" and "mandatory".
Implementation
A reference attribute now has a further configuration option Historicization. There are 3 options here:
- Current: Default. Reference to current objects.
- Historical: The value of the attribute is a historical object. If a current object is set, it is replaced by the corresponding historical object when saving.
- Mixed: The value can be either a current or a historical object.
The system selects an associated storage according to the value.
Test
TestReferenceMetaAttribute or manually
- Under Structures > Type demo, assign the object A0 to a DemoTypes.A A0 in the historicalReferences attribute and save.
- Change the value string and save.
- Open the object A0 assigned in the historicalReferences attribute:
- Expectation a dialog with a historical A is opened: The object cannot be edited and the value string has the value before the change.