loio
3a8dd1312c374a2983056247096772de

view on: demo kit nightly build | demo kit latest release

What's New in OpenUI5 1.82

With this release OpenUI5 is upgraded from version 1.81 to 1.82.

Version	Type	Category	Title	Description	Action	Available as of
1.82	Changed	Announcement	Third-Party Library Upgrades	Third-Party Library Upgrades `Handlebars.js` Library The `Handlebars.js` library has been upgraded from version 4.4.3 to 4.7.6. Upgrade to New jQuery Version We have upgraded the third-party jQuery library from jQuery 2.2.3 to jQuery 3.5.1. Several measures have been implemented to make this new version of jQuery delivered with OpenUI5 as compatible to the previous version as feasible. In particular, we have introduced a compatibility layer to ensure that most of your existing application or control code won't need adjustment. This could, however, introduce incompatibilities to the new jQuery version. For more information, see Upgrading from a Version Below 1.82 to understand any current and possible future impact. _{Changed•Announcement•Info Only•1.82}	Info Only	2020-09-17
1.82	New	Feature	Badge Implementation	Badge Implementation Badges display very short and important information that attracts the user’s attention. We have made improvements in these controls to implement badge: `sap.ui.integration.widgets.Card` – the badge is no longer in experimental state. For more information, see the Text Badge section and the Sample in the Card Explorer. `sap.m.Button` - the badge acts both as a visual eye catcher and as a counter to display a maximum of 4 digits or characters. It can be applied to any button type, but we recommend that you only use it on the `Default`, `Ghost`, `Transparent`, and `Emphasized` button types. For more information, see the Sample. The `<ui-integration-card>` HTML custom element now supports text badges. For more information, see the Sample in the Card Explorer. _{New•Feature•Info Only•1.82}	Info Only	2020-09-17
1.82	Changed	Feature	*Five New Icons Available in the SAP Fiori Tools* Icon Font**	*Five New Icons Available in the SAP Fiori Tools* Icon Font** Find the icon that fits your needs via the OpenUI5 Icon Explorer. _{Changed•Feature•Info Only•1.82}	Info Only	2020-09-17
1.82	Changed	Feature	OpenUI5 OData V2 Model	OpenUI5 OData V2 Model With the new version of the OpenUI5 OData V2 model, we introduced the new `ignoreMessages` binding parameter for the `sap.ui.model.odata.ODataPropertyBinding`. If `ignoreMessages` is set to `true`, model messages are not propagated to the binding. This is useful if a part of a composite binding is required for formatting, but not displayed itself. Depending on their format options, some composite types, such as `sap.ui.model.type.Currency`, automatically ignore model messages for some of their parts. Setting this parameter to `true` or `false` overrules this default behavior. _{Changed•Feature•Info Only•1.82}	Info Only	2020-09-17
1.82	Changed	Feature	OpenUI5 OData V4 Model	OpenUI5 OData V4 Model The new version of the OpenUI5 OData V4 model introduces the following features: The new `$$ignoreMessages` binding parameter is available for `sap.ui.model.odata.v4.ODataPropertyBinding`. If `$$ignoreMessages` is set to `true`, model messages are not propagated to the binding. This is useful if a part of a composite binding is required for formatting, but not displayed itself. Depending on their format options, some composite types such as `sap.ui.model.type.Currency` or `sap.ui.model.odata.type.Unit` automatically ignore model messages for some of their parts. Explicitly setting this parameter overrules this default. The `sap.ui.model.odata.v4.Context#requestProperty` method now also works for properties that are not part of the `$select` option of the underlying binding and were not fetched previously. The `sap.ui.model.odata.v4.Context#requestSideEffects` method now supports absolute paths. These must start with the entity container of the service, for example `/com.sap.gateway.default.iwbep.tea_busi.v0001.Container/TEAMS`. `The sap.ui.model.odata.v4.Context#delete` method is now supported for kept-alive contexts. A context can be kept alive with the `sap.ui.model.odata.v4.Context#setKeepAlive` method introduced with OpenUI5 1.81. Restriction: Due to the limited feature scope of this version of the OpenUI5 OData V4 model, check that all required features are in place before developing applications. Double-check the detailed documentation of the features, as certain parts of a feature may be missing. While we aim to be compatible with existing controls, some controls might not work due to small incompatibilities compared to `sap.ui.model.odata.(v2.)ODataModel`, or due to missing features in the model (such as tree binding). This also applies to controls such as `TreeTable` and `AnalyticalTable`, which are not supported in combination with the OpenUI5 OData V4 model. The interface for applications has been changed for easier and more efficient use of the model. For a summary of these changes, see Changes Compared to OData V2 Model. For more information, see OData V4 Model, the API Reference, and the Samples in the Demo Kit. _{Changed•Feature•Info Only•1.82}	Info Only	2020-09-17
1.82	Changed	Control	`sap.ui.integration.widgets.Card`	`sap.ui.integration.widgets.Card` We have updated the UI5 Web Components dependency of the Adaptive Cards to the v1.0.0-rc.8 version. With this update the Adaptive Cards receive the theming and custom theming support. Now you can use both High Contrast Black and High Contrast White themes, or add a custom theme, as the Web Components are compatible with the UI Theme Designer tool. For more information, see the High Contrast Black and the High Contrast White samples in the Card Explorer. _{Changed•Control•Info Only•1.82}	Info Only	2020-09-17