02.05.2013 Views

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

MKS Implementer 2006 Administration Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Rules and Actions<br />

You have the option to convert all data at the same time, or gradually convert subsets of data,<br />

for example, by product, user, department, or project. Perhaps your business model requires<br />

only the conversion of DRs (not SRs)—the conversion tool has the flexibility to accommodate<br />

each of these scenarios, and more. The Work with Design Requests and Work with Service<br />

Requests subsetting functions are used to select the DRs or SRs for conversion.<br />

As explained in “Set a User’s Default Issue Management System” on page 253, <strong>Implementer</strong><br />

allows you to designate on a user basis which issue tracking system a user is working with. In<br />

other words, you can temporarily have groups of users using DesignTracker, while other<br />

users are using <strong>MKS</strong> Integrity. This approach is beneficial to larger organizations with many<br />

end users, as it allows you to train and migrate groups of individuals rather than all users at<br />

once.<br />

<strong>Implementer</strong> provides a conversion tool that is delivered in the form of the Convert DT to<br />

<strong>MKS</strong> Integrity (ICVTDT) command. Unlike most <strong>Implementer</strong> commands, this command<br />

works together with a conversion property file that resides on the <strong>Implementer</strong> Server. The<br />

conversion results post to a conversion log on the same system. Using the conversion tool,<br />

you are able to generate the conversion properties file you use to map existing DesignTracker<br />

data and fields to corresponding values already defined in <strong>MKS</strong> Integrity. Details on the<br />

ICVTDT command begin on page 438. Information on mapping data begins on page 441.<br />

Once the conversion properties are properly set up and you have all the required data<br />

mapped, the conversion tool is used to convert the DesignTracker data to <strong>MKS</strong> Integrity<br />

issues. Information on using the conversion tool begins on page 433.<br />

The data conversion is complete when all applicable data is converted to <strong>MKS</strong> Integrity<br />

issues and no users are set to use DesignTracker for issue management. Information on post<br />

data conversion activities begins on page 454.<br />

Rules and Actions<br />

The conversion tool allows you to convert existing DesignTracker DRs, SRs, and DR entity<br />

information to <strong>MKS</strong> Integrity issues and related change packages. You can convert subsets of<br />

DRs and/or SRs, making it possible to have groups of DRs or SRs convert differently<br />

depending on the values specified in the conversion properties file when the conversion<br />

runs.<br />

DRs must have no open locks to convert. Once converted, a DR cannot be associated with a<br />

lock, for example, a converted DR cannot be used in check out. Editing a converted DR or SR<br />

is allowed; however, any changes made to a converted DR or SR are not updated to the<br />

corresponding <strong>MKS</strong> Integrity issue. Thus, a good business practice is to only make changes to<br />

the new issue.<br />

433

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!