Internal Application Versions
Use Add Version feature to update versions of your internal applications to incorporate new features and fixes, test Beta versions, and comply with organizational compliance standards. Versioning has many benefits for testing and for compliance. You can push beta versions for testing purposes, allow Apple iOS devices to ‘roll back’ to a previous version. and also push approved or compliant versions of applications to devices.
When you select an application from the Resources > Apps > Native > List View page, the app detail view page is displayed. The Add Version feature is available on the MORE menu at the upper-right of the apps details page.
Note: The system can recognize a different version of an application without using the Add Version option. However, EXE, ZIP files can be some of the exceptions since the UEM console cannot interpret the package. If you add a different version of the application as if it were new, the system displays the Retire Previous Versions check box on the Details tab.
When adding a new version of an application, you can see the following in the Details tab:
- Uploaded UEM Version – This identifier is the UEM version you are uploading into the console.
- Assignments Copied From – This identifier is the version immediately preceding the uploaded version, from which the uploaded version inherits assignments.
- Latest version – This identifier is the highest numbered version in the console and it gets deployed to devices that enroll in the assigned group.
Versioning Example – Beta Testing
Deploy multiple versions to test applications. Upload a beta version of an application and deploy it to beta users at the same time you have a non-beta version available to your regular users. After you test the beta version, you can replace the existing, non-beta, version with the tested version.
Sourcing the App Version Value
Workspace ONE UEM gets the application version that displays in the AppVersion field from various places depending on the platform. You cannot upload duplicate versions of an app.
| Platform | Parameter | Found In |
|---|---|---|
| Android | versionName displays App Version but versionCode controls the ability to version | .apk package |
| iOS macOS |
CFBundleVersion CFBuildShortVersionString |
info.plist |
| Windows Desktop | Version=“X.X.X.X” | AppManifest.xml |
| Windows Phone | Version=“X.X.X.X” | WMAppManifest.xml |
Support for Revision Number in the Internal App Version
When you upload a lower version of an app when the higher version is already available on the console, you are required to maintain separate UEM versions of the app.
To eliminate the overhead of maintaining separate UEM versions, internal app version numbers now include a fourth decimal place, which is the revision number.
With the availability of the fourth decimal place, you can do the following without modifying the UEM version:
- Upload an application’s lower version to the console when a higher version is already uploaded.
- Upload apps with four decimal version numbers.
- Upload apps with the same version but different build numbers. The fourth number is automatically incremented after each successful app build.
Note: The internal version number of any apps that were previously uploaded remain unchanged.
App Version and Incrementation
You can upload multiple versions of an application no matter the App Version number, but for most platforms, the App Version controls the application’s deployment. Workspace ONE UEM manages the Uploaded UEM Version depending on its App Version value.
| Platform | App Version |
|---|---|
| Android | versionCode must increment up because downgrading versions is not supported. Workspace ONE UEM can accept applications with lower versionCode values. However, it manages the assignments based on the order of the App Version. For example, if you have deployed an App Version 3.1 of an application, you have an older App Version 1.1 still in the console, and you upload App Version 2.1, Workspace ONE UEM manages the versions with these behaviors: Migrates assignments from version 1.1 (Assignments copied From) to 2.1 (Uploaded UEM Version). If devices have 2.1 and 3.1 assigned (and both are active), Workspace ONE UEM sends install commands for 3.1 (latest version) since that is the highest version that devices are eligible to receive. When you select Retire the Previous Version at the time of uploading 2.1, the console retires 1.1 (Assignments copied From) and not 3.1 (latest version). |
| iOS and macOS | BundleVersion or the BuildShortVersionString can increment up or down because downgrading versions is supported. Note: macOS does not support downgrading to a lower version of an app. You can upload a lower version of the application and push it as the available version. |
| Windows Desktop | App Version=“X.X.X”, the first three decimals, must increment up because downgrading versions is not supported. Workspace ONE UEM can accept applications with lower App Version values. However, it manages the assignments based on the order of the App Version and migrates assignments from the previous version to the Uploaded UEM Version (the one you are uploading). If devices have the Uploaded UEM Version and the latest version assigned (and both are active), Workspace ONE UEM sends install commands for the latest file version since that is the highest version that devices are eligible to receive. When you select Retire Previous Version at the time of uploading the new file version, the console retires the previous version and not the latest version. |
| Windows Phone | Version=“X.X.X.X”, the first four decimals, must increment up because downgrading versions is not supported. Workspace ONE UEM can accept applications with lower App Version values. However, it manages the assignments based on the order of the App Version and migrates assignments from the previous version to the Uploaded UEM Version (the one you are uploading). If devices have the Uploaded UEM Version and the latest version assigned (and both are active), Workspace ONE UEM sends install commands for the latest file version since that is the highest version that devices are eligible to receive. When you select Retire Previous Version at the time of uploading the new file version, the console retires the previous version and not the latest version. |
You can deploy multiple versions to test applications. Upload a beta version of an application and deploy it to beta users at the same time you have a non-beta version available to your regular users. After you test the beta version, you can replace the existing, non-beta, version with the tested version.
Manage Version Control of Your Internal Application
The version control allows you to manage changes to files over time. Workspace ONE UEM uses two different version values to manage version control of internal applications. The App Version number is the coded version set by the developer of the application. The UEM Version number of the application set by the Workspace ONE UEM console. It is derived from the App Version number and is used to determine the order of all versions in the console so that assignments can be properly inherited.
Maintain Multiple Versions of Your Internal Application
You can control versions of internal applications with Add Version and Retire Previous Versions. Workspace ONE UEM can replace an internal application on devices but it does not deploy multiple versions to devices. You can have multiple, active versions in the console for management. Replacing a retired version depends on the App Version value. If you want multiple versions of an application in the UEM console do not select the Retire Previous Version check box on the Details tab. This check displays when you add a version of an application. If you do not select Retire Previous Version, and you add an application version, Workspace ONE UEM assigns the higher App Version to devices. You can Deactivate application versions rather than retiring them to remove them from device assignments.
Complete the following steps to manage multiple versions of internal application in the Workspace ONE UEM console:
- Navigate to Resources > Apps > Native and select the Internal tab.
- Click the application, and go to Detail view and select Add Version.
- Upload the updated file.
-
Configure the Retire Previous Versions check box on the Details tab.
Setting Description Enable Retire Previous Version Workspace ONE UEM unassigns the lower App Version and assigns the higher App Version to devices. The lower version is not available for the deployment in the Workspace ONE UEM console.
Apple iOS is the exception. These devices can receive lower App Version assigned through retiring previous versions in the Workspace ONE UEM console.Disable Retire Previous Version Workspace ONE UEM unassigns the lower App Version and assigns the higher App Version to devices. If it is still Active, the lower version is available for deployment in the Workspace ONE UEM console. -
Select Save & Assign to use the flexible deployment feature.
Roll Back Versions Using Retire and Deactivate
Workspace ONE UEM uses the Retire Previous Version option to roll Apple iOS applications back to a previous version that is marked active. Rolling back versions depends on the Version value. Workspace ONE UEM pushes the application version with the previous Version number, not the previous App Version number.
You can roll back versions using Retire and Deactivate.
- When you Retire an application, the results might vary depending on the presence of other active versions and the Push Mode of the active versions.
-
When you Deactivate an application, Workspace ONE UEM removes it from the devices it is assigned to at the specified organization group and all its child organization groups.
If there is a lower, active version of the application, then that lower version pushes to devices. If there is a higher numbered version in a higher organization group, that version is still available to devices.
Protect Production Version of your Proprietary Application
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.
