Skip to Content

SAP Fiori Launchpad Notification Center badge number doesn't update in SAP Fiori Client

Hi community!

I've been implementing Notification Center for SAP Fiori Launchpad (FLP) in SAP Cloud Platform Portal, according to this documentation:

(SAP Gateway configuration) https://help.sap.com/viewer/68bf513362174d54b58cddec28794093/7.51.1/en-US/624c610308344f0eb2452b544f969a20.html

(SCP Portal configuration) https://help.hana.ondemand.com/cloud_portal/frameset.htm?ff2c8359cc5b46dda26712387ebba7aa.html

I've got it working fine while accessing the FLP via a browser (e.g. Chrome). When sending a notification from SAP Gateway, the FLP Notification Center badge gets updated automatically.

The problem is when accessing the FLP from Fiori Client (for Android & iOS). The Notification Center badge doesn't get updated automatically. I have to reopen the Fiori Client app for it to appear.

Browser:

Badge number updates automatically

iOS:

Badge number doesn't get updated automatically

Do anybody know if this is a bug or intended? Or any workaround?

Thanks in advance!

browser.png (10.3 kB)
ios.jpg (23.7 kB)
Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    Nov 20, 2017 at 03:41 PM

    Well, reading the Fiori Launchpad Notifications Service source code I found this comment:

    Fiori Client doesn't update if new notifications are sent (via Notification Hub) but they are updated if a push notification (via SCPms) is sent to the mobile device!

    Add comment
    10|10000 characters needed characters exceeded

  • Dec 06, 2018 at 01:48 PM

    Hi Christian! can you provide details of how you configured the notification hub to send the notifications to SCP's Launchpad? I successfully trigered notifications from the backend to the GW system but I don't know where I set in the GW system that the notifications must be propagated to SCP's Launchpad.

    Thanks a lot!

    Add comment
    10|10000 characters needed characters exceeded

  • Dec 07, 2018 at 02:05 AM

    Yeap I read them but they don´t mention where you set in the GW system that the notifications must be sent to the SCP launchpad. I've set in SCP the destination and Cloud Connector pointing to GW, and all the configuration in both the GW and S4 systems. I triggered the notification from S4 successfully....but something is missing...how does the GW system know that the notification must be propagated to SCP?

    Thanks for replying!

    Add comment
    10|10000 characters needed characters exceeded