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
Enhancement
Generated code for specialized objects currently has the possibility to implement a callback that is called after the deletion (and after the commit) (PersistentObject.handleDelete()). In particular, this callback is not suitable for recursively performing further deletions based on a deletion.
Improvement
Callback that is called before a persistent object is deleted(Modification PersistentObject.notifyUpcomingDeletion()) . This callback can still access the object under deletion to collect data. Recursive deletion operations can then be performed in a result callback.
Test
- See #26554: Solution of WebFolder instances deletes its contents in this way.