Major
Detail
Detail
Detail
#27029
Failure to use PropertyInitializer for list-valued properties.
If a tl:PropertyInitializer is configured on a property, it is used to predefine the field value in the declarative form.
If a tl:ConfigurationItem with such a property is created within a list, this initializer is not applied.
Code migration
Fixed the bug that caused GenericFunction used in derived properties not to be set to null for "Mandatory" unset properties in the path. GenericFunction`s have to handle this. See also migration in #18097:
Implementations of GenericFunction used in derived properties must be able to handle null as a value for each of their parameters.
* This can be found, for example, by calling the call hierarchy in Eclipse on Derived.fun().
* Theoretically, it is sufficient to consider only those derived properties that refer to mandatory properties, or other derived properties that refer to mandatory properties. However, since the type of property can change in derivatives of the interface, this is difficult to keep track of and can lead to errors in future changes or extensions of the type hierarchy. Therefore, the functions of all derived properties should be changed accordingly.
Test
TestDeclarativeForms.script.xml