Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Overview

Deployment groups provide a means to create multiple system configuration profiles. Each mobile worker is associated to a single deployment group and therefore its configuration. which are associated to mobile workers. Although completely devoid of any semantic ties to the system, they are commonly used to separate configurations for different types of mobile workers, mobile workers that work in different geographical locations, or mobile workers that focus on specific types of service. 

To keep the design simple and easy to understand a few rules are enforced:

  • At least one deployment group must be defined
  • Deployment groups are not hierarchical - they can not be nested inside other deployment groups
  • A mobile worker must be associated to a deployment group
  • A mobile worker can only be associated to a single deployment group

Related pages:

Should the need arise that requires a mobile worker to be part of multiple deployment groups (which is not directly supported), the solution is to create a new deployment group that contains the combined data from the other two. For example, if the deployment groups Technician and Manager exist, yet there is a mobile worker that is both a technician and manger and needs the configuration from both groups, a third group, such as TechnicianManager, should be created. 

Items Controlled by Deployment Groups

The following items are configured at a deployment group

  • Products
  • Mobile Application Configuration

Default Deployment Group

The system is preconfigured with a default deployment group named Default

  • No labels