Copy a Release

A new copied Release can be built within the same Project or in a different Project. Once created, the Release can be updated with Subject Areas to match those in an existing Release.

You can copy and create a new release including Subject Area and Milestones details, from an existing Release in either the same Project or another Project. In Mappings, the new Release automatically builds out the Subject Areas, Datasets, Targets, and Sources, along with their mappings.

The Copy from Release process copies the following data:

All Datasets of the original release.
Targets assigned to each Dataset.
Only the custom reports registration data is copied; however, users must manually create the associated views.
Only the Mappings that match the Target and Source fields are copied.
Note
The Mapping statuses are set as New so users can update mapping actions to specific requirements.

Only custom ETL tasks/jobs registration data is copied; however, users must manually create the associated rules and views.

This topic is related to the following sections:

Copy a Release

To copy and create from an existing release:

In the Releases panel, click Menu (…) > Copy Release in the Menu column of an existing release that you want to copy from. The Copy a Release wizard is displayed.
In the Release tab, validate the field information that are copied from the existing release you selected. Modify the field information as required for Release Name, Description, and Start/End Dates (if different from the defaulted date range). Refer to the Release Tab section for more information of the fields displayed in this tab.
Copy a Release wizard
If required, select a security profile from the Security Profile list.
Note
If the user is not assigned as a Manager of any security profiles, they will not see any values in the Security Profile list. Click the Manage Profiles icon to access Security Profiles in the Admin module.
Specify a Release Owner and click the Relevancy Attributes tab.
Optionally, you can enter the values in the fields of the Relevancy Attributes tab based on your requirements for your project. These fields are used in the conversion process to provide relevancy for the data. For example, the NewDays_Customer field could have a value of 50, meaning that any new customers with at least 50 days are included for the conversion.
Access the Milestones tab and select the required Milestones to copy from the existing release you selected.
Access the Deployments tab and enter unique ZDeploy, Deployment Name information to add the required deployments for this release. Refer to the Deployments Tab section for more information.
Access the Development Areas tab. By default, the development area(s) of the release you are copying from are displayed.
Note
You can add additional development areas or remove the copied ones as needed. Refer to the Development Areas Tab section for more information.
Access the Sources tab. This tab allows you to copy over or modify the information of the source tables mapping to the target tables linked to the datasets registered in the Subject Areas of this release.
Click the Save icon.

Milestones for the new release are displayed to match the same as the existing release, which indicates that the Release Copy process was successful.

The Subject Areas are not copied to enforce the user to add them and to UPDATE the working Database and working Datastore. Within Mappings > Datasets, the Subject Area is identified.

New Release created using the Release Copy process

Release Tab

See the table below for field definitions for copying a release in the Release tab:

Field	Definition
Project ID*	The associated Project defaults, but can be changed with a drop-down selection. (Required)
ETL Tool*	ETL Tool used for conversion of migration data. (Required) Note This setting overrides the default setting in Administer > Setup > Parameters.
Release Name*	Name of the Release. (Required) Modify the name as required.
Description	Long name or description of release, Ex: Release 1 - US or South 1 - Master Data.
Start Date	Project Release start date. (see Note below)
End Date	Estimated Project Release end date. (see Note below)
Remediation	Turn on this toggle to enable Remediation for the Release report execution. Note A Release should expect to remediate one half of the Milestones during the first half of the Project, and turn it off for the second half to avoid masking any readiness errors late in the Release.
Active	Turn on this toggle for status of the Release for future-state design mapping and migration. Note Defaults as Active.
Release Owner	The Owner who is responsible for the entire project release. Note Select from the drop-down list of Syniti Migrate users.
Release ID	The system generates a Release ID when you create a new release.

Note
At this point the date range for Start and End Dates should be set, each level depends upon the level above date range to select the current date range.

Deployments Tab

Deployments must be unique throughout the entire Migration installation. Therefore, they do not copy as part of the Copy from Release process. Create new Deployments as required manually during the Release Copy process.

When you are in the Deployments tab, enter the ZDeploy and Deployment Name information for a Deployment. You can add more than one deployment for the release during the Release Copy process.

When you finish the Release Copy process, click the Edit button of the Deployments you added to assign a Deployment Lead, or to update the priority or order of the deployments in the Release.

In the Deployments tab, click the Add button to create a new Deployment.

See the table below for field definitions for adding or updating a Deployment:

Field	Definition
ZDeploy*	Short name that appears on all validation reports to segment data. (Required)
Deployment Name*	Name of the Deployment. (Required)
Index*	Sequence of the list. Value increases by factor of 10 for each new entry. (Required)
Deployment Lead	Business user responsible for this Deployment. Note Select the value from a drop-down list.
Active	Toggle for status of the Release for future-state design mapping and migration. Note Defaults field as Active.

Note
Deployments are set to be unique across a set of projects and releases. The same ZDEPLOY name cannot be entered more than one time. The error message below displays should the user attempt to enter the same ZDEPLOY Name more than once.

Project Setup: Deployment: Error message

When finished with edits, click the Save SaveIcon icon to complete.

Development Areas Tab

The Development Area ties the Dataset Design Subject Area to a Release within Project Setup, so that when we import the dataset within Mappings, the list of Datasets is aligned to the Subject Areas in the Dataset Design.

The Release Copy process may fail if the Development Area is not defined in the new Release. When you are in the Development Areas tab, specify the Subject Area and Development Area information.

In the Development Areas tab, click the Add button to create a new Development Area.

The Development Area is set in one of two ways, based on the ETL Tool designated within the Release. If the ETL Tool is SAP Data Services, then the Development Area panel contains three fields - Subject Area, Development Area, and Working Datastore.

Project Setup: Development Area dialog box

If the ETL Tool is Migrate ETL, then the Development Area panel contains two fields - Subject Area and Development Area.

If in the future, the user needs to add another Subject Areas from a different Release of the same Project, then add that Subject Area to the list and start the Release Copy process again. This builds out the new Subject Area details - It knows to NOT over write existing Mappings.

When you finish the Release Copy process, click the Edit button of the Development Areas you added to update the its details (if required) in the Release.

See the table below for field definitions for adding a Development Area (Working Database):

Field	Definition
Subject Area*	Select the name of the Subject Area for Project Release from the drop-down list. (Required)
Development Area*	Name of the Syniti Migrate Datasource to which a database management environment is linked and where ETL processing occurs. (Required)
Working Datastore*	Name of the Data Services Datastore to which the working database is linked and where ETL processing metadata is located. (Required)

When finished with edits, click the Save SaveIcon icon to complete.

Copy from Release Fails

Should the Release Copy process fail during the save, an Error message displays with message " Save Failed." The user may only exit the process at this point to correct the error.

Click OK and then exit the Release to update and produce deployments and subject area.

Copy of the Release into Mappings

By copying the Release, the user also produces mappings setup for the New Release and down stream processes including Dataset, Target table, ~~Target Reports~~, and Source Table assignments. Each Source contains the field Mappings as well. However, all fields are set to Mapping Status = New and Build Status = New. This assists in the process for completion of mapping exercises.

Note
It copies all of the Datasets, and there is not a filter to remove some of the datasets from a Subject Area copy from Release.

Should the user Add a Subject Area in Project Setup that is NOT also included in the Copy From Release, that Subject Area builds out in Mappings, however, it does not contain a Dataset, Targets, or Sources. Those need to be manually setup by the user.