major
nice-to-have
minor
#25217
Layout-Export führt zu invaliden Komponenten-Referenzen bei Referenzierung einer bestehenden Komponente
#25327
Modell-Editor: Falsche Kompositionsmarker, wenn Container-Typ in Diagramm von Content-Typ gezogen wird
defect
(User-visible)
minor
#25768
DataItemControl reagiert inkonsequent auf DataField.setDownload()
When a `DataItemControl` is created, the download configuration of the `DataField` is taken into account, so that if the download is disabled, no corresponding command is registered. However, this configuration is ignored during rendering, so a download button is always displayed to the user. If the download is disabled in the field and the user clicks the button, an exception is thrown and the user is presented with a technical error message. Therefore, the `DataItemControl` should also take the download configuration into account during rendering. This error occurs only in the immutable state.
Improvement
If a DataField is immutable, it uses the DownloadImageRenderer to render the download button. This renderer displays a download button regardless of the configuration—even if downloads are not permitted at all. With the new isDownloadAllowed field, the configuration is now taken into account, and the button is not rendered.
Code Migration
The constructor of the `DownloadImageRenderer `, ` DownloadImageRenderer(boolean downloadAllowed) `, has been updated to include the ` downloadAllowed ` parameter. `INSTANCE ` creates a ` DownloadImageRenderer ` with ` downloadAllowed = true`.
Test
In the technical demo under “Forms,” two immutable DataFields were added under “DataField.” One of them allows downloads, while the other does not. The buttons must be rendered accordingly.