Skip to Content
Technical Articles
Author's profile photo Adam Harkus

Disabling the Fiori Launchpad timeout in SAP Cloud Platform Portal

After 20-minutes of inactivity, the Fiori Launchpad session is timed out by default, disconnecting all oData services and requiring a refresh to proceed, not ideal if your end-user is in the middle of data entry, etc.

At the moment, disabling the timeout is only achievable through what’s called a Shell Plugin app, which is a SAPUI5 app that runs in the background of the Launchpad.

The official online guide will get you partway there, but there are some vital omissions…


Here’s my template below, simply copy this in place of the generated Component.js file.

<namespace> on the guide is launchpad.timeout.launchpadtimeout or <namespace>.<app name>

I’ve reconfigured the <URL> in the guide to work for all your SAP Cloud Platform Sub-Accounts (e.g. Dev, Test, and Prod).

], function (UIComponent, Device, models) {
	"use strict";

	return UIComponent.extend("launchpad.timeout.launchpadtimeout.Component", {

		metadata: {
			manifest: "json"

		 * The component is initialized by UI5 automatically during the startup of the app and calls the init method once.
		 * @public
		 * @override
		init: function () {
			// call the base component's init function
			UIComponent.prototype.init.apply(this, arguments);

			// enable routing

			// set the device model
			this.setModel(models.createDeviceModel(), "device");

			// make a request to the server every 15 minutes
			setInterval(function () {
				//Get the SAP Cloud Platform Sub-Account
				var href = $(this).attr('origin');
				var split1 = href.split("-"); // split by - 
				var secondSubString = split1[1]; // all characters AFTER the first -
				var split2 = secondSubString.split("."); // split by . 
				var subAccount = split2[0]; // all characters BEFORE the first .
					type: "HEAD",
					cache: false,
					crossDomain: true,
					uri: "https://flpnwc-" + subAccount + ""
					function (result) {"pingServer", "Successfully pinged the server to extend the session");
					function () {"pingServer", "failed to ping the server to extend the session");
			}, 900000); //15 minutes



Apart from the above, follow the official guide and the app should fire every 15 minutes, disabling the timeout!

I hope you found this blog post useful!




Assigned Tags

      1 Comment
      You must be Logged on to comment or reply to a post.
      Author's profile photo Daniele Baldo
      Daniele Baldo

      Hello Adam,
      Thank you for the tip.

      I have a fiori App on  SCP Launchpad that calls a xsodata service in background once every minute, with no user interaction
      so i would expect no session timeout, because calling a service is an activity, even if there is no user itneraction;  but after 20 minutes session disconnection occurs.

      Do you have any Idea why this happens?
      what  "20 minutes of incactivity" does exactly means?