What's New in SAPUI5 1.64

With this release SAPUI5 is upgraded from version 1.63 to 1.64.

Version

Type

Category

Title

Description

Action

Available as of

1.64

New

Control

sap.f.Card

The new sap.f.Card control complies with the visual design of the Integration Card (sap.ui.integration.widgets.Card). In contrast to the Integration Card, sap.f.Card provides more freedom in choosing the structure and the controls you can include, so that you can compose the card content area according to your needs. It enables you to decide and compose the card content area according to your needs.

The sap.f.Card consists of three elements: a container with background color and rounded corners, a header, and content areas.

For more information, see Cards, the API Reference and the Sample.

_{New•Control•Info Only•1.64}

Info Only

2019-03-28

1.64

New

Feature

Rule Builder: AST based DMN SFEEL

The rule builder now supports a new expression language: AST based DMN SFEEL. DMN SFEEL is an improvised approach to modeling business decision logic. It can be used both in text rules as well as in decision tables.

For more information, see Rule Builder Control Tutorial.

_{New•Feature•Info Only•1.64}

Info Only

2019-03-28

1.64

Changed

Feature

Key User Adaptation: Restricting Adaptation for Certain Controls

It is now possible to exclude certain controls from key user adaptation (formerly known as UI adaptation at runtime) by adding instance-specific design time metadata:

not-removable prevents controls from being removed.
not-adaptable prevents controls from being changed.

For more information, see SAPUI5 Flexibility: Enable Your App for UI Adaptation.

_{Changed•Feature•Info Only•1.64}

Info Only

2019-03-28

1.64

Changed

Feature

SAPUI5 Flexibility: New flexEnabled Flag

The flexEnabled flag in the sap.ui5 section of the manifest.json indicates whether the application supports key user adaptation and developer adaptation. If you set the flag, it's also possible to check via SAP Web IDE if your control IDs are stable.

For more information, see SAPUI5 Flexibility: Enable Your App for UI Adaptation.

_{Changed•Feature•Info Only•1.64}

Info Only

2019-03-28

1.64

Changed

Feature

SAPUI5 Flexibility: Simplified Terminology

We have improved and simplified the terminology for certain core terms in the area of SAPUI5 flexibility. Here's what has changed:

Old	New	Explanation
SAPUI5 flexibility services	SAPUI5 flexibility	Collection of features that allow upgrade-safe and modification-free UI changes of SAPUI5 apps on different levels
UI adaptation at runtime (RTA)	key user adaptation	Key users (business experts with special permissions) can adapt the UI of an SAPUI5 app that is running in the SAP Fiori launchpad for other users by means of intuitive WYSIWYG functions.
UI adaptation at design time (DTA)	developer adaptation	Developers can adapt SAPUI5 apps via the SAPUI5 Visual Editor in SAP Web IDE.

For more information on the features of SAPUI5 flexibility, see SAPUI5 Flexibility: Adapting UIs Made Easy.

_{Changed•Feature•Info Only•1.64}

Info Only

2019-03-28

1.64

Changed

Feature

SAPUI5 OData V4 Model

With the new version of the SAPUI5 OData V4 model, the number of decimal places of entered numbers is checked against the unit or the currency customizing when using the sap.ui.model.odata.type.Unit and sap.ui.model.odata.type.Currency types that were introduced with SAPUI5 1.63.

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.

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

_{Changed•Feature•Info Only•1.64}

Info Only

2019-03-28

1.64

Changed

Control

sap.f.DynamicPage

We have redesigned the content area of the DynamicPageTitle control so that the width of the expandedContent and snappedContent aggregations no longer depends on the width of the heading aggregation. Both expandedContent and snappedContent aggregations can now take the whole width of the DynamicPageTitle and are displayed below the heading and content areas.For more information, see the Sample.

_{Changed•Control•Info Only•1.64}

Info Only

2019-03-28

1.64

Changed

Control

sap.f.ShellBar (Experimental)

We have implemented an additional element that visualizes the number of notifications for the app (notificationsNumber property). It is displayed at the top right corner of the notifications button. When the resize breakpoint is hit and the notifications button enters the overflow area of the OverflowToolbar, the element is displayed at the top right corner of both the OverflowToolbarButton and the overflow area notification button.

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

_{Changed•Control•Info Only•1.64}

Info Only

2019-03-28

1.64

Changed

Control

sap.m.ComboBox

We have introduced grouping in the suggestions list of sap.m.ComboBox. This feature allows you to group items by certain characteristics, and to display a header. New group can be created in two ways:

If data binding is used, grouping is defined on the sorter in data binding.
Alternatively, you can add a group header programmatically as an instance of sap.ui.core.SeparatorItem with a text property by adding it to the items aggregation of the sap.m.ComboBox control. This transforms the sap.ui.core.SeparatorItem internally to sap.m.GroupHeaderListItem, and uses the text value as the header of the group.

In case a sap.ui.core.SeparatorItem without a defined text property is inserted in the aggregation items, the ComboBox will display only a horizontal separator without any text.For more information, see the API Reference and the Sample.

_{Changed•Control•Info Only•1.64}

Info Only

2019-03-28

1.64

Changed

Control

sap.m.DatePicker

With the new isValidValue function, you can receive information on the validity of the latest value provided in sap.m.DatePicker, not only on change but at any time, so that you can act upon an incorrectly entered date.For more information, see the API Reference and the Sample.

_{Changed•Control•Info Only•1.64}

Info Only

2019-03-28

1.64

Changed

Control

sap.m.Input / sap.m.ComboBoxBase (Experimental)

We have introduced a new experimental method showItems(fnFilter). It enables you to open a popup with suggestion items for the sap.m.Input, sap.m.ComboBox, and sap.m.MultiComboBox controls, and to filter the available items based on custom criteria.For more information, see the API Reference (sap.m.Input, sap.m.ComboBoxBase).

_{Changed•Control•Info Only•1.64}

Info Only

2019-03-28

1.64

Changed

Control

sap.m.Input / sap.m.MultiInput

We have introduced grouping for the suggestions of sap.m.Input and sap.m.MultiInput. This feature allows you to easily group items visually by separating the different groups via a distinguishable group header item. The functionality is available for inputs that use list suggestions and table suggestions.For more information, see the samples ( sap.m.Input, sap.m.MultiInput).

_{Changed•Control•Info Only•1.64}

Info Only

2019-03-28

1.64

Changed

Control

sap.m.SinglePlanningCalendar

We have introduced a new all-day logic that checks whether an appointment starts at 00:00 and ends at 00:00 on any day in the future.
We have introduced a cozy form factor, which provides larger interactive user interface elements. This facilitates your work with the control on mobile devices.

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

_{Changed•Control•Info Only•1.64}

Info Only

2019-03-28

1.64

Changed

Control

sap.ui.integration.widgets.Card

We have introduced a new Object card type, which displays the basic details for an object, such as a person or a sales order.For more information, see Cards and the Sample.
We have introduced a new Timeline card type, which displays time-related content.For more information, see Cards and the Sample.

_{Changed•Control•Info Only•1.64}

Info Only

2019-03-28

1.64

Changed

Control

sap.uxap.ObjectPageLayout

We have implemented the option to provide a simple, single-line title that takes up less space on smaller phone screens when the dynamic header of the ObjectPageLayout control is collapsed (snapped). You can enable it via the snappedTitleOnMobile aggregation.For more information, see the API Reference and the Sample.

_{Changed•Control•Info Only•1.64}

Info Only

2019-03-28

1.64

Changed

SAP Fiori Elements

SAP Fiori Elements

Analytical List Page

You can pass the variant ID as a URL parameter while navigating from an application to the analytical list page. For more information, see Managing Variants.

_{Changed•SAP Fiori Elements•Info Only•1.64}

Info Only

2019-03-28

1.64

Changed

Feature

Demo Kit API Reference

The API Reference documentation for non-class entities now displays the @see and @example tags of their JSDocs.For a preview of an @see tag, see the sap.ui.core.LabelEnablement namespace. For a preview of an @example tag, see the sap/base/util/merge function.
Based on your feedback, we have improved the API Reference documentation to include the borrowed Properties, Aggregations, and Associations in the respective sections. All the inherited entries are marked with a Borrowed from: label in the Description column with a link to the corresponding class.