What's New in SAPUI5 1.73

What's New in SAPUI5 1.73

With this release SAPUI5 is upgraded from version 1.72 to 1.73.

New Controls

sap.f.AvatarGroup (Experimental)

AvatarGroup is used to display a group of related avatars, arranged horizontally. The control allows you to display the avatars in different sizes, depending on your use case. Two group types are available: Group and Individual.

For more information, see the API Reference and the Samples.

Improved Features

Alternatives for the SAPUI5 Tools for Eclipse

As we have announced with SAPUI5 version 1.71, the SAPUI5 Tools for Eclipse are no longer updated. We have removed the corresponding documentation from the SAPUI5 documentation with version 1.73. To find out more about recommended alternatives, please read our blog post: SAPUI5 Tools for Eclipse - Now Is the Time to Look for Alternatives.

Export Functions

The sap.ui.core.util.Export class has been deprecated. To use export functions, sap.ui.export.Spreadsheet is available.

For more information, see Spreadsheet Export, the API Reference, and the Samples.

SAPUI5 OData V4 Model

The new version of the SAPUI5 OData V4 model introduces the following features:

  • Binding of operation parameters as described in OData Operations in the SAPUI5 documentation.

  • Methods for finding bindings that have become public:

    • sap.ui.model.odata.v4.ODataModel#getAllBindings
    • sap.ui.model.Binding#getPath
    • sap.ui.model.Binding#getContext
    • sap.ui.model.Binding#getModel
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. 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 smart controls (sap.ui.comp library) that do not support the SAPUI5 OData V4 model, as well as controls such as TreeTable and AnalyticalTable, which are not supported in combination 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.

For more information, see OData V4 Model, the API Reference, and the Samples.

Improved Controls

sap.f.semantic.SemanticPage

The fitContent property of the sap.f.DynamicPage control is now also exposed in sap.f.semantic.SemanticPage. It's used to optimize the responsiveness and behavior of the control and we recommend using this property when displaying content of adaptive controls that stretch to fill the available space. For more information, see the API Reference.

sap.m.Button

Four new button types were introduced in the sap.m.ButtonType enum. Designed as message triggering buttons, use them to open sap.m.MessagePopover. Each button type has a dedicated meaning.

  • Critical
  • Negative
  • Success
  • Neutral

For more information, see the API Reference.

sap.m.ComboBox, sap.m.MultiComboBox

We have updated the behavior of the showItems method. When the control's picker is opened, the dropdown arrow is not in pressed state, as it was previously. Now, pressing the dropdown arrow for the first time opens the control's picker with all items, and with the second press the picker is closed. For more information, see the API Reference.

sap.m.Dialog

We have enabled responsive padding support. Application developers can now configure sap.m.Dialog and enable its responsive padding in the SAP Fiori 3 themes.

For more information, see Enabling Responsive Paddings According to the Control Width.

sap.m.Input

A change event is now fired when the browser autofill fills an input.

Note

If showValueHelp or showSuggestion are set to true, the native browser autofill will not fire a change event.

For more information, see the API Reference.

sap.m.Label

A visual change was introduced for the sap.m.Label control to align it with SAP Fiori Design Guidelines. The asterisk is now positioned on the right side of the text. For more information, see the API Reference and the Sample.

sap.m.list, sap.m.StandardListItem

The usability of the additional information text and its combination with title and description has been improved for these controls. The information text is no longer truncated if it is shorter than or equal to the character limit predefined by the control. For more information, see the Card Explorer.

sap.m.MessagePopover

We have exposed the groupItems property and navigateBack function as APIs in the control. Using the navigateBack function you can navigate back to the list page, and with the groupItems property you can configure whether or not items should be grouped. For more information, see the API Reference.

sap.m.NotificationListItem, sap.m.NotificationListGroup

We have redesigned the notifications, and now they are lighter, easy to use, and aligned with the SAP Fiori 3 user experience. The changes include:

  • The priority of the notifications is now visualized with a status icon.
  • Action buttons in the sap.m.OverflowToolbar could now be hidden.
  • Collapse/expand functionality of the sap.m.NotificationListGroup is implemented with an arrow button instead of text.
  • For the sap.m.NotificationListGroup, we have enabled an item counter, which represents the count of currently loaded items inside this group. It can be visible or hidden using the new showItemsCounter property.
  • The new authorInitials property is now introduced for sap.m.NotificationListItem. It is visualized as an avatar, and used as a fallback when the authorPicture is not provided. The background color of the avatar is chosen randomly.
For more information, see the API Reference and the Samples.

sap.m.NumericContent

A new adaptiveFontSize property is now introduced to meet different country/locale requirements according to the Unicode Common Locale Data Repository (CLDR). For more information, see the API Reference and CLDR.

sap.m.PlanningCalendar

We have added a new headerId parameter to the rowHeaderClick event, which enables developers to directly access row header by ID.

Note

Do not use this feature for PlanningCalendar’s rowHeader modification.

For more information, see the API Reference.

sap.m.ProgressIndicator

With the new displayAnimation property, you can now determine whether a percentage change is displayed with or without animation. For more information, see the API Reference and the Sample.

sap.ui.comp.SmartField, sap.ui.comp.SmartFilterBar, sap.ui.comp.SmartTable

You can now search for empty strings for dates of type Edm.DateTime, Edm.DateTimeOffset, and StringDate, for example, in the value help or the personalization dialog.

sap.ui.integration.widgets.Card
  • We have improved the support for the relative date ranges. This allows the card developers to use date ranges, such as lastYear or nextQuarter inside the card's manifest. Such automatically calculated date ranges can be used in data requests or other card attributes. For more information, see Integration Card Date Range Handling in the Card Explorer.
  • We have added a new format namespace to hold formatters used in expression bindings, and added a predefined date formatter method to it. For more information, see the Sample in the Card Explorer.
  • The custom HTML element to consume cards on any web page is refactored. Now, height and width are specified in the standard CSS syntax and no longer as separate tag attributes. For more information, see the Sample in the Card Explorer.
sap.ui.layout.cssgrid.ResponsiveColumnLayout

This control now also supports Microsoft Internet Explorer 11, due to the implemented polyfill. For more information, see the API Reference and the Sample.

sap.ui.table.AnalyticalTable, sap.ui.table.Table, sap.ui.table.TreeTable

The navigated property that was introduced in version 1.72 is now also available for these controls (if no row actions are available). The property shows a navigation indicator at the end of a row to indicate that the user has either already navigated to further details or can navigate to further details from the item, depending on the application use case. For more information, see the API Reference and the Sample.

sap.uxap.ObjectPageHeader

With the new objectImageBackgroundColor property, you can now determine the background color of the icon or the image placeholder used in the sap.uxap.ObjectPageHeader. For more information, see the API Reference and the Sample.

sap.uxap.ObjectPageLayout

With the new sectionChange event, you can identify when the page is scrolled to a specific section. The section and subSection event parameters are provided when the event is fired. For more information, see the API Reference.

Demo Kit Improvements

Search Highlighting in Search Results and API Reference Tree

You can now easily find the results you're interested in with the new search highlighting functionality that we implemented for the Search Results page and the API Reference tree filter.