A proprietary, non-store, Workspace ONE UEM application, like Secure Launcher, is seeded or included in the Workspace ONE UEM instance. It is part of the Workspace ONE UEM Installer and you deploy it to devices with a profile or with other settings in the console. Some enterprises want to test versions of these applications before they deploy them to production. You can add a proprietary Workspace ONE UEM application to the Workspace ONE UEM console for testing using test groups to keep the application separate from your production environment.

Workspace ONE UEM includes safeguards to prevent the removal of production versions of Workspace ONE UEM proprietary applications when you remove the test versions from the console. You can add and remove the test version by following a specific task order. Consider the following best practices when you remove the test versions from the console:
  • Whenever possible, test applications in a separate environment with a testing instance of theWorkspace ONE UEM console.
  • Workspace ONE UEM always uses the application ID to identify the test version of the proprietary application. When you use the application removal command, remove the test version before you retire or delete the application. If you skip this step, Workspace ONE UEM does not queue application removal commands for these test applications.