This topic provides an conceptual overview of Publishing and Representations, along with sections about Visualizing CAD Represented Parts and Assembly Features, Visualizing Documents, and Dynamic Documents.

To load a model into Creo View, the associated document or part must be published. Publishing is a visualization feature that creates the necessary Creo View files from the CAD model. Windchill documents can always be published because they store the necessary CAD model data. Parts can only be published if they are associated with an EPMDocument. (You can also publish the WTPart structure for standalone WTParts.) If a part has not been published, it can be loaded into Creo View, but no geometry is visible. Data without associated CAD content can be viewed, but not published, in Creo View.

Windchill systems are typically configured so that publishing takes place automatically as CAD documents are checked into the system by Windchill Workgroup Managers. However, the publish operation is also available in the WVS user interface, and by creating schedule jobs.

As a result of publishing, a representation for the object is created. The representation stores the Creo View files created for the object. A single part or CAD document may have multiple representations for different configurations of an assembly; however, one representation is designated as the default representation. When a thumbnail is shown for a CAD document or part, the thumbnail is of the default representation.

If CAD documents are loaded into Windchill by Windchill Workgroup Managers, WVS can publish a representation of this data. Multiple representations can be generated (such as in the case for an assembly), illustrating different configurations of the structure. The generation of a representation can occur automatically or by user request. Publish requests are queued for processing. Users may monitor the queue and the status of the publish job.

The Representations of Windchill Documents — such as CAD Documents, EPMDocuments, and WTDocuments — may also be loaded into Creo View so that their primary content and attachments can be viewed and annotated. Because the content of some documents (such as PDFs or image files) may be loaded into Creo View directly, they do not need to be published. Certain types of files or documents can be published; for example, Microsoft Office files can be published to PDF format.

Each representation can have many associated annotations. Annotations are added and saved to Windchill from Creo View and can be viewed from Windchill. If a representation has an associated annotation, the annotation can later be deleted if desired.

A Dynamic Document is a sub-class of the EPMDocument object and also a content holder for files authored in Arbortext Editor or other document-related files, such as graphics. Dynamic Documents have the following capabilities:

• They can store Arbortext Editor-generated XML files and related files, such as graphics.

• They can be related to other Dynamic Documents to allow representation of the complex dependencies that exist among the constituent parts of a structured document.

• They can contain representations of non-Creo View-type data, such as PDF and HTML content.

• They can have metadata and attributes.

Dynamic Documents can be published into the supported Arbortext output formats. See Configuring Publishing for Windchill Arbortext Authored Dynamic Documents for information about this feature.

For more information on the integration of Arbortext Editor and Windchill, see “Configuring Arbortext Publishing Engine for the Windchill Vizualization Services” in the Arbortext Help Center.