What's New in SAPUI5 1.98

With this release SAPUI5 is upgraded from version 1.97 to 1.98.

Version	Type	Category	Title	Description	Action	Available as of
1.98	Changed	Feature	SAPUI5 OData V2 Model	SAPUI5 OData V2 Model The new version of the SAPUI5 OData V2 model introduces the following features: The `sap.ui.model.odata.v2.ODataListBinding#create` method, which allows to create transient entries in a list binding similar to its counterpart in the OData V4 model. For more information, see Creating Entities. You can now create inactive contexts using `sap.ui.model.odata.v2.ODataListBinding#create`. There is no POST request for an inactive context. The context will become active as soon as any of its properties is changed. Once this happens, the `createActivate` event is raised, enabling the application to create a new inactive context. Inactive contexts do not influence `sap.ui.model.odata.v2.ODataListBinding#getCount`. They are neither pending changes nor are they reset by `sap.ui.model.odata.v2.ODataModel#resetChanges`. For more information, see Creating Entities. The `getAllCurrentContexts` method for list bindings returns all current contexts without raising a request.For more information, see `sap.ui.model.ListBinding#getAllCurrentContexts`. _{Changed•Feature•Info Only•1.98}	Info Only	2022-01-27
1.98	UI Changed	Announcement	Chart Personalization Dialog Updated	Chart Personalization Dialog Updated Note: The following information concerns important changes for end users. These changes may require end users to adjust and/or test cases to be adapted, but they won't stop or disrupt software or processes. We have improved the dialog based on UX research. The panel for the dimension and measure selection has been updated and the option to select a chart type has been removed from the dialog. The switch is now available from the Chart toolbar. _{UI Changed•Announcement•Info Only•1.98}	Info Only	2022-01-27
1.98	UI Changed	Announcement	Draft-Enabled Apps (OData V2): Draft Toggle Button Moved	Draft-Enabled Apps (OData V2): Draft Toggle Button Moved Note: The following information concerns important changes for end users. These changes may require end users to adjust and/or test cases to be adapted, but they won't stop or disrupt software or processes. In draft-enabled list reports and object pages, the Hide/Show Draft Values toggle button has been removed from the toolbar. The option to hide or show draft values can now be found in the Editing Status dropdown list. For more information, see Toggling Between Draft and Saved Values. _{UI Changed•Announcement•Info Only•1.98}	Info Only	2022-01-27
1.98	Changed	Feature	SAPUI5 OData V4 Model	SAPUI5 OData V4 Model The new version of the SAPUI5 OData V4 model introduces the following features: You can now replace a row context of a list with a sibling entity of the same collection. The sibling entity must be available as a :1 navigation property and is accessed with an operation binding. For more information, see Draft Handling with the OData V4 Model. An application can now create inactive contexts in a list binding using the `bInactive` parameter of `sap.ui.model.odata.v4.ODataListBinding#create`, provided the update group of the binding is an `Auto` group. There is no POST request for an inactive context. The context will become active as soon as any of its properties is changed. Once this happens, the `createActivate` event is raised, enabling the application to create a new inactive context. Inactive contexts do not influence `sap.ui.model.odata.v4.ODataListBinding#getCount`. They are neither pending changes nor are they reset by `sap.ui.model.odata.v4.ODataListBinding#resetChanges` or `sap.ui.model.odata.v4.ODataModel#resetChanges`. For more information, see Creating an Entity. The `sap.ui.model.odata.v4.ODataListBinding#getAllCurrentContexts` method returns all current contexts without raising a request. The experimental `sap.ui.model.odata.v4.ODataContextBinding#moveEntityTo` method introduced with SAPUI5 1.95 is deprecated. _{Changed•Feature•Info Only•1.98}	Info Only	2022-01-27
1.98	Changed	Control	`sap.m.DateTimePicker`, `sap.m.TimePicker`	`sap.m.DateTimePicker`, `sap.m.TimePicker` We have introduced a shortcut button that focuses the current time. The button is shown if the new `showCurrentTimeButton` property is set to true. For more information, see the API Reference and the Sample. _{Changed•Control•Info Only•1.98}	Info Only	2022-01-27
1.98	Changed	Control	`sap.m.DynamicDateRange` (Experimental)	`sap.m.DynamicDateRange` (Experimental) When the user types something in the input field of the control, the displayed suggestion items now appear in groups if the `enableGroupHeaders` property is set to `true`. We have added new standard options to the control that represent the first or the last day of the current week, month, quarter, or year. The `StandardDynamicDateRangeKeys` is now an enumeration with keys matching the values. The default value of the `DynamicDateRange` control’s `options` property is now a full array of the keys (before it was an empty array). For more information, see the API Reference and the Samples. _{Changed•Control•Info Only•1.98}	Info Only	2022-01-27
1.98	Changed	Control	`sap.m.IconTabBar`	`sap.m.IconTabBar` There is a change in the way how the control computes and displays the number of tabs that are in the overflow buttons at both sides of the tabs area, when the property overflow mode is set to `StartAndEnd`. Now, only the top-level tabs are counted and not the nested sub-tabs. For more information, see the API Reference and the Sample. _{Changed•Control•Info Only•1.98}	Info Only	2022-01-27
1.98	Changed	Control	`sap.m.Label`	`sap.m.Label` We have introduced a new `showColon` property. If set to `true`, a colon (:) character is added to the label. This feature is useful in cases when the Label is used independently. In contrast, when the Label is in a Form or in a Simple Form, the colon (:) character is displayed automatically regardless of the value of the `showColon` property. For more information, see the API Reference. _{Changed•Control•Info Only•1.98}	Info Only	2022-01-27
1.98	Changed	Control	`sap.m.List`	`sap.m.List` You can now display an avatar in your list instead of an image or icon. We have integrated the `sap.m.Avatar` control as an aggregation of `StandardListItem`. For more information, see the API Reference and the Sample. _{Changed•Control•Info Only•1.98}	Info Only	2022-01-27
1.98	Changed	Control	*`sap.m.p13n`**	*`sap.m.p13n`** We have made personalization within a table or list more reusable. Different panels with reusable content for the various types of personalization are now available for freestyle use in your application. The following panels are available (as experimental APIs): `sap.m.p13n.SelectionPanel` Defines a number of properties that allow you to select and deselect fields as columns in your table, for example, and to change their order. `sap.m.p13n.SortPanel` Defines a number of properties that allow you to sort your items based on various criteria, for example, in ascending or descending order. `sap.m.p13n.GroupPanel` Defines a number of properties that allow you to group your data. The panels are aggregated to `sap.m.p13n.Popup` (experimental), which serves as a container for all the panels. For more information, see the API Reference and the Sample. _{Changed•Control•Info Only•1.98}	Info Only	2022-01-27
1.98	Changed	Control	`sap.m.SinglePlanningCalendar`	`sap.m.SinglePlanningCalendar` With the new `firstDayOfWeek` property, you can now set the first day of a week displayed in the Week and Month views of the control. If there is no valid value set, the default from the user locale is used. For more information, see the API Reference and the Sample. _{Changed•Control•Info Only•1.98}	Info Only	2022-01-27
1.98	Changed	Control	`sap.m.upload.UploadSet`	`sap.m.upload.UploadSet` For the `uploadCompleted` event, an additional JSON response object is now passed. Along with it, some of its parameters are also passed such as response, `responseXML`, `readyState`, status, and headers. It helps you to understand if the upload is complete. _{Changed•Control•Info Only•1.98}	Info Only	2022-01-27
1.98	Changed	Control	`sap.ui.comp.smartchart.SmartChart`	`sap.ui.comp.smartchart.SmartChart` We have improved and simplified the usability of the View Settings dialog for the `SmartChart` control and made it more consistent with the personalization dialogs for the other smart controls. The following changes have been made: The dialog now shows the data visualized based on fields and layout options (formerly called "roles") in a table that is grouped by dimensions and measures (formerly called "type"). You can now select the chart type in the toolbar only. The selected fields are shown automatically. The dialog now automatically provides layout options that are compatible with the selected chart type. You can select new dimensions or measures in an additional row. For more information, see the Sample. _{Changed•Control•Info Only•1.98}	Info Only	2022-01-27
1.98	Changed	Control	`sap.ui.comp.smartfilterbar.SmartFilterBar` and `sap.ui.comp.smartfield.SmartField`	`sap.ui.comp.smartfilterbar.SmartFilterBar` and `sap.ui.comp.smartfield.SmartField` `SmartFilterBar` and `SmartField` now support the `com.sap.vocabularies.UI.v1.PresentationVariant.SortOrder` annotation for value lists with fixed values. This allows you to overwrite the backend sorting. For more information, see the API Reference and the Sample for `SmartFilterBar`, the API Reference, and the Sample for `SmartField`. _{Changed•Control•Info Only•1.98}	Info Only	2022-01-27
1.98	Changed	Control	`sap.ui.comp.smartfilterbar.SmartFilterBar`	`sap.ui.comp.smartfilterbar.SmartFilterBar` Until now, `SmartFilterBar` was using `sap.m.DatePicker` for single date filters that use the `Edm.DateTime` OData type with the `sap:display-format="Date"` annotation, and `Edm.String` OData type with the `sap:filter-restriction="single-value"` annotation. Now, the control supports the new `sap.m.DynamicDateRange` control for single date filters. This allows you to store semantic dates and restore them later when navigating or selecting a variant. In addition, we've adopted new single date options such as the first day of the current week, last day of the current week, first day of the current month, etc. `SmartFilterBar` now also supports the option to set a default operator for date range and single date controls. With this improvement, we’ve made it a lot easier to change the default operator in the XML view via control configuration. Note that this method is not applicable for operators that need a parameter, for example 'Next X Days' where X is the required parameter. For more information, see the Sample. _{Changed•Control•Info Only•1.98}	Info Only	2022-01-27
1.98	Changed	Control	`sap.ui.comp.valuehelpdialog.ValueHelpDialog`	`sap.ui.comp.valuehelpdialog.ValueHelpDialog` After introducing the visualization of multiple consecutive whitespace characters in the `SmartField` and `SmartFilterBar` controls in versions 1.96 and 1.97 respectively, we've now added this feature to the `ValueHelpDialog` control as well. _{Changed•Control•Info Only•1.98}	Info Only	2022-01-27
1.98	Changed	Control	`sap.ui.integration.widgets.Card`	`sap.ui.integration.widgets.Card` We have introduced a new filter type – Search (experimental). To define it, you only have to set the filter's `type` property to `Search`, and then specify the optional initial value of the filter and the placeholder of the field. For more information, see the Search Filter section and the Sample in the Card Explorer. Integration cards now support (experimentally) CSRF tokens as a method to prevent CSRF attacks. For more information, see the CSRF Tokens section and the Sample in the Card Explorer. The submit action of the Adaptive card supports binding syntax. This allows card developers to map the values entered by the end user to the payload structure expected by the back-end service. For more information, see the Action Handlers section and the Sample in the Card Explorer. We have added support for more HTTP request methods. Together with GET and POST, Integration cards now also support PUT, PATCH, DELETE, OPTIONS, and HEAD methods. For more information, see the Data Handling section in the Card Explorer. Object cards are (experimentally) enhanced with new item types and a new attribute. The new item types are `NumericData`, which shows some KPIs, and `Status`. The new attribute is `maxLines` - it represents the maximum number of lines the text can take. For more information, see the Object Card section, the To Do Card sample, and Additional Object Details sample in the Card Explorer. We have updated the `sap.ui.integration.widgets.Card` of type Adaptive with the new 1.01 version of UI5 Web Components. For more information, see the Adaptive Card section in the Card Explorer. We have updated the `sap.ui.integration.widgets.Card` of type Adaptive to support the newest templating and markdown features available for Microsoft Adaptive Cards, by getting the latest versions of `adaptivecards-templating`, `adaptive-expressions`, and `markdown-it`. Due to changes in the templating syntax, developers should adapt their applications when they switch to version 1.98. For more information, see the Adaptive Card section and the Templating and Markdown Samples in the Card Explorer. _{Changed•Control•Info Only•1.98}	Info Only	2022-01-27
1.98	Changed	Control	`sap.ui.richtexteditor.RichTextEditor`	`sap.ui.richtexteditor.RichTextEditor` We have updated the TinyMCE version 5 used in `sap.ui.richtexteditor.RichTextEditor` to TinyMCE 5.10.2. We recommend switching to the newer version, as v4 is no longer supported by TinyMCE and will not receive updates. For more information, see sap.ui.richtexteditor and the Samples. _{Changed•Control•Info Only•1.98}	Info Only	2022-01-27
1.98	Deprecated	Control	`sap.f.IllustratedMessage` / `sap.m.IllustratedMessage`	`sap.f.IllustratedMessage` / `sap.m.IllustratedMessage` The `sap.f.IllustratedMessage` and its related classes are now moved to the `sap.m` library. The `sap.f` classes and their documentation are kept for compatibility reasons and are marked as deprecated. All of them extend their `sap.m` version.For more information, see the API Reference. _{Deprecated•Control•Info Only•1.98}	Info Only	2022-01-27
1.98	Deprecated	Control	*`sap.m.P13n`**	*`sap.m.P13n`** The following entities have been deprecated and replaced with the new personalization panels: `sap.m.P13nDialog` `sap.m.P13nColumnsPanel` `sap.m.P13nSortPanel` `sap.m.P13nGroupPanel` _{Deprecated•Control•Info Only•1.98}	Info Only	2022-01-27
1.98	Changed	SAP Fiori Elements	SAP Fiori elements for OData V2	SAP Fiori elements for OData V2 The following changes and new features are available for SAP Fiori elements for OData V2: Keyboard shortcuts for standard actions such as create, delete, edit, etc., can now get redirected to extension actions that replace the standard action. For more information, see Keyboard Shortcuts. An additional filter option, All (Hiding Drafts), is now available for the Editing Status filter field, for all draft applications. It replaces the draft toggle button in the list report table toolbar. Also, with this change, the draft toggle feature is available by default in draft-enabled applications. For more information, see Toggling Between Draft and Saved Values. It’s now possible to mass edit records in the list report page using the Edit dialog. For more information, see Enabling Editing Using a Dialog (Mass Edit) in the List Report. You now have an option to navigate from the list report to an object page directly in edit mode. For more information, see Navigation to an Object Page in Edit Mode. A validation of required fields is now possible before the object create request for non-draft objects. For more information, see Validation of Required Fields in Non-draft Applications. The visual filter section in the Adapt Filter dialog now supports dropdown-based filtering. The visual filters are now filtered based on the selection made, such as: Visible, Active, Mandatory, etc. The visual filters now display the text associated with the units such as currency or unit of measures. For more information, see Visual Filters. _{Changed•SAP Fiori Elements•Info Only•1.98}	Info Only	2022-01-27
1.98	Changed	SAP Fiori Elements	SAP Fiori elements for OData V4	SAP Fiori elements for OData V4 The following changes and new features are available for SAP Fiori elements for OData V4: The `FilterBar` building block now supports default values and custom filters. For more information, see Building Blocks. SAP Fiori elements now enables you to navigate to a different internal target. For more information, see Example: Enable Internal Navigation to Different Detail Page. Users can now navigate to an app by clicking on the header of a KPI card. For more information, see Creating Key Performance Indicator Tags. Optimizations for the automatic column width calculation in tables are available for the `FieldGroup` and `Date`, both in display and edit mode. For more information, see Setting the Default Column Width. SAP Fiori elements now supports restrictions for the MIME type and file size for `Edm.Stream` properties. For more information, see Different Representations of a Field. _{Changed•SAP Fiori Elements•Info Only•1.98}	Info Only	2022-01-27