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.61 to 1.62.
Version
Type
Category
Title
Description
Action
Available as of
1.62
New
Control
sap.m.GenericTag
sap.m.GenericTag
The new sap.m.GenericTag control displays complimentary information related to the current page, such as key performance indicators (KPI) and situations.
It consists of four different parts:
A required status indicator with semantic colors (A)
An optional icon that is displayed in the same color as the status indicator (B)
A required text that is truncated automatically (C)
An optional content area that can display either a control of type sap.m.ObjectNumber or a warning icon (D)
The control can move to the overflow area of sap.m.OverflowToolbar.
A card is a user experience design pattern that displays the most concise pieces of information in a limited-space container. It helps users structure their work in an intuitive and dynamic way.
Analytical card
Using cards, you can group information, link additional details, and present a summary. You can also get direct insights without leaving the current screen and choose further navigation options. Each card is designed in a different style and contains various content formats.
The List card is used to display multiple list items of all kinds.
The Analytical card is used for data visualization with various chart types.
Cards can be used by referencing the sap.ui.integration library.
sap.ui.integration.widgets.Card is a self-contained user interface element, connected to a manifest and used as a widget.
OpenUI5 routing now supports navigation to components in addition to the already existing routing to views. You configure the routing in the component’s manifest. Moreover, the target component can also come with its own routing, which integrates via enhanced configuration in the manifest.
The new version of the OpenUI5 OData V4 model introduces the following features:
Bound actions on collections can now be executed using the header context of the sap.ui.model.odata.v4.ODataListBinding. If the returned entity is part of the same entity set, the promise of sap.ui.model.odata.v4.ODataContextBinding#execute can be resolved with a return value context.
sap.ui.model.odata.v4.Context#requestSideEffects was introduced in OpenUI5 1.61 and now resolves side effects in :n navigations reloading only affected properties.
The ## syntax for branching into the MetaModel as described in sap.ui.model.odata.v4.ODataModel#bindProperty is now also available in property bindings.
Non-primitive values are supported in property bindings with binding mode OneTime and target type "any".
The following methods can now be executed while a binding is suspended:
filter, sort, changeParameters, setAggregation, and updateAnalyticalInfo of sap.ui.model.odata.v4.ODataListBinding
changeParameters of sap.ui.model.odata.v4.ODataContextBinding
refresh method of all bindings
When the binding is resumed, a request reflecting all the changes by these methods is triggered.
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. 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 together 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.
The control can now display several items at once. This functionality is implemented through a new customLayout aggregation of type sap.m.CarouselLayout. The sap.m.CarouselLayout defines how many items are displayed in the visible area of the sap.m.Carousel control and has a visiblePagesCount property, which determines the count of items to be displayed.For more information, see the API Reference and the Sample.
Changed•Control•Info Only•1.62
Info Only
2019-01-31
1.62
Changed
Control
sap.m.Column
sap.m.Column
The sortIndicator property now shows a sort icon when a column is sorted. For more information, see the API Reference for the sortIndicator property.
Changed•Control•Info Only•1.62
Info Only
2019-01-31
1.62
Changed
Control
sap.m.ComboBox
sap.m.ComboBox
In order for the ComboBox to be aligned with the rest of the input controls and the already available features, we updated the used list structure of the control from sap.m.SelectList to sap.m.List, and respectively updated the protected API getList. For more information, see the API Reference.
Changed•Control•Info Only•1.62
Info Only
2019-01-31
1.62
Changed
Control
sap.m.ListBase
sap.m.ListBase
You can now use more values for the highlight property. These values are provided by the sap.ui.core.MessageType and sap.ui.core.IndicationColor enumerations. To define a custom semantic for the highlight color, you can use the new highlightText property. For more information, see the API Reference for the highlight property.
Changed•Control•Info Only•1.62
Info Only
2019-01-31
1.62
Changed
Control
sap.m.OverflowToolbar
sap.m.OverflowToolbar
We extended the sap.m.sample.OverflowToolbarSimple sample to demonstrate the behavior of grouped controls. It contains two pairs of grouped controls: Label with Input and Label with Select.For more information, see the Sample.
The sap.m.OverflowToolbar now allows sap.m.GenericTag to move into the overflow area.For more information, see the Sample.
Changed•Control•Info Only•1.62
Info Only
2019-01-31
1.62
Changed
Control
sap.m.SinglePlanningCalendar
sap.m.SinglePlanningCalendar
You can now select or deselect single appointments either by clicking or tapping on the appointment or by using the keyboard arrow keys to navigate to the appointment and then select or deselect it by pressing the space bar or the [Enter] key. You can enter multi-selection mode using key combinations (for example, [Ctrl + click] for Microsoft Windows Operating Systems or [Cmd + click] for Mac Operating Systems).
The sap.m.SinglePlanningCalendar now has a new stickyMode property which allows users to select which toolbars will be fixed while scrolling.
The new information value in the sap.ui.core.ValueState enumeration is now supported by the infoState property of StandardListItem. For more information, see the API Reference.
Changed•Control•Info Only•1.62
Info Only
2019-01-31
1.62
Changed
Control
sap.tnt.SideNavigation
sap.tnt.SideNavigation
We have implemented a selectedKey property of sap.tnt.SideNavigation, with which you can easily set the selected item, when the control is bound to a model. For more information, see the API Reference and the Sample.
Changed•Control•Info Only•1.62
Info Only
2019-01-31
1.62
Changed
Control
sap.ui.core.support.RuleEngineOpaExtension
sap.ui.core.support.RuleEngineOpaExtension
The rule engine OPA extension, which allows Support Assistant checks, has been enhanced with a new assertion. The new getReportAsFileInFormat assertion allows storing past history in window._$files in a preferred format. For more information, see the API Reference and the Sample.
You can now use more values for the highlight property. These values are provided by the sap.ui.core.MessageType and sap.ui.core.IndicationColor enumerations. To define a custom semantic for the highlight color, you can use the new highlightText property. For more information, see the API Reference for the highlight property.
Changed•Control•Info Only•1.62
Info Only
2019-01-31
1.62
Changed
Feature
Demo Kit Improvements
Demo Kit Improvements
Demo Kit Landing Page
We added a block on the welcome page about the UI5 Evolution project. It contains a short description with a link to the interactive documentation page about the project. For more information, see Best Practices for Developers.
We added a live code editor to the Demo Kit welcome page that showcases a simple app. You can edit the code directly and see your changes immediately in the Result area.
Settings Dialog in Samples Section
You can now switch the Content Density of the Demo Kit samples to Condensed.