Creating a Migration Set
Configuration Migration Sets
Configuration Migration Sets are assembled through a dedicated user interface page[1].
This page enables the user to select the top level items, and include them in a set. It also provides the option to exclude dependent items from the top-level migration items.
Migration sets are assembled through a dedicated Integration Point - Configuration Migration Integration Point. This IP allows the user to create a full migration set.
Including Configuration Items
Configuration rules in Oracle Health Insurance are hierarchical in nature; complex configuration rules are a composite of more basic configuration rules.
To facilitate 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 page offers the option to either create a full migration set or to include only a user-defined selection of the available configuration items in the migration set.
By default, a newly created migration set is a full migration set.
Switching the Full Migration Set? toggle, opens the Configuration Items section at the bottom of the page.
This section lists the the items that are available for migration.
For each available top level configuration item, the user can include all records or just a selection of records. The 'Remove All From Set' option removes all the records for this configuration item from the migration set.
Selecting the 'Select Specific' radio-button enables the 'Select Specific' link to a window where the user can select one or more records.
Below is the list of configuration items that can be included in a configuration migration data set. Each entry mentions which dependent items are auto-included.
| Top Level Item | Automatically Includes | Optional Excludes |
|---|---|---|
access role |
access restriction |
|
agent configuration |
agent configuration integration |
integration |
boilerplate text |
||
destination |
||
dynamic logic |
message |
message |
exchange property |
||
floorplan |
floorplan tag details |
|
integration |
access restriction |
access restriction |
subflow |
destination |
destination |
message |
||
user sequence |
Optional Excludes
The migration function automatically determines what other configuration is required to successfully install the selected configuration items on the target environment.
The exclude options, that are available for each top level item, enable the user to override this behavior so that not all dependent items are included in the migration set. This feature is relevant in a scenario where the dependent configuration items are placeholders that are not meant to be moved to another environment.
Intended User
The functionality described on this page is intended for a configuration expert user. Selecting and including configuration items in a set requires that you know which configuration rules are ready for migration, and which are not.
Creating and saving a migration set in this page does not make the migration set available for other environments to import; this is a separate step described in Building a Configuration Migration Set.
| Creating a migration set is a two-step process. First, the user specifies what is in the set. Second, the user triggers the process that creates the payload based on what is specified in the first step. Any subsequent change to the migration set requires both steps to be repeated. |