Usage

Common Tasks


Searching for Applications

The simplest way to use Fetch is to use the Search Applications functionality.

Alt text

Upon searching and finding a result, an Administrator can see details provided by the Software Vendor about the application, choose the version, architecture and filetype (if multiple exist) and then add it to the upload queue.

ℹ️ Notes

Application Search results default to:

  • The latest version available
  • x64 (then x86, then arm64) architecture
  • .msi installer type if they exist, otherwise it will default to .exe
  • Changing any of these results re-evaluates the available options:
    • e.g. If a user changes the version selected in the dropdown list, it will then attempt to set the other options of the dropdowns to the defaults mentioned above.


Queuing Multiple Applications

You can queue multiple applications from each page and have them upload sequentially.

Alt text

Editing Application Parameters

Once you have added an application to the queue, you can right-click on the Application entry and either remove it from the queued items or edit the default Configuration Parameters used to create the application in the Workspace ONE Catalog.

Alt text

ℹ️ Notes

When editing the application configuration, you can enable the text fields options by clicking the edit button next to the entry.

Uploading Apps

When you have queued your applications, you can select either ‘Download Only’ or ‘Upload to UEM’ to process the queue. Download Only mode will only download the installers allowing you to scan or process them later. Upload to UEM will download the application install and automatically upload and create the application in the Workspace ONE UEM Application Catalog.

Alt text

ℹ️ Notes

Uploading an application to UEM will not assign it to any Assignment Group. You must manually add the assignments from the Workspace ONE UEM Admin Console.


Importing an Application Inventory

You can upload an existing application inventory report in .csv format with only 3 columns in the following order (with headers):

app_name, app_package_id & app_version

this is the naming standard from Workspace ONE Intelligence

Fetch will then process this file and give you the results of what it has in its database vs. the report.

See here for an Example Report from Workspace ONE Intelligence.

Alt text

ℹ️ Note

The results will load incrementally when scrolling to the last item in the current view

Reviewing Matches

An “Exact Match” is where Fetch has matched the App Name with the exact same version from its database. A partial match is where it has found the application by name, but could not match on an exact file version.

By default, the results list only shows Exact or Partial Matches. You can change the Filter to show all results (include No Match) and if you want you can remove a result from the list using the x icon. On a Partial or Exact Match result, you can click the “+” icon and add the Application to the Upload Queue if desired.

Alt text

ℹ️ Note

  • You can remove unwanted results from the Results List by pressing the x button on the entry.

  • Once a matched application has been reviewed and added to the queue, you can edit the default configuration parameters by right-clicking on the queued item. When editing the application configuration, you can enable the text fields options by clicking the edit button next to the entry.

ℹ️ Scalability Info

Fetch has been tested by importing and processing application inventories of up to 5000 applications.


Application Updates

This workflow allows you to identify which of your existing managed applications in your Workspace ONE Applications have updates available. Fetch queries your Workspace ONE UEM environment and attempts to match applications using the “App Name” configured in UEM. If Fetch can match the application it will query the database for updated application versions.

Alt text

From here the Administrator can review (by pressing the +) and add any updates to the queue. The ‘Review Results` dialog will select the next latest version in the version list by default.

ℹ️ Important

When reviewing an update for a matched application, Fetch will only show versions that are newer than version returned from Workspace ONE UEM.

Fetch also identifies the filetype (exe/msi) of the existing installer to select the appropriate type in the results selection view.

ℹ️ Note

In the above example, 7-Zip shows multiple times as there are multiple versions of 7-Zip added to the console. This allows Administrators to add and view updates when there is a use case to have multiple versions of an App in the Console.

Once you have added an application to the queue, you can right-click on the Application entry and either remove it from the queued items or edit the default Configuration Parameters used to create the application in the Workspace ONE Catalog.

When editing the application configuration, you can edit the available options by clicking the edit button next to the entry.


Bulk Upload of Local Apps

This process allows you to do a bulk upload of your Enterprise Applications that you maintain the installers for, or a list of verified or custom list of installers that you maintain on your file servers. Once you upload a manifest (in .csv format), Fetch will validate some basic information (entered data is complete, data types are correct, files exist) and then uploads the installer and creates the associated Native App in UEM.

The main aspect of this process is that you specify a local file path (that the Fetch Application can access) of the installers you want to upload to UEM, along with all the required metadata that is needed to add the Application to the App Catalog. This workflow does not use any of the metadata within the Fetch Database.

Alt text

Here is an example of the contents of the manifest template:

Alt text

These columns correlate to the metadata required by the Workspace ONE Application API/Console.

There are additional options in the manifest templates that allow you to change any or all of the available configuration options that are available in the UEM Console UI. This means you can enter all the custom information needed to deploy and install the application directly in the manifest.

The manifest template is now saved as a .xslx file, and where there are multiple choice options for configuration settings, they are shown in a dropdown inside this spreadsheet allowing simpler and more accurate manifests.

ℹ️ Important

You need to ensure you still save as or export your manifest as a .csv file.

See here for an Example Local Applications Manifest for you to enter the relevant data in to.


Scan Folder of Downloaded Apps

On all pages that download application installers, there is a “Download Only” option. This allows you to only download the installers for further testing etc.

To complete the upload of these applications once downloaded, you can go to the ‘Scan Folder’ page and select the location where your previously downloaded installers are saved.

This will then scan the selected folder recursively and import the application (and its metadata) into Fetch ready to be uploaded to Workspace ONE UEM.

Alt text

ℹ️ Important

When downloading installers in “Download Only” mode, Fetch saves the files in the following structure:
{Your_Saved_Download_Path}\{PackageIdentifier}\{Version}\{Architecture}\{FileType}\{Filename}

Alongside this file, Fetch also creates a metadata.json file that contains the information needed to create the application in UEM. If you delete this file, the application cannot be imported in to Fetch using this method.

ℹ️ Note

This is process is only intended to import applications downloaded using Fetch. If you want to upload your own applications/installers, use the Local Source Applications process.