Representation Export Plus - User Documentation
Details
| Name | Description |
|---|---|
| Wex ID | com.wincomplm.wex-repexport-plus |
| Name | Representation Export Plus |
| Version | 1.12 |
Overview
Representation Export Plus extends Windchill’s Core PDM module by making it faster and easier for users to export published representations. This offers significant productivity gains. The extension also eliminates human error in missed representations, as well as missed exports on desired workflow triggers like promotions or changes. Windchill users may interactively export for a single representable or multi-selection of representables (including from a search result). The extension may also automate exports triggered by an event or using a workflow robot.
The results of the export may be saved in a specified folder on the server or presented as a direct download to the user. The export also generates an XML metadata file for each exported object with the attributes of its representation and representable. The Windchill administrator may configure the export behavior. Additionally to the features offered by Representation Export, this extension allows to export a set of representations as documents that can be stored back in Windchill, offering a full traceability and sending them as emails to lists of predefined users.
Representation Export Plus is often used with Promotion Validate and/or Watermarking to automate rule-validated and stamped packages.
Features
- Exports the Representations from 1 or more objects
- Supports Promotion Request and Change Objects
- Exports XML meta data file for each Representation.
- Export results can be saved to a server location or downloaded locally as a zip
- Provides two workflow robots for triggering export for a Promotion Request or a Change Notice.
- Adds a “Representation Export” UI Actions to the menus and search results
- Adds Event Listener for Set State Event on Change Notices and Promotion Requests.
- Can be fully configured by the Administrator
- Creates a Document with the result of the export as primary content
- Sends an e-mail with the created Document to a list of recipients
- Can be configured to export only what is in the collection
- Can be configured to export drawings only in selected states
User Guide
The objective of this extension is to allow for the export of published representations of objects quickly and easily. The export can be executed for a single or a collection of representables through the User Interface, triggered by an event or using a workflow robot. In addition the export is available from the search results. The results of the export will either be saved to a folder on the server or presented as a direct download to the user. A single XML meta data file will also be generated for each exported object which includes attributes of the representation and its representable. The behaviour of the export can be configured by the administrator through the use of configurable options. The plus version also includes features to save the export as a document and send it as an email to a list of predefined users.
See the standard extension documentation for the standard guide.
If the extension has been configured to send an E-mail to the Users when the export is complete, a document will be created with the result of the export as primary content and be sent to the list of users that was specified in the configuration.
The UI controls in the tool bar allow you to add related cads to the table or children of the selected part.
Configuration
Distribution
| Option | Description |
|---|---|
| Email Recipients | List of all the recipients of the email. If this is set, Role email Recipients will be ignored |
| Email from address | The address shown as the sender of the email |
| Email Subject | The subject of the Email |
| Email Recipients with specific role | Select a role to email all of its members. If email Recipients is set, this option will be ignored |
Generated Document
| Option | Description |
|---|---|
| Container of the generated Document | The container that will contain the enerated Document |
| Folder of the generated Document | The folder that will contain the generated Document |
| Type of the generated Document | The type that the generated Document will have |
| Use default Document number | Use this option if the custom OIR that is used does not create a number for the Document |
Collector
| Option | Description |
|---|---|
| Max number of children to be collected | If the amount of bom children collected goes past this count no further children will be collected |
| Part child states | When the user collects in the UI the structure only these states will be selected (the view will also match) |