Skip to content

Feature: App Enabler

Overview

This feature enables packages that the user can access while disabling unneeded packages.

To use this feature, set useAppEnabler to true within Launcher "settings" configuration.

If there are packages that should not be affected by this feature, add them to the "untouchables" collection. Packages identified as untouchable will not be enabled or disabled by the App Enabler feature.

Flow

The enabling / disabling of packages occurs during one of three timeframes:

  1. Initial configuration load

  2. After a configuration update occurs (new configuration is installed)

  3. After a session change (login or logout)

When the App Enabler logic is invoked, it looks at the list of installed applications, then gets a list of whitelisted applications that the current user can access (per group inclusion).

The App Enabler will then build a list of applications to disable and a list of applications to enable. If any of the applications exist within the 'untouchables' collection, they are ignored.

Once the collections are built, platform services are invoked to enable and disable the packages.

Technical Notes

Configuration:

useAppEnabler: Indicates use of package enabler

untouchables: List of packages to ignore

Example:



   "settings": {
        ...
       "useAppEnabler" : true,
       ...
   }
...
   "untouchables" : [
      "com.android.(.*)",
      "com.airwatch.(.*)",
      "com.bluefletch.ems.support",
      "com.bluefletch.ems.auth"
    ],


Feature Introduced

Feature Introduced in Launcher 1.x.

Works in conjunction with Groups / Group_Inclusion whitelisting of applications.