Neptune DXP - SAP Edition 24.11.0 Changelog

The message about a system exceeding the allowed time without a heartbeat was cut short due to a bug. Now, the message is presented in its full length.

If your SAP System can only reach public internet via a proxy server and that proxy requires authentication, you can now create an RFC connection in transaction SM59 under the HTTP Connection to External Server.

We now make available the program /NEPTUNE/HEARTBEAT. We strongly recommend using this program to set up a job that runs daily in order to ensure that the license heartbeat is executed. Since the heartbeat is only relevant once per day, we recommend scheduling this job during off-peak hours, such as early in the morning, between 00:00 and 01:00 AM. In this program, if needed, you can save a variant with the RFC connection as previously described. If the selection-screen-parameter is left empty, it will execute the heartbeat using the normal proxy server and port that are saved in Cockpit → System Settings → General → Proxy Server.

The automatic user cleanup for users that have not logged in using Neptune DXP in the last 120 days or for users that have reached their expiry date, or have been deleted in SAP, will now happen every day. A description was added in the Licensed Users tool in the Cockpit for the expired users.

In Neptune DXP - SAP Edition 24, all navigation in the launchpad is based on semantic hash objects. Loading an application using AppCache.Load will not automatically create a change in hash navigation. That can be an issue if the launchpad implementation relies on hash navigation, like using AppCache.Back. Neptune recommends that the param load="nav" is used. This will create a proper hash navigation and an accompanying menu entry with the active application that can be used to navigate to the open application at any time. In case you just want a specific hash navigation we have now introduced the parameter semantic action to the AppCache.Load function. Setting semantic action will create a hash navigation using the following template #neptunenavigation-YOUR_APP_yoursemanticaction.

AppCache.Load("YOUR_APP" {
  semantic: "yoursemanticaction"
});

The Neptune Multi Column Launchpad Layout now supports sidebars for section groups (sub-tile groups). An additional navigation column has been added to the Neptune Multi Column Launchpad Layout, so that a true multidimensional 3-column layout can be created in the Neptune Launchpad.

Some settings were not applied correctly for section groups (sub-tile groups).

The Neptune Element Query framework can now handle column changes all the way down to XXSmall and XXXSmall, making it possible to handle 1 and 2 cell columns in the Neptune Launchpad. The smallest column sizes can be very useful when implementing the new navbar and sidebar columns in the Neptune Multi Column Launchpad Layout.

It’s now possible to add a message in the Neptune Cockpit tile group configuration that will be shown in the Neptune Launchpad in the tile group header.

Custom hash navigation can now be used in tiles occurring multiple times in a launchpad.

When a user wants to open a tile via the launchpad search on top within a launchpad and that tile is added via a tile group that is added as an action type "Tile Group" from another tile (nested tile group that is added as a tile group link) then this tile was not opened when clicking on the corresponding search result item.

When a user would enter incorrect credentials on the logon screen of a PWA-enabled launchpad, a pop-up prompt would show asking for username and password. Even if the correct credentials were entered in this pop-up, it would count as an incorrect password attempt, because the credentials entered in the first attempt would still be considered. Due to this, users could get locked even when entering correct credentials. This has now been changed, so there is no pop-up and further attempts are handled properly.

As of version 24.10.0002 it is no longer required to install the SAPUI5 versions on the back-end server when Neptune is used in a front end/back end split scenario.

Configured images did not render correctly in splash screens.

The hierarchy list was not populated with the correct entries.

The launchpad syntax check dialog will now include links to artifacts with the found syntax error. Syntax check has been enhanced to include:

Opening an app with an RFC destination (application class in a different system), could lead to a runtime error in the back-end system. In the browser one would see error message "AppCache.getView: 200 - OK", while ST22 in the back end would show:

Runtime Errors         OBJECTS_OBJREF_NOT_ASSIGNED
ABAP Program           /NEPTUNE/CL_NAD_URL_HANDLER===CP

A tile configured to be opened in a dialog would set a semantic object. This would mess up the launchpad navigation.

The hierarchy list was not populated with the correct entries.

It is no longer allowed to manually enter a package, instead the package selection dialog must be used.

If properties in an app would have text in quotes, such as "My Text" during creation and extension of this application, this text would cause the application to break because the text quotes would not be escaped. This has now been fixed.

The association initialFocus has been added to the UI5 control sap.m.ResponsivePopover.

When importing and saving an app that has an RFC destination, the Web App Designer would only open the app, if the RFC destination as well exists in the system the app was imported to. This has now been fixed: the app can be opened, but not activated.

It is no longer allowed to change from a non-local package to a local package.

It is no longer allowed to change from a non-local package to a local package.

When defining an API endpoint within the API Designer and the corresponding method is using exception classes, you are able to influence the http status codes that should be returned when the exception is raised during run-time of the API by implementing interface /NEPTUNE/IF_HTTP_STATUS_CODE~GET_STATUS in the exception class. However, there was no way to reflect this run-time behavior within the OpenAPI 3.0 specification at design-time. We now introduced a new method /NEPTUNE/IF_HTTP_STATUS_CODE~ENHANCE_EXCEPTION that allows you to set the status code of the exception that is represented in the Swagger specification.

method /neptune/if_http_status_code~enhance_exception.
" This would show as status code 400 instead of the default 500 Internal Server Error
      io_exception->set_http_status_code( iv_status_code = '400' ).
endmethod.

When pressing the button "Copy to Clipboard" in the dialog of the Swagger Definition in the API Designer, a JavaScript error would occur.

It is no longer allowed to change from a non-local package to a local package.

It is no longer allowed to change transportable artifacts (App, I18n Text & Translation, API and SAP UI5 Theme) from a non-local package to a local package.

When manually entering a package, a verification is added to ensure that the package is valid.

If the Neptune sorter is enabled on a sap.m.Table, the table is sorted on the first rendering. If the table used in a dialog or similar UI control that will render the table over and over again, the sorting was not called. If the data had changed, the sorting could potentially be incorrect.

With Neptune DXP - SAP Edition 24 a mobile client name can have an i18n binding assigned to be translatable. When creating a mobile client ZIP for a mobile client that has such an i18n binding assigned to the name, we now resolve that to the default attribute value to be used in Cordova and MBS.

The default Neptune logo and branding image have been updated to new format.

The files app.css and manifest.appcache are no longer created, updated, or served from the MIME repository (path /neptue/public/application). Instead, they are generated from the activated app data upon request.

With Neptune DXP - SAP Edition 24.10.0000 there was a bug introduced that led to an error when opening a Neptune App from an SAP Standard Fiori Launchpad.