Windchill System Administrator's Guide

Context Considerations in Import and Export
Export Container Availability
The software manages objects within logical entities called containers. The
container concept is used to separate objects that belong to different working
contexts.
This topic discusses the following in its sub-sections:
• Access to objects and the import or export of objects at the appropriate
context level
• Controlling context in import operations
This topic explains export container availability for Product, Library, Project,
Organization, and Site.
Product, Library, or Project Level Container Availability
At the Product/Library/Project level, the export action is available to end users
(with read access) and administrators of the context itself, its parent context (the
Organization) or a Site Administrator.
The Export action is available on the property (details) page of any of the
following types of objects:
• WTPart, WTDocument, Reference Document, and End Item which is also
known as WTProduct.
Any IBA values and IBA definitions must be exported with the object
instances. The associated type definitions, either soft types or hard types, must
be exported as well.
• All soft type and hard type definitions. In most cases these are instances of
modeled subclasses of WTPart, WTDocument, and End Item which is also
known as WTProduct.
• Supported objects in a folder.
The export must include the definition of the modeled subclass as if it were a
soft-type.
You can export EPMDocuments through the Import/Export Manager.
Additionally, the Export user interface will be available to administrators of site,
organization, product, and library contexts through the Export/Import Manager
on the Utility tab. This user interface allows administrators to search within a
context for objects to export. The search returns objects created within the context
container. To export data from a Project Context, the user should use the export
action from the Project Details page.
6-4 Windchill System Administrator’s Guide