When you edit an iOS or Android App Catalog app, the Push Notification field is also available. When Push Notification is enabled for an App Catalog, App Catalog users receive a notification when there are updates of the apps they have installed from the App Catalog.
With an iOS App Catalog app, Push Notification was disabled by default because you cannot enable it until you upload a Push Notification SSL Certificate. For more information on enabling Push Notification for an iOS App Catalog, see Push Notification for an App Catalog.
With an Android App Catalog, Push Notification was enabled by default when you added the App Catalog to Apperian. If you do not want to use Push Notification, clear the check box. Keep in mind, however, that Push Notification is an efficient and effective way to inform your users of app updates; Apperian recommends that you keep it enabled.
Push Notification is not supported with Web and Windows 8 App Catalogs.
Note that with all App Catalogs, available updates will be listed on the Updates page of the catalog; this is unrelated to Push Notifications.
When you edit a native application and upload a new binary file, Apperian creates a new version of the application. When you edit an iOS or Android hybrid app, Apperian creates a new version when you choose the Rebuild option. Each time you update an application, the date of the update, Version Number, Author, and Version Notes are recorded in a version history. You can view Version History and when you .
Rebuilding is required if you want to change the web URL for the hybrid app or modify its user interface options. You may also choose to rebuild the app's binary for other reasons. For example, you may want to rebuild the hybrid app using a new release of Apperian that takes advantage of more recent system architectures. For more information about hybrid apps, see Hybrid Apps (Delivering a Web App as a Native App).
Apperian stores up to 10 versions of an application. You may always want your users to have access to the latest version of an application, or you may want to assign different versions to different groups of users. For example, you can assign a beta version of an app to your Test group so they can test it while other groups continue to have access to the previous "production-ready" version. Access to older versions of an app also provides a way to "roll back" users to a previous version if a serious issue is found in an application. For more on managing multiple versions of an application, see Application Versions.
When you update an iOS or Android app (including hybrid apps), you can make the update mandatory to specify that users who have the app installed are required to update to the new version by a particular date. Users are prompted to install the update when they log in to the App Catalog, and are not allowed to continue using the App Catalog until they install all mandatory updates. You can also apply the Self Updating App policy to an app to prompt users to install an update when they launch the application, in addition to when they log in to the App Catalog. For more information on this policy, see Self Updating App.
For more information on deploying updates, see Managing Application Updates.
Before you upload a new version of a native app, make sure that you have the necessary file.
Expand the Applications field.
If you are updating a native (non-hybrid) application, click the button next the the Application Type checklist to browse and select a new application binary file.
(Optional for Android Apps and Hybrid Android Apps) Select the Add shortcut to Home screen when the user installs the app option if you want a shortcut for the app to automatically be added to the device's Home screen after the app is installed.
If this option is enabled for the App Catalog, the shortcut is created after the user installs the catalog and opens it for the first time. If the catalog was installed before you selected the option, the shortcut is created after the user Force Stops the catalog and re-opens it, or installs an update of the catalog.
(Optional) Under Application Type, specify the device form factor(s) on which the app can run. By default, an app is marked to run on any devices that have the appropriate capabilities. You can override the default setting and choose one or both of the Phones and Tablets options. For more information on these settings, see Override Device Form Factor.
If you modify the supported form factors for an app and there are users who have already installed the app on a form factor that is not supported with the updated version, those users will not receive a push notification nor will the app be listed on the Updates page of the App Catalog.
Update the Name, Version Number, and Author fields as needed. If you uploaded a new application, those fields default to the value in the application file.
(Optional; displays only when adding an iOS or Android app) Select or clear the Mandatory for All Assigned Groups check box. When selected, the app will be mandatory for users in any of the groups to which the app is assigned. If you want to make the app mandatory for certain groups only—not all assigned groups—do not select this option. Instead, select the Mandatory option next to the desired groups in the Groups section.
If an app is mandatory, users are required to install it before they can use the App Catalog. When a user logs in to the App Catalog, the following message box displays prompting the user to download all mandatory applications.
Note that if a user's device does not meet the app's minimum OS requirement, the app is not treated as mandatory. Also, if the user has already installed the application, the Mandatory setting has no impact. Use the Application Update Settings (step 11) to require users who have already installed an app to install the update.
(When updating an iOS app file) Under Notify Users, select an option for notifying iOS App Catalog users about the update. This is called a "push notification." A push notification performs two tasks:
Which Notify Users options are available depends on whether you are updating an app that is signed for Ad Hoc distribution or Enterprise distribution.
Ad Hoc Distribution: If the app is signed for Ad Hoc distribution, choose one of the following options:
Notify all users
Notify all App Catalog users who have installed the app.
Notify new users
Notify all App Catalog users whose UDID (Unique Device Identifier) has been added to the iOS Distribution Provisioning Profile since the app was added or last updated.
Do not notify users
Do not notify any App Catalog users about the update.
These push notification options are not supported for Ad Hoc-provisioned apps on devices running iOS 7, but those device users will still see the update listed on the Updates page of the App Catalog.
Enterprise Distribution: If the app is signed for Enterprise distribution, select the Send push notification to App Catalog check box to notify all users who have installed the app. Clear the check box if you do not want to notify any App Catalog users about the update.
Regardless of which Notify Users option you select, a user will receive a push notification only if the user is running an App Catalog for which the Push Notification feature is enabled. For information on enabling Push Notification, see Push Notification for an App Catalog.
(When updating an iOS or Android app file) Complete the Application Update Settings to make an update mandatory or optional for users who have already installed the application.
To make the update mandatory, select one of the following options:
When an update is mandatory, the following message box displays when a user logs in to a native App Catalog (or launches the App Catalog, if already logged in); the user cannot continue to use the App Catalog until all mandatory updates are installed. Note that this message does not display when the user is logged into the web App Catalog. Also, if a user's device does not meet the app's minimum OS requirement, the app is not treated as mandatory.
|To leave it up to the user to decide when and if to update, select Set to never. The user can, at any time, install the update via the Updates page of the App Catalog.|
Expand the Groups field and then follow these steps to modify the app's group assignments. When the application is Enabled, members of the assigned groups will be able to access the application in App Catalog. You can also assign an app to a group when adding or editing the group. For more information on groups, see Managing Groups.