DXP22.10.0006 Changelog

When running a PWA offline, neptune.UserDefault.numberGrouping & neptune.UserDefault.numberDecimal were not read from cache, resulting in failing number formatters using neptune.Formatter in input fields.

It is now possible to specify the cordova android engine that should be used when generating the mobile client. This setting can be found in Cockpit → Mobile Client → Device → Preferences, in the Android section.

By default the end user can rearrange tiles, add new tiles, add new screens and move tiles around. This launchpad customization can be disabled for the whole launchpad. Now it’s also possible to disabled end user customization for a single section (tilegroup). So, now it’s possible to have locked sections in your launchpad and have other sections open for customization.

When deleting all CSS from an application, the Neptune table containing the style data will be deleted, but the generated app.css file would not be updated.

When a Launchpad HTTP Header has been provided (NeptuneLaunchpad) but the corresponding launchpad doesn’t exist now we return a 400 Bad Request HTTP Response.

If the launchpad main menu is shown in the header, the menu is shown on a seperate header line in Neptune DXP 22, this follows the SAP Fiori Design Guidelines. By public demand, we’ve broght back the option to have the main menu shown inline in the very top of the launchpad, together with all the rest of the header buttons. The overflow mechanism still works nicely when the menu is shown inline, an overflow button will open a popover with the remaining menus if there is not room enough in the header itself.

Neptune Launchpad Layout background images could only hold 30 characters. Setting background using gradients would not be possible, because the value would often be too long and therefore result in corrupted CSS.

When loading applications in the launchpad sidepanel, the application ID could not include special characters like /. It’s now possible to also load the same application multiple times with different start parameters into the side panel, so that multiple documents can be handle reusing the same JS view.

When navigating back in the list of AppCacheNav pages (apps & screens), the screen scroll position was not always maintained. In some cases the top of the screen would be shown instead of the position before an application was opened. Setting AppCacheNav.autoFocus to false solved the issue.

All editors in cockpit tool applications will now live detect light/dark theme changes.

The new Insert function in ModelData would not use the parameter record correctly.

When running a Neptune application in the Neptune Launchpad as a JS view, translated text with special characters would not be transfered correctly.

When setting the UI5 version for the app as 1.108. some objects in some libraries, like sap.f , were removed when they shouldn’t.

Exporting a classic launchpad with tiles added directly to the launchpad would not choose all tiles & tilegroups. When migrating a Neptune Launchpad from NEPTUNE_LAUNCHPAD_DESKTOP to NEPTUNE_LAUNCHPAD_STANDARD, tiles with parents would not be migrated.

When changing settings for "Screen Changes" in the Neptune Launchpad. Live apps in sections (sub tilegroups) were not redrawn in the DOM.

When Importing an XML File that has been created from DXP6 "Export" Cockpit function into a >= Neptune DXP 21 System via the Cockpit "Import" function you might have gotten an error and no changes would show up. This was related to a shorteing of certain fields and would eventually lead to a CX_SY_CONVERSION_DATA_LOSS exception in call transformation id. This now has been resolved.

When the launchpad global search dialog was closed, the focus was lost if the screen was too small to contain the search field. Now either the seach field or the search button will be focused depending on the visibility of the search field.