Administración especializada > Soporte de visualización y publicación > WVS Publish Rules > About Publish Rules
  
About Publish Rules
Publish Rules provide increased control over what is published. You can specify rules for different scenarios, such as whether publishing is triggered by check-in, a schedule, or a manual creation from Windchill. You can also specify custom behaviors based on the type or number of the object that triggered the publish, or combinations of any of the conditions.
For example, if a PDF file is published and added to a Representation, a new WTDocument can be created to contain the PDF file as its primary content, thereby increasing the enterprise manageability of that PDF file. The new WTDocument is associated with the Representable that holds the Representation, which allows historical tracking of the WTDocument’s primary content. This association is called a PublishedContentLink. The Publish Rules allow you to tailor the post-publish behavior to your needs.
Support for the generation of additional file types during publishing. Two elements, File and Additional-Files along with a template called PublishRules-AdditionalFiles.xml, are used to generate additional file types during publishing. Once publishing is complete and a representation is stored, the AdditionalFilesPostPublishDelegate copies the content (additional files) of the representation to a WTDocument. This gives enterprise control and visibility of the published content separately from the CAD Document structure, while maintaining a record of the association through a PublishedContentLink. Also, the additional files can be deleted from the original representation using the delete-original <post-publish> parameter. If the WTDocument already exists, the delegate code iterates the WTDocument, providing a means to track the history through the iteration history of the WTDocument.
* 
Publish Rules are specified using an XML file. It is assumed that the reader of this document has a basic understanding of XML.
The terms Dynamic Documents and EPMDocuments are both used in this section. Dynamic Documents are specific to Arbortext and are a type of EPMDocument.