Following several customer requests, we have simplified and improved the functionality of the SAP Fiori launchpad shell plugin with the Slipstream Engine component that ships with SAP Screen Personas 3.0 Service Pack 10 release. We introduced the Slipstream Engine component with service pack 6 to enable rendering of SAP GUI transactions on mobile phones and tablets. In this blog, when I refer to Slipstream Engine or an application running in Slipstream Engine, I am talking about an ERP transaction in SAP S/4HANA or ECC that is using Slipstream Engine for rendering, rather than SAP GUI for Windows or SAP GUI for HTML.
The new SAP Fiori launchpad plugin behavior for in service pack 10 includes:
- A confirmation prompt that is displayed when users navigate away from Slipstream Engine in SAP Fiori launchpad
- The standard SAP Fiori launchpad shell back button in Slipstream Engine can now be made to function exactly as the back button present in the loaded classic SAP GUI transaction.
This blog serves to provide more information about these features, as well as how the features can be disabled/enabled according to users’ needs.
The confirmation prompt that opens when users close a Slipstream Engine application is a measure intended to prevent potential data loss when users accidentally navigate away from transactions by pressing the back button in the SAP Fiori launchpad shell. This feature is enabled by default for all Slipstream Engine tiles, but it can be switched off globally or individually for specific tiles.
To suppress the navigation confirmation prompt, use the
parameter in the SAP Fiori launchpad Designer.
- To disable the confirmation message for a given tile: Apply the parameter to the Slipstream Engine Tile Configuration.
- To disable the confirmation message globally: Apply the parameter to the Slipstream Engine Target Mapping. This will block the message for all tiles that point to this target mapping
The functionality of the standard SAP Fiori launchpad shell back button in Slipstream Engine has now been simplified to ensure it functions similarly to the back button present in the given transaction. This includes transaction screen specific features, such as triggering various confirmations and data validation checks to ensure integrity when users navigate back to previous screens in their process. This means that the SAP Fiori launchpad shell back button assigned to a transaction rendered with Slipstream Engine will work in the same way that the back button on a classic SAP GUI transaction rendered outside of SAP Fiori launchpad would.
In situations where the back button is not present or disabled for a given screen – the SMEN transaction, for example – pressing the SAP Fiori launchpad shell button will trigger navigation to the previous intent, which is usually the SAP Fiori launchpad home page.
You can create similar functionality with other transactions accessed through SAP Fiori launchpad by disabling the screen back button in the SAP Screen Personas flavor.
To do so:
- Navigate to the screen that is the landing page for the Slipstream Engine SAP Fiori launchpad tile in the Slipstream Engine standalone service.
- Open the SAP Screen Personas Flavor manager.
- Select the desired flavor and open the Flavor editor.
- Select the Dynpro back button (“wnd/tbar/btn“).
- From the Home tab, select: More Options > Read Only.
- Save the changes.
Now, when the screen is loaded in Slipstream Engine and users press the SAP Fiori launchpad shell back button, they will be taken to the home page instead of the previous step in the transaction’s workflow.
The recent changes for the Slipstream Engine Shell plugin introduce additional measures and simplifications to ensure consistency and data integrity, as well as prevent accidental data loss when working with classic SAP GUI transactions rendered using Slipstream Engine in an SAP Fiori launchpad environment.
Setting Up the Slipstream Launchpad Plug-In for On-Premise SAP Fiori Launchpad:
Setting Up the Slipstream Launchpad Plug-In for Cloud Portal Launchpad: