04.12.2012 Views

Windchill System Administrator's Guide

Windchill System Administrator's Guide

Windchill System Administrator's Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

*<br />

444-@@<br />

<br />

<br />

content<br />

filename<br />

EngineReq<br />

<br />

Properties in Mapping Rules Files<br />

The preceding examples showed how to place properties in mapping rules files.<br />

The chapter in this document about <strong>Windchill</strong> Export and Import describes the<br />

properties that you can use to control <strong>Windchill</strong> Import. You set properties in<br />

mapping rules files by editing the files, and you cannot use the xconfmanager<br />

utility for this purpose. If you are not setting properties through a graphical user<br />

interface or in a mapping file, you add or edit properties with the xconfmanager<br />

utility, which is discussed elsewhere in this guide.<br />

Do Not Map Number Attributes for MCAD Documents<br />

About Mapping Rules<br />

COPY Element<br />

The number attribute of an MCAD document in the <strong>Windchill</strong> database is a string<br />

identical to the document's Pro/ENGINEER file name. If you change an MCAD<br />

document's number attribute by a mapping rule or by altering the object when it is<br />

on the local disk, you create data that is incompatible with the assembly files that<br />

refer to it. Attempting to repair a number change by reverting to the original<br />

information does not succeed because the software perceives an attempt to check<br />

in the renamed object as an attempt to duplicate an existing object.<br />

Each mapping rule is an XML element within the mapping rule file. Each<br />

mapping rule element, except for one that specifies copying, has at least two subelements:<br />

and . These two sub-elements determine whether the rule<br />

applies for any given element in an imported or exported XML file. If multiple<br />

rules in a file could apply to an element in an imported or exported file, only the<br />

first rule applies.<br />

The following examples show the types of rules and how to apply them to a<br />

variety of attributes. To work with attributes that do not appear in the following<br />

examples, you need to understand XML and read the XML file that you are<br />

mapping.<br />

By default, all elements in a source XML file are copied into the resulting XML<br />

file, and consequently it is not necessary to specify a rule that copies elements<br />

without alteration. If any rule specifies an action other than copying for an<br />

element, copying does not occur and the other rule controls the result for the<br />

C-8 <strong>Windchill</strong> <strong>System</strong> Administrator’s <strong>Guide</strong>

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

Saved successfully!

Ooh no, something went wrong!