DXP22.10.0009 Changelog

We have changed the way exceptions are handled in an API call. This includes API calls maintained in the API Designer API calls from the API Factory. Read more

When calling an API Designer API from a frontend system (using RFC Destination) and return a Status Code this has not been returned back to the frontend system.

When trying to create an Entity Set in an API Factory Class you would get a console log error and cannot create the entity set.

Previously, the Launchpad, PWA, and Mobile Client setup lacked support for certain language scenarios. Specifically, the language set using the sap-language URL parameter was not always utilized, and it was not possible to provide users with a list of languages for the login screen translation while still allowing the SU3 language setting to determine the logged on language. If "SAP User Default" is chosen in the settings, then the DYL user parameter will be used if present, otherwise the standard language set in SU3 will be used. If the parameter sap-language is added to the URL, it will be the prioritized language. Read more

The Neptune Launchpad has undergone a significant upgrade, empowering users with an unprecedented level of control over customization. Gone are the days of all-or-nothing customization, as now you have the ability to fine-tune your preferences with precision. The customization framework allows you to enable or disable specific features, giving you complete control over your Launchpad experience. To ensure maximum efficiency, we have replaced the resource-intensive jiggle effect with a sleek move icon and dotted border for movable tiles. These exciting enhancements are available on both the launchpad and mobile client configurations, so you can enjoy a seamless user experience across all devices. Read more

When changing a PWA launchpad and a reload is required and the launchpad is opened with the neptune ui debug flag (…​&neptune-ui-debug=true or …​&debug=true) the launchpad would reload twice:

When clicking on a tile, the tile will be set in busy mode until the app has been loaded. UI5 adds a tab area to the right and left of busy areas, these areas took up 1 cell in the Neptune Launchpad CSS Grid, causing all the tiles to move to the right (left if you use RTL language). We now set these tab areas to be hidden in the launchpad grid.

Tiles with a URL action would not set the active app title in the launchpad.

Favicon would be added to the HTML header area in mobile clients. The corresponding favicon image was not exported, leading to console errors. Now the favicon is no longer added to the HTML header for mobile clients.

If favorites are enabled in a launchpad, an add/remove from favorites button will be displayed in the user menu. This button was not removed when navigating back to the launchpad.

When a URL is opened from a tile inside the Neptune Launchpad, the closing operation could leave the launchpad with an empty screen area.

If a tile has "Open Tilegroup" as action, the tile will now show up in the tilegroup where-used list.

The panel holding dynamic tile content would have a border radius that in some scenarios would clip the chart content.

In the ABAP logon screen, the "Show Password" text was read from the database and therefore not shown on the logon screen.

The onNavigation event handler would have a reference to the tilegroup instead of the tile application start parameters.

Some UI5 attributes did not handle pure number values. Zeroes would be truncated and not kept in the string.

When applications had "Hide Header" enabled, hitting the enter key in an input field would trigger launchpad navigation.

Applications (tiles) in the global search list are now sorted according to the Cockpit Launchpad/Mobile Client Configuration.

When the screen is resized, the global search will be closed, so that the rendering of search list can be correctly displayed in either a grid or in tabs.

Support for GIF files has been added to the media library.

The Launchpad onNavigation event handler would not send in start parameters from the URL semantic navigation hash data.

The init parameter (second parameter) in the Launchpad onNavigation event handler would always be true. Now the init parameter will be true only when it’s called the first time.

When long pressing on a tile in the launchpad on an Android device, the device would vibrate to indicate that the popup with the menu options was open. On some devices the vibration would end before the popup was opened, causing the user to stop long pressing. Then the long press turned into a normal press, which would open the application. The vibration is now removed.

When checking off the "Do not allow public network traffic!" setting in the cockpit, the cockpit would still try to load documentation from the Neptune Portal.

If a launchpad section (subtilegroup) does not have a menu text or title, it will not be added to the header menu sections. The tiles in the section will still be added to the screen.

If only one favorite was present in the favorite list, removing the favorite using the tile context menu or the user settings menu item would not remove the favorite from the list. Only from the Manage Favorites dialog could this last favorite be removed.

The custom tile action script was not created correctly.

It’s now possible to use data formatters for only day/month and day/month/short year.

The Neptune Splash screen was hidden after a theme change. The theme change event handler was called too often, this would hide the splash screen too early.

The create dialog in the Neptune Cockpit Launchpad & Mobile

A few launchpad fields were not translated correctly into Danish.

When using the Neptune Qaurtz Layout, or any other layout with a "negative" dark header, the new global search field would not have styling for the dark header background.

If a PWA or Mobile Client has multiple languages enabled, it the language live change from the launchpad settings menu would not be saved to cache.

Clicking on the collapse button in the left menu tree did not collapse the tree.

Tiles would be displayed in the global search, even though they were set to not be included in menus.

Sections (sub-tilegroups) would not be hidden from menus and global search in all scenarios, even though they were set to not be included in menus.

When running a Neptune application in a parent object using AppCache.Load, the view would not have any height defined. A styleclass with height:: 100% is now added to the child view when the child view is created. Then the child view content will take up available space inside the child view.

It’s possible to add customer login page info to a Neptune Launchpad. This login page info will be updated with any new configuration each time a user opens a launchpad. Sometimes it’s desirable to keep some info in the login screen, like a build version. So, it’s now possible to manipulate the login information in the "After Menu Items" enhancement spot.

The "Public Access" setting known from the Mobile Client configuration has been added to the Launchpad/PWA settings too.

When loading a launchpad, PWA or mobile client, 30+ models are loaded from cache. The cache counter was not issolated to only increase when getting cache from the update function. In one case this resulted in multiple calls to the ABAP backend GET_MENU_LIST method. Now the model cache is read and one dedicated callback will handle the update.

Calling sap.n.Lunchpad.UpdateTileInfo & AppCache.reloadDynamicInfo, not all tile elements were updated with new info right away.

The function sap.n.Artifact.recentCategories would fail in some cases when the data multi model was not initiated with deep data.

It’s possible to right click or long press on launchpad tiles to open the tile context menu. On some Windows touch devices, the native context menu would interfere with the launchpad context menu.

The new search in the Neptune Launchpad has tiles grouped pr screen (tilegroup). Now, tiles will be grouped into each screen section (sub tilegroup).

When loading an application in a dialog using AppCache.Load from a standalone application, the dialog close button would not be visible.

It is not recommended to use the sap.m.Shell UI5 control in applications running in the Neptune Launchpad. If a Shell object is used and it has the appWidthLimited property set to true, the application would in some screen sizes overflow, so that the application content would not be visible.

The sidepanel where the tile help opens will now show a busy indicator until the documentation is loaded. The tile help link text "Help" is now translated in the launchpad. The tile help link text can also be customized in the tile configuration.

The SU3 user settings dialog did not take daylight saving time into consideration when displaying timezones.

After Login (Appcache.AfterLogon) the AppCache_inPassword control was cleared but not the AppCache_txtPassword that will be filled if the user ticks the checbkox "Show Password". Now also the AppCache_txtPassword is cleared after Logon.

When using PWA enabled Launchpad, you can now also use OAuth Authentication allowing you to have SSO (Saml2) based authentication in your PWA! Before this was only possible in Mobile Clients.

The active app title was not displayed on screens below 600px width. Now the active app title will be displayed on all screen sizes, but it will shrink if there is not enough room in the launchpad header area.

In the past, users of the SAP Enterprise Portal who utilized the Mobile Client encountered a frustrating issue when attempting to change their password. Specifically, any error messages related to the "Change Password" process were not visible on the mobile client’s screen, leaving users in the dark about what went wrong (for instance, the message "New password cannot contain old password"). However, we have since rectified this problem and are pleased to announce that error messages from the "Change Password" flow are now displayed on the mobile client. This improvement will greatly enhance the user experience, providing a more seamless and efficient authentication process.

When using Basic authentication and the login fails you now do get more precise error messages (same as the error messages you would get through authentication via the /neptune/webapp node).

iOS is very strict when loading UI5 objects. All dependencies must be available or required before use, no synchronously loading of modules. The Timeline & DateTimePicker needs a special waitForThemeApplied module which is now loaded in the UI5 bootloader event handler automatically, so that it is available for usage immediately. When you use a UI5 object that requires special modules, Neptune will load them before the app JS view is created. If you are using UI5 components directly in code you need to handle this yourself. Example for the Timeline control:

There was a bug that caused that biometric authentication could only be used for the initial authentication. After locking the device, it would not be possible to reauthenticate by using fingerprint or FaceId.

Updating tile info/subtitle dynamically using sap.n.Launchpad.UpdateTileInfo, would not work if the tile header had no image. Yes, strange but true ;)

Cordova Android 12 was recently released, please see release notes for details. This version makes it possible to target features of Android 13 (Tiramisu) devices. The option to use cordova android engine 12 has been added in the Neptune Cockpit: Mobile Client→Device→Preferences→Android→Cordova engine version. This version is the default in the newest version of cordova cli 12. Please note that cordova android 12 is not yet supported in Neptune MBS, but we expect to add the support shortly.

The ModelData script from the Open Edition has been slightly improved. The script has been alligned between the Open Edition and the SAP Edition.

The Neptune specific notification list control has a special binding concept. The new centralized JSON handler didin’t convert data correctly resulting in an empty list.

When saving without activating an extension app and changing an attribute binding directly afterwards, a shortdump would be result in some cases.

Small improvement to the extension framework to prevent duplication of code when enhancing an already existing object in the base application.

When clicking the close button in the create new application dialog, opening an app afterwards would lead to an error stating that the application did not exist.

The homeIcon attribute in the sap.m.App or sap.m.SplitApp object would be generated as a string and not a proper JS object.

Application content aware help would not work in dialogs.

The model would not be generated when adding model source to a sap.ui.comp.filterbar.FilterBar control.

API structures would only be requested from the server by Model Binding dialog. So if the Attribute Binding dialog was opened before the Model Binding dialog, the attribute table would be empty.

When activating an app immediately after pressing the comment toggle button in the code editor, the action would not be registered.

The import button for translations in extensions was deactivated.

Corrected a bug that prevented the commenting/uncommenting of code in scripts, when an app would be activated immediately after pressing the button to comment/uncomment. The code would not retain the change.

The second time entering the app designer in an extension app, the Import button for translations would be deactivated. This has now been fixed.

When there is an iView Error from the SAP Enterprise Portal authentication this is now show to the user in the mobile client login screen.

You can now enable mouse over functionality for the Cockpit Navigation List, giving you faster access to Cockpit tools.

Some special characters are used in the Neptune Cockpit applications. If the SAP system is not Unicode, the encoding of views would not encode the special characters correctly, cause cockpit views with the special characters to fail when loading.

The label on the create buttons in the Neptune Cockpit services have been changef from "Add" to "Create".

The search for tilegroups in the Cockpit Tilegroup Service, would not exclude the tilegroup it self.

The application /NEPTUNE/F4_SEARCH_HELP is now translated into all 31 supported languages.

A stricter validation of the Neptune ICF configuration has been introduced. If the nodes 'server' and 'public' are not created under the 'neptune' node, and these are not assigned user credentials, an error message will be provided. More details about how these nodes should be set up can be found in the installation guide.

In the program /NEPTUNE/DELETE_LOG_ENTRIES there were missing parameters referring to the API Logs.