04.12.2012 Views

Windchill System Administrator's Guide

Windchill System Administrator's Guide

Windchill System Administrator's 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.

Default Values for Overridable Conflicts<br />

Life Cycle<br />

Team<br />

Some import conflicts will cause import failure. This section explains the default<br />

values that are assigned when the listed conflicts are successfully overridden.<br />

There are 2 cases in which a life cycle conflict occurs:<br />

• The life cycle of the object in the XML file doesn't exist in the database, in<br />

which case import fails -- a non-overridable conflict.<br />

• The life cycle of the object in the XML file is different from the one in<br />

database, in which case the following import actions yield the following<br />

results:<br />

– Default -- The database object remains unchanged.<br />

– Import as latest iteration -- The life cycle of the newly created object is<br />

the life cycle of the previous iteration in the database.<br />

– Import as new version -- The life cycle of the newly created object is the<br />

life cycle from the XML file<br />

– Import as checked out -- The life cycle of the newly created object is the<br />

life cycle of the previous iteration in the database.<br />

– Modify non-versioned attributes -- The life cycle of the newly created<br />

object is the life cycle from the XML file.<br />

– Update checked out object in place-- The life cycle of the newly created<br />

object is the life cycle of the checked out object in the database.<br />

There are 2 cases in which a Team conflict occurs:<br />

• The team of the object in the XML file doesn't exist in the database, in which<br />

case the team of the newly created object is the team of the previous iteration<br />

in the database.<br />

• The team of the object in the XML file is different from the one in database, in<br />

which case the following import actions yield the following results:<br />

– Default -- The database object remains unchanged.<br />

– Import as latest iteration -- The team of the newly created object is the<br />

team from the XML file.<br />

– Import as new version -- The team of the newly created object is the team<br />

from the XML file.<br />

– Import as checked out -- The team of the newly created object is the team<br />

of the previous iteration in the database. This behavior is chosen because<br />

C-22 <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!