This time we have put the following features into the release:
- EDIT: HCP Subscription hidden
- New Version Schema
- Enhanced Data on Application Overview Screen
- Capability based Push Enhancements
- One Time Passcodes
- Active User GLAS reporting
HCP Subscription hidden
This is just a configurational change in the trial landscape and not really a feature. As of now, the HCPms Admin Cockpit (HTML5 App) and the HCPms core (JAVA App) is not longer visible in the HCP Cockpit under “Subscriptions”, this is to prevent accidentally changes on the trial subscription for HCPms. You can manage and access HCPms subscription under “Services”.
New Version Schema
As of today we use a new versioning schema to label our releases. While the “16” indicates the year, “02” indicates the month of the release. This is inline with the SAP cloud versioning.
Enhanced Data on Application Overview Screen
Sometimes small improvements take a long time to mature. As a product manger I was trying to put these “feature” in for a real long time, but due to it’s minor priority it was constantly shifted from one release to another. At some point in time you have to really push the small things as well – otherwise they will contaminate your backlog. And finally, we have enriched the information on the Application Overview screen to show the URLs that the developers want to know, like Onboarding URL, Application URL that is the result of your configuration, push API URLs and more:
|used to configure your app|
Mobile App URL
|endpoint created by this App configuration, used within the App to access the Primary Back-End URL|
|Subscription based Push API (NetWeaver/OData feed subscription callback URL)|
Enhanced Push API URL
|Push API that let’s you send notifications too e.g. all users of an App|
|URL where you send your POST request to get an APPCID|
And this is how it looks like:
Capability based Push Enhancements
Maybe you already have seen the Capability based push scenario that mainly applies to Fiori Launchpad based applications. You can read more about that here: help.hana.ondemand.com
With this release of SAP HANA Cloud Platform mobile services we have extended the flexibility to handle the badge numbers you want to send to your mobile app that is comprising multiple push notification receiving apps. If you have such an application the back-end system typically has no clue about this and can only see the “capability”, which serves as an abstraction layer to the one-to-one push. This layer is entirely located on HCPms.
So with this release the back-end can attach a badge number per capability, which results in better and more accurate badge numbers on the mobile device, since HCPms will calculate the correct badge number for your app.
Let’s assume you send:
to the user “Peter”. Now, HCPms examines the capabilities for Peter that are registered. Currently Peter has an App that is registered for “capability2” and “capability3”, so HCPms send a notification to Peters device A with a badge count of 2. On Peters tables (device B) there is an App that is registered for “capability1” so another notification is send to device B with a badge count of 2.
One Time Passcodes
If you want to use one time passcodes to let your users enter your app, you can easily enable OTP in the Admin UI:
Unfortunately, that is only half of the story. There are some prerequisites to match before you activate this configuration.
This whole scenario is based on the assumption that you have configured your HCP account to use the SAP Cloud Identity Service to authenticate your mobile users. In addition, you need to use the SAP Authenticator App. So in order to use OTP you need:
- SAP HANA Cloud Platform mobile services
- SAP Cloud Identity Service
- SAP Authenticator
- A Mobile App using the Logon Component of the SAP Mobile SDK (SP11 PL01)
Then you need to establish trust between all parties according to the various guides.
Once you have setup all the prerequisites, your users will be challenged with an OTP whenever the users’ session need to be renewed.
Please make sure that the tradeoff between security and usability fits to your use case. For example, it would make no sense to use OTP in a B2C like application displaying public available product information. If you have a high security mobile app with sensitive data that then this feature is a perfect fit to your use case.
Active User GLAS Reporting
For all customer who are interested in a B2C license for HANA Cloud Platform mobile services, we have introduced the licensing audit for our B2C license, based on “active users” as part of the GLAS auditing report.