Page tree
Skip to end of metadata
Go to start of metadata

 

From the Applications page of the EASE Portal, you can edit an application to:

  • Modify the metadata associated with it (for example, its description).
  • Modify attributes such as whether it is enabled, mandatory, and available for Direct Install.
  • Modify group and category assignments.
  • Change the files associated with it (icon, media files, and screenshots).

If you are editing a native iOS, Android, Windows Phone, or Windows app, you can also upload a new application binary to create a new version of the app. 

If you are editing an iOS or Android hybrid app, you can choose the Rebuild option to generate a new version of the application binary—saving any modifications you made to the web URL, user interface option, or access lists.  
  

Edit the Application

To edit application information:

  1. On the EASE Portal navigation bar, click Applications. Use the Search box to search for a specific application.
     
  2.  

    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 EASE. 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, Windows 8, and Windows Phone 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.

     

Update an Application

When you edit a native application and upload a new binary file, EASE creates a new version of the application. When you edit an iOS or Android hybrid app, EASE creates a new version when you choose the Rebuild option.
  

 Click here to understand when rebuilding a hybrid app is required...

Rebuilding is required if you want to change the web URL for the hybrid app, or modify its user interface options or access lists (whitelist and blacklist). 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 EASE that takes advantage of more recent system architectures. If you have any questions about when a rebuild may be recommended, contact support@apperian.com.  For instructions on editing and rebuilding a hybrid app, see Edit or Update an Application.

 
EASE 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. With a mandatory update, you can optionally apply the Application Update Compliance policy to enforce that the mandatory update is installed within a defined grace period. For more information on applying a grace period, see Application Update Compliance. 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 Begin

Before you upload a new version of a native app, make sure that you have the necessary file.
  

 Click here for details...
When updating this application type...You will need...
iOS App (IPA File)

A new version of the IPA (.ipa file) for the application. This file must contain a bundled .mobileprovision file (distribution provisioning profile). The provisioning profile is bundled with the app during the signing process; for more information, see Distribution Provisioning Profiles.

Android App (APK File)A new version of the APK (.apk file) for the application. Note that if the APK was built using Xamarin Studio, check that it meets the requirements described in Xamarin Application Requirements.
Windows Phone App (XAP File)A new version of the XAP (.xap file) for the application. Before the app can be distributed to your App Catalog users, it must be signed with the same enterprise certificate used to sign the Windows Phone App Catalog. If you upload a XAP that is signed with a different certificate, you can download a signing package to re-sign it after it is uploaded. For instructions, see Use the Signing Package.
Windows Installer (MSI File)A new version of the MSI (.msi file) for the application. For more information on this file type, see Windows Application File Formats.
Windows App (ZIP File)A new version of the ZIP (.zip file) for the application. For more information on this file type, see Windows Application File Formats.
Windows Executable (EXE File)A new version of the EXE (.exe file) for the application. For more information on this file type, see Windows Application File Formats.

To update an application:

  1. On the EASE Portal navigation bar, click Applications
     
  2. Click the Edit link by the hybrid application you wish to edit. 
     
  3. Expand the Applications field.
     

  4. 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.

     If you are updating a hybrid application, click here...
    1. If you want to rebuild the hybrid application, scroll down to select the Rebuild option below the Author field. You must select Rebuild if you want to modify the application's web URL and other hybrid app options, such as whether to show a navigation bar at the top of the web view.
       

    2. (Optional) In the Web URL field, enter a URL (up to 1024 characters) for the web application. Be sure to enter the complete URL, including the scheme/protocol name. HTTP and HTTPS protocols are supported.

    3. (Optional) Modify these options to change the behavior of the hybrid app. 

      OptionPlatformDescription
      Show navigation bar at top of web viewiOS & Android

      Select this option if you want a navigation bar to show in the web view of the app on the user's device. The navigation bar will include Back, Forward, and Reload Page buttons.
       

       Click here for an example...

      Allow links to open new tabsiOS only

      Select this option to specify that links open in a new tab within the web view rather than re-use the current tab. If the user later closes the new tab, focus returns to the original tab. Note that this option is designed to work only with links that are defined with the JavaScript window.open method; other types of links will open in the current tab. For developer details on creating links with this method, see Window open() Method.
      _

       Click here for an example...

      Allow app to open files in other appsiOS & Android

      Select this option if you want users to be able to tap on links in the hybrid app to open files in other apps. For example, if the app links to a PDF file, the user will be able to choose to open that file in any PDF viewer app available on the device. If you do not enable this option, the hybrid app will instead attempt to open the file directly in the webview. Note that in a hybrid Android app, the webview cannot open PDF files, so you should enable this option if the app includes links to that file type.

      With iOS, this feature supports multiple file types. With Android, it currently supports PDF files only. If you want your hybrid Android app to open different files types in other apps, please contact support@apperian.com.

      _

       Click here for an example on iOS...

       

       Click here for an example on Android...

       

      Enable access listsiOS & Android

      Select this option to define or modify access lists that will control a user's access to URLs while working in the application. Once you check this box, Whitelist and Blacklist fields display.

      • A Whitelist authorizes access to the specified list of URLs only. When users are using the app, they cannot access any URLs that do not match entries in the whitelist. The Web URL for the hybrid app is always whitelisted.
          
      • A Blacklist blocks access to the specified list of URLs, even if those URLs are also in the whitelist.
      • Each field can include a maximum of 512 characters.
      • Separate URLs with commas.
      • Enter URL patterns in the form Scheme://Domain/Path.
      • Scheme can be http or https.
      • Domain is the host domain. For example: example.com
      • Path is optional. It can be a directory or web page.
      • The * wildcard is valid in the Domain or Path. For example: http://*.example.* or https://doc.example*

      Once you type in the Whitelist or Blacklist field, the Unauthorized Access Page URL field displays. Use it to specify the page to which users will be redirected when they try to access an unauthorized page.

     

  5. (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. 

  6. (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.

     

  7. Update the NameVersion Number, and Author fields as needed. If you uploaded a new application, those fields default to the value in the application file.

  8. In the Version Notes field, enter a description of the update.
     
  9. (Optional) Select or clear the Enabled check box to enable/disable the app. A disabled app and its associated media files do not display in the App Catalog for any users unless the app is sent on an approval process workflow. During a workflow, members of the group assigned to the workflow will be able to access the app from the App Catalog, regardless of whether the application is enabled or disabled.

    If you are updating an iOS app after policies were applied to it, this check box will be cleared; you cannot select it unless you are uploading a version of the app that was signed after policies were applied to it.
     
  10. (Optional) Select or clear the Direct Install check box to enable the application for direct install. For information on the Direct Install feature, see Delivering Applications via a Direct Install URL
     
  11. (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 onlynot 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.
     

  12. (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:
     

    • Flags the App Catalog icon on the user's Home screen with a notification badge that identifies the number of updates available.
    • Lists the updated app on the Updates tab in the user's App Catalog.


    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.

    _

  13. (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.

    Mandatory
    Update
    1. To make the update mandatory, select one of the following options:

      • Set to today prompts users to install the update the next time they log in to the App Catalog.

      • Select a specific date in the calendar field to prompt users to install the update when they log in to the App Catalog on or after that date.

      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.
    2. (To enable the Application Update Compliance policy) Select the Revoke access to the app catalog and apps wrapped with Enterprise SSO check box, if it is not already selected, and then choose the number of days for the grace period. The number defaults to the number selected for the Application Update Compliance policy on the Policies page. The grace period starts after the update becomes mandatory. For example, if in the previous step you set the mandatory date to June 1, 2014 and then you select a compliance period of 30 days, the grace period will start on June 1, 2014 and end at 12:00 a.m. GMT on July 1, 2014. Every day at 12:00 a.m. GMT, EASE checks that all mandatory updates have been installed within the grace period. On devices where updates have not been installed within the grace period, EASE automatically revokes access to the App Catalog and any apps wrapped with the Enterprise SSO policy. If all devices for a user are noncompliant, EASE also disables the user.


      Note: If this option is not displayed, it means the feature is disabled for your organization. To enable the feature, contact Apperian Customer Support.
    Optional
    Update
    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.

     

  14. Click OK to save your changes.
     

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 view details about the application.

Change Group Assignments

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.

  1. Select or deselect groups. 

    When you select a group, it assigns the "Latest version" of the application. "Latest version" means that members of the group will always have access to the latest version of the app in the App Catalog. When you edit an application, you may see that some groups have a specific version assigned to them rather than "Latest version." When there are multiple versions of an app, you can assign a specific version to a group while adding or editing the group; you cannot assign specific versions to a group while editing the application. For instructions on assigning a specific version, see Add a Group or Edit a Group


  2. (Optional) To make the application mandatory for a group, select the checkbox in the Mandatory column. Note that you can mark an app as mandatory for specific groups only if the Mandatory for All Assigned Groups is not selected. If there is a check in the Mandatory column for all selected groups and you want to make the app mandatory for only some of those groups (or none of them), scroll up to expand the Applications field and clear the Mandatory for all Assigned Groups checkbox.



When an application is sent on an approval workflow, users in the group assigned to the workflow (on the Settings page) are able to access the application from the App Catalog. Group access during a workflow is separate from the groups you select in this field. For more information, see User Access During an Approval Process.