1. User Guide
  2. More
  3. Object Migration

Object Migration

Object Migration is the process of migrating or moving objects between environments.

You may want to migrate objects for reasons such as managing global deployments on multiple environments or creating multiple environments so that you can separate the development, testing, and production processes.

Prerequisites to Migrating Objects

In order to migrate objects, users must be mapped to the Object Migration Admin Group.

Note:

Identity Administrator Group users cannot migrate objects if they are not mapped to the Object Migration Admin Group.

Migration Object Types

You can migrate (import/export) the following object types by clicking the Object Migration icon on the left menu.

  • Schedule: Provides the instruction to schedule the execution of defined processes. When a schedule is migrated, the associated batch is also migrated.
  • Batch: A group of jobs that are scheduled to automatically execute at a preset interval of time without any user intervention. When a batch is migrated, the batch and the associated pipeline information are also migrated.
  • Batch Group: A set of individual batches are consolidated to form a single Batch Group. When you migrate a batch group all the batches, tasks, and pipeline information associated with that batch group are also migrated.
  • Pipeline: A pipeline is an embedded data processing engine that filters, transforms, and migrates data on-the-fly. Pipelines consist of a set of data processing elements called widgets connected in series, where the output of one widget is the input to the next element.
  • Threshold: The threshold limit associated with values of set variables for scenarios in FCCM Cloud Service. These threshold values are set when scenarios are created or installed and can be changed, if required.
  • Job: Jobs provide a set of instructions to execute Workflow Pipelines, based on the set threshold values.
  • PMF Process: PMF Processes are defined to sequence the Workflow Pipelines, the applications, and to design the artifacts that participate in the pipelines, to implement the pipelines. When exporting a PMF Process, dependent metadata such as data fields, transition rules associated with the PMF process are taken care of.
  • Roles: Roles are used to map functions to a defined set of groups to ensure user access system security.
  • Groups: Groups are used to map Roles. Specific User Groups can perform only a set of functions associated with that group.