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.36 to 1.38.
Version
Type
Category
Title
Description
Action
Available as of
1.38
Changed
User Documentation
Improved Documentation
Improved Documentation
Thanks a lot to all of you who have used the Demo Kit feedback function! We have received lots of comments, many of which regarding our tutorials, and are continuously improving the documentation based on your findings.
Please carry on giving us your feedback: even though we cannot update the documentation straight away, your feedback will be considered in the next version!
New or reworked documentation chapters that are not mentioned in the following sections:
jQuery has been upgraded to version 2.2.3. This upgrade may have an impact on apps developed with OpenUI5.
Changed•Announcement•Info Only•1.38
Info Only
2016-06-29
1.38
New
Feature
Icon Explorer
Icon Explorer
We have 46 new icons, and some existing icons have been redesigned - check the Icon Explorer in the Demo Kit for details.
New•Feature•Info Only•1.38
Info Only
2016-06-29
1.38
New
Feature
Multiple preprocessors for XML views
Multiple preprocessors for XML views
We have enhanced the XML view so that it is now capable of running more than one preprocessor per hook. Additionally, the new hook viewxml has been introduced. For more information, see Preprocessing XML Views.
New•Feature•Info Only•1.38
Info Only
2016-06-29
1.38
New
Feature
OpenUI5 OData V4 model
OpenUI5 OData V4 model
We are providing an initial version of the OpenUI5 OData V4 Model. This model supports the following:
Read access
Updating properties of OData entities via two-way-binding
Operation (function and action) execution
Grouping data requests in a batch request
Server-side sorting and filtering
Restriction:
This is the first version of the OpenUI5 OData V4 model. Due to its limited feature scope, we recommend you do not use this release to develop applications that are to be used in production systems. Please look at the detailed documentation of the features, as certain parts of a feature may be missing which you might expect as given. While our intention was to be compatible with existing controls, existing controls might not work due to small incompatibilities compared to sap.ui.model.odata.(v2.)ODataModel, or due to missing features in the model. Up to now, only limited tests with controls have been done with the OpenUI5 OData V4 model. The interface for applications has been changed to make usage of the model easier and more efficient. A summary of these changes is documented in the section Changes Compared to OData V2 Model.
The control opens a hierarchical menu and enables quick triggering of the last action of the menu item selected. In Regular mode it always opens the menu, whereas in Split mode it can be also used directly as a button to trigger the currently displayed menu item’s action. In Split mode it can display either the default menu item or the last selected one.
The ObjectMarker control represents the status of an object with icon and/or text. It can be interactive (as a link) or non-interactive. It has the following predefined types:
Flagged
Favorite
Draft
Locked
Unsaved
An object might have multiple ObjectMarkers at the same time but the editing states (Locked, Draft, and Unsaved) are mutually exclusive.
sap.m.RangeSlider is a new input control that is used to select a range of values. The RangeSlider has two slider handles that can be moved along a predefined numerical range scale. This control extends the sap.m.Slider and introduces additional functionality.
New•Control•Info Only•1.38
Info Only
2016-06-29
1.38
New
Control
sap.m.StepInput
sap.m.StepInput
The StepInput control allows the user to change the input value with a predefined step. The value can be changed using the increment/decrement buttons or keys on the keyboard. On the desktop, when using the keyboard [PgUp] and [PgDn] keys, the value increases/decreases two steps at a time.
sap.ui.layout.ResponsiveSplitter is a layout control that is used to visually divide the content of its parent. The control is responsive and can adjust its contents to any screen size. On smaller screens, pagination is used to allow navigation to all splitter panes.
The Press and EnterText actions now support a larger number of controls and can now be executed on embedded controls by specifying the control suffix. For more information, see the API Reference for Press and EnterText and the Sample.
Changed•Feature•Info Only•1.38
Info Only
2016-06-29
1.38
Changed
Control
sap.m.ComboBox
sap.m.ComboBox
Is now supported on mobile phones. The list of available values will open as a full-screen dialog on small devices.
The new loadItem event makes it possible to defer initialization of items in the ComboBox dropdown list control to a point in time when the items are required. This helps to improve performance.
The GenericTile control has a new responsive design that significantly improves the user experience, it has also been optimized for larger smartphones. The GenericTile adjusts its size to fit all the different display sizes of the current devices supported by OpenUI5 (see Browser and Platform Support). The main changes are the tile size, font size, padding, the new ImageContent control, and new samples showing the variety of use cases for the GenericTile.
The sap.m.ImageContent control can be used to include images in a tile. It can be embedded in the content area of the GenericTile control.
The new keyboardMode property for the List and Table controls determines the keyboard handling for these controls. The Navigation value of the property enables a mode that allows you to navigate within a large number of items, for example, table cells, using the tab key, whereas the Edit mode can be used to edit a limited number of items.
Changed•Control•Info Only•1.38
Info Only
2016-06-29
1.38
Changed
Control
sap.m.MaskInput
sap.m.MaskInput
You can now use escape characters in the MaskInput definition to be able to use the predefined rule characters as immutable ones.
Changed•Control•Info Only•1.38
Info Only
2016-06-29
1.38
Changed
Control
sap.m.MessagePopover
sap.m.MessagePopover
sap.m.MessagePopover has been improved and can now be resized. Resizing is only possible when the MessagePopover is opened from the footer on a desktop.
Changed•Control•Info Only•1.38
Info Only
2016-06-29
1.38
Changed
Control
sap.m.NotificationListItem
sap.m.NotificationListItem
The control has two improvements:
The control responsiveness is updated for better usability on large screens (more than 640 pixels width) – the buttons are now located on the right side of the text.
The Show More button for toggling expand/collapse mode can now be hidden with the use of the new property hideShowMoreButton.
sap.m.Popover has four new values for its PlacementType:
PreferredBottomOrFlip
PreferredLeftOrFlip
PreferredRightOrFlip
PreferredTopOrFlip
They determine the preferred position of the Popover and how it behaves when there is insufficient space for it on the screen. These properties allow the Popover to flip over and cover some of the content below it.
To upload a new version of a file to the UploadCollection list, the openFileDialog method is available. You can provide a pushbutton in the header area and if one entry in the UploadCollection list is selected, the API method will be called.
The ViewSettingsDialog control now gives you the opportunity to modify filter detail page items on the fly with the help of the new event filterDetailPageOpened. This event is fired each time after the filter detail page is accessed, notifying the outside world that the page is loaded along with the information for which filter the respective details are displayed. This allows a handler to be attached that alters the filter detail items aggregation.
sap.ui.commons.ColorPicker supports HSL (Hue Saturation and Lightness) mode. This mode works better with modern browsers and it does not require intermediate conversion back to RGB. Additionally, there is a new input field for the alpha (transparency) value for more precise color definition.
Changed•Control•Info Only•1.38
Info Only
2016-06-29
1.38
Changed
Control
sap.ui.layout.Form / sap.ui.layout.SimpleForm
sap.ui.layout.Form / sap.ui.layout.SimpleForm
You can now add a toolbar to a form container or the form itself.
sap.ui.table.TreeTable now supports AutoExpand paging if it is bound to an OData model.
By setting numberOfExpandedLevels as a binding parameter (e.g. in the bindRows call of the TreeTable), you now can specify the initial expansion depth. This feature is only available for OData services exposing a property marked with the annotation hierarchy-node-descendant-count-for. This also means the service has to respect a $filter statement on the annotated Level property, and returns the entries sorted. You can find the specification for this and all other hierarchy annotations in the SAP Community Network under SAP Annotations for OData Version 2.0.
Changed•Control•Info Only•1.38
Info Only
2016-06-29
1.38
Changed
Control
sap.ui.unified.Menu
sap.ui.unified.Menu
To significantly increase the usability of sap.ui.unified.Menu, a delay has been added to the closing of submenus.
ObjectPageHeader can be integrated with the SideContent scenario. A new sideContentButton aggregation has been added. This aggregation has a new button, which appears after the actions buttons and triggers opening the side content for additional information.
It supports scrolling to a particular section, based on its ID. This allows easier access to all parts of the application and consistent navigation back to a previous position within the ObjectPage.
Performance is improved for the use case with no Blocks. The ObjectPage now supports lazy loading with the stashed property of the ObjectPageLazyLoader. As a result, you avoid the additional creation of XML views for each Block.
