8 Exporting and Importing Objects

Object Migration is the process of migrating or moving System Settings and Parameters 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.

You can replicate the System Settings and Parameters from one environment to another without manually re-setting everything to save manual effort and prevent human error.

Prerequisites

• The IHUB Administrator must have access to the Object Migration Admin (OBJMIGADMIN) Group Role before using the Admin Configuration Migration functionality.
• When migrating CM_ADMIN related Objects, if the PMF_PROCESS workflow and User Groups are unavailable in the target environment, you must first migrate the associated PMF_PROCESS workflow and User Groups.
• When migrating IHUB_ADMIN related Objects, if the User Groups are unavailable in the target environment, you must first migrate the associated User Groups.

Note:

• If User Groups are not available in the target environment, User Groups migration is required for Security Mapping and Case Actions/Statuses.
• Report Types must be migrated from Reference Data upload (applicable for Security Mapping).

Migrating CM_ADMIN Related Objects

• The PMF_PROCESS workflow migration is required for Case Actions, Case Statuses, Case Types, Case Priority, and Case Rules and is not required for Business Domain, Case System Parameters, and Jurisdictions.

About Exporting and Importing Objects

You can migrate (import/export) the following Object Types using the Admin Configuration Migration functionality:

• Schedule: Schedule provides instructions to schedule the execution of defined processes. When a schedule is migrated, the associated batch is also migrated.
• Batch: A batch is a collection of jobs that are planned to run automatically at predetermined intervals without any user input. When a batch is migrated, the batch and the associated pipeline information are migrated.
• Batch_Group: A set of individual batches are consolidated to form a single Batch_Group. When migrating a Batch_Group, all the associated batches, tasks, and pipeline information is also migrated.
• Pipeline: A pipeline is an embedded data processing engine that runs inside the application to filter, transform, and migrate data on-the-fly. Pipelines are a set of data processing elements called widgets connected in series, where the output of one widget is the input to the next element.
• 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 of the applications, and to design the artifacts that participate in the Pipelines, to implement the Pipelines. Export of the PMF process will take care of dependent metadata, such as data fields, and transition rules associated with the PMF process, that are defined in PMF.
• Role: Roles are used to mapping 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.
• CM_ADMIN : The CM_ADMIN object type refers to all the case management-related admin screens in the FCCM Cloud application. Under this object type, you can export case management related admin metadata and settings for Business Domain, Case Actions/Statuses, Case Priority, Case Rules, Case System Parameters, Case Types, Jurisdictions and Security Mapping.
• IHUB_ADMIN: The IHUB_ADMIN object type refers to all the investigation hub-related admin screens in the Investigation Hub application. Under this object type, you can export Investigation Hub related admin metadata and settings for Default Graph UI Settings, Manage Case Template, Configure Match Quality of Events, Workflow Manager and Case Designer.