DXP21.10.0007 Changelog

If a launchpad or mobile client was set up to use multiple languages, the language would not be used in the logon process. This issue was introduced in DXP21 Patch 6 when solving another language related bug.

When the neptune.ValueHelpField is used the result list is now sorted by all visible columns as default. That should now match exactly the SAP Standard F4 Help default sorting.

In DXP 21.10.0006 a bug was introduced that in a multi-client setup when accessing neptune cockpit or launchpad through the browser with the /webapp icf node you could be getting a white error page stating "Not authorized to access client xxx". This is now resolved.

When trying to change the password from the login screen of a launchpad or the Cockpit, there was a bug that caused a "400 session timed out" error. This has now been fixed.

When sending an interface attribute back to SAP in an AJAX_ID call in the App Designer the request body JSON has been not valid. By introducing double quotes in the propertys of the request body object now we can also handle interface attributes as keys which contain special characters like ~ but even sap namespace separators (forward slashes) are possible.

In special circumstances you could have gotten the error message "Failed to load API definition" when trying to open Swagger UI in an API Factory Class.

Region role and Aria Label has been added to the navigation area including navigation items to open applications. Accessibility text has been added to the button that open and close the navigation panel showing open applications.

When loading a Neptune launchpad, the backend ABAP method /NEPTUNE/CL_NAD_APPCACHE→GET_MENU_LIST. Now, USERNAME & USERNAME_PORTAL are also passed on to the AUTH_CHECK_TILE_GROUP method.

The "Send debug data button" would be visible in the launchpad settings dialog, event though debug was not enabled.

When using the FileUploader control in an app with RFC destination specified, the file upload fails with a dump (CALL_FUNCTION_RECEIVE_ERROR) in the backend destination system. This is now resolved.

The system ID has been added to the ID when creating application views. In normal launchpads this will not have any noticable effects. Only in launchpad that has been enhanced to handle multiple systems, the system ID is vital to tell applications with the same ID from different systems apart. But in all cases it’s pretty nice to have the system ID present together with the client and language in the view ID.

We’ve added the option to show the Neptune Cockpit Services as a list in the left navigation panel. When an item is clicked in the list, a list of services in the section will be shown. The display and position of the Running Services, Menu and Favorites can be configured in the user settings dialog. The Cockpit will of course remember the choice made and present the navigation panel in the same state the next time the Cockpit is opened.

When adding inline documentation to labels in Neptune applications, the help icon would be placed wrong in the UI, if the label was added to a Simple Form with the layout set to ResponsiveLayout.

"Login" was spelled "Ligon" in the Login Page tab.

Editor tools have been added to the "Layout Style (CSS)" Cockpit Launchpad Layout Service and the Script Editor in the Cockpit Enhancement Service.

When importing media pack files created with the cordova-res commando, the import would not recognize the default icon.png images.

The default Neptune splash screen would be used, even though a splash screen was defined centrally on a launchpad that should be used in all layouts without splash screen defined.

Missing events have been added to the sap.n.PlanningCalendarRow, to enable drag’n’drop and resizing of appointments. New code snippets to handle the different events have been added to the App Designer.

If a special header text color and background color is maintained in the layout configuration, the colors were not applied to the initial login screen.

The preview button in the Cockpit Mobile Client service has been removed. It makes no sense to run a mobile client in a browser directly. If you want to test your mobile client without building and installing all the time, you should ⇒ Build ⇒ Download ⇒ Extract ⇒ move index.html from one of the merges folder to the www folder ⇒ Run in browser with Web security disabled…​ See more details on how to do it here.