Refactoring of Android agent enrollment workflows

Content

• Completes device enrollment as a part of device provisioning - Executes device enrollment as a part of device provisioning to enforce management and policies before users start using the device. In the previous releases, users were able to skip the mandatory enrollment screens and then modify the security settings on the device.
• Fixes issues with Zero-touch parameters.
• Optimizes retry logic.
• Resumes enrollment after restart from where it left off.
• Centralized error handling
  
  • Displays a uniform error screen across all steps in the enrollment flow, with support to Retry and Abort.
  • Returns error messages relevant to the current enrollment step on the enrollment screen.

    Old Screen	New Screen

  • Displays the enrollment stages with the help of labels or titles, allowing users to easily track the progress of the enrollment. In the previous releases, only a spinning animation was displayed.

    Note: By default, the enrollment workflow changes are available for Device Admin, Profile Owner, SPS, Device Owner (token-based) enrollments only. Supported only on Android devices running OS version 7 and later.

  • After successful enrollment, if the configured policies have not reached the device, MaaS360 displays the text "Waiting to apply MDM policy" in the MaaS360 Settings > Enforced Policies.

    

  Enabling new enrollment workflows changes to other modes of enrollment

  Device Owner (DO) and Work Profile on Corporate Owned (WPCO)

  Add the following key-value pair to the QR code and Zero Touch JSON file when you create the enrollment configuration in the MaaS360 Portal.

  • Key: use_new_enrollment_flow
  • Value: true