MKS Implementer 2006 Administration Guide

Appendix C: Converting DesignTracker Data to MKS Integrity
444
conversion of mapped values is finishes, or create the issues by using the value specified
as the alternate value, and then query the issues in MKS Integrity and change them as
needed.
Long Text Fields and Descriptions
In DesignTracker, all text information displays using a fixed font size, whereas MKS Integrity
uses a variable font size. Similarly, the long descriptions in DesignTracker allow for a
limitless amount of data, whereas the long text fields in MKS Integrity have a size limit. The
conversion tool handles these database variances as follows:
When converting long text fields in DesignTracker, each line of text is separated with a
“new line” character in MKS Integrity (paragraphs are not created). If existing text is
spaced to form columns of information, this format is not replicated in MKS Integrity.
If the data for a long description exceeds the limit of the MKS Integrity field, during the
conversion the extra text and corresponding message are written to the error log. This
allows you to manually enter the data into another field, for example, using cut and
paste, or edit the text to a size that fits in the field. When this occurs the text in the issue
field indicates a truncated value.
Hierarchical Field Considerations
DesignTracker allows for parent/child data relationships, where some fields are sub-fields of
other fields, resulting in a hierarchical data structure. The hierarchical field considerations
apply to the following DesignTracker fields:
Product/component
Product/version
Company/division
Company/division/department
MKS Integrity does not support user defined hierarchical data; thus, you can place this type
of data into a Pick or Short Text data type, as explained in “Field Values” on page 442. When
you generate the property file, the description for all hierarchical entries is built based on the
hierarchical field values. Once converted, the data in MKS Integrity is separated by a forward
slash “/” to indicate the different data levels.
For example, in the company/division/department field:
ACME Mfg is the company description for ACME Manufacturing
Widgets is the division description for WID
Accounting is the department description for ACCT
The generated key is:
ACME/WID/ACCT=ACME Mfg/Widgets/Accounting