Creating a Migration Set

Migration sets are assembled through a dedicated user interface page. This page allows the user to select the top-level migration items that should be included in the set, and provides options on which dependent items to exclude.

The page is divided into two sections. The upper region shows the created configuration sets. Per set, a user has the option to include certain types of linked reference data. These options apply across the entire migration set, for example, if the user opts to include agents, then all agents that are linked to one or more items in the data set are included.

Including Reference Data

The reference data inclusion option is restricted to records that are linked to the migrated configuration payload. For example, if the source environment has 100 agents, but only 60 of them are linked to the configuration in the payload, then only the 60 linked agents are migrated.

Reference Data	Automatically Includes
agents	agent address country country region dynamic logic prefix
brokers	broker address country country region dynamic logic
providers	individual provider: bank account number bank account validation country country region dynamic logic (bank account validation and name format) prefix provider (service address organization provider) provider specialty provider title rendering address service address specialty title organization provider: bank account number bank account validation country country region dynamic logic (bank account validation) provider (parent organization provider) provider specialty service address specialty

If a migration set includes linked reference data, it also automatically includes any setup configuration that is required; there is no option to exclude the supporting configuration. For example, if an agent resides in a country (top level item) that has not been explicitly added to the migration set, then the configuration migration function will still add the country (to ensure a successful migration for that agent).

Including Configuration Items

The bottom region on the page shows which configuration items are included in the selected configuration set. This area allows a user to quickly include all products with or without the dependent products. Migrating with the products means that the products are also part of the migration payload; migrating without means all references to products are migrated, but the product itself is not included in the payload. For this option to work, the product must be present on the target environment prior to the migration.

The intended user for this page is the configuration expert, that is, the same user that has made the configuration changes. This is the person who knows which changes are ready for migration, and which are not. It is important to note that creating and saving a migration set in this page does not make the igration set available for other environments to import; this is a separate step controlled through another page and most likely another user.

Below is the comprehensive list of configuration items that can be included, per individual record, in a configuration migration data set. Each entry mentions which dependent items are auto-included and which dependent items can be excluded as an option.

Top-Level Item	Automatically Includes	Optional Excludes
access role	access restriction access restriction grant data access group	-
activity type	dynamic field usage [1]. flex code system parameter set parameter set dynamic line	-
address type	-	-
add-on	add-on detail	product
boilerplate text	-	-
brand	-	-
bulk update definition	-	dynamic logic enrollment product
business event definition	-	-
business event rule	business event definition	dynamic logic
calculation period	-	-
callout rule	-	dynamic logic process flow
capitation contract	-	-
change event rule	-	dynamic logic fee definition output definition
collection method	-	-
connector configuration	dynamic logic	dynamic logic
country	bank account validation	dynamic logic
country region	country	-
currency	-	-
covered service tier	-	-
dynamic field usage (displayed as usage in the UI)	dynamic logic field flex code system message	-
dynamic logic	dynamic logic reference sheet message	reference sheet
enrollment product	adjustment rule assigned provider group label currency enrollment product add-on enrollment product account definition enrollment product adjustment enrollment product adjustment value enrollment product category enrollment product detail enrollment product premium schedule enrollment product provider group enrollment product time period line of business parameter domain parameter domain value schedule definition schedule dimension value	add-on enrollment product type parameter alias policy account definition premium schedule product provider group
enrollment product type	enrollment product category organization premium schedule type reinsurance exclusion reinsurance setting schedule definition	-
enrollment type	-	-
enrollment response definition	-	dynamic logic
exchange rate	currency	-
excluded attribute	-	-
fee definition	-	dynamic logic fee schedule
fee schedule	currency default time period fee schedule line schedule definition schedule dimension value	dynamic logic
flex code group	flex code detail	-
flex code system	dynamic logic field flex code flex code field usage flex code set detail flex code system message	flex code group
floor plan	-
gender identity	-
group client	add-on adjustment rule assigned provider group label bill receiver broker agent switch rule data access group enrollment product enrollment product category group account group account add-on group account adjustment group account available product group account available product add-on group account broker agent group account collection setting group account insurable class group account premium schedule group account product group account product adjustment group account product adjustment value group account product premium schedule group account product provider group group account time period group client group client adjustment group client billing account group client broker agent group client collection setting group client premium schedule group commission rate insurable class organization parameter domain parameter domain value premium schedule premium schedule type premium bill allocation schedule definition	collection method dynamic logic parameter alias process flow provider group
HTTP link	-	dynamic logic
insurable class	-	-
insurable entity type	-	-
insurance type	insurable entity type supported insurable entity type	-
line of business	access restriction	-
macro definition	-	dynamic logic bulk update definition
marital status type	-	-
message	-	-
message group	message group detail	message
never in force reason	-	-
output definition	-	dynamic logic
parameter alias	-	-
pend reason	-	-
pend rule	brand	dynamic logic message message group pend reason process flow
policy account definition	-	-
policy account transaction type	-	-
policy identifier type	-	-
prefix	-	-
premium schedule	currency default time period premium schedule line premium schedule type premium tier schedule definition schedule dimension value	dynamic logic
premium tier	enrollment type premium tier enrollment type
process flow [2]	access restriction
product	-	-
product covered service	-	-
provider assignment type	-	-
provider group	provider group affiliation	-
reference sheet	dynamic field usage [3] reference sheet line	-
schedule definition	adjustment rule currency default adjustment value default time period dynamic field usage parameter alias premium schedule type schedule dimension schedule dimension value surcharge rule	add-on dynamic logic
specialty	-	-
title	-	-
user sequence [4]	-	-
validation rule [5]	-	dynamic logic message
waiver reason	-	-
widgets	-	-

Optional Excludes

Configuration rules in Policies are hierarchical in nature; complex configuration rules are a composite of more basic configuration rules. For example, pend rule is a composite of dynamic logic and message group (and more) as well.

To assist the user in assembling a migration payload, the migration function automatically determines what other configuration is required to successfully install the selected configuration item on the target environment. The exclude options allow the user to carve out configuration records from that automatic inclusion. Consider the following example to clarify.

Enrollment product A refers to premium schedule B. In this context, premium schedule B is a dependent item to enrollment product A. If enrollment product A is selected for migration, the user has the option to include the referenced premium schedule as part of that migration as well.

Because an enrollment product is also a top-level item, the user can alternatively choose to migrate enrollment product A without migrating premium schedules as well. This alternate approach requires that premium schedule B is already present on the target environment. This allows the user to have separate configuration tracks, for example, the updates to the enrollment product using premium schedule B can be migrated before migrating the updates to premium schedules itself.

Dynamic Field and Record Usages

Configuration items can be extended with dynamic fields and records. If an extended item is included in the payload, the dynamic field and record values and the related dynamic field usages are automatically included as well. The target environment requires the dynamic field usages in order to know where it can find and update the dynamic field values.

---

1. An activity type can rely on a single dynamic field usage record that serves as an integral part of the activity type by connecting the parameter sets of the activity type to their definition. This dynamic field usage record is not visible in any user interface page, but is migrated as part of the activity type.

2. Applies to both policy process flows and group client process flows.

3. Each reference sheet relies on a single dynamic field usage record that serves as an integral part of the reference sheet by connecting the reference sheet to its definition. This dynamic field usage record is not visible in any user interface page, but is migrated as part of the reference sheet.

4. User sequences can only be created in the target environment. If the sequence already exists in the target environment it is not updated.

5. Applies to both policy and group validation rules.