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


Wrapping an application is the process of applying Apperian's application policies to add layers of security, management, and measurement capabilities to the app. When you first apply policies to an app, Apperian creates a new version of the app with an application wrapper that defines its policies. Because it is a new version of the app, you need to re-sign it; this is the case with any new version of an application. Once the app is re-signed, it is ready to deploy to your users—unless there are other functions you want to perform first, such as inspecting the application to screen for risky behavior and vulnerabilities.

After a wrapped app is deployed, you may need to modify its application policies to adapt to changing business needs or take advantage of new application policies. Most policy changes take effect immediately, but some require you to re-wrap the app and deploy an update to users. Either way, Apperian guides you through the process.

 Click here to see the message indicating whether users need to update the app...

In some situations, you need to force Apperian to apply a new wrapper so that you can take advantage of features and enhancements that depend on the latest version of the wrapper. When this is necessary, Apperian lets you know in the description of the new feature or enhancement listed in the Release Notes and
What's New. 

Follow the procedure below to rewrap an app with a new policies wrapper. 

To rewrap an app with a new policies wrapper
  1. (Optional) Mark the application update as mandatory to ensure that users install the new version of the app that is created with this procedure. You can mark the update as mandatory before you reapply the policies and re-sign the app. When you mark an update as mandatory, users are prompted to install it when they log in to the App Catalog, and they cannot continue using the App Catalog until all mandatory updates are installed.

     Click here for steps to mark the application update as mandatory...
    1. On the Admin Portal navigation bar, click Applications.
    2. Click the Edit link next to the application.
    3. Expand the Application field.
    4. Under Application Update Settings, click Set to today to force users to update the application the next time they attempt to log in to the App Catalog.

    If an app is wrapped with the Self-Updating App policy, Apperian makes it even easier for users to stay current with the latest version of an app. Rather than relying on the user to initiate installation of an application update through the App Catalog, Apperian instead prompts the user to update while the user is launching the app. If a user launches an app wrapped with the Self-Updating App policy when there is a mandatory update of the app available, the user must either install the update or exit the app. When an update is optional, or when the date for a mandatory update has not yet been reached, the user can choose whether to install the update. If the user does not install the update, the user can continue to use the currently installed version. For more information on this policy, see Self Updating App.

    For more information on application update settings, see Managing Application Updates.

  2. Go to the Applications list and click the Policies link next to the application you want to rewrap.

  3. Click the Remove button to the right of the status message to remove all policies. 

  4. Select the policies you want to reapply to the app. They may be the previously applied policies or a different selection.

  5. Click Apply. After the policies are successfully applied, the Current Policy Status will change to Pending Signing

  6. Click the Signing tab to open the Signing page for the app. 

  7. On the Signing page, sign the app with the same credentials previously used to sign it. For instructions on signing through Apperian, see Sign an App (Admin Portal).

    When you sign the app, you can select options to enable the app and notify users about the update via a push notification.  

    If you do not want to sign the applications through Apperian, you can download a signing package that includes the app's binary file and a signing script. For instructions on signing apps outside of EASE, see Sign an App (Signing Package)