Managing Data

The Windchill installation establishes a set of business object types that are available in the site context and then can be inherited by organization contexts and then by application contexts. The use of object types allows you to categorize objects by providing a set of attributes and user interface functions for each type. For example, objects that are typed as documents (using the type wt.doc.WTDocument) have a different set of attributes and actions available in the user interface than those objects typed as parts (using wt.part.WTPart).

Display Name	Object Type	Description
Document	wt.doc.WTDocument	General documents such as text files or Microsoft Word documents
Analysis Activity	wt.change2.WTAnalysis Activity	Change data that assigns an analysis task to a user
Change Task	wt.change2.WTChange Activity2	Change data that assigns product development work to a user
Change Investigation	wt.change2.WTChange Investigation	Change data that collects information about the root cause of a product problem
Problem Report	wt.change2.WTChangeIssue	Change data that reports a potential product problem
Change Notice	wt.change2.WTChange Order2	Change data that collects all tasks required to implement a product change
Change Proposal	wt.change2.WTChange Proposal	Change data that proposes a solution to a product problem
Change Request	wt.change2.WTChange Request2	Change data that collects all change impact data required for a decision
EPM Document	wt.epm.EPMDocument	This type is the parent type of subtypes for the following business objects: • CAD documents (type:<prefix>. DefaultEPMDocument) • dynamic documents (type: <prefix>.DynamicDocument) • burst configuration files (type: <prefix>.BurstConfiguration) • diagnostic documents (type: <prefix>. DiagnosticDocument) • notes (type: <prefix>.Note) • Symptom Set
Part	wt.part.WTPart	A database object that represents a component of assembly in a product structure
Promotion Request	wt.maturity.PromotionNotice	A request to change the state of one or more objects to a new life cycle state with the selection of a review process.
Part Instance	wt.part.WTProductInstance2	A serialized copy of a product built according to a specific configuration
Variance	wt.change2.WTVariance	An authorization to depart from the as-designed configuration for a specific number of units or for a specified time period. Variances consist or deviation and waivers. A deviation is a planned departure from the as-designed configuration before the part is built. A waiver is a written acceptance of nonconformance.
Variant Specification	com.ptc.wpcfg.doc.Variant Spec	The collection of options specified for a particular configurable part structure in preparation for creating a variant. The variant specification, in essence, defines the characteristics of the variant that should be created from the configurable part structure.