DDPostPublishDelegate
The DDPostPublishDelegate extends the EPMPostPublishDelegate by creating a Dynamic Document, with the Dynamic Document's content (usually a PDF file) coming from the Representation. The DDPostPublishDelegate allows data from an application (such as Creo Parametric) to be inserted into an Arbortext Dynamic Document structure, and the lightweight data to be viewed in Arbortext Editor
Additionally, any markups and annotations can be used in the Editor and subsequently published to provide tightly controlled, lightweight figures/illustrations in technical publications that are tied to real modeled CAD data. Similar to the DefaultPostPublishDelegate, a PublishedContentLink is maintained between the data and the lightweight data objects for use with Arbortext Editor.
The tables below list the valid <post-publish> parameter names for the DDPostPublishDelegate and describes how each parameter is used.
Required Parameters
The following parameters are required for the DDPostPublishDelegate class.
Parameter Name
Definition
delegate
Must be com.ptc.wvs.server.publish.DDPostPublishDelegate.
name
The Name of the Object that the PostPublishDelegate is to create/iterate. The Name must be unique among all Objects of its Type in order to guarantee that the delegate finds the right Object to iterate.
cad-authoring-application
The Authoring Application to associate with the Dynamic Document to be created.
Optional Parameters
The following parameters are optional for the DDPostPublishDelegate 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.
type
The type of object that the PostPublishDelegate is to create. If specified, the Type can be specified by its Logical Identifier and must be a soft-type of wt.doc.WTDocument. If not specified, the DDPostPublishDelegate creates a wt.epm.DynamicDocument.
title
Title of the Dynamic Document.
description
Description of the Dynamic Document.
container-oid
The object identifier string of the container to use for initial creation of the Dynamic Document.If this value is not specified, container-name is checked; if both are not specified, the 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 initial creation of the Dynamic Document. If a name is used and that name does not exist, or there is more than one container with that name, 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 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 initial creation of the 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 is created. For example:
To specify the root folder:/ /default/Default
* 
Specifying the root folder using default is not case sensitive. All subfolders 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.
content-description
A description for the content of the Dynamic Document.
lifecycle-template
The life cycle template to associate with the Dynamic Document.
lifecycle-state
The life cycle state to associate with the Dynamic Document.
published-content-link
The create Published Content Link indicator creates a Published Content Link unless it is specified to the value of false.
Est-ce que cela a été utile ?