DXP24.10.0001 Changelog

When using a system with a too low SP you would have gotten a syntax error stating Formal parameter E_PHIO_ID does not exist after importing the initial DXP 24 release transport. This is related to the field E_PHIO_ID in method IF_MR_API~GET_BY_IO that has been downported by SAP to all SAP_BASIS versions from 700 - 751. It is present in 731 SP30 (minimum SAP Basis Release for Neptune DXP - SAP Edition 24) however not in 740 SP11. We now avoid using this field, thus not relying on decently patched SAP_BASIS versions.

When using the tile open action "ABAP Report (Beta)", it might have happened that the result table was shown when the report is executed but the busy indicator would be kept active. This could have happened when the resulting ALV list has colored cells. In addition to that there was a size limit of 100 variants that would have shown in the "Variants" dialog. This has now been increased to 1000.

When using an SAP Query with the tile open action "ABAP Report (Beta)", the resulting list would only contain 100 entries even though the query should select a bigger result list.

The Neptune Launchpad will now use the browser back button window.history.back function. You can take advantage of this and implement hash-based navigation inside your own applications. Register to listen for the hash change event. In your event listener, make sure to only handle hash navigation from your own app using a custom hash nav ID scheme.

const navPrefix = (typeof localViewID !== "undefined") ? `${localViewID}--` : "";

window.addEventListener("hashchange", () => {
    if (location.hash.startsWith("#prom")) {
        App.to(neptune.byId(`${navPrefix}${location.hash.slice(1)}`));
    } else {
        App.to(promHome);
    }
});

neptune.Shell.attachInit((data, navObj, fromSplitView)=>{
    if (location.hash.startsWith("#prom")) {
        App.to(neptune.byId(`${navPrefix}${location.hash.slice(1)}`));
    }
});

location.hash = "promOne";

Fixed issue where the same existing language would be listed multiple times per object. Adjusted suggested i18n attribute name to include object and object attribute names. Fixed issue where it was possible to add duplicate i18n attribute names. Fixed the translation transfer. So, the correct text for translation was always created. Making the formatter script available after attribute conversion.

When using a custom UI5 control within an app, an error occurred and showed up in the console with message Missing initializer in const declaration.

When adding a new custom control object to the UI tree, the default object name will not include any dots found in the component name and an attempt at converting the dot notation into a camel case name will be done. For example, a my.custom.input custom component will be named myCustomInput.

Corrected an issue where short dumps occurred in the back-end system when loading an app that had a mix of both standard UI5 controls and the same components as custom controls.

When creating a new custom UI5 control, a check has been implemented to verify that the name of it includes a dot and is written in dot notation, like my.custom.control, for example.

When adding a new custom control object to the UI tree, the default object name will not include any dots found in the component name, and an attempt at converting the dot notation into a camel case name will be done. For example, a my.custom.input custom component will be named myCustomInput.

When displaying the Cockpit tools as widgets, you’ll now be able to assign a color to the widget area, as well as maintain the favorites from the widget. The favorites tool will be marked with the widget area color in the dedicated favorite widget.

Many of the tool attributes will have a help icon attached to the attribute label. A click on the help icon will open a text area or a pop-up that displays attribute relevant help information. Sometimes the help information will include interactive graphics reflecting the attribute settings.

Fixed a bug on the export/import for the layouts of Launchpad, Tile and Tile Group where not all tables were being exported/imported. Fixed a bug on the Export tool, where the names and descriptions would show the i18n binding path instead of the actual text.

A standard Neptune launchpad will show all content in one main column. You can now add a sidebar to create a 2-column layout in your launchpad.

The tile layout configuration options have been deprecated and moved to the Tile Layout tool. All the settings in the tile will still work, but Neptune recommends that tile layout settings are now configured in the dedicated Tile Layout tool.

A lot of new settings for the tile group layout have been added. This is configured in the new Tile Group Layout tool. Existing tile group color configurations have been migrated to the new tool.

Some improvements were done regarding the performance of the licensing logic.

All navigation in the Neptune Launchpad is hash-based, every screen, section, and tile will have its own hash navigation ID. We are now taking full advantage of that and enable the usages of the built-in back functionality from any device. The back button in the Neptune Launchpad will now act exactly the same as the browser back button using the window.history.back function.

If a "Live Application" tile was set to fill the entire card, the tile action was not built resulting in an error.

New configuration settings for tile layout have been added, with even more low-code configuration options to manipulate the tile look and feel.

A new tool for tile group layout configuration has been added, with lots of low-code configuration options to manipulate the tile group look and feel.

A standard Neptune launchpad will show all content in one main column. You can now add a sidebar to create a 2-column layout in your launchpad. This is implemented in the tile group configuration.

Added support in the launchpad for Vietnamese language.

The Create Dialog of an API was not verifying if the provided path is already used in a different API. Thus, the API was created syntactically incorrect. This is now prevented and a corresponding error message is shown in the Create Dialog.

An API created with the Neptune API Designer can now be copied. You just need to open the corresponding API you want to copy in display mode and press the "Copy" button.

The names displayed will always be the most recent for each artifact.

Icons are available in both light and dark mode.

It’s possible to change the package assignment of an already existing theme.