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

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

April 4, 2018

Deprecation of v1 API Endpoints

As originally announced last year, the following v1 endpoints are now deprecated in favor of the corresponding v2 endpoints. If you have any questions, please contact Customer Support.

v1 Endpoint

v2 Endpoint

GET /v1/applications/

GET /v2/applications/

GET /v1/applications/(app_psk)

GET /v2/applications/(app_id)

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

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

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

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

GET /v1/applications/<app_psk>/likes/reviews/

GET /v2/applications/<app_psk>/likes/reviews/

GET /v1/applications/app_catalogs/

GET /v2/applications/app_catalogs/

GET /v1/applications/user/

GET /v2/applications/user/

GET /v1/catalog/applications/

GET /v2/catalog/applications/

GET /v1/catalog/applications/(app_psk)

GET /v2/catalog/applications/(app_id)

GET /v1/catalog/applications/downloaded/

GET /v2/catalog/applications/downloaded/

GET /v1/catalog/applications/featured/

GET /v2/catalog/applications/featured/

GET /v1/catalog/applications/mandatory/

GET /v2/catalog/applications/mandatory/

GET /v1/catalog/applications/popular/

GET /v2/catalog/applications/popular/

GET /v1/catalog/applications/updates/

GET /v2/catalog/applications/updates/

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

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

GET /v1/catalog/search/

GET /v2/catalog/search/

GET /v1/devices/(device_psk)/users/(user_psk)

GET /v2/devices/(device_id)/users/(user_id)

GET /v1/devices/users/(user_psk)

GET /v2/device_users/users/(user_id)

GET /v1/downloads/install/applications/all

GET /v2/downloads/install/applications/all

GET /v1/downloads/mandatory/applications/all

GET /v2/downloads/mandatory/applications/all

GET /v1/downloads/update/applications/all

GET /v2/downloads/update/applications/all

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

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

GET /v1/groups/(group_psk)/users/

GET /v2/groups/(group_id)/users/

GET /v1/groups/applications/(app_psk)

GET /v2/groups/applications/(app_id)

GET /v1/users/

GET /v2/users/

GET /v1/users/(user_psk)

GET /v2/users/(user_id)

GET /v1/users/info

GET /v2/users/info

POST /v1/catalog/authenticate/

POST /v2/catalog/authenticate/

GET /v1/reports/(report_name)/

GET /v2/reports/(report_name)/



March 21, 2018

Limited User Manager Role

This release introduces a new user role named: Limited User Manager

Users with this role:

  • Can view, create, edit, and delete users only in groups they are assigned to.

  • Can only create, edit, and delete users with the User role.

  • Can only view the Users page.

  • Can’t create or edit groups.

For example, if a user has the Limited User Manager role and is only a member of Group A, he can view and modify other users assigned to Group A, but not to Group B or Group C.

For more information about this and other user roles, see Roles.

Change to Non-SSL API Requests

Previously, if an API request was made using non-SSL (HTTP), the request was redirected to SSL (HTTPS) and processed.

Now, the Apperian API will only accept requests made using HTTPS. When requests are made using HTTP, the API now returns an error message.

Important

Using HTTPS ensures that sensitive information is protected. Customers should ensure that all API requests are made using HTTPS.  

March 7, 2018

Applications Page Sort Order

The Admin Portal now remembers the order in which columns are sorted on the Applications page when you navigate away from the page or log out.

Android App Catalog Updates

Sometimes there may be a need to install an older version of an app (here, version refers to the actual app binary’s version, not the version in Apperian). In this case, Android requires that the newer version is uninstalled before the older version can be installed.

To ease confusion when this situation occurs, the Android App Catalog now prompts the user to uninstall the currently installed version before installing the older version. This alert also appears when trying to install an app signed with different credentials.

IMPORTANT

To take advantage of this improvement, all customers must update to the latest Android App Catalog and distribute it to your users. To obtain the latest App Catalog, contact Customer Support.

February 21, 2018

Reports Page Update

It is now easier to navigate the Reports page in the Admin Portal, and the page now includes descriptions for each report.

As announced in the February 7 release notes, the following reports are no longer available in the Admin Portal:

  • Download Activity

  • Login Activity

  • Signing Activity

  • Password Change Activity

  • Direct Install Activity

Tip

You can use the Feeds API to access the data that was previously only available through these reports.

Improved App Versions Endpoint

We have introduced a new v3 endpoint in the Applications API:

Function

V2 Endpoint

V3 Endpoint

List Version Information for an Application

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

GET /v3/applications/(app_id)/versions/

This new v3 endpoint returns all versions of an app and lists all version information, including information about the install file. The v2 endpoint only returned a small subset of version information.

The v3 endpoint also allows for the full functionality of searching, sorting, and paginating the JSON response, as described in Controlling GET Responses.

IMPORTANT

The v2 endpoint listed above will be deprecated in Q3 2018. When this happens, code that interfaces with the v2 endpoint may not work as expected.

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

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

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

New Look for Apperian Documentation

We are in the process of updating Apperian product documentation (Release Notes, Apperian Documentation Center, API Reference, etc) to better reflect the overall Arxan brand identity and fully integrate as one company. This is a style update only; no content has changed.

These style updates coincide with the launch of the all new www.arxan.com.

The Admin Portal and default App Catalog will be updated soon as well.

Deprecation of v1 API Endpoints

Over the past year, we have introduced new versions of several API endpoints (listed here: API Resources That Will be Deprecated).

These endpoints will be deprecated on April 4, 2018.

Code that interfaces with the v1 endpoints may continue to work for a short period of time past April 4, but you should modify it to work with the v2 versions as soon as possible.

February 7, 2018

Policies Enhancements

This release introduces major updates for policy management in Apperian with a brand new API and an improved Admin Portal experience.

Policies API

We are introducing a new API endpoint called Policies that allows you to automate the policy process. Now, you can programmatically configure policies and apply them to apps without using the Apperian Admin Portal.  

For an in-depth overview of the Policies API and instructions on how to use it, see the Policies API Guide.

The following new resources are available:

Function

Resource

List All Policies

GET /v2/policies/

List Data for a Policy

GET /v2/policies/(policy_id)/

List Policies Applied to an App

GET /v2/applications/(app_id)/policies/

Apply Policies to an App

POST /v2/applications/(app_id)/policies/

Remove Policies from an App

DELETE /v2/applications/(app_id)/policies/

Create a Preset Policy Configuration

POST /v2/policies/(policy_id)/configurations/

List Data for a Preset Policy Configuration

GET /v2/policies/configurations/(configuration_id)/

Update a Preset Policy Configuration

PUT /v2/policies/configurations/(configuration_id)/

Delete a Preset Policy Configuration

DELETE /v2/policies/configurations/(configuration_id)/

Policies UI Updates

In addition to the new Policies API, we have updated the UI for the Policies Page and an app’s Policies Tab in the Admin Portal.

In light of these policies changes, we have improved the Policies documentation so it is now easier to navigate and find the information you're looking for. Take a look: Managing Application Policies.

Policies Page

We haven’t changed any functionality on the Policies page, but we have improved the way users interact with policies.

Previously, the page required you to expand every policy to view the Enabled by Default checkbox, even those with no additional options.

Now, the Enabled by Default checkbox is replaced by an On/Off toggle that is visible for every policy on the page. Policies with additional options are now now indicated by a “cog” icon which you can click to expand the policy and configure the options.

Notes

  • The Policies page no longer indicates which apps have policies applied.
  • Blue Cedar Network policies are temporarily unavailable in the Admin Portal, but can still be managed by Customer Support.

Policies Tab

We haven’t changed much about the functionality of the Policies tab, but we have vastly improved the layout and made it easier for users to view and navigate the page.

Now, instead of displaying a long list of policies and options, the Policies tab is divided into the following sections:

  • The No-Registration Mode section only appears at the top of the page if No-Registration Policies are enabled for your organization. This section replaces the No-Registration Mode checkbox that was previously at the bottom of the page.

  • The Policy Status section appears at the top of the page and includes the app's policy status and buttons for applying and removing policies. The policy status messages are now more informative.

  • The Policies Enabled by Default section only appears if an administrator has selected On for any policies on the Policies page. The policies here are selected by default, but you can clear the selection if you don't want to apply those policies to a specific app. This section disappears when policies are applied to an app.

  • The Policies Available section lists the policies that can be applied to the app. Some apps have additional options that should be configured for the policy to work properly. If a policy includes additional options, they appear when you select the policy.

  • The Policies Applied section lists all policies that are currently applied to the app. You can select and clear policies in this section, and modify their options. If you clear the checkbox for a policy in this section, it will be removed from the app the next time you click Apply Policies (the policy will appear back in the Policies Available section).

This screenshot shows the Policies tab after policies have been applied, so the Policies Enabled by Default section does not appear.

Note

Apps are no longer disabled while applying policies.

Feeds API

We have added a new API endpoint called Feeds.

The Feeds API is used to retrieve raw data (as JSON) from a subset of the reports that were previously only available in the Admin Portal. The benefit of this new API is that you can create an automated process to retrieve large amounts of data and analyze it in your own business intelligence tools.

The following reports are now available as feeds:

  • App Usage

  • Download Activity

  • Login Activity

  • Signing Activity

  • Password Change Activity

  • Direct Install Activity

The following new resources are available:

Function

Resource

Return a List of Available Data Feeds

GET /v1/feeds/

Return Feed Information

GET /v1/feeds/(feed_name)/field_info

Return Feed Data

GET /v1/feeds/(feed_name)/


Reports Enhancements

This release introduces new Reports API functionality and continues the Admin Portal UI enhancements that began in the last release.

Reports API

The Reports API endpoint is not new, but we are adding new resources that work similarly to the new Feeds resources. The updated Reports API returns data in JSON format, and also allows you to filter, sort, search, and choose a different format (CSV, or Excel).

The following new resources are available:

Function

Resource

Return a List of Available Data Reports

GET /v2/reports/

Return Report Information

GET /v2/reports/(report_name)/field_info/

Return Report Data

GET /v2/reports/(report_name)/

IMPORTANT

The existing Reports API resource (GET /v1/reports/(report_name)/) will be deprecated on April 4, 2018. Customers currently using the existing v1 resource should update their code to call the new v2 version.

Reports UI Updates

Our last release kicked off improvements to the look and feel of Reports in the Admin Portal, and now we’re bringing the same improvements to the remaining Admin Portal reports.

The overall functionality remains the same, but you’ll notice a clean and modern interface with a new Filters section that allows you to fine tune the results. You can also now export the report as a Microsoft Excel file in addition to CSV.

As part of this update, and in light of the new Feeds API, we will be removing the following reports from the Admin Portal:

  • Download Activity

  • Login Activity

  • Signing Activity

  • Password Change Activity

  • Direct Install Activity

IMPORTANT

These reports will no longer be available from the Admin Portal as of February 21, 2018. However, each of these reports now has a corresponding data feed available through the new Feeds API, so you’ll still have access to the data.

January 24, 2018

Reports UI Updates

We are improving the look and feel of Reports in the Admin Portal. We’ve initially only updated the User Details report, but all reports will see the same refresh over the next few releases.

The overall functionality remains the same, but you’ll notice a new clean and modern interface with a new Filters section that allows you to fine tune the results.

You can also now choose to export the report in CSV or Excel format.

January 10, 2018

Deprecation of URL Access Lists for Hybrid Apps

Based on research into the way clients use our tools, we have decided to remove the URL Access List feature for hybrid apps. If you have any questions or concerns, contact Customer Support.

December 13, 2017

Biometric Authentication Enhancements

IMPORTANT

To take advantage of the authentication improvements in this release, all customers must:

  • Update to the latest version of the iOS App Catalog. To do so, contact Customer Support.

  • Reapply any policies that require authentication (for example, Enterprise SSO), re-sign the app, and deploy the updates to your users. For instructions, see Rewrap an Application.

Face ID Support

The iOS App Catalog and certain policies now support Face ID. In addition, with the introduction of the iPhone X and Face ID, we now refer to Touch ID and Face ID together as “biometric authentication”.

To reflect this, the Touch ID section on the Settings > Authentication page is now Biometric Authentication. When enabled, the setting allows the use of both Face ID and Touch ID depending on the device (alerts and icons automatically adjust to display Touch ID or Face ID).

End User Experience

We have also taken this opportunity to improve the experience for App Catalog users when biometric authentication is enabled.

Users are now presented with more informative prompts.

The login page now shows an appropriate icon depending on whether the device uses Touch ID or Face ID.

Users can now control whether biometric authentication is enabled via a toggle in the App Catalog sidebar.

Note

When biometric authentication is configured with SSO, the App Catalog now remembers the enabled status when a user closes an app.

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 Customer Support.

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 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 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 Reapply Policies to an App.

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 Customer Support.

  

On This Page
  • No labels