The source and publication documents form a relationship
through object-valued properties on the Document class. A publication
document points to a source document as either a non-dependent document
or a dependent document, depending on the option that is specified
in the original publish request. If a dependent publication document,
a metadata relationship exists that causes the publication document
to be deleted if the source document is deleted.
When a document is republished, the publication document
is related to a previous publication document in different ways depending
on the original publish request and the capabilities of the previous
document. The following examples describe the publication document
behavior upon republishing:
- Specifying a version option when you republish a document that
supports versioning results in two versions of the same document version
series, or versioning and replacing the current publication version.
Typically you republish a document because a new version of the source
exists.
- Specifying a replace option when you republish a document that supports versioning results in a
new version in that version series. The previous version is deleted.
- If a publication document does not support versioning, then the version option to republish a
document is not valid. When you specify the replace option, a new document is created and the
previous document is deleted.
Note: Publishing
a document that consists of multiple content elements results in only
the primary, or first, content element being published. In this respect,
publishing does not support multiple content element documents.
For
versionable documents, the Publishing Designer has the following options
regarding the actions to take upon republishing:
- Version the current publication document (Version & Keep)
- Version and replace the current publication document (Version &
Replace)
- Add a publication document (Add & Keep)
- Add a publication document and replace the current document (Add &
Replace)
Each of these republish options is valid for the publishing
types. The following section describes how moving a publication document
or filing it in multiple folders affects the publishing types and
republishing options:
- Publishing types:
- Native publishing does not have
any limitations on republishing a publication document that was moved
to or filed in multiple folders. The Add republish cases uses the
target folder that is specified in the publish template for the new
publication document. The Version republish cases create a version
the publication document instead of creating a publication document,
and therefore the versioned publication document automatically appears
updated in the locations it is filed in.
- Publishing to PDF does not have any limitations on
republishing a publication document that was moved to or filed in
multiple folders. The Add republish cases uses the target folder that
is specified in the publish template for the new publication document.
The Version republish cases create a version the publication document
instead of creating a publication document, and therefore the versioned
publication document automatically appears updated in the locations
it is filed in.
- Publishing to HTML does not have
any limitations on republishing a publication document that was moved.
However, republishing a publication document that was filed in multiple
folders has limitations. Filing the publication document in multiple
folders is not recommended for the Add republish cases and is not
supported for the Version republish cases.
- Republishing options:
- The Add republish cases use the target folder that is specified
in the publish template for the new publication document, and therefore
it is irrelevant for the republish operation if the publication document
was filed in multiple folders. However, if you file a publication
document, which includes subsidiary folders with files, into multiple
folders, you must manually copy the subsidiary folder with files to
all the folders to ensure that the publication document continues
to be displayed correctly.
- The Version republish cases are not supported when a publication
document was filed in multiple folders because the code is not designed
to create copies of the subsidiary folder with files in all folders
that the publication document is filed in. At the beginning of the
republish operation, a check to see if the publication document was
filed in multiple folders is done and, if found to be true, the publish
request is set to in-error and the republish operation is stopped.
These publishing cases are summarized in the following table:
Publishing type |
Republishing option |
Moved to a different folder |
Filed in multiple folders |
Native publishing |
Add cases |
Supported |
Supported |
Native publishing |
Version cases |
Supported |
Supported |
Publishing to PDF |
Add cases |
Supported |
Supported |
Publishing to PDF |
Version cases |
Supported |
Supported |
Publishing to HTML |
Add cases |
Supported |
Requires manual intervention |
Publishing to HTML |
Version cases |
Supported |
Not supported |