additional-file-primary

The text associated with this attribute is a Java regular expression that matches the name of the additional file that is to be added to the WTDocument as primary content. The regular expression must always resolve to select a single file. If the regular expression resolves to more than one file, a random file is selected.

additional-file-secondary

The text associated with this attribute must be a Java regular expression that matches the name of all additional files that are to be added to the WTDocument as secondary content.

delete-original

This is an additional attribute that can be added to a post-publish element that already contains an additional-file-primary or additional-file-secondary attribute. If this attribute is set to "true" then the original files that match the regular expression are deleted from the original representation

number

The number of the object that the AdditionalFilesPostPublishDelegate 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 AdditionalFilesPostPublishDelegate 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

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

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 "false" or "no" (case insensitive), then no Published Content Link (PCL) is created. This is the only way to not create a PCL. If any other string is used, then a PCL is created. That string is used for the name (or type) of the PCL. Multiple param-sets are allowed, so there can be multiple PCL names. In the case where multiple PCLs are named differently, a different link to a different WTDocument is created for each name. If some or all PCLs have the same name, then one wtdoc will be created and iterated for each identical name after the 1st name. A PCL is created for each iteration. Finally, in the case where the "published-content-link" attribute is not included in the param-set, a WTDocument is created and then iterated for each "nameless" published-content-link.