Neptune DXP 23.10.0000 Changelog

All launchpad navigation now relies on semantic objects. This implementation allows Neptune to manage browser history navigation effectively. Functions such as window.history.back and window.history.go work seamlessly within Neptune DXP. Additionally, Neptune handles browser history navigation within Fiori applications by focusing on Neptune-specific semantic objects. Custom semantic objects are no longer supported, and Neptune DXP semantic objects are limited to four categories:

The handling of multi-user logon, logoff, and lock has been made more intuitive in Neptune DXP 23. Users can now easily navigate these options. The pincode screen provides the following information and actions:

The inactivity timeout has been tweaked to begin on the last user activity, instead of when the launchpad, PWA, or mobile client is suspended.

All the launchpad event handlers known from the sap.n.Shell object can now be used in standalone applications where they are relevant. The shell functionality has been integrated into the global Neptune object. Therefore, you should use neptune.Shell.attachInit and neptune.Shell.attachBeforeDisplay, among others, in the future.

Neptune Launchpad has improved its compliance with Web Content Accessibility Guidelines (WCAG) 2.1 A&AA.

Dynamic tiles request new content from the server at specified intervals defined in each tile’s configuration. To reduce system load, backend ABAP handler methods should be lightweight. In case the load from dynamic content becomes excessive, it is now possible to halt all requests.

When using the API_TILE_INFO method in class /NEPTUNE/CL_NAD_SERVER to send dynamic data to the frontend, you can pass a timestamp along with the new dynamic data. When the frontend requests dynamic data again, the timestamp is sent back to the server in the Ajax call. This enables you to check if the frontend requires new data and, if not, you can inform the frontend that no update is needed.

For open applications represented by an icon in the launchpad header, the hover menu has been removed. Instead, a proper ARIA label has been added to the open app header icons for improved compatibility with touch devices.

Much of the jQuery code in the Neptune Launchpad has been replaced with vanilla JavaScript for modernization.

The Neptune-generated getCache and setCache model functions now return a Promise, allowing you to chain calls and ensure that cached data has been read before accessing it.

Open app items have been optimized to fit better into standard UI5 controls. Borders have been adjusted to match the color scheme of other launchpad elements. The open app items have the same height as the application header, and the open/close item at the bottom matches an application footer’s height.

The normal desktop launchpad logon screen is a Neptune-specific adaptation of the SAP Basic Login screen created by CL_ICF_BASIC_LOGIN`. Neptune has created the page so that it matches the login screen found in Neptune PWAs and Neptune Mobile Clients. CSS from custom UI5 themes is now also used in this logon screen. Also theme specific fonts are now used in the initial logon screen.

If you choose to update dynamic tile info directly in the Launchpad frontend using sap.n.Launchpad.UpdateTileInfo, the update function will only update values if the update object has the specified property.

A new setting in the Neptune Launchpad/Mobile Client Cockpit tools allows enabling the display of extra information in the left content menu.

The logo in the top left corner can be set by customers. We’ve seen that applied logos are not created specifically to fit the launchpad header. So the height has been changed to fit larger logos into the launchpad header. If your logo has a shape that does not fit into the recommended 2.375rem height, you can adjust this in the launchpad global style section or in the layout style section:

When a single user logs in, the user selection screen is omitted when opening a mobile client. Instead, the PIN code is promptly displayed and ready for input. The PIN code screen will also appear when a user locks a mobile client in cases where only one user is logged in. However, if biometric login is enabled, face recognition will instantly unlock the device. In this scenario, the user selection screen will be displayed.

Cordova has not yet fully implemented support for the status bar in Android 12 and later. Neptune closely monitors Cordova’s development and will incorporate any changes as they are released.

Cordova has not yet implemented support for the new splash screen API and animated icons introduced in Android 12 and beyond. Neptune closely tracks Cordova’s development and will implement these changes once they become available.

When creating a mobile client, it will be assigned both a semantic version and a technical patch version, which are derived from the DXP version. Neptune strongly recommends using the assigned versions as they are. While the semantic version can be adjusted as needed, it’s essential to note that the technical patch version cannot be altered to ensure compliance with the requirements of Google and Apple App Stores. You can now view the patch version number in the mobile client build list and within the build detail view.

A lot of the files in a Mobile Client build, consist of the UI5 source files. They are the same for every Mobile Client build, so UI5 source files will be compiled into a start .zip file on the very first build. Subsequent builds will grab the compiled UI5 .zip file and just add the small dynamic configuration files to the .zip file. This will reduce the Mobile Client build time drastically. From minutes to seconds!

A slight increase in space has been applied between tiles. All launchpad layouts will now adopt the tile margin, consistent with layouts based on the Horizon Theme.

Improved support for status bars has been implemented for Android and iOS. By default, the status bar’s background color will match the mobile client header color defined by the theme’s CSS variable --sapShellColor. The text color in the status bar will, by default, correspond to the theme’s brightness. For example, a light theme like SAP Horizon Morning will feature dark text, while a dark theme like SAP Horizon Evening will display light text.

AppCache.Load will now return a Promise. This means that you can load an app and respond to the result through the Promise. Additionally, you have the flexibility to load a view and receive the result view, allowing you to perform any necessary actions. If you set load="external", Neptune will not do anything with the view

In previous Neptune DXP versions, when using AppCache.Load to load a child app into a parent object in a standalone application, a new child view instance was created with each AppCache.Load call. Starting with Neptune DXP 23, when loading an application in a parent object using AppCache.Load in a standalone application, the onInit and beforeDisplay event handlers will be triggered in the child application upon its initial load. When the child application is loaded a second time into the same parent object, only the beforeDisplay event will be invoked. This improvement significantly enhances performance and streamlines data handling.

A tile can accommodate an image in one of three ways: as a background, inline below the title, or positioned above the title. Previously, setting the image size only affected background images, with inline and top-placed images automatically using cover or contain. Now, you have the option to size inline and top-placed images within the tile content area using Fill, None, or Scale Down.

When saving a tile, the cockpit will now verify that both the dynamic application and AJAX ID are configured, especially when the tile type is designated as dynamic.

All dialogs in Neptune Cockpit services now have a proper initial focus element.

You can now directly copy a launchpad or mobile client from the detail view.

UI5 controls descended from the sap.ui.core.Element control inherit the 0..n customData aggregation. This means that virtually all UI5 controls can handle the customData aggregation. You can now add a sap.ui.core.CustomData control to all these UI5 controls. Custom data objects have only a few but powerful properties:

UI5 controls descended from the sap.ui.core.Element control inherit the 0..n layoutData aggregation. This means that practically all UI5 controls can handle layoutData aggregations. There are various layoutData aggregations, each tailored to a specific UI5 control, designed to provide precise layout control. It’s essential to note that adding a sap.m.FlexItemData aggregation to a UI5 object is meaningful only when that object is positioned within a sap.m.FlexBox control. Similarly, sap.m.ToolbarLayoutData will take effect only when applied to objects added to a sap.m.Toolbar.

The following new UI5 controls have been introduced:

UI5 CDN versions have been deprecated for some time. Now, you can only utilize a locally installed UI5 version or provide a full path to a sap-ui-core.js file.

In Neptune DXP 23, the following UI5 controls have been deprecated but are still available for use: