You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With this release OpenUI5 is upgraded from version 1.107 to 1.108.
Version
Type
Category
Title
Description
Action
Available as of
1.108
Deprecated
Feature
Deprecations
Deprecations
There are currently no major deprecations. For a complete list of all deprecations, see Deprecated APIs.
Deprecated•Feature•Info Only•1.108
Info Only
2022-11-03
1.108
Changed
Feature
TypeScript Demo App
TypeScript Demo App
A new TypeScript To-Do List demo app is now available in both the Demo Apps and the Samples sections of the Demo Kit. For more information, see the Samples.
Changed•Feature•Info Only•1.108
Info Only
2022-11-03
1.108
Changed
Control
sap.m.IllustratedMessage
sap.m.IllustratedMessage
We have introduced a new illustration breakpoint variant Dot, suitable for spaces that don't have a lot of vertical space. For more information, see the API Reference.
Changed•Control•Info Only•1.108
Info Only
2022-11-03
1.108
Changed
Control
sap.m.Avatar
sap.m.Avatar
Up to three Latin letters can be displayed as initials in a sap.m.Avatar. For more information, see the API Reference and the Sample.
Changed•Control•Info Only•1.108
Info Only
2022-11-03
1.108
Changed
Feature
Replacement for jQuery.fn.control
Replacement for jQuery.fn.control
To become more independent from specific jQuery functionality, we now provide the new sap.ui.core.Element#closestTo method as a replacement for the jQuery.fn.control extension function, which is commonly used to retrieve the nearest OpenUI5 control that wraps a given DOM element. The new method returns a single OpenUI5 element instead of the array of OpenUI5 elements returned by jQuery.fn.control. You might therefore need to add an outer loop when migrating your code to the new API.
The new version of the OpenUI5 OData V4 model introduces the following features:
We now provide "deferred delete" requests: You can call the sap.ui.model.odata.v4.Context#delete method with an API group; the back-end request is then only sent when ODataModel#submitBatch is called for this API group. For more information, see Deleting an Entity.
We have improved our documentation of how to overwrite value list annotations in local annotation files. For more information, see Value Lists.
The dataRequested and dataReceived events introduced with OpenUI5 1.106 for the sap.ui.model.odata.v4.ODataModel now provide the path for additional property requests.For more information, see the API Reference for ODataModel.dataReceived and ODataModel.dataRequested.
Changed•Feature•Info Only•1.108
Info Only
2022-11-03
1.108
Changed
Feature
OpenUI5 OData V2 Model
OpenUI5 OData V2 Model
The new version of the OpenUI5 OData V2 model introduces the following features:
We now support "deep create" requests for navigation properties of cardinality "many". For more information, see Deep Create.
We now provide the new sap.ui.model.ClientTreeBinding#getCount method.For more information, see the API Reference.
When you use an sap.ui.model.type.Currency, sap.ui.model.odata.type.Currency, or the currency instance of sap.ui.core.format.NumberFormat, entered currency codes are now parsed case-insensitively where possible.
We have introduced the new calendarWeekNumbering format option for sap.ui.core.format.DateFormat.
Changed•Feature•Info Only•1.108
Info Only
2022-11-03
1.108
Changed
Control
sap.m.Carousel
sap.m.Carousel
We have improved the keyboard interaction and accessibility of the control. The initial focus is now on the active carousel item, unlike before, when it was on the carousel container. This allows you to focus on a concrete item and provides more information to the screen readers.For more information, see the Sample.
Changed•Control•Info Only•1.108
Info Only
2022-11-03
1.108
Changed
Control
sap.ui.integration.widgets.Card
sap.ui.integration.widgets.Card
The Adaptive card now uses the recently released 1.7.0 UI5 WebComponents bundle. For more information, see the Adaptive Card Learn section in the Card Explorer.
You can now configure the visibility of the card footer using the new visible boolean property. Card developers can set this property in the manifest. Additionally, they can add it to the Configuration.js, which will also enable card administrators, who are using the Configuration editor, to control the visibility of the card footer. For more information, see the Card Footer section and the Sample in the Card Explorer.
We have made the loading placeholder for Analytical cards more detailed to better reveal the expected loading content. For more information, see the Sample.
We have (experimentally) enhanced the sap.ui.integration.Extension with a new loadDependencies lifecycle hook. As a card developer, you can use it to load critical dependencies for your extension, without which the data cannot be displayed. While the dependencies are loaded, the card displays a loading animation. This hook is asynchronous, so other tasks won't be blocked. For more information, see the Card Extension section and the Sample in the Card Explorer, and the API Reference.
A new visible property is now introduced for icons and avatars to achieve consistency in representation if an empty value for the src property is used in the card manifest. The new property is available for:
Default Header
Sap.f.CardHeader
ObjectContent
TableContent
List Content
For more information, see the Sample in the Card Explorer.