Files-Actions Manifest Options for Android

You must select all the desired Android options for your Files-Actions product component.

PROCEDURE

1. Add the Manifest Actions for your Android File-Action.

   Settings	Descriptions
   AirWatch MDM Agent Upgrade	Install the new Omnissa Workspace ONE Intelligent Hub to the device. Before using this file/action, see Upload a Workspace ONE Intelligent Hub APF File, Upgrade File-Action for more information.
   Apply Custom Settings	Apply custom, OEM-specific device settings based on the selected XML file. You must upload the custom XML or ZIP file as part of the file/action. Supported Devices: - Android Motorola Solutions devices with the Android Hub v7.1+ - Upload the ZIP file created by MSI. - Android Zebra devices with the Android Hub v7.2+ and Zebra's MX Service App installed on the device. - Create your XML configuration file using Zebra Stage Now. - Upload the XML configuration file and select it from the drop-down menu. - After pushing the product containing an Apply Custom Setting file/action, the status information reports in the Job Log. If an error occurs, the failed response XML is reported in the Job Log. For more information, see Product Job Statuses.
   Copy Files	Copy files from one location to another on the device.
   Create Folder	Create a new folder on the device.
   Delete Files	Delete files from the device.You can delete multiple files in a folder by using the * and ? wildcards. For example, /$external$/sdcard/Downloads/*.txt deletes all text files in the Downloads folder of the SD card and /$internal$/Downloads/????.dat deletes all DAT files that are exactly 4 characters long in the Downloads folder of internal storage. You can also use ** to execute a recursive search of all nested folders. For example, /$internal$/Downloads/**/*.doc deletes all DOC files from anywhere inside the Downloads folder of internal storage, no matter what folder it's in.
   Install Unmanaged Application	Install an unmanaged .APK file. Workspace ONE UEM does not add the app to the managed app list. Enterprise wipes or unenrollment do not remove the app from the device. You must use the Uninstall Unmanaged Application file/action. Consider adding Uninstall Unmanaged Application to the uninstall manifest of any product including the Install Unmanaged Application file/action.
   Move Files	Move files from one location to another on the device.
   OS Upgrade	Install a new OS upgrade and the relevant Workspace ONE Intelligent Hub. For more information on this option, see Create an OS Upgrade File-Action, Android.
   Reboot	Restart the device.
   Remove Folder	Remove a folder from the device.
   Rename File	Rename a file on the device.
   Rename Folder	Rename a folder located in the device.
   Run Intent	Run command lines and arguments on the device. See RunIntent Action, File-Action Android for more information.
   Uninstall Unmanaged Application	Uninstall an unmanaged application. Enter the package ID of the app.

2. When finished adding actions to the Manifest, select Save.

What to do Next

Path Variables – For all file management-related actions listed above (copy files, create folder, delete files, move files, remove folder, rename file, and rename folder), you have the option of inserting a path variable for both source and target, as applicable. The use of these variables in your Files/Actions path means you are not required to account for the randomly generated OEM-specific path definitions in the creation of your Files/Actions.

$internal$ – Use this variable at the beginning of your path to indicate your source/target path to be read from/written to the internal storage space. Supports read and write actions. For example: /$internal$/agreement/license.txt addresses the file license.txt in the agreement folder on the device's internal storage space.

Note: $internal$ does not work with all Files/Actions.

$external$ – Use this variable at the beginning of your path to indicate your source path to be from the external memory card storage, which the device must feature. External storage supports read-only access so any usage must involve a memory card that has been properly formatted and furnished with the correct files in the correct locations. For example: /$external$/sdcard/license.txt reads the file license.txt from the sdcard folder found on the device's external memory card storage.