Building a central Launchpad using SAP Launchpad Service – Enabling Notifications
|Building a central Launchpad using SAP Launchpad service on SAP BTP
[Update 2021]: Note that this asset was created before our branding changes related to SAP technology were announced on January 2021. Note that SAP Cloud Platform Launchpad was renamed to SAP Launchpad service, and SAP Cloud Platform Portal was renamed to SAP Cloud Portal service
[UPDATE: 23-Aug-2022]: The Supported S/4HANA version required to enable notification is SAP S/4HANA OP-1909 (SAP_GWFND-754 SP06) or above.
[Update Nov-2022]: Please note that this blog was published prior to the re-branding related to SAP Build portfolio, which was announced at SAP TechEd 2022. SAP Launchpad service and SAP Work Zone come together under the SAP Build Work Zone brand, with two editions: standard edition (formerly SAP Launchpad service) and advanced edition (formerly SAP Work Zone). You can learn more in this announcement blog post: SAP Build Capabilities Explained | SAP TechEd | SAP News Center
Notifications are a great way to make users aware of the situation and get their attention.
Recently, the Launchpad service on SAP Business Technology Platform (BTP) has been enabled to display notifications from custom apps as well as SAP solutions like S/4HANA on-premise & cloud. Some of you may recall that this capability used to be available as part of the Fiori 2.0 Notification center which is part of the Portal service running in the Neo environment. Since then, there has been lot of updates to the Notification channels and this blog post will give you a glimpse of how the notifications can be enabled on the Launchpad service (Cloud Foundry environment). To use this notification capability, you would need to be on SAP S/4HANA 2020 (SAP_GWFND-755) or above. Please refer to the SAP Help documentation and SAP Note 3005409 for changes in the per-requisites.
The configuration steps for enabling Notifications are documented in SAP Help documentation
My colleague Jocelyn Dart had previously provided an overview of the Notification Center. Most of the concepts around how to setup the backed SAP system for workflow/situation handling remains the same. As mentioned in blog post post, there are 3 components which you need to know for Notifications:
- Notification Providers: are enabled and registered in your backend system – For example: Workflow provider, Situation provider etc. These providers will send notifications whenever an event happens in the backend system to the Notification Hub
- Notification Hub: collects and distributes notifications to various channels – Email/Websocket(on-premise Launchpad)/Cloud (services running on SAP BTP including Launchpad service)
- Notification Center: is the client which receives the notifications. This would be the Fiori Launchpad or Mobile apps
Within the Site Manager of your Launchpad service, you will now be able to see the Notification settings. This will be required for the trust setup with the backend SAP system.
Within the site settings, you will now see an option to show notifications.
Once this is enabled and you start receiving notifications, you can personalize them within the settings (at runtime)
The setup and configuration is documented in this SAP Help documentation. You will need to configure RFC destinations, setup Notification Channel Hub and also update your runtime destinations in SAP BTP.
Once your configurations are in place, you can test the notifications using the demo transaction shown below.
Here is how the notifications will start to appear under the bell icon within your Fiori Launchpad. I have both the screens displayed side-by-side in the animated gif below.
Many thanks to my colleague Thilo Berndt for helping me with the setup.