MKS Implementer 2006 Administration Guide

Mapping to the Project Field
Generating and Configuring the Conversion Properties File
Some fields in the conversion property file can be mapped into the Project field. Fields that
are mapped into this field automatically parse using a forward slash “/” as the project
hierarchy delimiter. All project levels must be created with the appropriate hierarchy. For
example, the company/division/department value of Acme/Widgets/Accounting has the
project hierarchy:
Acme
Widgets
Accounting
If you are mapping to a project field data type, the Implementer conversion properties value
must have a forward slash (/) at the beginning of the new field name, for example, /Acme/
Widgets/Accounting.
NOTE This option is valid only if you are not using Implementer projects with
MKS Integrity issues for project tracking as described in the “Implementer project
field” description on page 230.
New Issue Number
MKS recommends you assign the MKS Integrity new issue number to one of the user defined
fields in DesignTracker so it is included in reports and queries. If a previously converted DR
or SR is included in a query used for conversion, it is excluded even if the new issue number
is not stored in a user defined field.
Generating the Conversion File
The following tasks allow you to generate an initial conversion properties file. The values
listed in the initial file are based on your existing DesignTracker data. For each applicable
DesignTracker field value, you need to define the corresponding conversion value to assign
in MKS Integrity.
The overall success of your data conversion relies upon the accuracy of your data mapping.
For assistance with completing this task, see the table of the Implementer conversion
properties on page 446.
445