Neptune DXP - SAP Edition 24.15.0 release notes

The following styleClassPadding attributes was added in previous DXP versions, but the UI5 framework has no support for the styleClassPadding CSS classes:

The newly added support for all UI5 aggregation types in the App Designer has led to the deprecation of the following UI5 controls:

The shortcut Ctrl+D / CMD+D can now be used to duplicate an object in the App Designer.

UI5 controls added in newer UI5 versions are now hidden by default in the App Designer, if the used UI5 version does not support them.

When there are multiple hits in different events for the same object, this is now reflected in the result list of Script search in the App Designer. Additionally, there is a new column Attribute/Event that shows in which event or attribute the hit is located.

Keyboard action shortcuts are now correctly disabled when the application is in display mode, preventing unintended interactions.

Messages in the neptune.MessageArea are now aligned to the left and displayed in a list format with wrapping, making them easier to read and distinguish.

The following new UI5 controls are now available:

Several UI5 controls were missing the tooltip, styleClass, styleClassMargin, styleClassVisibility and enableCompactMode pseudo attributes. These have now been added: styleClass, styleClassMargin, styleClassVisibility and enableCompactMode to all controls that support the addStyleClass method, and tooltip to all controls that support the setTooltip method.

The PlanningCalendarAppointment in the sap.m library has been renamed to its real name CalendarAppointment and moved to the correct sap.ui.unified library.

Deprecated UI5 controls are now hidden by default in the App Designer. You can enable the option to show deprecated controls in the Library pane settings.

The App Designer now supports all UI5 aggregation and association types in all UI5 controls. This means that you can use all default UI5 aggregations and associations without limitations in the App Designer. The inline UI5 documentation has been updated to reflect this change and provide guidance on how to use aggregations and associations.

Typescript Compiler Target is now correctly disabled when the application is in display mode.

If you have more than one active client in the system, in Cockpit tool Application Usage, the usage can be counted for each client independently.

Uploading a translation file now correctly applies all translations. A field mismatch between the export and import functions has been resolved.

The internal utility methods to encode and decode base64 now properly support UTF-8.

Unlicensed anonymous access attempts are now correctly blocked, returning a 403 Forbidden response to prevent unauthorized entry into the platform. Instances where the license permits Anonymous Access remain unaffected.

The API Destination will no longer be passed via URL parameter but instead as an HTTP header field.

The /neptune/webapp icf node did not serve the proper CORS headers on OPTIONS preflight requests.

When running Neptune applications in the standard Fiori launchpad, the i18n texts were not loaded and thus not shown in the application.

List and detail page heights now handled properly to utilize available horizontal space and avoid overflowing.

The Create API dialog displays any errors inline, instead of closing and using toasts

Transport selection dialog adjusted to always refresh on opening and staying open during the whole save/delete flow. Also, transport selection for cloud flavor systems require manual step outlined in the transport selection dialog.

When switching between display and edit mode, the app stays on the current tab instead of resetting. The edit mode/dirty state button handling reworked to not drop clicks/events on first edit.

The Usages tab is cleared on Copy/Create instead of keeping the previous items.

The AppCache.Load load=init & parentObject combination is now supported in the Launchpad. An initial call that does not load the child app into the parent container. The onInit event handler is triggered.

When the parent app is ready to load the child app, the following code can be used. The onInit event handler is not triggered again. Only the onBeforeDisplay event handler is triggered.

A type mismatch that could cause runtime errors (DUMPS) in the Launchpad’s Most-Used feature, triggered once an app’s usage count reached a certain threshold, was resolved. The Launchpad now handles high-usage scenarios reliably without interruption. Related to #605.

Enhanced the /NEPTUNE/HEARTBEAT program with improved messaging and logging for greater operational transparency. Performance has been optimized, and online license handling on system copy is now more robust and reliable.

The biometric plugins for iOS (cordova-plugin-ios-faceid) and Android (cordova-plugin-android-fingerprint-auth) were replaced with the cross-platform plugin cordova-plugin-fingerprint-aio. This plugin is more actively maintained and allows for a more consistent and reliable biometric authentication experience across both platforms.

When using Okta as authentication provider, the user could not use the Okta MFA code options (SMS, Voice call, Okta Verify code) for the second-factor authentication. Before this bugfix, the only working MFA option was push with Okta Verify. Now, the user can use all Okta MFA code options for the second-factor authentication.

Since DXP24, iOS mobile clients did not run with SAPUI5 version 1.71 unless you configure CORS and exclude the Castana plugin. Now iOS mobile clients work without CORS setup and SAPUI5 version 1.71.

A small timeout was introduced before the relogin is triggered in case of an expired token. This stabilized the relogin process and prevented the relogin from triggering too early.

From the Where-Used list, you can directly call the App Designer with the selected app.

In the OData Source tool, a button to display the metadata document was implemented.

If Proxy is disabled, or you are using HTTP Destinations via SM59, in the URL field, you can now use the value help to call the system’s OData catalog service and pick an OData service from there.

Target Host, Port, Protocol and Login Credentials can now be maintained via transaction SM59 "Type G - HTTP Destination".

The Proxy Class Name is now automatically translated to upper case to prevent further errors.

Loading Neptune DXP- SAP Edition applications that contain an object with the name Image in a Neptune DXP - Open Edition Launchpad led to a Javascript error. The application could not be opened in that case.