Configuring tasks and capabilities

ArcGIS for Windows Mobile provides a set of built-in tasks you can configure for your field workers' workflow. You can also extend these tasks or develop new ones using ArcGIS Runtime SDK for Windows Mobile.

You can also develop extensions, also known as capabilities, with the SDK and add them to your project.

You can configure built-in tasks, custom tasks, and capabilities in Mobile Project Center. They deploy automatically with the project. For details on developing custom functionality and adding it to your project, see the SDK help.

NoteNote:

In ArcGIS for Windows Mobile 10.0 and earlier, field crew tracking and field crew logging were included as part of the tasks and capabilities. Starting from 3.0, these two capabilities are implemented as configurations for an operational map layer, which minimizes restrictions on the schema of the layers. For more information, see Configuring map layer properties and Configuring logging and field crew layers.

Tasks described

By default, every mobile project includes a set of built-in tasks that you can configure, reorder, and remove from your project. Each task performs the same functionality in Windows as it does on Windows Mobile devices. Tasks include:

Configuring tasks and capabilities

You can configure both built-in and custom tasks and capabilities using the Tasks and Capabilities tabs in Mobile Project Center. For custom tasks/capabilities, configurable properties depend on how you implement the task/capability. For built-in tasks, you can configure the following properties:

Including custom tasks and capabilities in mobile projects

A custom task or capability comes as two or three components, each being a separate .dll file. You need to develop a component for Mobile Project Center so that you can include the task/capability to a mobile project and that you can configure the task/capability in Mobile Project Center. You must build and deploy a separate .dll file for each platform on which the field application runs. That is, if you deploy your task/capability to both field applications (the application for Windows Mobile devices and the application for Windows devices and laptops), then you must build two separate .dll files. Since a separate .dll is required for each platform, you can program the task/capability to deliver different functions.

Deploying custom tasks and capabilities

After you develop the custom task or capability assemblies, store them in specific locations on your computer (see Deploying and updating custom tasks/extensions for details) so that when you start Mobile Project Center, the task or capability appears on the Tasks or Capabilities tab (respectively). You can then add the task or capability to your project.

When you save a project that includes a custom task/extension, Mobile Project Center automatically includes a copy of the corresponding assembly with your project data and packages them together. When you share or deploy the project, the custom task or capability is deployed as well automatically.

Using tasks and capabilities in field applications

Default tasks work similarly in functionality across both field application platforms even though the user interface is different. Custom tasks and capabilities, however, can work differently across platforms.

Built-in and custom tasks that you add to your project appear the same way in the task list of both field applications. Custom capabilities, on the other hand, may not have a user interface component but will perform certain actions or extend existing functions in other tasks. For example, the custom-built Map Snapshot capability only has a menu item for your field crew to capture the map content to an image file. See the Map Snapshot Extension for more information.

TipTip:

To view all default and custom tasks and capabilities available within a project on a field device, use the About the Project menu in the field application.

8/16/2013