IllustrationPostPublishDelegate
IllustrationPostPublishDelegate extracts files from the published C3DI representation and stores them as separate dynamic document or document objects in Windchill. The graphic-file-type rule determines the required graphic files to be extracted from the published C3DI representation. You can view the published content by navigating to Customize > Related Objects > Published Content. For more information about including post-published content in a XML bundle, see the section “Parts List Illustration Post Published Content” in Bundle Publishing Output.
Required Parameters
The following parameters are required for the IllustrationPostPublishDelegate class.
Parameter Name
Definition
delegate
Must be com.ptc.wvs.server.publish.IllustrationPostPublishDelegate.
name
The name of the post-publish content must be unique. PTC recommends that you use EPM_NUMBER and FIG_NAME in the name, as shown in the following patterns:
When the name of the post-published content is specified as {EPM_NUMBER}{FIG_NAME}, the name of the post-published content contains the number of the parts list illustration and the name of the figure in the parts list illustration.
When the name of the post-published content is specified as {EPM_NUMBER}-{EPM_NAME}{FIG_NAME}, the name of the post-published content contains the name of the parts list illustration, the number of the parts list illustration, followed by the name of the figure in the parts list illustration.
graphic-file-type
The file extension of the files to be extracted and post-published. For example:
<post-publish name="graphic-file-type">.*\.png</post-publish>
For examples of these publish rules XML elements, refer to the SamplePublishingRules.xml file in the <Windchill>/codebase/com/ptc/arbortext/windchill/worker directory.
Optional Parameters
The following parameters are optional for the IllustrationPostPublishDelegate class.
Parameter Name
Definition
number
The number of the object that the PostPublishDelegate is to create/iterate. If specified, the Number must be unique among all Windchill objects of this type. If not specified, the Number is automatically generated.
* 
If partlistBundleCcfParam. transformImage is set to true, the partlistBundleCcfParam. transformImageTypes is specified, and the type parameter value is wt.doc.WTDocument or its sub type, append a file extension to the number parameter value to publish the post-publish content to a bundle.
If you append {FIG_NAME} to the number parameter value, the file extension is included in the post-publishing value for the number. For example:
<post-publish name="name">{EPM_NUMBER}{FIG_NAME}</post-publish>
If {FIG_NAME} is not included in the number parameter, manually append the file extension in the post-publishing rule for the number. For example, .jpeg is appended in the following post-publishing rule:
<post-publish name="number">{EPM_NUMBER}.jpeg</post-publish>
type
The type of object that the PostPublishDelegate is to create. The Type can be specified by its Logical Identifier and it must be wt.doc.WTDocument, a subtype of wt.doc.WTDocument, Dynamic Document, or a subtype of Dynamic Document. If not specified, the IllustrationPostPublishDelegate creates a EPMDocument.
container-oid
The object identifier string of the container to use for the initial creation of the WTDocument or Dynamic Document. If this value is not specified, container-name is checked; if both are not specified, the WTDocument or Dynamic Document is placed in the same context as the Document being published.
container-name
The Path (see example below) to the container or the name (string value) of the container to use for the initial creation of the WTDocument or Dynamic Document. If a name is used and that name does not exist, or if there is more than one container with that name, then post-publishing is stopped, and an error message is displayed. Container-name is only checked if container-oid is not set. If this value and container-oid are not specified, the WTDocument or Dynamic Document is placed in the same context as the Document being published.
Example: /wt.inf.container.OrgContainer=PTC/wt.projmgmt.admin.Project2=TestProj
folder
The folder path for the initial creation of the WTDocument or Dynamic Document.
In Windchill 10.2 M020 and later, if the folder is not specified, it uses the folder path of the representable. If the folder does not exist in the context specified, the missing folders in the path are created. For example:
To specify the root folder:/ /default/Default
* 
By default, the root folder name is not case sensitive. All subfolders names are case sensitive.
To specify a first-level folder under the root folder:/MyFolder /Default/MyFolder/default/MyFolder
To specify multi-level folders, separate the folder names with “/”:/first/second /first/scond/third/Default/first/second/Default/first/second/third
* 
Since subfolders are case sensitive, /Default/first/second specifies a different folder than /Default/First/second.
lifecycle-template
The life cycle template to associate with the WTDocument or Dynamic Document.
lifecycle-state
The life cycle state to associate with the WTDocument or Dynamic Document.
published-content-link
The create Published Content Link indicator creates a Published Content Link unless the value is specified as false.
Was this helpful?