This topic covers the available Custom XML to be implemented with Workspace ONE Launcher for Android in each version.

Configure Custom XML for Launcher

The Custom Settings payload can be used when new Android functionality releases or features that Workspace ONE UEM console does not currently support through its native payloads. Use the Custom Settings payload and XML code to manually enable or disable certain settings.

Be sure you are using the right characteristic type for your profile type:
  • For Android profiles, use characteristic type = "com.airwatch.android.androidwork.launcher".
  • For Android (Legacy) profiles, use characteristic type = "com.airwatch.android.kiosk.settings".
To configure the custom XML:
  1. Navigate to Resources > Profiles & Baselines > Profiles > Add > Add Profile > Android.
  2. Configure the profile's General settings,
  3. Configure the applicable payload (for example, Restrictions or Passcode).You can work on a copy of your profile, saved under a "test" organization group, to avoid affecting other users before you are ready to Save and Publish.
  4. Save, but do not publish, your profile.
  5. Select the radio button from the Profiles List View for the row of the profile you want to customize.
  6. Select the XML button at the top to view the profile XML.
  7. Find the section of text starting with <characteristic> ... <characteristic> that you configured previously, for example, Restrictions or Passcode. The section contains a configuration type identifying its purpose, for example, restrictions.
    Note: Be sure to always modify at least one number or character in the UUID before pasting into the UEM console. The UUID values are a sequence of values within 0-9 and a-f. Any one value can be changed to another within these ranges to distinguish this from the base UUID in this docs page. This helps avoid issues when using multiple profiles with the same UUID.
  8. Copy this section of text and close the XML View. Open your profile.
  9. Select the Custom Settings payload and select Configure. Paste the XML you copied in the text box. The XML code you paste should contain the complete block of code, from <characteristic> to <characteristic>.
    1. This XML should contain the complete block of code as listed for each custom XML.
    2. Administrators should configure each setting from <true /> to <false /> as desired.
    3. If certificates are required, then configure a Certificate payload within the profile and reference the PayloadUUID in the Custom Settings payload.
  10. Remove the original payload you configured by selecting the base payload section and selecting the minus [-] button. You can now enhance the profile by adding custom XML code for the new functionality.Any device not upgraded to the latest version ignores the enhancements you create. Since the code is now custom, you should test the profile devices with older versions to verify expected behavior.
  11. Select Save & Publish

Use the sections below to find the custom XML.

Offline Mode for CICO (Beta)

Available in Workspace ONE Launcher 21.04

Offline mode allows employees can continue their work even when they are unable to log in due to network issues. You can designate a Launcher profile as an offline mode profile which can only be accessed when the device is offline.

To Beta offline mode, enroll your device into a UAT environment that has data-driven UI enabled, such as CN135.

Push the following custom XML to your organization group to enable offline mode:
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
 <parm name="EnableOfflineMode" value="True"/>
 </characteristic>

Disable FocusMonitoring API

Available in Workspace ONE Launcher 4.8

On Samsung devices, Launcher defaults to using the Samsung Focus Monitoring API. This allows Launcher to automatically foreground applications without the user having to grant the Android Usage Access Permission. The admin can disable this feature using the following custom XML. Disabling this feature on Samsung devices will require users to grant the usage access permission on the first launch of Launcher.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="DisableFocusMonitoring" value="True"/>
</characteristic>

Show Popup Notifications

Available in Workspace ONE Launcher 4.8

Admins can generate popup notifications regardless of channel priority using this custom XML. To show popups, the notification bar cannot be disabled. Admins can create popups regardless of how the app sending the notification prioritizes its notification channel.

After Android O, popups will only show if the app sending the notification sets a notification channel to show popups, but this custom XML bypasses that behavior.

For generating popup for all allowed apps:
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="ShowPopupNotification" value="True"/>
</characteristic>
For generating popup for specific apps:
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="ShowPopupNotification" value="com.application1.package, com.application2.package"/>
</characteristic>

Hide Enable Notifications Button

Available in Workspace ONE Launcher 4.8

Admins can hide the “Enable Notifications” button from the Launcher dropdown menu by using the following custom XML.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="AllowEnableNotification" value="False"/>
</characteristic>

Disable Sensor Orientation

Available in Workspace ONE Launcher 4.8

Use this setting to prevent the device from switching to reverse portrait mode or reverse landscape orientation.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="DisableSensorOrientation" value="True"/>
</characteristic>

Speed Lockdown

Available in Workspace ONE Launcher 4.7

Use this custom XML to block device access when exceeding a specified speed threshold.
<parm name="SpeedLockdownSettings" value="{&quot;speed&quot;:&quot;20&quot;, &quot;unit&quot;:&quot;0&quot;, &quot;timeThreshold&quot;:&quot;10000&quot;, &quot;troubleshootPasscode&quot;:&quot;1234&quot;, &quot;headerText&quot;:&quot;Too Fast&quot;, &quot;messageText&quot;:&quot;Stop to unlock&quot;}" />

The default values are as followed:

  • Unit = 1 (m/h)
  • TimeThreshold = 5000 (5 seconds)
  • HeaderText = "Device Locked"
  • MessageText = "Come to a complete stop to unlock device"

The accepted values are as followed:

  • Speed > 0

  • Unit = 0 - km/h , 1 - m/h (default = m/h)

  • TimeTheshold > 0 (in milliseconds)

  • TroubleshootPasscode (length > 0)

  • HeaderText (length > 0 chars < 15 chars)
  • MessageText (length > 0 chars < 30 chars)

Runtime Permissions

Available in Workspace ONE Launcher 4.6

Use this custom XML if you want to enable the Runtime Permissions prompt for end users.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
                    <parm name="RunTimePermissionSetting" value="0"/>
                    </characteristic>
The value can be one of the following :
  • "0": Runtime permission prompt displays and the user cannot continue until all the permissions are granted. (Required)
  • "1": Runtime permission screen displays but is not mandatory to grant all the permissions. (Optional)
  • "2": Runtime permission screen is not displayed. (Not Required)

Write Settings Permission

Available in Workspace ONE Launcher 4.6

You can enable the 'Write Permissions' prompt during Launcher setup which allows users to change system settings inside the Launcher profile. When users go to configure settings inside the Launcher, for example, if the user wants to change screen brightness or change auto-rotate settings from inside the Launcher, they are no longer prompted to allow the permission at that time as the permission was granted during setup.

<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
                    <parm name="WriteSecurePermissionSettings" value="True"/>
                    </characteristic>

Skip overlay permission screen

Available in Workspace ONE Launcher 4.6

Use this custom XML to over to skip the 'Draw over other apps permission" which is used for adding overlays and blacklisting apps. This permission displays during initial Launcher setup.

 <characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
                <parm name="SkipOverlayPermissionScreen" value="True"/>
                </characteristic>

Actionbar Settings

Available in Workspace ONE Launcher 4.6

If you want to set a default action bar title to display during Check-in/Check-out (CICO) screen, this custom XML lets you configure Launcher to always retain the action bar title.

Since this XML is applicable for CICO, it should be pushed for the staging user. If the retainChildTitle is set to false or ignored, the defaultTitle will always be used in CICO action bar. If the child user has lookup values like username or email and retainChildTitle is set to true, that title will be retained, i.e. the email of the last user will appear in the CICO screen. During Launcher first configuration, it uses the default title.

<characteristic type="com.airwatch.android.kiosk.settings" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
                    <parm name="ActionBarSettings" value="{&quot;retainChildTitle&quot;:&quot;True&quot;, &quot;defaultTitle&quot;:&quot;Vmware - Airwatch&quot;}" />
                    </characteristic>

Wallpaper Scale Type

Available in Workspace ONE Launcher 4.5+

When using an image in Launcher settings, changing the device orientation can change the scaling of the image. For example, if you use a square image in Portrait mode and the rotate the device to Landscape mode, it changes to fit the entire screen instead of maintaining the square scaling.

If you want to set the scale type of the wallpaper to remain the same for different screen orientations, the following custom XML can be used:

<chara:teristic type="com.airwatch.android.kiosk.settings" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="WallpaperScaleType" value=" {&quot;portraitScaleType&quot;:&quot;FIT_CENTER&quot;, &quot;landscapeScaleType&quot;:&quot;FIT_XY&quot;}"/>
</characteristic>

App Pinning

Available in Workspace ONE Launcher 4.5+

App pinning allows you to pin icons at the bottom of the Workspace ONE Launcher screen similar to how any native launcher functions. The icons are placed in a bottom bar and remain pinned to the screen as users swipe through different screens. The basic custom XML is a JSON array of items that are to be added to the bottom bar:
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="HotSeatBarSettings" value="{&quot;HotSeatBarSettings&quot;: [
{&quot;pName&quot;: &quot;com.android.chrome&quot;,&quot;title&quot;: &quot;GoogleChrome&quot;,&quot;applicationType&quot;: &quot;misc&quot;,&quot;position&quot;: &quot;1&quot;} ]}"/>
</characteristic>
The parameters to add an application:
  • pName - Indicates the package name of the application that has to be added. If an admin has not mentioned the package name, the application is not added to the bottom bar. This field is required.
  • title - Indicates the application name that has to be displayed on the screen. This field is required.
  • position - Indicates the position of the application to be added to the bottom bar. Position attribute is 0 indexed.

    The application is not added to the bottom bar if the admin :

    • Has not added the position attribute.
    • If the position is greater than the number of columns that are configured in the Launcher profile.
  • applicationType - This attribute indicates the type of shortcut that has to be added to the bottom bar. This field is required. The value should be one of the following:
    • Misc - Miscellaneous application
    • Public - Public application
    • Internal - Internal application
    • Bookmarks - Bookmark
  • folderName - indicates whether the application has to be added in a folder.
    Note: If you want to add multiple applications to the same folder, then the folder name for all those applications should be the same and the position of all the applications should also be the same.
  • URL - Indicates the URL that the bookmark has to load. The field us required if applicationType is set to Bookmarks.
  • subPackageNames - Specifies which activities should be added in case of multi-launch application. Activity names must be comma-separated as shown in the above XML.
  • LaunchAppOnStartup - Specifies whether the application should be launched as soon as the profile is loaded.
Note: If a dynamic application (application with * in package name) is added to the bottom bar, then a folder is created with the name equal to the value of the "title" attribute and all the applications included in the subpackage will be added to that folder.
Use Case Custom XML
Add an application to bottom bar Miscellaneous
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="HotSeatBarSettings" value="{&quot;HotSeatBarSettings&quot;: [
{&quot;pName&quot;: &quot;com.android.chrome&quot;,&quot;title&quot;: &quot;GoogleChrome&quot;,&quot;applicationType&quot;: &quot;misc&quot;,&quot;position&quot;: &quot;1&quot;}]}"/>
</characteristic>
Public
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="HotSeatBarSettings" value="{&quot;HotSeatBarSettings&quot;: [
{&quot;pName&quot;: &quot;com.android.chrome&quot;,&quot;title&quot;: &quot;GoogleChrome&quot;,&quot;applicationType&quot;: &quot;public&quot;,&quot;position&quot;: &quot;0&quot;}]}"/>
</characteristic>
Internal
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="HotSeatBarSettings" value="{&quot;HotSeatBarSettings&quot;: [
{&quot;pName&quot;: &quot;com.android.chrome&quot;,&quot;title&quot;: &quot;GoogleChrome&quot;,&quot;applicationType&quot;: &quot;internal&quot;,&quot;position&quot;: &quot;1&quot;}]}"/>
</characteristic>
Add a bookmark to the bottom bar
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="HotSeatBarSettings" value="{&quot;HotSeatBarSettings&quot;: [
{&quot;url&quot;: &quot;https://www.google.com&quot;,&quot;title&quot;: &quot;Google&quot;,&quot;applicationType&quot;: &quot;bookmarks&quot;,&quot;position&quot;: &quot;1&quot;}]}"/>
</characteristic>
Add folder with multiple applications to the bottom bar
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="HotSeatBarSettings" value="{&quot;HotSeatBarSettings&quot;: [
{&quot;pName&quot;: &quot;com.android.chrome&quot;,&quot;title&quot;: &quot;GoogleChrome&quot;,&quot;applicationType&quot;: &quot;misc&quot;,&quot;position&quot;: &quot;1&quot;,&quot;folderName&quot;: &quot;googleApps&quot;} , {&quot;pName&quot;: &quot;com.google.android.gm&quot;,&quot;title&quot;: &quot;Gmail&quot;,&quot;applicationType&quot;: &quot;misc&quot;,&quot;position&quot;: &quot;1&quot;,&quot;folderName&quot;: &quot;googleApps&quot;} ]}"/>
</characteristic>
Add a multi Launch application
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="HotSeatBarSettings" value="{&quot;HotSeatBarSettings&quot;: [
{&quot;pName&quot;: &quot;com.lotus.sync.traveler&quot;,&quot;title&quot;: &quot;IBMVerse&quot;,&quot;applicationType&quot;: &quot;misc&quot;,&quot;position&quot;: &quot;2&quot;,&quot;subPackageNames&quot;: &quot;Verse,Mail,Actions&quot;}]}"/>
</characteristic>
Add an application with Launch on startup to the bottom bar
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="HotSeatBarSettings" value="{&quot;HotSeatBarSettings&quot;: [{&quot;pName&quot;: &quot;com.*&quot;,&quot;title&quot;: &quot;ComApps&quot;,&quot;position&quot;: &quot;3&quot;}]}"/>
</characteristic>
Add an application with Launch on startup to the bottom bar
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="HotSeatBarSettings" value="{&quot;HotSeatBarSettings&quot;: [
{&quot;pName&quot;: &quot;com.android.chrome&quot;,&quot;title&quot;: &quot;GoogleChrome&quot;,&quot;applicationType&quot;: &quot;misc&quot;,&quot;position&quot;: &quot;1&quot;,&quot;LaunchAppOnStartUp&quot;: &quot;true&quot;}]}"/>
</characteristic>

Staging Admin Passcode

Available in Workspace ONE Launcher 4.4.1+

Users can exit the Workspace ONE Launcher from the check-in/check-out screen by entering the password specified in the custom XML. After checkout, the staging admin passcode will be replaced by the end user profile admin passcode. Since the admin icon must be displayed in the check-in/check-out screen, the custom XML must be pushed for the staging user. Use this custom XML to enable an admin icon in the login screen:
<characteristic type="com.airwatch.android.kiosk.settings" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="StagingAdminPasscode" value="1234"/>
</characteristic>

Allow Staging Activities

Available in Workspace ONE Launcher 4.4+

You can allow activities or Package Names for end users after devices have been checked out. This custom setting can be used in following scenarios:
  • Allow activities or package names at parent Organization Group.
  • Allow activities before end user profile lands on the device.
Use this custom XML to allow activities in the check in/check out screen:
<characteristic type="com.airwatch.android.kiosk.settings" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="AllowStagingActivities" value="{&quot;AllowStagingActivities&quot;: [ {&quot;pName&quot;: &quot;com.android.settings&quot;,&quot;cName&quot;: &quot;com.android.settings.LanguageSettings&quot;}, {&quot;pName&quot;: &quot;com.android.settings&quot;,&quot;cName&quot;: &quot;com.android.settings.WifiPicketActivity&quot;} ]}"/>
</characteristic>

Allow Log Collection

Available in Workspace ONE Launcher 4.4+

If admin wants to collect logs for a certain use case or in certain scenarios, use this Custom XML and request the debug logs from the Workspace ONE UEM console:

<characteristic type="com.airwatch.android.kiosk.settings" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec"><parm name="AllowLogCollection" value="True"/></characteristic>

Allow Staging Profile

Available in Workspace ONE Launcher 4.2.1+

If the customer assigns a single profile to all the users at the parent Organization Group level, then use this custom XML:
<characteristic type="com.airwatch.android.kiosk.settings"
        uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec"><parm name="AllowStagingProfile"
        value="True"/></characteristic>

Settings Overlay for Android Tablet

Available in Workspace ONE Launcher 4.2+

This overlay can be used with allow list custom settings areas for users on Android tablets to prevent the user from accessing settings outside of the Launcher interface. To implement an overlay, use the following Custom XML:
<characteristic type="com.airwatch.android.kiosk.settings" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="TabletOverlaySettings" value="{&quot;activityNames&quot;:&quot;com.android.settings.Settings$lockAndsecuritySettingsActivity,com.sonyericsson.setupwizard,com.honeywell.systemtools.autoinstall&quot;,&quot;potraitPercentage&quot;: &quot;60&quot;,&quot;transparency&quot;:&quot;100&quot;,&quot;landscapePercentage&quot;: &quot;50&quot;}"/characteristic> 
The above custom setting has multiple parameters:
  • activityName: When this parameter is added the overlay appears only when the settings are accessed through the particular activity.
  • portraitpercentage: This parameter configures the overlay percentage in portrait mode.
  • transparency: This parameter configures the overlay transparency in terms of percentage.
  • landscapePercentage: This parameter configures the overlay percentage in landscape mode.

Force Reset Launcher Layout on Profile Update

Available on Workspace ONE Launcher 4.2+

Through use of Workspace ONE Launcher if given the ability, users can move folders and application around to their preference. Normally these rearrangements are maintained when profiles or the Launcher are updated. To revert to the original configuration, this custom XML can ignore the user preference and go back to the original layout:
<characteristic type="com.airwatch.android.kiosk.settings" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
 <parm name="AllowProfileReset" value="True"/>
 </characteristic>

Set Launcher as Default after Reboot

Available on Workspace ONE Launcher 4.2+

Currently, when a user exits Workspace ONE Launcher using admin passcode and reboots the device, Workspace ONE Launcher is not set as the default launcher. To set Workspace ONE Launcheras the default launcher for the device, the profile must be pushed again.

This setting is used in cases where an environment administrator exits Workspace ONE Launcherand forgets to reenter the secure launcher after completing their tasks. This feature works only on select Android devices, namely, Honeywell, Zebra and Samsung.

In cases where the launcher opens after a delay, the length of time can be defined in seconds in the XML below:
<characteristic type="com.airwatch.android.kiosk.settings" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
 <parm name="AllowLaunchOnReboot" value="5"/>
 </characteristic>

Allow Staging Settings

Available in Workspace ONE Launcher 4.1+

In Workspace ONE Launcher, the option of toggling Wi-Fi is only available in the staging screen. If a user wants to configure Wi-Fi settings, long press on the Wi-Fi icon to launch the native Wi-Fi settings. Since this setting has to be accessed in the staging screen, the below custom xml must be pushed for the staging user (parent organization group). This can be configured by using below flag:

<characteristic type="com.airwatch.android.kiosk.settings" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="AllowStagingSettings" value="True"/></characteristic> 

Floating Home Button Setting

Available with Workspace ONE Launcher4.0 +

In COSU mode, the HOME and RECENTS buttons are disabled making it hard for a user to switch between the applications. Workspace ONE Launcher provides a way to have a similar home screen experience by adding a Floating Home button.

Functionalities of the Floating Home button:

  • The Floating Home button is shown on top of any application. Clicking the Floating Home button launches the home screen which is Workspace ONE Launcher since it is the default home application.
  • The Floating Home button can be moved across any part of the screen.
  • The Floating Home button, if not touched for a particular amount of time, fades so that it allows to read the content below it.
  • The Floating Home button becomes active again when the user touches it back.

Note: By default the Floating Home button is added in Multi-App and Template modes.

The Floating Home button can be configured by using the below setting:
<characteristic
          type="com.airwatch.android.kiosk.settings"
          uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec"><parm name="HomeFloatingButtonSetting" value="{&quot;Size&quot;:&quot;Small&quot;,&quot;Color&quot;:
          &quot;#F377F7&quot;,&quot;TimeToFade&quot;:&quot;5&quot;,&quot;FadeValue&quot;:&quot;3&quot;}"/></characteristic>
Things that can be configured for the Floating Home button:
  • Size: Indicates the size of the Floating Home button. The possible values: Small, Medium, Large.
  • TimetoFade: Indicates the time in seconds for Floating Home button to fade away.
  • Color: Indicates the color of the Floating Home button. color must be specified in a Hex code Eg: #F377F7.
  • FadeValue: Indicates the amount of fading required.

Remove Floating Home Button Setting

Available with Workspace ONE Launcher 4.0+

In COSU mode the Home and Recents buttons are disabled making it hard for a user to switch between the applications. Workspace ONE Launcher provides a way to have a similar home screen experience by adding a Floating Home button.

The floating home button can be removed by using the below setting:
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="RemoveHomeFloatingButtonSetting" value="True"/></characteristic>

Allow Home Floating Setting

Available with Workspace ONE Launcher 4.0+

The Floating Home button is enabled for Android compliant devices only. On some devices, the default home button may be inaccessible. This is applicable only for non-Android devices and only in MULTIAPP and TEMPLATE modes. If an admin wants the Floating Home button functionality, use the below Custom XML.
<characteristic type="com.airwatch.android.kiosk.settings"
          uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec"><parm name="AllowHomeFloatingSetting" value="True"/></characteristic>

Single App Floating Button Setting

Available with Workspace ONE Launcher 4.0+

In Single application mode launcher provides a Floating action button for users to access different launcher settings. This button can be configured by using the below setting:
<characteristic
          type="com.airwatch.android.kiosk.settings"
          uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec"><parm name="SingleAppFloatingButtonSetting" value="{&quot;Size&quot;:&quot;Small&quot;,&quot;TimeOut&quot;:
          &quot;2&quot;,&quot;FixPosition&quot;:&quot;true&quot;}"/></characteristic>

Things that can be configured for floating action button:

  • Size: Indicates the size of the floating action button. Possible values: Small, Medium, Large.
  • Timeout: Indicates the time in seconds for floating button to fade away. Should be an integer only.
  • FloatingTimeoutValue custom flag is now deprecated from version 4.0 instead we should use this flag.
  • FixPosition: When enabled, the user cannot move the floating action button. It is positioned at the right end corner. This setting replaced the FixSettingsPosition from previous versions.

Allow Localized App Names

Available with Workspace ONE Launcher 4.0+

Currently in Launcher application names are displayed according to the names that are set on the console. Admin can use this flag to display application names according to the language set on the device:
<characteristic
          type="com.airwatch.android.kiosk.settings"
          uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec"><parm name="AllowLocalizedAppNames" value="True"/></characteristic>

Extra Lock Task Packages

Available with Workspace ONE Launcher 4.0+

This setting specifies the packages that are allowed to be launched but are not on the allow list.By default launcher automates the process of allowlist settings and other application ,but in any case if some application cannot be launched then we can use this flag.Note: This is only for troubleshooting purposes.
<characteristic
          type="com.airwatch.android.androidwork.launcher"
          uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec"><parm name="ExtraLockTaskPackages"
          value="com.android.settings,com.google.android.chrome/></characteristic>

Skip Usage Access Permission

Available with Workspace ONE Launcher 4.0+

In case the customer has no use case of using usage access permission they can use the below custom profile to skip this permission being asked from launcher during configuring.
<characteristic
          type="com.airwatch.android.androidwork.launcher"
          uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec"><parm name="SkipUsageAccessPermission" value="True"/>
      </characteristic>

Skip CosuSetup - COSU

Available with Workspace ONE Launcher 4.0+

Launcher 4.0 uses new native Android APIs for Google EMM Registered enrollments in the standard Android profile. These new APIs fall under the umbrella of Corporate-Owned Single-Use (COSU) mode. Some features are removed while using COSU mode, this is purposeful to be able to drastically increase the security of the Launcher application. Please see the drawbacks and benefits below, use this custom XML tag to skip COSU mode setup.
<characteristic
          type="com.airwatch.android.androidwork.launcher"
          uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec"><parm name="SkipCosuSetup" value="True"/></characteristic>

When in COSU mode (Lock Task mode), devices running versions of Android older than 9.0 will see some features disabled by default. Impacted features include the removal of the Notification / Status Bar at the top of the screen, and the Home & Recent Task soft keys at the bottom of the screen.

By using COSU mode (default), the level of security is greatly improved within the Application.

In DO mode COSU will be configured by default, In case the customer's use cases are not satisfied then they can disable COSU setup.

Display Lock Screen Message

Available with Workspace ONE Launcher 3.3+

The Lock Screen message displays a custom message on the lock screen. You can customize the message with the following attributes:

  • Message - Indicates the text to be displayed on the lock screen. If a message is not included in the XML, then the checked-out user name is displayed instead.
  • Position - Indicates the position of the text on the lock screen.

    Values = topLeft, topRight, topCenter, bottomLeft, bottomRight, bottomCenter and center. If position is not included in the XML, the position defaults to topCenter.

  • TextSize- Indicates the size of text in sp units.
  • TextColor - Indicates the color of the text in hexadecimal format.
To enable and implement this feature, the setting must be pushed down through the custom settings payload:
<characteristic type="com.airwatch.android.kiosk.settings"
          uuid="eadfebd8-7f4c-4837-b9dd-dfcf31bd84e6">
<parm name="DisplayLockScreenMessage"
          value="{&quot;message&quot;:&quot;AirWatch&quot;,&quot;position&quot;:&quot;topRight&quot;,&quot;textSize&quot;:&quot;20&quot;,
          &quot;textColor&quot;:&quot;#4E993E&quot;}"/> </characteristic>

Hot Swap Profile Caching

Available with Workspace ONE Launcher 3.3+

As check-in/check-out is common, users often check out the same device but have to wait a considerable amount of time for profiles to be a. As a result, AirWatch has enhanced the Hot Swap functionality to limit the number of profiles that are cached during check-in/check-out.Profiles are cached for the value specified in the custom setting. If a new profile is added to the cache and the number of cached profiles exceeds the specified value, the most recent specified number of profiles are cached and the initial profiles are deleted. Additionally, the title bar icons of the profiles are cached, but not the wallpapers.To enable and implement this feature, the setting must be pushed down through the custom settings payload:
<characteristic type="com.airwatch.android.kiosk.settings"
          uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec"><parm name="MaxProfilesAllowed" value="Value"/></characteristic>

Restrict Power Off/Restart/Safe Mode Options

Available with Workspace ONE Launcher 3.3+

Users can easily exit secure launcher by rebooting into safe mode. To enter into safe mode:
  1. Press and hold power button on the device.
  2. On the screen, touch and hold Power off.
  3. The "Reboot to Safe mode" dialog displays.
To prevent this, AirWatch has an API to disable the power off button on SAFE devices; For non-SAFE devices admins can use the following Custom XML profile. To enable and implement this feature, the setting must be pushed down through the custom settings payload:
<characteristic type="com.airwatch.android.kiosk.settings"
          uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec"><parm name="DismissSafeRebootDialog" value="True"/></characteristic>
When users press and hold the power button, the power dialog displays. To dismiss this dialog, use the following custom XML - the dialog is dismissed after a one second delay. To enable and implement this feature, the setting must be pushed down through the custom settings payload:
<characteristic type="com.airwatch.android.kiosk.settings"
          uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec"><parm name="DismissPowerOffDialog" value="True"/></characteristic>

Selective App Cache Clearing

Available with Workspace ONE Launcher 3.3+

The Workspace ONE UEM console setting labeled "Clear App data on logout" will clear the data of all the assigned allowed application after logging out. Admins can provide a set of applications for which the data should not be cleared between check-in/check-out by using the following XML:
<characteristic type="com.airwatch.android.kiosk.settings"
          uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec"><parm name="DonotClearAppDataSet"
          value="com.airwatch.browser,com.android.testapplication"/></characteristic>

For each package ID included in the data set, the App Cache will not be cleared on check-in/check-out.

Restrict Folder Renaming

Available with Workspace ONE Launcher 3.3+

By default, AirWatch Launcher allows end users to rename folders as a part of the customization options. Administrators can now disable folder renaming. To enable and implement this feature, the setting must be pushed down through the custom settings payload:
<characteristic type="com.airwatch.android.kiosk.settings"
          uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec"><parm name="DisableFolderRename" value="True"/></characteristic>

Usage Access

Available with Workspace ONE Launcher 3.2+

Sent from the console to allow the user to navigate to Usage access settings.
<characteristic type="com.airwatch.android.kiosk.settings"
        uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="UsageAccess"
        value="True"/>
</characteristic>

Floating Button Timeout

Available with Workspace ONE Launcher 3.2+

Used to set the timeout value of the Floating Button in Single App Mode. Should be an integer only. If this is not sent from the Console, Launcher uses a default value of 10 seconds.
<characteristic type="com.airwatch.android.kiosk.settings"
        uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="FloatingTimeoutValue"
        value="15"/>
</characteristic>

Fix Floating Button Position

Available with Workspace ONE Launcher 3.2+

When enabled, the user will not be able to move the floating action button. It will be positioned at right end corner.
<characteristic type="com.airwatch.android.kiosk.settings"
        uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="FixSettingsPosition"
        value="True"/>
</characteristic>

Dynamic Whitelisting of Settings

Available with Workspace ONE Launcher 3.2+

This setting allows you to assign an allowlist of certain native setting which may not have been included in Launcher settings or it can be a native setting screen specific to OEM.

Details needed to allow a setting:

  • SettingName to be displayed on Launcher settings screen.
  • Packagename and classname or Action name of that particular native setting to launch.

If only Action is used:

<characteristic type="com.airwatch.android.kiosk.settings"
        uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="CustomSettings"
        value="{&quot;CustomSettings&quot;: [
{&quot;name&quot;: &quot;Location
        Settings&quot;,&quot;action&quot;:
        &quot;android.settings.LOCATION_SOURCE_SETTINGS&quot;}
]}"/></characteristic>

If packageName and class name is used:

<characteristic type="com.airwatch.android.kiosk.settings"
        uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="CustomSettings"
        value="{&quot;CustomSettings&quot;: [
{&quot;name&quot;: &quot;Manage Applications
        Settings&quot;,&quot;pName&quot;: &quot;com.android.settings&quot;,&quot;cName&quot;:
        &quot;android.settings.MANAGE_APPLICATIONS_SETTINGS&quot;}
]}"/>
</characteristic>

For additional information, please see the Android Developer Settings page.

Launcher Branding

Available with Workspace ONE Launcher 3.2+

Provides a proper combination of Action Bar color and Status Bar color (Light and dark) as recommended by Google. You may set different colors according to you company’s brand colors .

Auto Branding: If you do not want to specify individual colors you can use this flag. In order for this to work, title bar icon (logo) must be present.The extracted colors for branding are from the company logo.

To enable and implement this feature the below flag must be pushed down through the custom settings payload:
<characteristic type="com.airwatch.android.kiosk.settings"
        uuid="eadfebd8-7f4c-4837-b9dd-dfcf31bd84e6">
<parm name="AllowAutoBranding"
        value="true" />
</characteristic>

To personalize, then you can specify the title bar color, title text color, primary accent color, status bar color, and highlight color. Colors must be specified in hexadecimal color format:

<characteristic type="com.airwatch.android.kiosk.settings"
        uuid="eadfebd8-7f4c-4837-b9dd-dfcf31bd84e6"><parm name="AllowBranding"
        value="
{&quot;titleColor&quot;:&quot;#FC002E&quot;,&quot;titleTextColor&quot;:
        &quot;#F377F7&quot;,&quot;accentColor&quot;:&quot;#36E712&quot;,&quot;highlightColor&quot;:&quot;#4E993E&quot;,&quot;statusBarColor&quot;:&quot;#FC002E&quot;}"/>
</characteristic>

Dynamic Whitelisting of Activities

Available with Workspace ONE Launcher 3.2+

To allow a particular activity , specify a list of activities with package names in the below flag. These activities will not be visible on the Launcher settings screen.

<characteristic type="com.airwatch.android.kiosk.settings"
        uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="CustomActivities"
        value="{&quot;CustomActivities&quot;: [
{&quot;pName&quot;:
        &quot;com.example.demoapplication&quot;,&quot;cName&quot;:
        &quot;com.example.demoapplication.MainActivity&quot;},
{&quot;pName&quot;:
        &quot;com.example.demoapplication&quot;,&quot;cName&quot;:
        &quot;com.example.demoapplication.Main2Activity&quot;}
]}"/>
</characteristic>

Remove Welcome Screen

Available with Workspace ONE Launcher 3.2+

Currently, Launcher displays a welcome screen when it is pushed to the device. This can be removed by clicking the “Dismiss” (Cancel) button on the right lower corner. The below flag can be used to remove the Welcome screen.
<characteristic type="com.airwatch.android.kiosk.settings"
        uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="RemoveWelcomeScreen"
        value="True"/>
</characteristic>

Clear Application Data

Available with Workspace ONE Launcher 3.2+

Basically, in multi-user mode with checkin/checkout and Launcher, a user's data is cached/saved even after that user checks the device in.

Using OEM APIs that support it, Launcher will call Agent SDK API to clear the application data for all application that Launcher has allowed for a specific user if we use the below flag.

Workspace ONE does not clear application data for Anchor applications (Agent, Launcher, OEM Services).

To enable and implement this feature, the setting must be pushed down through the custom settings payload:

<characteristic type="com.airwatch.android.kiosk.settings"
        uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="ClearAppData"
        value="True"/>
</characteristic>

Inactivity Timer

Available with Workspace ONE Launcher 3.2+

Specify an amount of time in which the device will automatically lock the Launcher screen and require the previously signed in user to re-enter their password to re-access the Launcher screen. In addition, if there is a user that has currently locked the Launcher screen, there needs to be a mechanism/option to force sign out the user and return the Launcher to the initial login screen where a different/new user can then log into that device. Note, this feature is not compatible with Workspace ONE Access.

To enable and implement this feature, the setting must be pushed down through the custom settings payload:
<characteristic type="com.airwatch.android.kiosk.settings"
        uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="InActivityLock"
        value="True"/>
</characteristic>
If admin wants to specify the timeout value he can do so using the below flag . It must be an integer.The timeout value is in minutes.
<characteristic type="com.airwatch.android.kiosk.settings"
        uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="InActivityLock"
        value="True"/>
<parm name="InActivityTimeout"
        value="10"/>
</characteristic>

Hot Swap Profile Caching:

Available with Workspace ONE Launcher 3.2+

As check in/check out is done frequently, users often check out the same device but have to wait for a considerable amount of time for the profile to get applied after checking out. Workspace ONE can expedite this by caching profile per user when the user checks out that particular device for the first time.

To enable and implement this feature, the setting must be pushed down through the custom settings payload:
<characteristic type="com.airwatch.android.kiosk.settings"
        uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="CacheProfile"
        value="True"/>
</characteristic>

Allow WebView inside Launcher:

Available with Workspace ONE Launcher 3.2+

Disable the WebView that is built into Workspace ONELauncher. If there is no Browser installed on the device, web clips will not open. WebView will be disabled by default if admins want it enabled then they can do so by using the below flag:

<characteristic type="com.airwatch.android.kiosk.settings"
        uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="AllowBuiltInBrowser"
        value="True"/>
</characteristic>

Notification Access in Launcher:

Available with Workspace ONE Launcher 3.2+

Workspace ONE Launcher is capable of catching and displaying notifications to devices, but you need to enter the Admin mode on the device through password and enable it. End users cannot do it themselves. This flag will prompt end users to enable notifications while configuring Launcher.

For Phone:
<characteristic type="com.airwatch.android.kiosk.settings"
        uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="AllowNotificationPermission"
        value="True"/>
</characteristic>
For tablets, you will need to use another flag in conjunction with the above flag, because in some tablets the notification settings can be opened in fragmented view. If 'canLaunchNativeSettings' is already used then there is no need for this flag:
<characteristic type="com.airwatch.android.kiosk.settings"
        uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="AllowNotificationPermission"
        value="True"/>
<parm name="ForceTabletNotificationPermission"
        value="True"/>
</characteristic>
or
<characteristic type="com.airwatch.android.kiosk.settings"
        uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="AllowNotificationPermission"
        value="True"/>
<parm name="CanLaunchNativeSettings"
        value="True"/>
</characteristic>

Dynamically add shortcuts to Launcher screen:

Available with Workspace ONE Launcher 3.2+

Similar to adding of a setting to Launcher settings, you can add a shortcut to Launcher home screen by using the below flag by mentioning "shortcut name, package name, activity name" or "shortcut name, action name".

<characteristic type="com.airwatch.android.kiosk.settings" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="CustomShortcuts" value="{&quot;CustomShortcuts&quot;:
[{&quot;name&quot;:&quot; Manage Applications Settings&quot;,&quot;pName&quot;:&quot;com.android.settings&quot;,&quot;cName&quot;:
&quot;com.android.settings.Settings$DateTimeSettingsActivity&quot;},
{&quot;name&quot;: &quot;Locale Settings&quot;,&quot;pName&quot;:
&quot;com.android.settings&quot;,&quot;cName&quot;: &quot;com.android.settings.Settings$LocalePickerActivity&quot;}]}"/>
</characteristic>

Open Native settings in tablets:

Available with Workspace ONE Launcher 3.2+

In some of the tablets, native settings such as Wi-Fi, Bluetooth, Language etc. are opened in a fragmented view which allows users to access other settings as well, in such a case user can easily get out of launcher. So, by default, Launcher does not allow users to open settings unless they use the below flag. If the admin thinks that it is safe to open native settings in that particular tablet then he can use this flag and all the native settings which are allowed can be accessed. This is usually used along with dynamically allowed list settings flag (CustomSettings), custom shortcuts, custom activities and for notification access.

<characteristic type="com.airwatch.android.kiosk.settings"
        uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="CanLaunchNativeSettings"
        value="True"/>
</characteristic>

If you on want a particular native setting to be accessed and not other settings, use the flag: forceLaunch. This flag is used individually with each setting. If admin uses the flag: canLaunchNativeSettings,then all the allowed native settings can be accessed. If you want a particular setting, use the forceLaunch flag. This is usually used along with dynamically allow list setting flag(CustomSettings), custom shortcuts, custom activities and for notification access.

<characteristic type="com.airwatch.android.kiosk.settings"
        uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="CustomShortcuts"
        value="{&quot;CustomShortcuts&quot;: [
{&quot;name&quot;: &quot;Manage Applications
        Settings&quot;,&quot;forceLaunch&quot;: &quot;true&quot;,&quot;pName&quot;:
        &quot;com.android.settings&quot;,&quot;cName&quot;:
        &quot;com.android.settings.Settings$DateTimeSettingsActivity&quot;},
{&quot;name&quot;:
        &quot;Locale Settings&quot;,&quot;pName&quot;:
        &quot;com.android.settings&quot;,&quot;cName&quot;:
        &quot;com.android.settings.Settings$LocalePickerActivity&quot;}
]}"/></characteristic>

In the above XML (Customshortcuts) both Manage Applications and Locale Settings shortcuts will be visible on the Launcher screen, but users can only access Manage Application settings since it uses the forceLaunch flag.

The flagsforceLaunch or canLaunchNativeSettings must be present for custom settings to be visible on Launcher settings screen.

Clear Application Defaults

Available with Workspace ONE Launcher 3.2+

If there is no default set, then Android presents a dialog with all the applications which support that particular format. If a user chooses an application as the default application for any file, then that file is always opened in the same application until the user clears the default manually. Since there is no access to native settings inside Launcher, the user cannot clear the defaults.

The Clear Application defaults commands displays the Clear Application Default in Launcher Settings. All commonly used application types (PDF, Excel, Browsers, Images etc.) will be listed where users can clear defaults. The API to clear application defaults may not work on some OEMs, so Workspace ONE has made this as a configurable setting.
<characteristic type="com.airwatch.android.kiosk.settings"
        uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="AllowClearAppDefaults"
        value="True"/>
</characteristic>
In some devices, Workspace ONE cannot clear application defaults automatically. For these devices you can send the below flag in which case when the user tries to clear default, they are navigated to application details settings screen where they can do it manually.
<characteristic type="com.airwatch.android.kiosk.settings"
        uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="CannotClearAppDefaults"
        value="True"/>
</characteristic>

Cannot Clear Home Defaults (in some devices)

Available with Workspace ONE Launcher 3.2+

In some devices it is not possible to clear home defaults. For those devices, use the following flag to present the user with a clear default screen from which they can navigate to the native settings and clear the defaults manually:
<characteristic type="com.airwatch.android.kiosk.settings"
        uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="CannotClearDefaults"
        value="True"/>
</characteristic>

Boot Up Launchers

Available with Workspace ONE Launcher 3.2+

There are some boot up application which run after the device is restarted. These boot up applications are getting allowed even though they are not allowed on the UEM console. Workspace ONE maintains a list of allowed applications in the Launcher profile, but after reboot Workspace ONE Launcher takes some time to load this profile.

To prevent the application from being allowed, you can provide the package name of all the boot up application which are to be allowed.
<characteristic type="com.airwatch.android.kiosk.settings"
        uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="BootupLauncher"
        value="com.sonyericsson.initialbootsetup, com.sonyericsson.setupwizard,
        com.honeywell.systemtools.autoinstall/>
</characteristic>

Allow Status Bar

Available with Workspace ONE Launcher 3.2+

This feature provides the administrator with the ability to enable or disable the status bar on the device.
<characteristic type="com.airwatch.android.androidwork.launcher" uuid="568bc89d-1df8-4ce9-a041-e5a24acdb7ec">
<parm name="AllowStatusBar" value="True"/>
</characteristic>