About Setup Data Manager

The Setup Data Manager (SDM) is used to facilitate the data migration process from a source environment to a destination environment, and vice versa. Most customer implementations have multiple instances of the application such as Production and Test. Configuration items such as, rules, roster alarms, and dynamic issues which are initially created in a Test environment which allows unit testing without disrupting the production environment. Once the items are fully tested, the customer can use the Setup Data Manager tool to transport the entire configuration from the destination environment (Test) to a source environment (Production). The SDM tool eliminates the need to manually replicate a configuration and eliminates the chance of a misconfiguration. Moreover, in a multi-institution project implementation, teams can independently work on specific institutions in a development environment (source), and then migrate the data to a production environment (destination).

The SDM page displays the Setup areas available for transport in the Export tab where users can choose the configuration items to export. Once exported use the Import tab also located on the SDM page. To access the SDM tool in the System area of the application, the user must have Administrative authority granted in the Authority Levels section of the System area. For additional information see task topic, Setup Data Manager Export Import.

IMPORTANT
Both the source and destination environment must be of the same application version, and instance. The data migration process will fail if the source and destination environment are not the same version. It is very important that the source environment reflects the most current state of the production environment’s configuration so that configuration and/or dependent items do not override desired configuration settings when transporting data to the destination environment. For example, suppose that in the production environment the severity levels of the static issues were modified, but not updated in the development environment, this means if static issues are selected in the source environment (development) for export, when imported to the production environment - the static issue severity levels will look like the settings in the development environment. Careful review and consideration of pre-existing configurations in both the source and destination is recommended before importing setup items. Not all of the setup items are available in phase 1 or phase 2, if a setup item has a dependency that is not yet released the application will alert you, and the export for that setup item will not be allowed.

IMPORTANT

Both the source and destination environment must be of the same application version, and instance. The data migration process will fail if the source and destination environment are not the same version.

It is very important that the source environment reflects the most current state of the production environment’s configuration so that configuration and/or dependent items do not override desired configuration settings when transporting data to the destination environment. For example, suppose that in the production environment the severity levels of the static issues were modified, but not updated in the development environment, this means if static issues are selected in the source environment (development) for export, when imported to the production environment - the static issue severity levels will look like the settings in the development environment. Careful review and consideration of pre-existing configurations in both the source and destination is recommended before importing setup items.

Not all of the setup items are available in phase 1 or phase 2, if a setup item has a dependency that is not yet released the application will alert you, and the export for that setup item will not be allowed.

The SDM page is available as of application version 7.2. Setup items available for migration in v7.2 phase one are listed in the SDM v7.2 table at the end of this topic. Setup Items available for migration in phase two v7.3 are listed in the SDM v7.3 table. 1

GRAY NUMBER VALIDATION... Internal identifier (gray number) validation is supported upon export and import via SDM as of application version 7.3.2 Gray numbers are managed during the import and export process using Global Unique Identifiers (GUIDs). For example, suppose an institution with gray number five in a "Test" environment is exported to a "Production" environment where that same institution has gray number sixteen. Using the GUID match, the application will know that the institution with gray number 5 in the test environment is the same one as the institution with gray number sixteen in the production environment. Moreover, suppose Rules and Dynamic Arguments also reference the institution with gray number five in the test environment, when imported to the production environment, these items will automatically be set to reference gray number sixteen in the production environment. The same logic is applicable upon export. The SDM validates whether a gray number is valid, if the configuration of a rule contains an invalid gray number, the application will reference the rule with the invalid gray number and the export will be prevented.

MAPPING EXISTING DATA UPON IMPORT...

Application version 7.3 allows users to map existing Setup items with the same name in the source environment and the destination environment to prevent duplicate items with the same name from being imported to a destination environment. Rare usage when importing into a clean destination environment. Most likely to occur when preexisting configuration activity exists in both a source and destination environment.

SDM v7.2:

Authority	Special Day Group	Shift	Work Code Category
Login Policy	Notification Group	Shift Group	Request Note
Job Title	Formula ID	Shift Mask	Vacancy Strategies
Specialty	Attachment Category	Shift Times	Count Strategies
Group	Attachment Group	Logging Bucket	Institution
Pay Information	Attachment	Logging Behavior
Location	Terminology	Static Issues
Special Day	User Defined Field	Dynamic Value Group

SDM v7.3:

Closure Note	Order Information	List Chain	Auction
Closure Note Group	SKU	List Plan	Auction Group
Unit Type	Shift Split	List Target	Auction Item
Agency	Auction Quantity	Rule	Auction Plan
Region	Penalty	Roster View	Preference Profile
Station	Work Code	Roster Count	Preference
Unit	Dynamic Issue	Blueprint Job Allocation Pass	Custom Report
Position	Dynamic Value	Blueprint Job Allocation Strategy	Task
Event Type	Leave Threshold	Blueprint	Assignment Template
Extra/Backup Unit	List	Smart Blueprint	App Configuration

SDM v7.4:

Phase 3, application version 7.4 supports Import Manager Integrations for Workforce Dimensions and Workforce Ready. Both of these integrations require a license to view and access the corresponding integration section on the SDM page.

Imports SDM configurations for Import Manager Integrations of either Dimensions or Ready.
Exports SDM configurations for Import Manager Integrations of either Dimensions or Ready

When properties are selected in the Dimensions or Ready section, then those properties are included in the export, or inserted for import.

SDM v7.5.2

Added Accrual Group support in the Setup Data Manager.

SDM v7.5.4

Added Custom Template support in the Setup Data Manager. Also included validation check for any Custom Template associated with a Roster Export task via the Task Manager.