Tell us what you think

We want to create the best possible experience for our learners. Your feedback helps us to improve the experience for everyone.

SAP Learning Journey

Onboarding End Users

Objectives

After completing this lesson, you will be able to:

Overview

The last three units covered how the business content can be set up for access via SAP Build Work Zone, standard edition and the SAP Mobile Start app. Now it’s time to have a closer look at the native app itself.

For accessing the content using mobile devices, the users can be onboarded in two different ways:

Via QR code
Via Mobile Device Management (MDM) using managed app configuration

The second option is especially interesting for productive usage with lots of end users and where an MDM solution is in use.

Note

The app can be downloaded from Apple App Store, Google Play, and Tencent Appstore / 腾讯应用宝. The app is currently available for phones and tablets with Android 8 or iOS 15 and above.

Onboarding via QR Code

Each site created on SAP Build Work Zone, standard edition has an onboarding (Register) QR code; this can be obtained from the user settings by following the steps shown in the video:

Note

If you do not see the SAP Mobile Start Application tab in your user settings, you must enable (set to Yes) the SAP Mobile Start flag on the site settings using Site Manager.

When you open SAP Mobile Start app for the first time, you will see a Scan button on the initial screen. Choose the button to scan the above Register QR code for the site and follow the onboarding process.

Note

The Register QR code should be scanned using the SAP Mobile Start app, NOT the camera app on the device.

You have to log in with your user credentials and create a passcode that can be used for additional security. Once the onboarding process is finished, you can access the business content directly from the mobile device. The end-user credentials you use to log in to the app depends on the setup you followed for user authentication.

Hint

It is the same user that you used to access the site via the desktop using a browser in units 3 and 4.

If you used default identity provider (as in unit 3), it is a platform user
If you used Identity Authentication (as in unit 4), it is an Identity Authentication user

Onboarding via MDM Using Managed App Configuration

SAP Mobile Start supports onboarding based on mobile app configuration. In this case, the corresponding configuration can be pushed to end users via an MDM solution. The end users only need to click a Start button (instead of the Scan option) and directly start with the onboarding process to the configured site.

Prerequisite

An MDM solution that supports the following specifications:

For iOS, supports "Managed App Configuration"
For Android, supports "Enterprise App Restrictions"

Setup

SAP Mobile Start requires three different parameters/properties as part of managed app configuration. You can use the site URL to determine the parameter values required to onboard the mobile user. The site URL should have the following structure:

1. SAP Mobile Services Host

Property name	`com.sap.mobile.start.mobileServicesHost` The SAP Mobile Services host can be constructed by adding an "m" into the SAP Build Work Zone host of the site URL. This would look like:
Structure	`<tenant-subdomain>.m.launchpad.cfapps.<region>.hana.ondemand.com`
Example	`mytenant123.m.launchpad.cfapps.eu10.hana.ondemand.com`

2. Site URL

Property name	`com.sap.mobile.start.launchpad.launchUrl` The site URL is the same as the SAP Build Work Zone URL mentioned above. You should be able to copy it directly from the browser when you access the site. It looks like this:
Structure	`https://<tenant-subdomain>.launchpad.cfapps.<region>.hana.ondemand.com/site?siteId=<site-Id>`
Example	`https://mytenant123.launchpad.cfapps.eu10.hana.ondemand.com/site?siteId=678a6sd76a-bah1-as32-azdk1803hah`

3. Site ID

Property name	`com.sap.mobile.start.launchpad.siteId` Site ID should be set to the SAP Build Work Zone Site Id from the site URL.
Structure	The structure may vary, but in general it is blocks of numbers / characters divided by dashes "-".
Example	`678a6sd76a-bah1-as32-azdk1803hah`

With these three values, you will be able to move on with configuring the MDM solution. iOS and Android require different configuration settings, as outlined in the help documentation.

Note

The specific steps involved in the setup of managed app configuration can vary between the MDM solutions that are available in the market. Check the documentation for your MDM solution to implement the parameters mentioned in this section.

Next lesson