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 SAPUI5 is upgraded from version 1.62 to 1.63.
Version
Type
Category
Title
Description
Action
Available as of
1.63
New
Feature
Custom Currencies
Custom Currencies
Comprehensive support for formatting and parsing currencies has been part of SAPUI5 for a long time. We now extended the handling of custom currencies, so that you can also specify custom currencies per currency NumberFormat instance.
UI5 Web Components are a set of reusable UI elements, which can be used for your static websites or web apps with a minimal footprint. They bring the relevant SAPUI5 qualities and latest SAP Fiori user experience to the HTML level and enable you to build a complete, enterprise-ready, and responsive web app, even if you're already using a different web framework.
UI5 Web Components are not built on top of SAPUI5 and are not its successor. They are lightweight and independent UI elements, offered complementary to the framework.
We have implemented a new sap.f.ShellBar control, which is used as the uppermost section (shell) of the app. The control is fully responsive and adaptive, and corresponds to the latest SAP Fiori Design Guidelines.
UploadSet is a new control that enables users to upload one or multiple files from their computer, tablet, or phone and to attach them to your application. This control builds on the sap.m.UploadCollection control, providing better handling of headers and requests, unified behavior of instant and deferred uploads, as well as improved progress indication.
The new version of the SAPUI5 OData V4 model introduces the following features:
The new types sap.ui.model.odata.type.Unit and sap.ui.model.odata.type.Currency: The new types use the unit or currency customizing as provided by the back end in a special code list. For more information, see Currency and Unit Customizing in OData V4.
The method sap.ui.model.odata.v4.AnnotationHelper.format: This method can be used instead of v4.AnnotationHelper.value to generate bindings with type information and constraints. It also includes $Path in the result. To avoid the inclusion of $Path, resolve $path with the sap.ui.mode.odata.v4.AnnotationHelper.resolve$Path method. To create composite bindings with the new sap.ui.model.odata.type.Unit and sap.ui.model.odata.type.Currency types, use sap.ui.model.odata.v4.AnnotationHelper.format. For more information, see Meta Model for OData V4.
The binding parameter $$patchWithoutSideEffects: The parameter was introduced with SAPUI5 1.60 and can now be used for sap.ui.model.odata.v4.ODataListBindings. The parameter is now also inherited to dependent bindings to avoid inconsistent behavior that was caused by the missing inheritance.
Restriction:
Due to the limited feature scope of this version of the SAPUI5 OData V4 model, check that all required features are in place before developing applications. 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 smart controls (sap.ui.comp library) and SAP Fiori elements that do not support the SAPUI5 OData V4 model, as well as controls such as TreeTable and AnalyticalTable, which are not supported together with the SAPUI5 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.
We have introduced a fallback image behavior that handles situations when the provided image source path leads to a non-existing image. If the initials property is set, Avatar displays the set value, otherwise a default icon markup is displayed.For more information, see the Sample.
Changed•Control•Info Only•1.63
Info Only
2019-02-27
1.63
Changed
Control
sap.f.DynamicPage
sap.f.DynamicPage
We have implemented the option to provide a simple, single-line title that takes less space on smaller phone screens when the DynamicPageHeader is collapsed (snapped). You can enable it with the use of the new snappedTitleOnMobile aggregation.For more information, see the API Reference and the Sample.
Changed•Control•Info Only•1.63
Info Only
2019-02-27
1.63
Changed
Control
sap.f.semantic.SemanticPage
sap.f.semantic.SemanticPage
We have implemented the option to provide a simple, single-line title that takes less space on smaller phone screens when the SemanticPage header is collapsed (snapped). You can enable it with the use of the new titleSnappedOnMobile aggregation.For more information, see the API Reference and the Sample.
Changed•Control•Info Only•1.63
Info Only
2019-02-27
1.63
Changed
Control
sap.m.ObjectNumber / sap.m.ObjectStatus
sap.m.ObjectNumber / sap.m.ObjectStatus
You can now display both controls with a large font size, thus meeting the SAP Fiori Design Guidelines for displaying facets in the ObjectPageHeader. To use the larger font size, add the newly introduced CSS classes to the controls. For more information, see the API Reference (sap.m.ObjectNumber, sap.m.ObjectStatus), and the Samples (sap.m.ObjectNumber, sap.m.ObjectStatus).
Changed•Control•Info Only•1.63
Info Only
2019-02-27
1.63
Changed
Control
sap.m.Select
sap.m.Select
To ensure that the value states are displayed in all situations and devices, the control is now enabled to display the text set in the valueStateText property when the dropdown is opened.For more information, see the Sample.
Changed•Control•Info Only•1.63
Info Only
2019-02-27
1.63
Changed
Control
sap.suite.ui.microchart.BulletMicroChart
sap.suite.ui.microchart.BulletMicroChart
Bullet micro charts can now be used in delta mode with actual values.
Micro charts are now fully responsive and can adapt to a variety of parent container sizes, ranging from 64 px wide by 18 px high up to 320 px wide by 94 px high. This new responsive design allows you to embed micro charts in rows of a grid table (sap.ui.table.Table) and other controls. You can also assign custom tooltips to micro charts using expression binding.
For each micro chart, a smart micro chart is now available that can be bound to OData metadata.
For more information, see the API Reference and the Samples for individual micro charts.
Changed•Control•Info Only•1.63
Info Only
2019-02-27
1.63
Changed
Control
sap.ui.layout.cssgrid.CSSGrid
sap.ui.layout.cssgrid.CSSGrid
You can now set the CSSGrid breakpoints (large, medium, or small) to depend on the size of the parent container rather than the device screen size (media query). To enable the feature, use the new containerQuery property in the GridResponsiveLayout class. For more information, see the API Reference and the Sample.
Changed•Control•Info Only•1.63
Info Only
2019-02-27
1.63
Changed
SAP Fiori Elements
SAP Fiori Elements
SAP Fiori Elements
List Report and Object Page
General features:
You can now enable buttons to toggle between the draft and the saved version of records via a setting in the manifest.json. For more information, see Toggling Between Draft and Saved Values. The standard button to toggle between the active and draft versions of the records in draft-enabled applications (Display Active Version / Continue Editing) has been removed.
You can now add segmented buttons to tables on the object page to provide multiple views in a single table of the object page. For more information, see Adding Segmented Buttons to a Table Toolbar.
Using onBeforeRebindVisualFilterExtension controller you can group visual filter calls in one batch call. For more information, see Visual Filters.
Changed•SAP Fiori Elements•Info Only•1.63
Info Only
2019-02-27
1.63
Changed
Feature
Demo Kit API Reference Tree
Demo Kit API Reference Tree
We have improved the API Reference tree to use proper nesting of the SAPUI5 symbols based on a strict hierarchical structure. Fewer elements are now displayed on the root level, thus improving the user experience and shortening the time the user spends trying to find a specific symbol in the tree structure.