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.75 to 1.76.
Version
Type
Category
Title
Description
Action
Available as of
1.76
New
Feature
Team Calendar
Team Calendar
We have added a new demo application - the Team Calendar. It demonstrates the integration between sap.m.PlanningCalendar and sap.m.SinglePlanningCalendar controls, sharing the same data source. The Team Calendar can be used as a starting point for building a fully functional complex application. Find it in the Demo Apps.
New•Feature•Info Only•1.76
Info Only
2020-03-26
1.76
Changed
Feature
Card Explorer
Card Explorer
The Component card sample in the Explore section has been enhanced. To facilitate developers, we have added the option to download the bundle of all the files in the sample.
All the properties in the Learn section are now listed with their Since attribute. This will inform developers since which version each feature is available.
The new version of the OpenUI5 OData V2 model introduces the following features:
A new transitionMessagesOnly binding parameter is provided for the sap.ui.model.odata.v2.ODataListBinding class.
The updateAggregatedMessages parameter of sap.ui.model.odata.v2.ODataModel#read is now public.
Existing server messages can be retrieved from the model using the sap.ui.model.Context#getMessages method.
Changed•Feature•Info Only•1.76
Info Only
2020-03-26
1.76
Changed
Feature
OpenUI5 OData V4 Model
OpenUI5 OData V4 Model
The new version of the OpenUI5 OData V4 model introduces the following features:
You can now access the binding parameter of an operation, as described in OData Operations.
A property path provided to sap.ui.model.odata.v4.Context#requestSideEffects can be given the suffix "*" to enforce re-reading of all properties of the related entity.
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.
With the new autoFocus property, we’ve introduced the possibility to enable/disable the autofocus functionality of the FlexibleColumnLayout control.For more information, see the API Reference and the Sample.
We’ve introduced the columnResize event, which is fired when the resizing of each column of the control is complete.For more information, see the API Reference.
Changed•Control•Info Only•1.76
Info Only
2020-03-26
1.76
Changed
Control
sap.m.FacetFilter
sap.m.FacetFilter
Optimization regarding the initial database service query has been introduced. There are cases when the items aggregation for the FacetFilterList could take a long time fetching data from the database service. Now we have added а search event, that fires when the FacetFilterList is opened. This enables developers to register a handler function to prevent the default filtering behavior by calling the sap.ui.base.Event.prototype.preventDefault function. As a result, no list items are loaded initially. In this case, the developers have to define the filtering behavior at the application level inside the search event handler function. For more information, see the API Reference and the Samples.
Changed•Control•Info Only•1.76
Info Only
2020-03-26
1.76
Changed
Control
sap.m.List, sap.m.Table, sap.m.Tree
sap.m.List, sap.m.Table, sap.m.Tree
New indication colors are now available (provided by the sap.ui.core.IndicationColor enumeration) that can be used for highlighting table rows. For more information, see the API Reference.
Changed•Control•Info Only•1.76
Info Only
2020-03-26
1.76
Changed
Control
sap.m.plugins.DataStateIndicator
sap.m.plugins.DataStateIndicator
We made some improvements to this plugin class and the messages shown for the data state:
A new refresh function of the messages for each data state is available that re-evaluates the filter and then refreshes the message strip based on that information.
The filter property that is defined by the application can now also take the related control into account, along with the message, using the respective parameters.
An automatic pop-in mode has been enabled for the responsive table. For more information, see the API Reference for the related method, the API Reference for the related properties, and the Sample.
Changed•Control•Info Only•1.76
Info Only
2020-03-26
1.76
Changed
Control
sap.ui.integration.widgets.Card
sap.ui.integration.widgets.Card
We have added a type property for the configuration parameters inside a card. This property defines the data type of the parameter. Currently the type property is used only in UI adaptation at design time. For more information, see the Manifest Parameters section in the Card Explorer.
We have added support for the destinations to be resolved by the host environment. In the manifest, the card developer indicates the name of the destination and the request, which depends on this destination. On the host environment side, the host application developer creates a method that resolves the given destination name to a URL. For more information, see Destinations in the Card Explorer.
We have introduced optional application-level Host Actions that interact with the host environment. These specific actions are displayed by the card and processed back in the host environment. For example, sharing or removing a card. For more information, see Host Actions in the Card Explorer.
A new JsonDateTime parser is now used to properly parse dates. Some DateTime values may appear in JSON files as DateTime Wire format strings like /Date(700000+0500)/. The parser automatically splits the date string into parts, taking into account the time zone offset if present, and returns a valid date object. For more information, see DateTime Wire Format.
New indication colors are now available (provided by the sap.ui.core.IndicationColor enumeration) that can be used for highlighting table rows. For more information, see the API Reference.
The resizing of columns has been changed to improve the usability on tablet devices.
We have enabled custom colors to be used with the specialDates aggregation in sap.m.PlanningCalendar, sap.m.SinglePlanningCalendar, and sap.ui.unified.Calendar controls. This enhancement harmonizes with the legend aggregation where custom colors were already available. It is implemented with the new color property of type sap.ui.core.CSSColor in the sap.ui.unified.DateTypeRange control. For more information, see the API Reference and the Samples.