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.

October 17, 2018

This release includes the following changes, enhancements, and bug fixes:

  • The iOS App Catalog now supports iPhone XR, XS, XS Max screen resolutions.

  • Added more space between apps in the iOS App Catalog.

  • Prevented apps from becoming enabled after signing even though the Enable option was not selected.

  • Fixed an issue that caused some Android apps to crash when policies were applied.

October 3, 2018

This release includes the following changes, enhancements, and bug fixes:

  • We have removed the ability to use autocomplete on the login page of the Android App Catalog and any apps with policies that require authentication.
  • Based on our evaluation of Microsoft's official end of support policies, we are no longer supporting Windows Phone and Windows 10 Mobile.
  • Updated the Android hybrid app icon for compatibility with Android 8 and 9.

  • Disabled admins no longer receive app expiration emails.

  • Fixed an issue that prevented some users from logging out of the Android App Catalog when SSO is enabled.

September 19, 2018

iOS 12 Support

We are pleased to announce full support of iOS 12 for Apperian App Management.

This support does not require a new iOS App Catalog.

Android 9 Support

We are pleased to announce full support of Android 9 Pie and Android 8.1 for Apperian App Management.

IMPORTANT

To take advantage of Android 9 support, you must update to the latest Android App Catalog and distribute it to your users. To obtain the latest App Catalog, contact Customer Support.

Account Lockout Improvements

The Account Lockout Threshold password setting allows an administrator to set the number of failed password attempts before a user's account is disabled.

We have added more options to this feature:

  • You can now specify the length of time until the lockout timer resets after being triggered.

  • You can now specify whether the lockout is permanent or temporary.

    • If temporary, you can specify how long the lockout lasts before a user can log in again.

For more information, see Set Account Lockout Threshold.

September 5, 2018

Android Push Notification Upgrade

The Android App Catalog’s push notification functionality previously relied on the Google Cloud Messaging (GCM) service, which Google deprecated earlier this year.

We also discovered a related issue that prevented Apperian from communicating with GCM, which caused push notifications to stop working on the Android App Catalog.

Per Google’s recommendation, we have now migrated our Android push notifications to their new and improved Firebase Cloud Messaging (FCM) service.

IMPORTANT

Because Google will end all support for GCM next year, and in order to resolve the known issue, we strongly encourage all customers to upgrade to the newest version of the Android App Catalog and distribute it to your users as soon as possible.

If you don’t upgrade, your Android users will not be notified of app updates in the App Catalog.

To get started, contact Customer Support.

Additionally, depending on their version of Android, when your users first launch the updated Android App Catalog, they may encounter a prompt that asks to “Update Google Play Services”. Your users will need to follow this prompt in order to receive push notifications.

New Downloads API Resource

The following API resource is now available:

Download a Specific Version of an Application File

GET /v1/downloads/direct/versions/<version_id>

Use this resource to download a specific version of a native app’s binary file. You can also specify whether to download the originally uploaded file or the latest file, which may have policies applied or be signed differently from the originally uploaded file.

August 22, 2018

Miscellaneous Improvements

This release includes performance and security improvements.

End of Support for Older Android Versions

Because of known Android security vulnerabilities, we will end all support for Android versions 4.4.2 and lower beginning on October 1, 2018.

Note

To take advantage of a bug fix for Android push notifications, all customers can update to the latest Android App Catalog and distribute it to your users. To obtain the latest App Catalog, contact Customer Support.

August 8, 2018

App Publishing API - Hybrid Apps

This release adds support for creating and managing hybrid apps via the RESTful App Publishing API.

To add hybrid app you can simply send a POST request to /v1/applications/ with a hybrid object that specifies a URL and platform for the app. Additional details are accepted, but optional.

You can update a hybrid app with PUT /v2/applications/<app_id>/, and rebuild a hybrid app with POST /v1/applications/<app_id>/.

For more information about the requirements for managing hybrid apps and a description of the new hybrid object, see Hybrid App Data.


REMINDER

We encourage all customers to use these new resources in order to take advantage of the improvements in simplicity and efficiency offered by the RESTful API.

We will deprecate the old Publishing API later this year.

Miscellaneous Improvements

This release includes the following security improvements:

  • All user sessions now expire immediately when a user’s password is changed.

  • The Account Lockout Threshold setting is now set to 5 by default for new organizations. This change does not affect any existing organizations.

We also removed  the sort option from the Popular Apps tab in the App Catalog because it was redundant.

July 25, 2018

App Publishing API - App Catalogs

This release adds support for uploading and managing App Catalogs through POST /v1/applications/ and PUT /v2/applications/<app_id>/.

The interface for adding and managing App Catalogs is exactly the same it is for adding other native apps, except that you will upload an App Catalog app file.

Note

You can now also use the API to upload APNS Push Certificate for your iOS App Catalogs. To do so, use the new PUT /v3/organizations/<org_id>/ resource, which is described in the following section.

REMINDER

We encourage all customers to use these new resources in order to take advantage of the improvements in simplicity and efficiency offered by the RESTful API.

We will deprecate the old Publishing API later this year.

Organizations API Updates

This release introduces two new Organizations API resources.

In order to simplify the organization management process, the response from these new resources always returns an organization object in JSON form. For information about the data returned, see Common Organization Data.

List Data for a Specific Organization

GET /v3/organizations/<org_id>/

This resource returns information about the specified organization.

Update an Organization’s Attributes

PUT /v3/organizations/<org_id>/

This resource allows you to manage information about an organization, including many of the organization’s settings.

Tip

You may also use this endpoint to upload your APNS Push Certificate in order to enable push notifications for the iOS Catalog.

Deprecation of Unused Features

Based on research into the way clients use our tools, we have decided to remove the following features:

  • Device Registration Notification, which sends an email every time a user connects a new device. This feature is now deprecated as of this release.

  • Application Update Compliance, which sends an email to users that haven't updated an app after it becomes mandatory. We will deprecate this feature on August 22, 2018.

If you have any questions or concerns about either of these deprecations, contact Customer Support.

July 11, 2018

This release introduced a number of minor performance and security improvements.

June 27, 2018

Jailbreak/Root Status Enhancement

Previously, Apperian would only check if a device has been compromised by jailbreaking (iOS) or rooting (Andoid) if the Jailbreak/Root Protection policy was applied to an app.

Now, if a device has been jailbroken/rooted and ANY policy is applied to an app, Apperian reports the device’s status to the Admin Portal whenever a user opens an app with policies applied. The app will still launch normally unless the Jailbreak/Root Protection policy is applied to the app.

There is no change to the Jailbreak/Root Protection policy. As always, when the Jailbreak/Root Protection policy is applied to an app, if the device has been jailbroken/rooted, Apperian prevents the user from opening the app.

The jailbroken/rooted status appears on the Users > Device Details page, as it always has.

App Catalog Sorting

App Catalog users can now sort apps by Release Date and Name. Tapping the new sort icon (at the top right of any tab with a list of apps) opens the sort options.

We also made an app’s Release Date visible in the app list.

Users Page UI Update

We updated the user interface of the Users page so it matches the design of other pages in the Admin Portal. The functionality has not changed.

June 13, 2018

New App Versions API Resources

This release adds API support for viewing and updating specific versions of an app, including all stored previous versions.

New Resources

List Data for a Specific Version of an Application

GET /v1/applications/versions/(version_id)

Use this resource to view metadata for a specific version of an app.

Update Data for a Specific Version of an Application

PUT /v1/applications/versions/(version_id)

Use this resource to update metadata for a specific version of an app.

May 30, 2018

App Publishing API - Native Apps

In the previous Apperian release, we introduced a new RESTful API for creating and updating apps.

This release adds support for native iOS and Android apps.

Because of the way the API is designed, the interface for adding and managing native apps is almost exactly the same it is for adding public apps, except that adding a native app requires an app file.

The API documentation is updated to reflect the native app functionality. For more information, including a description of how to include a file in your API request, see POST /v1/applications/, POST /v1/applications/<app_id>, and PUT /v2/applications/<app_id>.

REMINDER

We encourage all customers to use these new resources in order to take advantage of the improvements in simplicity and efficiency offered by the RESTful API.

We plan to deprecate the existing Publishing API later this year.

App Details Header

In the Admin Portal, an app’s Details page header is updated with more basic information about the app.

The Usage Count and Download Count fields are updated whenever you refresh the page.

May 16, 2018

New App Publishing API

This release includes the first iteration of a new RESTful API for creating and updating apps.

Our goal with this update is to start fresh with a modern approach that will eventually replace the existing Publishing API, which is based on an older API framework. This initial release establishes the basic mechanism which will eventually publish and manage all supported app types.

IMPORTANT

This release includes support for public app store apps only (Apple App Store and Google Play). Future releases will add support for native and hybrid apps.

Now, adding an app from a public app store is as simple as providing a URL.To support this new approach, we added new resources to the Applications API. These new resources allow you to publish and update apps without using the Admin Portal web interface. To simplify the process, the resources all deliver an identical response (an application object), and they all accept a common set of data fields in the request.

IMPORTANT

Starting with this release, we encourage all customers to use these new resources in order to take advantage of the improvements in simplicity and efficiency offered by the RESTful API.

We plan to deprecate the existing Publishing API later this year.

New Applications API Resources

Add an Application

POST /v1/applications/

Use this resource to add an app to your organization.

When you provide a public store URL, the API automatically populates the app metadata (name, descriptions, icon, screenshots, etc) by pulling it from the public store.

Create a New Version of an Application

POST /v1/applications/<app_id>

Use this resource to add a new version of an existing app in your organization.

The most common reason to create a new version is to publish a new version of an app file, but this can also be used to refresh an app’s metadata from the public store.

Update an Application

PUT /v2/applications/<app_id>

Use this resource to update the metadata for an existing app in your organization.

We overhauled this existing endpoint to bring it in line with the new Add and Create endpoints. The v1 version of this endpoint is still available.

Miscellaneous API Changes

This release also includes a few additional updates:

  • The application object now includes a field called enabled, which allows you to change the app’s status via the API. This supplements the existing status field.

  • The API Documentation is updated with:

New Look for the Admin Portal

We’ve updated the icons and colors in the Admin Portal to better reflect the overall Arxan brand identity.

We also revised all references to the former EASE product name, as the product is now called Apperian App Management.

This is a style update only; there are no changes to existing functionality.

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.

Did You Know?

We have a new, more modern, and more powerful App Publishing API.

For more information, see Applications API.


On This Page
  • No labels