Bentley iCS for PDF CONNECT Edition Update 3.2 allows independent control over the destination document name, file name, and description, with full symbol support, for both rendition and source distributions.   Previously, only the destination file name could be specified using symbols, the destination rendition description could be controlled only via attribute mapping (with no symbol support), and the rendition extension was unconditionally appended to the rendition document name.

The destination rendition name patterns are specified in the ProjectWise Administrator rendition profile ‘Output File Naming Conventions’ component:

All of the pattern labels on this dialog have been prefixed with “Rendition” to avoid confusion with the optional source distribution renaming patterns in the rendition profile destination component.

The file name pattern label has been renamed “base file name” to clarify that this pattern does not include the extension. The rendition extension (i.e. .pdf, .tif) is automatically appended to the expanded base file name pattern. The extension is also automatically appended to the rendition document name unless the appropriate checkbox is checked.

The only required pattern value is the rendition base file name. If the document name pattern is undefined, it is assigned the same value as the file name pattern. If the description pattern is undefined, no description is assigned unless one is specified via attribute mapping.

If the destination description is specified via attribute mapping, it overrides any description pattern defined in the rendition profile component, even if the attribute mapping value results in an empty string.

The source distribution renaming patterns are specified in the ‘Source Distribution’ subdialog under the ProjectWise Administrator rendition profile ‘Output Destination Folders’ component:

All of the source distribution renaming patterns are optional. If undefined, the corresponding value from the original source document is used for the destination document.   Unlike the rendition file name pattern, the destination source document name and file name patterns must include the extension if an extension is desired.