DXP22.10.0010 Changelog

We added a new option that allows to run CSRF Protection in multi-browser-tab scenarios.

When calling API Factory with parameter $RFCDEST and that value contained JS it could have been possible to have a XSS scenario. Now we escape the value to avoid this.

When running a Mobile Client with SAP Username/Password the clear Text Password Field has not been cleared. Now after successful or failed logon the cleartext Password Field is cleared

When using a PWA enabled Launchpad and an external alias the dynamic tile data was failing.

In custom themes build on older 1.108 versions, the header in some dialogs would have a small transparent gap.

When saving the cockpit will now check that both dynamic application and AJAX ID are set if the tile type is set to dynamic.

The hideOnNoData property was introduced in UI5 1.84. A check for lower UI5 versions has been added, so that the property will only be applied when the launchpad is running UI5 1.84 and above.

The keyboard numpad can now also control the launchpad pin code screen.

When setting a tile to not show header, the launchpad content height would not be adjusted, leaving a gab at the bottom of the page.

A section (sub-tilegroup) header would still be visible even though the section did not include any tiles.

When a tile has a URL action (SAP Fiori App) and the opening is set to be done inline in the launchpad, the iFrame where the URL runs are now sandboxes, so that navigation happening inside the iFrame will not be parsed on to the parent launchpad.

Support for the DYL parameter has never been 100%. Now that the DYL parameter is really being considered, this can cause problems in systems where the DYL parameter is set, but was never used. If you want to enable the usage of the DYL parameter, this needs to be enabled in the Cockpit Settings Service.

If a launchpad is set to use the default user language, the DYL user parameter will be read. If the DYL parameter was not correctly formatted, a non-existing language was used in the launchpad language settings. It would cause the launchpad to crash in some circumstances. Now, the DYL parameter must match an installed 1-char language perfectly, with correct case, if not, the DYL parameter will be ignored.

If a launchpad was set to use default user language or browser default language and the SAP user had no language set in any of the many possible settings, the browser language was not chosen correctly. The system’s default language would be set even though the browser language was installed in the system.

The forgot a password link in the mobile client logon screen would not open correctly.

When an application includes documentation, the documentation application would set the global dialog backdrop canvas to not-visible, causing other dialogs to not be modal.

The launchpad CSS for compact toolbars was not targeting a specific class, causing the styling to be applied to customer applications too.

The Neptune system layouts were missing setting for mobile status bar colors.

When changing language in a PWA, application views would still be shown in the old language until the PA was reloaded. Now applications views will be requested based on the new language.

The event controlling window width did not handle open apps in the launchpad header, causing open app icons to disappear when resizing the window.

Showing PDF files on iOS 16+ using the PDFView would result in a blank screen. The PDFJS library has been updated to v.3.8.162 which solves the problem.

If a system is not a Unicode system, the Neptune server will not encode application Javascript view data, but instead send the application JS view data in pure text. This will ensure that any non-Unicode characters in Neptune applications will not cause the JSON encoding to crash.

Updating dynamic tiles in the launchpad with initial values, like an empty string or zero would not always work. The interface for the API_TILE_INFO method in class /NEPTUNE/CL_NAD_SERVER has been changed to receive a data structure and an update structure, like in a call to a BAPI function. All the old single value attributes has been deprecated. The old individual attributes can still be used, but parsing initial values into these individual attributes, might not be parsed on to the frontend dynamic tiles. And static values defined in the cockpit tile configuration might be overwritten. New interface usage example. Your code should, of course, set all this dynamically:

The dialog in the maintained screen was not set to scroll vertically. With a lot of screens in the launchpad, the last ones were not reachable.

An error where access to an unassigned object in /NEPTUNE/CL_NAD_APPCACHE→LANGUAGE_LIST would occur in rare cases.

If the launchpad is set up to have a lot of levels, the left side menu would be set to a width that fits the deepest level. That could be way to wide if only one or two levels were opened. Now the menu width will be change each time a menu item is expanded or contracted.

When running the Neptune Launchpad in Safari or Chrome on an iPad, the WebSQL fallback detection was not good enough in the minified Core.js script including the AppStorage script. Instead of falling back to IndexedDB, AppStorage would crash.

The table with time zones would not display all time zones, if additional time zones were configured in the SAP system.

If the user closed an app before an Ajax call would return, the Ajax success handler would try to set data to a null model. The check for destroyed models in the Ajax success handler has been improved to check for null too.

In some cases, the state would not be present in the model data when creating the notification list in the Neptune Launchpad. This would result in a Javascript error and an empty notification list.

If a tilegroup has an application added as an action, this will open the application inside the tilegroup and fill the entire tilegroup. It’s not possible to add tiles to a such tilegroup. But if tiles were added before the action was set, these tiles would show up in the menu. Some might have seen this as a feature, but this was not the intention of the tilegroup live application action. Now the tiles will not be selected from the SAP backend if an action has been added to the tilegroup.

A bug in the Cockpit Launchpad & Mobile Client tools set the display of the navigation side menu based on the wrong parameters, causing the side menu to be shown in some circumstances where it shouldn’t.

Menu navigation items set on tile groups with live application actions would not behave correctly. Multiple navigation items would be opened, and the close button would not close the opened application. Icons set on the navigation items will now be used in in the left menu for menu items and open applications. And for open applications in the left navigation and the section for open applications in the launchpad header.

Setting a timeout in PWA and Mobile Client configuration to control when a device should be locked, didn’t kick in before the device was suspended. If the screen was never turned of, the device would never lock. A new keyboard and mouse detection has been added, so that the timer begins to count down on the last input on the device.

Some older touch enabled Windows-based devices do not register right click and long press correctly, so that a long press will be interpreted as a normal click. This can cause a conflict with the new customization framework. An option to turn of right click and long press detection has therefore been added to launchpad and mobile client configuration. Tick this setting of if your cooperation uses any device where this is the case.

In some cases a tile would not have an icon placement defined, causing the icon on the card not to load.

Double click and long press fires a range of mouse events. The mouseup event was not fired on the second click in double click. When clicking on a tile, this issue would result in the opening of the customization dialog in a strange mode, were the screen would be blured.

A standard tile action can be to open a Neptune application. It’s possible to define parameters that will be sent into the applications init and beforeDisplay event handlers. If the tile type is dynamic, a special tile configuration is added independent of the regular application defined in the tile action. These two concepts have now been somewhat combined. Application parameters defined on the regular tile action will be parsed on to the application defined in the dynamic tile configuration. This way it’s possible to easily indentify the origin of the dynamic request. The last update timestamp is already beeing send with the request in the Ajax value parameter. If application parameters have been defined in the tile action configuration, these will de concatenated in the ajax value seperated by ||. You will have to split the ajax value to get the application parameters.

When deleting a Policy in the cockpit, the policy list was not updated after the deletion.

The search field in the Neptune Cockpit has been updated to fit into the Horizon Themes in UI5 1.108.

Data in the Licensed User table in the Neptune Cockpit was not updated frequently enough.

If a mobile client was published, it was always the latest build that would be shown in the Neptune Catalog. Now the active version is selcted when the list of mobile clients are build in the catalog application.

The busy indicator in the sync dialog would only be visible in the first call to AppSyncStart.

The Neptune Media Library now supports video files in .mp4 .avi, .mov & .wmv format.

In some search helps, the demandPopin property would be set to true on all columns. On small screens, all the columns would popin making the select box rendered incorrectly.

Corrected a bug where the default values for the search help parameters would not be read if the parameters were not visible.

When you are using a Tile with action Type "ABAP Report" and passing a ABAP Query Report (SQ01) it could have happened that you would get an error when running the report. This was due to the fact that the ALV Fieldcatalogue has not always been determined correctly.

If you were using a data element that should not be considered as JSON boolean and that would have as a name a substring of one of the data elements that are properly treated as boolean, then the data element was wrongly treated as boolean. Example: You have the following data elements defined:

Under certain conditions it could have happened that calling an extension app would lead to an exception in /NEPTUNE/CL_NAD_SERVER→UI5_ATTRIBUTES. The setup needed to be as follows: Inside the extension app you would add an "Add" extension to a ui5 control. Afterward, you would add a "Change" extension. Then you would define a attribute in the "Change" extension that is not defined or default in the base app.

When using VizFrame properties in one app and an extension was created, this component was not loaded correctly into the extension app. This was now been fixed.

Texts longer than 100 characters were being truncated at 100 characters. Now the full text (up to 255 characters) will be exported

Appointments & Interval Header bindings are now working with generic models. Multi model support will be added in DXP23.

The value table for the sap.m.Button#type property and sap.m.ObjectStatus#state, have been updated with the latest values.

Default theme is now preselected also when creating an app in the App Designer in SAP GUI.

Both app designers (Cockpit and SAP GUI) have now been aligned for uppercase/lowercase usage for saving setting "Allow ICF subnode" as well as the url that is generated when running an app standalone from the App Designer. Activating an app with this ICF setting in the Cockpit app designer could in certain cases give the error "Internal Server Error: APPLID not found".

When unlocking (pin code) a PWA enabled launchpad or a Mobile Client and you are offline, the afterUnlock Enhancement has not been called. This is now resolved. The ajax call to fetch changes to tile groups, tiles and apps is now skipped during offline re-authentication. In certain vpn scenarios, this call could result in a long timeout.

Since SAP version S/4 HANA 2021, the message returned when an object is locked has been changed to contain two variables. For these newer SAP versions, the message will now show the key of the locked object in addition to whom the object is locked by.

When you were using a PWA enabled Launchpad that uses OAuth as an authentication mechanism that didn’t work unless you enabled the checkbox "Create Login Cookies" in the Launchpad settings. This is now working also without Login Cookies.

neptune.Formatter.getDate was using the format parameter and not the pattern parameter to get a date instance based on the yyyyMMdd pattern.