MKS Implementer 2006 Administration Guide

Appendix C: Converting DesignTracker Data to MKS Integrity
434
Each DesignTracker DR and SR field is optionally mapped to an MKS Integrity field as
defined by you. DR entities and corresponding fields automatically convert to Implementer
change packages in MKS Integrity. Fields can either be omitted, or they can have the name of
an existing MKS Integrity field to populate with the data. The “Logged by User” and
“Logged Date” always convert to internal fields.
For each field you convert, if there is a master file in DesignTracker setup, the DesignTracker
field value is assigned to the corresponding MKS Integrity field value as defined in the
conversion properties file. This allows replacing the shorter abbreviated values common in
DesignTracker, with the longer, more descriptive values common to MKS Integrity. For
example, DesignTracker status values can be set to existing MKS Integrity state values.
After the data conversion, the DRs and related lock history remain in DesignTracker,
unchanged and available online to select DesignTracker users for historical and auditing
purposes.
TIP MKS recommends you assign the new MKS Integrity issue number to one of the
user defined fields on DRs and SRs so it is visible when displaying a DR or SR. This
also makes it available to include in reports and queries.However, this has no
impact on the fact that once a DR or SR is converted, it will not convert again even if
included in selection criteria.
User Profile and Resource Fields
Implementer attempts to convert all user profile and resource fields to the MKS Integrity user
values defined for Project Leader and Developer Resource.
Implementer retrieves the user ID that corresponds to the resource ID in the DesignTracker
Resource master file. From the user ID, the OS/400 user profile is retrieved from the
Implementer Work with Users function to verify if an MKS Integrity user ID is specified. If
any of these values are invalid or not specified, the alternate value is used.
In the event a name cannot convert, when defining the ICVTDT command parameters you
must specify a valid default user to assign to the issue if there is no conversion for the user or
available resource in DesignTracker.
NOTE This rule applies when mapping to an MKS Integrity user field. If mapping to
a text field, the original text maps to the new field.
Entities Added as Change Package Entries
When a converted DR is associated with a DesignTracker entity, an Implementer change
package is created based on the standard MKS Integrity change package creation rules.