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

This page describes new features and enhancements in recent releases of Apperian.

November 15, 2017

IMPORTANT

To take advantage of the updates and bug fixes in this release, all customers must update to the latest iOS and Android App Catalogs and distribute them to your users. To obtain the latest App Catalogs, contact support@apperian.com.

Bulk Import Improvements

We have further refined the user interface on the Bulk User Import and Bulk Group Import pages. Improvements include:

  • Better page organization, with more clearly defined options and new loading status indicators.

  • Improved handling of issues with the CSV file, with more specific messages and troubleshooting tips.

  • You can now edit every cell in the preview table.

The following screenshots provide a look at the new Import Groups and Import Users pages.

Import Groups

Import Users

For more information, see Import Multiple Users and Import Multiple Groups.

iPhone X Optimization

iPhone X

The iOS App Catalog is ready for use on iPhone X devices. 

If your App Catalog uses custom branding assets, you must create a new iOS Launch Image and send it to Apperian Support:

Name: Default-1100-2436h@3x.png

Resolution: 1125 x 2436

For more information about branding, see Branding App Catalogs.

We also encourage customers to test your apps on the iPhone X to determine whether they require new graphics or other tweaks to take full advantage of the new design and screen resolution.











App Catalog UI Updates

As part of our ongoing effort to improve the App Catalog user experience, we have made a number of minor visual tweaks and improvements to the iOS and Android App Catalogs.

Removing Unused Policies

The following policies are rarely used, and will be deprecated by the end of 2017:

  • Application Update Compliance

  • Require MDM Enrollment

November 1, 2017

Hybrid App UI Update

We’ve given hybrid apps a new look that feels more like a modern iOS or Android native app.

iOS

Android

iOS  improvements and changes include:

  • Navigation bar is now on the bottom.

  • Webpage name now appears at the top of the screen if there are no tabs.

  • If tabs are enabled, they appear across the top in place of the title bar.

  • Improved ability to open files, with a new iOS “share” button on the nav bar.

Android improvements and changes include:

  • Webpage name appears on the top of the screen.

  • The Back button has been removed, and backward navigation is now controlled by the device’s Back button.

  • A new Home option appears in the top menu, which navigates to the initial URL for the app.

  • A hybrid app can now open PDF files.

  • A hybrid app now asks for required device permissions.


Important

Customers must rebuild and re-sign their existing hybrid apps to take advantage of these updates. All newly created hybrid apps will include these updates automatically. For information about rebuilding hybrid apps, see Update an Application.

Google Play App Enhancements

The Version field, Version Notes field, and up to 5 screenshots are now automatically imported when adding a Google Play app.

You can also now change the language code at the end of a Google Play URL to import translated text.

October 18, 2017

New User Role

This release introduces a new role named: Developer

The role previously named Developer is now named: App Manager

The intent of the new Developer role is to create a user who only has access to a subset of apps. This is useful when organizations want to provide restricted access to external vendors, or differentiate between internal development teams.

This new Developer role can only view and manage apps that are assigned to groups the user belongs to. For example, if a user has the new Developer role and is only a member of Group A he will only see applications assigned to Group A, but not to Group B or Group C.

It made sense to us that this new role should be named Developer, but there was obviously an existing role with that name. We decided that the role formerly known as Developer should have a new name based on its broader scope. This led to the name App Manager, which we feel better represents the purpose of a user who manages every app in an organization.

For more information, see Roles.

API Impact

These changes also affect the Apperian API, which now takes a user’s role permissions into consideration when providing access to app and group data.

You may encounter situations where users with the User role are restricted in what they can access now compared to what they could access before this release. If this happens, you should review their role assignment to ensure that your users have access to the data they need.

UI Changes

In addition to the new role and name change, the Edit User page now displays a description beneath the Role field.

Deprecation of Email Provisioning

Based on research into the way clients use our tools, we have decided to deprecate the Email Provisioning feature. If you have any questions or concerns, contact Apperian Customer Support.

October 4, 2017

Bulk User Import Enhancements

In a previous release, we improved the process for importing multiple groups at one time. Now, we have continued that work to improve the experience when importing multiple users.

The following changes impact the existing behavior of this feature.

  • Previously, it was possible to use the Import Users feature to update the group membership of existing users. This is no longer possible.

  • Previously, the CSV file could include a Password column used to set a password for the imported users. This is no longer possible.

The Import Users page has been revamped:

  • All options now appear in the File Upload section.

  • The page now displays a preview of all rows in the uploaded CSV file.

  • Rows that contain errors are highlighted.

  • Messages on the page describe the errors.

  • You can modify highlighted cells to edit the data without uploading a new spreadsheet.

For more information, including revised instructions, requirements, and troubleshooting tips, see Import Multiple Users.

App Catalog Enhancements

We continue to enhance the app catalog experience with the following improvements:

  • The iOS app catalog Search icon now appears at the bottom right. Searching on iOS now looks and feels more like a native iOS app.
  • The Android app catalog now has a global search bar at the top of the app. The scroll bar no longer includes a Search tab.


These updates are automatically available to all customers as of this release; there is no need to upload new native App Catalog application files.


September 20, 2017

SSO Authentication in the Apperian Admin Portal

Apperian now offers single sign-on (SSO) authentication for the Apperian Admin Portal in addition to the App Catalog. As before, we support the SAML and OAuth protocols.

SSO authentication in the Admin Portal is made possible by the unique vanity subdomain feature that we added in a previous release. For more information about the vanity subdomain, see Vanity Subdomain.

To use SSO for the Admin Portal, your users must access the vanity subdomain URL for your organization (for example, https://organizationname.ease.apperian.com) . SSO authentication is not available through the https://ease.apperian.com login URL.

NOTE: When SSO is enabled, it is available for both the App Catalog and Admin Portal; SSO can’t be turned on for one and off for the other. However, you can effectively bypass SSO in the Admin Portal if you choose not to communicate the vanity URL to your users.

SSO for the Admin Portal is automatically available to customers who already use SSO authentication for your App Catalog. If you are not currently using SSO, and would like to enable it, contact Apperian Support.

For more information about how Apperian implements SSO, see Single Sign-On with Apperian.

App Catalog UI

We have made the following improvements as part of our ongoing effort to improve the App Catalog user experience:

  • The App Details page is now a lot easier on the eyes and more closely follows the UI design used by iOS and Android.

  • The native iOS app catalog now scales to fit the resolution of any device, and now uses the proper native elements for UI features such as the keyboard and battery icon.

Here's a look at the updated App Details page for iOS and Android:

iOS

Android

iOS 11

Apple released iOS 11 on September 19, and Apperian is pleased to announce full support.

Apple’s latest mobile operating system offers many exciting improvements and new features. For a full list of features and changes, see Apple’s official overview.

Apple Removes Support for 32-bit Apps

The most important change for Apperian customers is that iOS 11 removes support for 32-bit apps. This is a change that we’ve mentioned before and for which we have prepared.

In a previous release, we added functionality to the Admin Portal that warns administrators when adding a 32-bit iOS app. We also added various methods for identifying apps that use 32-bit or 64-bit architecture. For more information, see 32-bit Identification for iOS Apps.

If you haven’t yet, now is the time to ensure that all of your apps use 64-bit architecture, otherwise your users will not be able to use the 32-bit apps after upgrading to iOS 11.

Test Your Apps

Our research shows that, except for the 32-bit limitation, iOS 11 supports the functionality of all apps that run on iOS 10.

However, in addition to reviewing your apps for 64-bit compatibility, we also recommend that you test all of your apps on iOS 11 to ensure a smooth transition.

You may also want to test your apps on the new iPhone X when it arrives in November to determine whether they require new graphics or other assets to take full advantage of the new screen resolution.

Misc. Improvements

The following enhancements don’t have enough details to require their own sections, but we still want you to know about them:

  • In order to prevent some forms of malicious attack, we have disabled the ability for browsers to fill out text fields on Apperian login pages.

  • The Version Notes field character limit has been increased from 2,000 to 4,096 in both the Admin Portal and the Publishing API.

September 6, 2017

iOS 11

Apperian has been testing the iOS 11 beta and we are prepared for Apple’s next release.

As a reminder, we already implemented a message that warns administrators when you add or edit a 32-bit iOS app. The warning does not prevent admins from adding a 32-bit app.  

We will keep you updated once iOS 11 is officially released.

Reviews API Update

We have improved the performance of the Reviews API and introduced a new v2 endpoint:

FunctionV1 EndpointV2 Endpoint

List Rating and Review Data for a Specific Application

GET /v1/applications/(app_psk)/likes/reviews/

GET /v2/applications/(app_psk)/likes/reviews/


Note the following considerations when assessing the impact of this change:

  • The v1 version of the endpoint listed above will be deprecated in Q4 2017. When this happens, Apperian will no longer support code that interfaces with the endpoint.

  • Code that interfaces with the v1 endpoint listed above will continue to work for now, but you should modify it to work with the v2 version of the endpoint. If you have any questions or concerns about this timeline, please contact Customer Support.

  • All new code that interfaces with Apperian APIs should point to the latest version of this endpoint.

August 23, 2017

Android 8.0

Apperian provides full support for Android 8.0 Oreo, which Google began rolling out this week. For more information about Android 8.0, see Google’s announcement.

Be Prepared

For a seamless user experience, we recommend the following steps:

  1. Distribute the latest Android App Catalog to your users:

    1. Contact Apperian Customer Support to request the latest version of the Android App Catalog. For instructions, see Using Native App Catalogs.

    2. Once the new App Catalog is uploaded to Apperian, mark the app update as mandatory. For instructions, see Managing Application Updates.

    3. Re-sign the App Catalog with the same credentials used previously. When you sign, be sure to enable the app and notify users about the update. For instructions, see Sign an App.

  2. Re-apply the Self Updating App policy to any apps that use it, then distribute the updated apps to your users. For instructions, see Rewrap an Application.

  3. Inform users about the new process for installing unknown apps on Android 8.0, as described below.

Installing Unknown Apps

Android considers the App Catalog (and all apps distributed through it) to be “unknown” because they are not installed via the Google Play store.

The process for enabling installation of unknown apps in Android 8.0 is different from previous versions of Android. The configuration is now specific to individual apps rather than a global setting.

Users must follow this process for:

  • Chrome (or their browser of choice)
  • the App Catalog
  • any apps that use the Self Updating App policy

To permit installation of unknown apps in Android 8.0

  1. Go to Settings (or tap External Sources on the alert).
  2. Tap Apps and Notifications.
  3. Tap Advanced.
  4. Tap Special app access.
  5. Tap Install unknown apps.
  6. Tap the appropriate app.
  7. Tap the switch next to Allow from this source.

For more details and additional information about this change in Android 8.0, see the Android Developer’s Blog.

Bulk Group Import Enhancements

We have improved the experience when importing multiple groups at one time. The Import Groups page now displays a preview of all rows in the uploaded CSV file and highlights any rows with errors that must be resolved. Messages on the page describe the errors.

Additionally, you can now import greater than 10,000 groups at once.

For more information, see Import Multiple Groups.

Note

The “name” and “description” column headers are now case sensitive, but the CSV import requirements have not otherwise changed.

Discontinuing Support for Apple VPP

Based on research into the way clients use our tool, we have decided to discontinue support for Apple’s Volume Purchase Program. If you have any questions or concerns, contact Customer Support.

August 9, 2017

IMPORTANT

Based on the resolution to an issue in this release, clients with user devices running Android 4 and Android 5 must rewrap their apps.

As a best practice, Apperian encourages all clients to rewrap their apps periodically. For more information, see Rewrap an Application.

New v2 API Endpoints

We have updated a number of API endpoints to improve efficiency and performance. The following table lists the new v2 endpoints and the v1 endpoints they replace.

FunctionV1 EndpointV2 Endpoint
List Devices for UserGET /v1/devices/users/(user_psk)GET /v2/device_users/users/(user_id)
List Device-User DetailsGET /v1/devices/(device_psk)/users/(user_psk)GET /v2/devices/(device_id)/users/(user_id)
List Users in GroupGET /v1/groups/(group_psk)/users/GET /v2/groups/(group_id)/users/
List UsersGET /v1/users/GET /v2/users/
List User DetailsGET /v1/users/(user_psk)GET /v2/users/(user_id)
List Information About the Authenticated UserGET /v1/users/infoGET /v2/users/info
Authenticate User and Register App CatalogPOST /v1/catalog/authenticate/POST /v2/catalog/authenticate/

Note the following considerations when assessing the impact of these changes:

  • Not all Apperian API endpoints have been versioned; endpoints not listed above have not changed.
  • The v1 versions of the endpoints listed above will be deprecated at some point in 2018. When this happens, Apperian will no longer support code that interfaces with those endpoints.
  • Code that interfaces with the v1 endpoints listed above will continue to work for now, but you should modify it to work with the v2 versions of the endpoints. If you have any questions or concerns about this timeline, please contact Customer Support.
  • All new code that interfaces with Apperian APIs should point to the latest version of each endpoint.

Discontinuing the Application Approval Process Feature

Based on research into the way clients use our tool, we have decided to remove the Application Approval Process feature.

We have found that the feature is rarely used, and we believe that testing with app versions and groups provides a much better experience. For example, you can assign a beta version of your app to a test group while all your other users continue using the production version. To learn more, see Application Versions.

If you have any questions or concerns, contact Customer Support.

July 26, 2017

New Session API

IMPORTANT

As of this release, the Session API is the only method for extending a user’s session expiration time. If you have been using any other endpoints to extend a session you must update your process to use the Session API. 

We have added a new API called Session. This API is used to extend a user’s token expiration time by setting the timeout period to the value specified for the organization. For more information, see Session API Reference.

For example, if your organization's session timeout is set to 5 minutes, and the session begins at 12:00, the session expires at 12:05. If you call this endpoint between 12:00 and 12:05, say at 12:03, the session is refreshed and now expires at 12:08.

Previously, a user’s session was extended automatically whenever any API call was made. This new Session API replaces that existing behavior, and other API calls no longer extend a user’s session.

An organization's session timeout period is set by Apperian. For more information, contact Apperian Support.

App Catalog Enhancements

We continue to enhance the app catalog experience with the following improvements:

  • Web, iOS, and Android app catalogs now have “pull to refresh.”
    • Previously, app catalog pages updated their content whenever a user changed tabs. This could occasionally lead to slow performance.
    • Now, all pages refresh only after the “pull to refresh” action (except for the Updates page, which still updates whenever it’s opened).
    • To do this: place a finger on the page, pull down until you see an arrow at the top of the page, and then release. This is a common mobile UI action, and should feel immediately familiar to your users.
  • The App List on the Android app catalog now uses a device’s screen size to dynamically adjust the amount of app icons that appear.
  • The Featured Apps section has an improved scrolling mechanism which feels smoother. 


These updates are automatically available to all customers as of this release; there is no need to upload new native App Catalog application files.

July 12, 2017

User API Tokens

Administrators can now create API tokens for any user in the system. Tokens are especially useful for automated tasks or processes, but can replace user authentication credentials (username and password) for any API call.

Apperian recommends using this method of authentication to integrate with the Apperian API for repetitive automated tasks.

A new Settings > API Tokens page in EASE allows you to create, view, and revoke tokens. Tokens can also be created and revoked via the Organizations API.

For more information, see Manage API Tokens.

Faster App Signing in EASE

This release includes many behind the scenes improvements to the EASE signing server, but the primary benefit for customers is that signing apps in EASE is now much faster.

IMPORTANT

You must now use the signing package to sign apps that include watchOS apps. Apps that include watchOS components can no longer be signed with the EASE signing server. For more information, see App Extensions and Entitlements.

June 28, 2017

App Catalog Updates

We are excited to officially release the App Catalog updates we’ve previewed over the past few releases. This is the first step in a total App Catalog redesign which will roll out gradually over the upcoming months.

These updates are automatically available to all customers as of this release; there is no need to upload new native App Catalog application files.

App Catalog UI Enhancements

This release introduces a number of updates and enhancements to the App Catalog user interface (UI), including:

  • iOS and Android App Catalogs now have improved navigation bars and other minor UI changes which take inspiration from the App Store and Google Play.
    • The Windows App Catalog UI is not affected.
  • The web App Catalog UI has been completely overhauled, and now dynamically adjusts to resemble the native App Catalog for the device it's running on.
    • On Apple or Windows devices, the web App Catalog resembles the native iOS App Catalog; on Android and Blackberry devices it resembles the native Android App Catalog.
  • Branding options are now standardized across web and native App Catalogs. All of your existing branding assets will work automatically with the new UI updates. For more information, see Branding App Catalogs.

The following screenshots provide a look at the updated UI: 

iOS
Android

 

Web App Catalog Vanity Domain

All organizations now have access to a vanity domain name—a unique URL which is automatically created based on the organization name. For example, https://examplecompany.appcatalog.apperian.com

This URL can be found on the web App Catalog details tab in EASE, and is also displayed in the new user invitation email. Apperian Support can change the domain name.

IMPORTANT

To avoid potential confusion, contact Apperian Support to change the domain name before you invite any new users into the organization. 

Existing links to the web App Catalog now redirect to a generic Apperian branded login page where users can use their credentials to access your organization’s App Catalog.

32-bit Identification for iOS Apps

Apple has announced end of support for 32-bit apps as of iOS 11. To prepare for this, we’ve added a message that warns administrators when you add or edit a 32-bit iOS app. The warning does not prevent admins from adding a 32-bit app.

 Administrators also now have new options for reviewing their existing apps to determine whether they use a 32-bit or 64-bit architecture:

  • A new column called Architecture is available in the Version History table on an app’s Details tab. 
    • Bonus: The Version History table is now sorted by date in reverse, so the most recent version always appears at the top of the list.
  • A new report called App Information provides basic details about every app version in the system, including App Name, Platform, Minimum Supported OS Version, Version, and Architecture. The Architecture column indicates whether an app is 32-bit, 64-bit, or both, and is only populated for the most recent app version.

Report Enhancements

 The following enhancements have been made to EASE reports:

  • The Reports page now lists reports alphabetically.
  • The Download Activity report now tracks anonymous download activity (users who download an app but have not yet authenticated). Anonymous downloads are represented in the User ID column by <IP address>@<org ID>
    • For example, 70.215.11.88@202
  • The App Usage report now automatically shows data from the previous 7 days.

June 14, 2017

User Enabled Touch ID Authentication

In a previous release we added the ability for administrators to enable Touch ID authentication on iOS devices. We’ve improved upon that functionality by now allowing users to choose whether or not they want to use Touch ID for apps on their own device.

Now, when Touch ID authentication is enabled on the Settings page (or when enabled for SSO by Apperian Support), a new bar appears at the bottom of the login screen for the iOS App Catalog or any iOS apps that use policies that require authentication.

A Refresh link appears (on the app catalog only) when Touch ID is enabled for SSO authentication, and is used to clear username and password values on the login screen.

IMPORTANT

To take advantage of this enhancement, you must:

  • Update to the latest version of the iOS app catalog. To do so, contact Apperian Support.
  • Reapply any policies that require authentication (for example, Enterprise SSO or Self Updating App), re-sign the app, and deploy the updates to your users. For instructions, see Rewrap an Application.

Check Location Services Policy Enhancements

The Check Location Services policy now provides multiple options for displaying an alert on a user’s device:

  • Mandatory: The alert appears every time a user opens the app, and users can't use the app until they enable location services on their device.
  • Voluntary: The alert appears, but users can continue using the app without enabling location services. You can set the number of minutes that should elapse before displaying the alert again after a user dismisses it.
  • No Alert: The alert never appears, but location services data is recorded for the Location Services Status report.

The alert message now varies depending on whether it is mandatory or voluntary.

Mandatory

Voluntary

After upgrading, the Check Location Services policy is set to Voluntary and 5 minutes by default for any apps already using the policy.

For more information, see Application Policies.

Note

This update does not require that you reapply the Check Location Services policy or re-sign any apps. However, if you choose not to reapply and re-sign, the messages will differ slightly from those shown above.

May 31, 2017

Account Security Enhancements

This release adds new options for securing user accounts on the Settings > Password Requirements page. For more information, see Set Password Requirements.

Password History

The new Password History settings, available for both users and administrators, allow you to prevent users from entering new passwords repeatedly in an attempt to reuse an old password right away.

Enforce password history sets the number of unique new passwords that must be associated with a user before an old password can be reused. Set to 1 by default, with a maximum of 30.

Minimum password age sets the amount of time (in hours) that must pass before users can create a new password. Set to 0 by default, which effectively disables the setting until a positive value is entered.

Administrators can change a user's password at any time, regardless of how these settings are configured.

Account Lockout

The new Account Lockout setting, also available for both users and administrators, allows you to set the number of times a user can enter an incorrect password before their account is disabled (locked out). Once a user’s account is disabled in this way, the user is prevented from logging in again until an administrator manually enables the user's account. Administrators can enable users at any time, but can’t unlock their own account.

Account lockout threshold is set to 0 by default, which effectively disables the setting.

Older versions of the Android app catalog incorrectly count each invalid login attempt twice. To avoid this issue, customers are encouraged to upgrade to the latest version of the Android app catalog.

May 17, 2017

End of Support for BlackBerry Apps

As of June 2017, Apperian will no longer support the delivery of native BlackBerry applications. This decision is based on customer feedback and an overall decline in BlackBerry app usage in the marketplace.

Customers currently using the Web Catalog to deliver BlackBerry apps should notify their users as soon as possible.

This is NOT end of support for BlackBerry devices. Customers with BlackBerry 10 devices can use the Web Catalog or the Android App Catalog (on BlackBerry 10.3 or higher) to deliver Android apps. For more information about BlackBerry support, see Supported Platforms.

May 5, 2017

Touch ID Support for iOS for App Catalogs and Policies

You can now enable Touch ID Authentication when using Single Sign-On (SSO) authentication for iOS devices. Previously, Touch ID was only available for EASE Authentication.

When enabled, Touch ID support now also extends to any app with policies that require authentication (for example, Enterprise SSO or Self Updating App).

To enable this feature for EASE Authentication, you need to update your App Catalog and re-apply policies to any apps which use the Enterprise SSO or Self Updating App policies. For more on enabling Touch ID with standard EASE Authentication, see Specify the User Authentication Method.

To enable this feature for Single Sign-On authentication, contact support@apperian.com.

March 22, 2017

Touch ID Authentication with the iOS App Catalog

If your organization is configured for standard EASE Authentication (the EASE built-in authentication mechanism), you can now enable users to log in to the iOS App Catalog using Touch ID, as long as Touch ID is set up on their devices. 

By default, Touch ID is not enabled for an EASE organization; to enable it, go to Settings->Authentication in the EASE Portal. Once Touch ID is enabled, users will need to log in one time using username and password; on subsequent logins, they will be prompted to authenticate with Touch ID instead.

Note:  To get this feature, update to the latest iOS App Catalog and distribute it to your iOS users. To obtain the latest catalog, contact support@apperian.com.

Touch ID is also supported with SSO authentication using certain SSO providers. If your organization is using SSO authentication and you are interested in enabling Touch ID, contact support@apperian.com for more information.

For more on enabling Touch ID with standard EASE Authentication, see Specify the User Authentication Method.

March 8, 2017

Application Metadata Stored for Each Version

Prior to this release, EASE stored application metadata at the application level. This meant that when users viewed details about an app in the App Catalog, they saw metadata associated with the latest version of the application, regardless of which version(s) they had access to in the catalog. Now EASE stores the metadata for each version of an application so that users can view the unique data associated the versions they are accessing. 

versions1.pngThe example to the right shows the details page in the App Catalog for two versions of the Benefits app: V2.0 and V2.2 (the latest). Each version has a different name, icon, version note, and short and long description.

EASE now stores the following metadata at the version level:

  • Name
  • Icon
  • Version Number and Notes
  • Short and Long Description
  • Form Factor
  • Minimum OS Version
  • Custom Metadata

In upcoming releases, EASE will store additional data at the version level, such as screenshots and application reviews.

Application metadata will be stored at the version level for any app that you add or edit from this release forward. It does not apply to metadata associated with older versions of apps created prior to this release.

To learn more about managing multiple versions of your applications in EASE, see Application Versions.

With new web services endpoints, this enhancement is also available to customers and partners who interface with Apperian APIs. For more detail, see New V2 API Endpoints.

New V2 API Endpoints

Storing application metadata at the version level rather than the application level is an architectural change to the EASE data model. Therefore, Apperian has created new versions of several API endpoints in order to offer this new functionality while continuing to support customer applications that interface with the original v1 endpoints.
  

 Click here for a list of new v2 endpoints and the v1 endpoints they replace.

Function

V1 Endpoint

V2 Endpoint

List All Applications

GET /v1/applications/

GET /v2/applications/

List Data for a Specific Application

GET /v1/applications/(app_psk)

GET /v2/applications/(app_id)

Get Inspection Report for Latest Version of Application

GET /v1/applications/(app_psk)/inspections/

GET /v2/applications/(app_id)/inspections/

List Version Information for an Application

GET /v1/applications/(app_psk)/versions/

GET /v2/applications/(app_id)/versions/

List App Catalog Data

GET /v1/applications/app_catalogs/

GET /v2/applications/app_catalogs/

List Applications for a Specific User

GET /v1/applications/user/

GET /v2/applications/user/

List Applications for the Authenticated User’s Device

GET /v1/catalog/applications/

GET /v2/catalog/applications/

List Data for a Specific Application

GET /v1/catalog/applications/(app_psk)

GET /v2/catalog/applications/(app_id)

List Downloaded Applications

GET /v1/catalog/applications/downloaded/

GET /v2/catalog/applications/downloaded/

List Featured Apps

GET /v1/catalog/applications/featured/

GET /v2/catalog/applications/featured/

List Applications with Mandatory Updates

GET /v1/catalog/applications/mandatory/

GET /v2/catalog/applications/mandatory/

List Apps in Order of Popularity (# of Downloads)

GET /v1/catalog/applications/popular/

GET /v2/catalog/applications/popular/

List Applications with Updates

GET /v1/catalog/applications/updates/

GET /v2/catalog/applications/updates/

List Data for a Specific Version of an Application

This is a new endpoint.

GET /v2/catalog/applications/versions/(version_id)

List Apps in a Specific Category

GET /v1/catalog/categories/(string: category_id)/applications/

GET /v2/catalog/categories/(string: category_id)/applications/

Search Application Data

GET /v1/catalog/search/

GET /v2/catalog/search/

Install All Native Applications

GET /v1/downloads/install/applications/all

GET /v2/downloads/install/applications/all

Install All Mandatory Applications

GET /v1/downloads/mandatory/applications/all

GET /v2/downloads/mandatory/applications/all

Install All Application Updates

GET /v1/downloads/update/applications/all

GET /v2/downloads/update/applications/all

List Applications in Group

GET /v1/groups/(group_id)/applications/

GET /v2/groups/(group_id)/applications/

List Groups Associated with a Specific Application

GET /v1/groups/applications/(app_psk)

GET /v2/groups/applications/(app_id)

For a list of all v1 and v2 endpoints, see the HTTP Routing Table.

 

Note the following considerations when assessing the impact of these API changes:

  • Not all Apperian API endpoints have been versioned; endpoints not listed below have not changed and are still listed as v1.

  • The v1 versions of the endpoints listed below will be deprecated in Q3 of 2017. At that time, Apperian will no longer support code that interfaces with those endpoints. Apperian will provide further information, including a more specific timeline, before any endpoints are deprecated.

  • Code that interfaces with the v1 endpoints listed below will continue to work for now, but you should modify it to work with the v2 versions of the endpoints before Q3 of 2017. If you have any questions or concerns about this timeline, please contact support@apperian.com.

  • All new code that interfaces with Apperian APIs should point to the latest version of each endpoint.

 

February 22, 2017

"Last Active Date" in Device Details Report

The Device Details report now includes a “Last Active Date” column. This column, which already displays in the Devices table on a user’s details page, identifies the date when the user last interacted with EASE from the device. Interaction includes any type of communication between the device and EASE.

For more information on running the Device Details report and other reports, see Running Reports.

Search and Other Enhancements on the Groups Page

To improve the user experience and provide more information for EASE administrators—especially those working with large numbers of groups—the Groups page in the EASE Portal includes multiple enhancements:

  • Search field lets you search on group name and description to filter the list.
  • Pagination controls allow you to page through large lists of groups and adjust the number of groups displayed per page.
  • New Applications and Users columns display the number of apps and users currently assigned to the group so you can gather that information at a glance without having to view group details.

For more information on managing groups, see Managing Groups.

Screenshots in the Windows Phone/Mobile App Catalog

App Catalog users on Windows Phone/Mobile devices can now view screenshots on an app’s details page if screenshots were uploaded for the app via the EASE Portal. 
  

February 8, 2017

Disassociate a Device from a User

When a user first logs in to the App Catalog from a device, EASE creates an association between that device and the user. These associations are listed in a Devices table on the user’s Details page in the EASE Portal. Over time, the table may become outdated, listing devices the user no longer uses. EASE now lets you remove a device from the Devices table to disassociate it from the user. Once you remove a device, it is no longer listed in the user’s Devices table, nor is it listed in “real-time” reports, such as the Device Details report.

Disassociating a device from a user does not impact any other associations between that device and other users. Also, if you disassociate a device from a user and the user logs in to EASE from that same device again in the future, EASE reassociates the device to the user.

For instructions on removing a device, and more detail on what happens when you do, see Disassociate a Device from a User.

Easily Identify Assigned Users When Editing a Group

When editing a group in the EASE Portal, you can now click a Show Assigned link to list only the users currently assigned to the group. This is very helpful when managing large numbers of users.

For more information, see Edit a Group.

January 25, 2017

Server Certificates Application Policy

The Server Certificates policy lets you upload one or more trusted SSL (X.509) certificates that a wrapped app can use when establishing an SSL connection with the servers it needs to access. Similar to how browsers have a pre-installed list of trusted SSL certificates, this policy lets you pre-install a list of certificates on a per-app basis.

The Server Certificates policy uses Blue Cedar Networks Mobile App Protection (MAP) and is not part of the base EASE product. If MAP policies are currently disabled for your organization and you are interested in using this policy or any other MAP policies, contact Apperian Customer Support.

For more information, see Application Policies.

Hybrid App Enhancement: Open Files in Other Apps

Prior to this release, if a user tapped on a file link in a hybrid app, EASE would attempt to open the file directly in the app’s webview. This presented a limitation with hybrid Android apps because the webview could not open PDF files.

Now when you add or edit a hybrid app, you can select an option to allow the app to open files in other apps. When users tap on a file link in a hybrid app built with this new option, a menu will display from which the user can select an application to use to open the file.

With hybrid iOS apps, this feature supports any file type. With hybrid Android apps, this feature currently supports PDF files only; EASE will attempt to open other file types in the webview. Apperian is continually enhancing EASE functionality; if you have other file types you want to support with your hybrid Android apps, let us know by contacting support@apperian.com.

The following illustration shows the user's experience opening a file in an iOS hybrid app.



For instructions on adding a hybrid app and setting this new option, see Add an Application. To support this option with one of your existing hybrid apps, you will need to edit and rebuild the app and then sign and redistribute the update. For instructions on rebuilding a hybrid app, see Edit or Update an Application.

App Catalog Version Number Displayed

When you are troubleshooting an issue with one of your App Catalog users, it is helpful to know which version of the catalog the user is running. If you know the user’s version, you can ensure it is the latest and greatest by comparing it with the version of the catalog currently uploaded to your EASE organization. You can also provide the version number to Apperian Customer Support so they can better assist you when needed.

The App Catalog now lists its version number in the side menu next to organization name.

 

January 11, 2017

Identify Inactive Devices

Many of your users install the App Catalog on multiple mobile devices and upgrade to new devices fairly regularly. On the user details page in the EASE Portal, EASE now helps you identify unused or underused devices that might be sitting idle in a desk drawer or forgotten in an employee’s backpack. The Devices table, which lists all the mobile devices on which the user has logged in to the App Catalog, includes a new Last Active Date column that identifies when the user last interacted with EASE from each device. Interaction includes any type of communication between the device and EASE, such as listing apps in the App Catalog and updating an app.

For instructions on viewing details about an EASE user, see View User Details.

Feature Apps in the Windows Phone App Catalog

At the top of the Popular apps page in the Windows Phone App Catalog, users can now browse a collection of featured applications curated by an EASE Administrator. Featured apps display in an auto-scrolling carousel, with a quote listed under the app name. This feature—already available with iOS and Android App Catalogs—is a great way to promote applications and drive their adoption within your organization.

Selecting the apps you want to feature in a catalog is a simple drag-and-drop process through the EASE Portal. For instructions, see Select Featured Apps for the App Catalog.


 


  

December 14, 2016

Improved iOS App Catalog User Experience (App Button Behavior)

To provide iOS App Catalog users with a more consistent user experience, we have modified the button behavior for native applications that were previously installed on the device. Once a user installs a native app, the button now changes from INSTALL to a Cloud Download image button.

Prior to this release, the INSTALL button was designed to change to OPEN once an app was installed, but due to restrictions with the iOS operating system, that behavior was not always consistent; sometimes the button changed to INSTALLED instead of OPEN, or remained OPEN even if the user deleted the app. Now, as long as the app was previously installed, the Cloud Download button displays and the user can tap it to download and install the app—regardless of whether the app is still installed on the device.

This is the only change to the application buttons in the iOS App Catalog. Other buttons (RUN, UPDATE, and APP STORE) are unchanged.

There are no changes to buttons in the Android, Windows Phone, and Windows 8/10 App Catalogs. In those catalogs, the INSTALL button still changes to OPEN after the app is installed.

For more detail on the application button behavior for all types of apps with each App Catalog platform, see Application Buttons.

New Blue Cedar Networks MAP Application Policies

Apperian EASE now supports Mobile App Protection (MAP) 3.12.2, the latest version of Blue Cedar Networks MAP. This version includes enhancements to all MAP application policies, as well as the new Client Certificates policy. Additionally, MAP 3.12.2 supports multidex Android apps and 64-bit iOS apps. Support for 64-bit apps means you can now apply MAP policies to any of your iOS apps, including iOS hybrid apps (which EASE builds as 64-bit apps).

The following table lists the old and new policy names, and describes the new Client Certificates policy. For details on these policies as well as Apperian application policies, see Application Policies.

Old PolicyNew Policy
App-Level VPN

Secure Microtunnel

This policy requires that you have the Blue Cedar Networks Atlas Platform.

Require Passphrase

Local App Authentication

In addition to functionality provided with the Require Passphrase policy, this new policy also supports fingerprint authentication
Encrypted DAR (Data at Rest)Encrypted Data at Rest
Copy-Paste Protection

Data Sharing

The old Copy-Paste Protection policy could not be used in conjunction with Apperian policies. That is no longer a restriction with the Data Sharing policy.
N/A

New Policy! Client Certificates

This policy requires that you have the Blue Cedar Networks Atlas Platform.

This policy works with the Blue Cedar Networks Atlas Platform to provide a client certificate from your Atlas Gateway server and store it on the user’s device. The application can then present this certificate to sites it needs to access, thereby allowing the user to skip additional logins and have a smoother mobile experience. You can configure the policy so that the client certificate is presented only to a defined “white list” of URLs.

With the old MAP policies, some policies needed to be applied in certain combinations. This is no longer the case; you can apply MAP policies individually or in any combination.

Blue Cedar Networks MAP policies are disabled by default in EASE. If you are interested in applying them, contact Apperian Customer Support at support@apperian.com.

Apps that are currently wrapped with Blue Cedar Networks policies will continue to work, but Apperian encourages you to reapply policies to those apps as soon as possible in order to take advantage of all policy enhancements. After you reapply policies, you will need to re-sign the apps and deploy the updates to your users. For instructions, see Rewrap an Application.

For more on application policies, see Managing Application Policies.

Ability to Upload Images in Hybrid Apps

To enable users to take fuller advantage of an application’s functionality, hybrid apps created through EASE now let users:

  • Add existing photos from Gallery (Android hybrid apps). iOS hybrid apps already supported the ability to add images from Photos.
  • Add new photos taken with the device camera (Android and iOS hybrid apps).
      

To get this enhancement for an existing hybrid app, you need to rebuild and re-sign it and then deploy the update to your users. For instructions, see Update an Application.

November 30, 2016

Data Filtering with the Reports API

To improve the efficiency of the Reports API, you can now filter on the value of one or more report columns to limit the data returned. Which columns are filterable varies for each report. For example, with the App Usage report, you can filter on user_id, device_id, and app_id.

Use the new column filters alone or in conjunction with Start and End date URL parameters.

For details on using the Reports AOI, including a table listing filterable columns for each reports, see the Reports API documentation.

  

Location Services Status Report

If you are using the Check Location Services policy to encourage users to enable location services for certain apps, you can now monitor the location services status for users/devices running those apps. The new Location Services Status report lists each check performed by the Check Location Services policy whenever the status is different than the previous status.

An "Enabled" status indicates that all necessary location settings are enabled and the user can take advantage of GPS features built into the app; a "Disabled" status indicates that Location Services are disabled on the device and/or the app is not set to allow location access.

To start seeing status in this report for any apps that already use the Check Location Services policy, you will need to reapply the policy, re-sign the app, and deploy the update to your users. For instructions, see Rewrap an Application.

For instructions on running the Location Services Status report and other EASE reports, see Running Reports. For more information on the Check Location Services policy, see Application Policies.

  

On This Page
  • No labels