DefaultPostPublishDelegate
The DefaultPostPublishDelegate is specific to Arbortext authored Dynamic Documents (EPMDocuments).
Once the publishing of a Dynamic Document is complete and a representation is stored, the DefaultPostPublishDelegate copies the content of the representation to a WTDocument. This is done to give enterprise control and visibility of the published content separately from the Dynamic Document structure, while maintaining a record of the association through a PublishedContentLink. Additionally, if the WTDocument already exists, the delegate code iterates the WTDocument, thus providing a means to track the history through the iteration history of the WTDocument.
The tables below list the valid <post-publish> parameter names for the DefaultPostPublishDelegate and describes how each parameter is used.
Required Parameters
The following parameters are required for the DefaultPostPublishDelegate class.
Parameter Name
Definition
delegate
Must be com.ptc.wvs.server.publish.DefaultPostPublishDelegate.
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.
Optional Parameters
The following parameters are optional for the DefaultPostPublishDelegate 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 DefaultPostPublishDelegate creates a wt.doc.WTDocument.
title
Title of the WTDocument.
description
Description of the WTDocument.
container-oid
The object identifier string of the container to use for initial creation of the WTDocument.If this value is not specified, container-name is checked; if both are not specified, the WTDocument is placed in the same context as the EPMDocument 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 WTDocument. 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 WTDocument is placed in the same context as the EPMDocument being published.
Example: /wt.inf.container.OrgContainer=PTC/wt.projmgmt.admin.Project2=TestProj
folder
The folder path for initial creation of the WTDocument.
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/second/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 WTDocument.
lifecycle-template
The life cycle template to associate with the WTDocument.
lifecycle-state
The life cycle state to associate with the WTDocument.
published-content-link
The create Published Content Link indicator. If true, yes, or create, a Published Content Link is created. If not specified or any other value, a Published Content Link is not created.
Est-ce que cela a été utile ?