DXP21.10.0014 Changelog

The cockpit app designer has not handled repair transport tasks up until now. So when activating apps in foreign namespaces, such as the standard delivered Neptune apps, the MIME for the css could not be modified or created, and the activation would fail. This now works as it has done in the SAP GUI version of the App Designer. It is a requirement that the namespace of the package that the app belongs to can be modified in the system.

We aligned the API Exception Handling both from API Factory and API Designer. Exceptions are now handled by one central exception handler /neptune/cl_exception_handler⇒instance→get_response_from_exception. A big benefit of this is that Exceptions will now be reflected as JSON Response Bodies, so you have a lot more information on the client side and can handle those a lot more precise. Here is an example of a CX_SY_ZERODEVIDE exception with Exception Chaining (PREVIOUS):

When upgrading from an older Neptune version, some search fields would still be located in the App Designer looking fine, but would not be rendered at run time.

The neptune.UserDefault object would be empty in standalone applications.

When clicking on the change password link after first entering an incorrect password, and then correcting it, the user would get prompted to define a pin code instead of being able to change the password.

When you accidentally added a line break at the end of the Service URL of an OData Source the generated Javascript Code would get syntactically incorrect due to the line break at the end of the URL. Line Breaks are now automatically removed from the Service URL.

When using an SAP Domain in a select box and setting the load=init, the App Designer would throw a syntax check error.

The table personalization object would not remember applied settings when reloading an application.

The generated JavaScript code to call a Rest API from the index.html inside a mobile client (NEPTUNE_LAUNCHPAD_STANDARD and corresponding extension Applications) did have a relative URL leading to a Rest API Call file:///neptune/api/…​;. Those URLs are now generated absolutely.

The native launchpad login screen was missing the show password option.

It was not possible to create a custom ui5 control based on sap.m.StepInput & sap.m.SearchField. This is now possible.

Version control for UI5 attributes in the App Designer has been improved. Now the App Designer will present attributes relevant for the UI5 version set in the app settings. You will still need to build and activate your applications on the version you intend to run them on in the Neptune Launchpad/Fiori Launchpad. If you activate an app and use an attribute at design time that is not available in the runtime UI5 version, you will get an error.

It’s now possible to create an application with only scripts in it and no UI5 objects.

Plugins are now copied from the template application.

When using Microsoft Azure as authentication type in a Mobile Client and assigning an ICF Subnode to it the neptune_login_ping call was not considering the icf subnode. This is now resolved.

When active app title is enabled in a Neptune PWA or Mobile Client, the title would not show after a second unlock.

When a PWA or a mobile is running offline, live tile applications was not loaded.

The Cookiemaster plugin is not working properly for iOS, causing issues with multi-user scenario with Azure AD logon. Cookies are now cleared by using the cache busting provided by InAppBrowser. There are two cookie storages HTTPS and WK and this will clear WK.

When deleting an application in the Web App Designer, an "Application does not exist!" error message would be displayed beneath the Open App dialog.