For Appeon Workspace published on the online app store such as Apple App Store, Google Play etc., the upgrade is controlled by the online app store.
For Appeon Workspace built into the product and distributed in AEM, the upgrade is controlled by the Appeon Workspace itself. When PowerServer is upgraded, the Appeon Workspace installed on the mobile device will be automatically upgraded the next time when it connects with the PowerServer; unless you have turned off the Check for Workspace Updates option in Appeon Workspace. Refer to Checking for Appeon Workspace updates for how to enable it.
For Appeon Workspace that is created by the developer and distributed via AEM, the auto-upgrade feature will work when you do the following:
-
When you create the package of Appeon Workspace using the PowerServer Toolkit Package tool, the Support Workspace Auto-Upgrade and Check for Workspace Updates option in Appeon Workspace must be enabled.
Refer to the section called “Customizing and packaging Appeon Workspace” in PowerServer Toolkit User Guide for how to enable the Support Workspace Auto-Upgrade and Check for Workspace Updates option.
-
When PowerServer is upgraded, you will need to create an updated package of Appeon Workspace using the PowerServer Toolkit Package tool. Be sure to use the same package settings as before especially the Display Name and App ID Suffix (for iOS) or App Identifier (for Android) when creating the package. These settings as well as the build number (which is automatically obtained from the product) will be used in the file name of the package, and you should not change this file name, because Appeon Workspace checks the file name to determine whether it is a different build of the currently installed package. And only when the build number is higher than that of the installed package, the auto-upgrade feature will work.
Refer to the section called “Customizing and packaging Appeon Workspace” in PowerServer Toolkit User Guide for how to set the Display Name and App ID Suffix (for iOS) or App Identifier (for Android).
-
You will have to upload these packages via AEM, and AEM will record whatever information required for the auto-upgrade feature to work, for example, the package file name, the build number, the download URL etc., so that once Appeon Workspace connects with the PowerServer, Appeon Workspace can reliably check for the updated packages according to these information and then automatically get upgraded.
For details about how to upload files and set the download URL in AEM, refer to the section called “Mobile App Distribution” in PowerServer Configuration Guide for .NET.
The auto-upgrade feature of the standalone mobile app works in the same way too.
