Customize the Onboarding Flow

The onboarding flow is comprised of the following UI components:

• End user license agreement (EULA) screen
• Activation screen
• Authentication screen
• Set passcode and verify passcode screens
• Usage consent screen and crash report consent screens.

The visibility and the content of each screen will vary depending on the different application configurations and client code customization.

In this section, we explain the onboarding-related callbacks in FlowStateListener based on the WizardFlowStateListener class generated by the SAP BTP SDK Wizard for Android.

Please see Flows Extension Point and FlowStateListener in the Flows Component of SAP BTP SDK for Android for detailed information on all of the flow states and callbacks.

The FlowActionHandler class allows you to insert your own logic at certain points in the onboarding flow, such as adding your own passcode validation or barcode validation after the default rules are executed, adding an algorithm for user name or email obfuscation when displaying the user information, or adding a parser for barcode content when scanning QR codes, etc.

Similar to the FlowStateListener, you need to extend the FlowActionHandler class to implement the corresponding methods and set your own FlowActionHandler instance for the FlowContext instance using the FlowContext.setFlowStateListener(listener: FlowStateListener) method.

This section provides some sample implementations for the methods in the FlowActionHandler class.

Congratulations! You have learned how to customize an onboarding flow!