Enable Multi-User for Your Android Application

Open the previously created project from wizard generation.

In Android Studio, on Windows, press Ctrl+N, or, on a Mac, press command+O, and type WelcomeActivity, to open WelcomeActivity.java.

On Windows, press Ctrl+F12, or, on a Mac, press command+F12, and type startFlow, to move to the startFlow method. For the FlowContext instance, change the parameter of the method setMultipleUserMode from false to true.:

FlowContext flowContext = new FlowContextBuilder()
            .setApplication(appConfig)
            .setMultipleUserMode(true)
            .setFlowStateListener(new WizardFlowStateListener(
                    (SAPWizardApplication) context.getApplication()))
            .build();

Notice that the setting will only take effect with the very first user onboarding. Once a user is onboarded,
this setting will be saved into local database, all flows afterwards will use the same setting from the database and ignore the one inside flowContext. To change this setting, you need reset application to bring up onboarding process, and the new setting will be updated into local database after onboarding.

Re-run (quit first) the app and notice that the onboarding process is same as single user mode, except that no biometric authentication screen is shown. After onboarding, put the app in background until the unlock screen appears. In multi-user mode, there is a button SWTICH OR ADD USER at the bottom of the screen.

Click the button, the user list is shown. You can either select existing user from the list or click the ADD USER icon on the right top of the screen. This will start the onboarding process for the new user.

Open the previously created project from wizard generation.

In Android Studio, on Windows, press Ctrl+N, or, on a Mac, press command+O, and type WelcomeActivity, to open WelcomeActivity.kt.

On Windows, press Ctrl+F12, or, on a Mac, press command+F12, and type startFlow, to move to the startFlow method. For the FlowContext instance, change the parameter of the method setMultipleUserMode from false to true.:

val flowContext =
            FlowContextBuilder()
                .setApplication(appConfig)
                .setMultipleUserMode(true)
                .setFlowStateListener(WizardFlowStateListener(activity.application as SAPWizardApplication))
                .build()

Notice that the setting will only take effect with the very first user onboarding. Once a user is onboarded, this setting will be saved into local database, all flows afterwards will use the same setting from the database and ignore the one inside flowContext. To change this setting, you need reset application to bring up onboarding process, and the new setting will be updated into local database after onboarding.

Re-run (quit first) the app and notice that the onboarding process is same as single user mode, except that no biometric authentication screen is shown. After onboarding, put the app in background until the sign in screen appears. In multi-user mode, there is a button SWTICH OR ADD USER at the bottom of the screen.

Click the button, the user list is shown. You can either select existing user from the list or click the ADD USER icon on the right top of the screen. This will start the onboarding process for the new user.

For offline application, enable Allow Upload of Pending Changes from Previous User option on server side first. Go to the SAP Mobile Services cockpit and select your application from the application list. Click Mobile Settings Exchange in the assigned features list:

Scroll down to the bottom of Client Configuration tab and enable Allow Upload of Pending Changes from Previous User option

Open the previously created project from wizard generation. Enable setMultipleUserMode for FlowContext instance same as online app.

In Android Studio, on Windows, press Ctrl+N, or, on a Mac, press command+O, and type OfflineWorkerUtil, to open OfflineWorkerUtil.java.

On Windows, press Ctrl+F12, or, on a Mac, press command+F12, and type initializeOffline, to move to the initializeOffline method. For the OfflineODataParameters instance, change the parameter of the method setForceUploadOnUserSwitch from false to true:

offlineODataParameters.setForceUploadOnUserSwitch(true);

For offline application, enable Allow Upload of Pending Changes from Previous User option on server side first. Go to the SAP Mobile Services cockpit and select your application from the application list. Click Mobile Settings Exchange in the assigned features list:

Scroll down to the bottom of Client Configuration tab and enable Allow Upload of Pending Changes from Previous User option

Open the previously created project from wizard generation. Enable setMultipleUserMode for FlowContext instance same as online app.

In Android Studio, on Windows, press Ctrl+N, or, on a Mac, press command+O, and type OfflineWorkerUtil, to open OfflineWorkerUtil.kt.

On Windows, press Ctrl+F12, or, on a Mac, press command+F12, and type initializeOffline, to move to the initializeOffline method. For the OfflineODataParameters instance, change the value of parameter isForceUploadOnUserSwitch from false to true:

val offlineODataParameters = OfflineODataParameters().apply {
            timeout = 5
            isEnableRepeatableRequests = true
            storeName = OFFLINE_DATASTORE
            currentUser = FlowContextRegistry.flowContext.getCurrentUserId()
            isForceUploadOnUserSwitch =
                true
            val encryptionKey = UserSecureStoreDelegate.getInstance().getOfflineEncryptionKey()
            val key = if (encryptionKey == null) {
                val encryptionKeyBytes =
                    EncryptionUtil.getEncryptionKey(OFFLINE_DATASTORE_ENCRYPTION_KEY_ALIAS)
                val defaultKey = Base64.encodeToString(encryptionKeyBytes, Base64.NO_WRAP)
                Arrays.fill(encryptionKeyBytes, 0.toByte())
                defaultKey
            } else encryptionKey
            storeEncryptionKey = key
        }.also {
            // Set the default application version
            val customHeaders = it.customHeaders
            customHeaders[APP_VERSION_HEADER] = appConfig.applicationVersion
            // In case of offlineODataParameters.customHeaders returning a new object if customHeaders from offlineODataParameters is null, set again as below
            it.setCustomHeaders(customHeaders)
        }

Re-run (quit first) the app. Notice that the onboarding process and add/switch user process are same as online app.