Enhancement
Major
Detail
Bugfix
Detail
#26484
In-app template for grid and tables: Function "Verifier for use as list item" does not get component model
#26885
Constraints on declarative forms with arguments from a container reference lead to errors for new elements
#26922
With generated subject classes, a default provider of an attribute in a non-structure class does not get a create context
Bugfix
The error is in ScriptingUtil.findNodeByValuePath(List<ModelName>, TLTreeModel, LabelProvider, ActionContext). There it checks if the tl:ModelName is a tl:NamedValue or a tl:LabeledValue. If it is neither one nor the other, actionContext.resolve(valueRef) is called. The correct thing to do there would be to pass a "value context" as the second parameter.
Cause is #21150.
Test
No test. It would take too long to find a view where this still occurs. All existing views with scripts do not seem to be affected.