Publishing creates a new document, called a publication document, according to the specifications in the publish template selected by the user, and the optional style template specified in the publish template. For example, a manager might maintain a Procedures Guide (a Microsoft Word document) and publish it in HTML format to the /Department folder, which is available to all members of the department.
You can think of a publish template as a wizard that Workplace users can use to create new documents by publishing existing documents. Advanced users create publish templates using the Publishing Designer application. A publish template is saved as a versionable document in the Publish Template class and acquires the class' Default Instance Security.
A publish template has the same access rights as any other versionable document except that the Publish access right appear only in Enterprise Manager, which prevents users and authors from publishing a publish template.
To publish a document, the user selects the document and the publish template. The user must have Publish access rights to the document and View Content access rights to the publish template, as well as the permission to add objects to the destination folder.
The publish template specifies the location, properties, and security of the publication document. The template author has the following options for applying security on the publication document:
See Specify publication document security in the Publishing Designer Help for more information on these options.
When an author updates a previously published source document, the author might also want to update the publication document. The publish template specifies what occurs when a source document is republished. A republished document can replace the existing publication document or add a version to it, and:
-or-
The publish template specifies whether to delete publication documents when the source is deleted (a source document can have many publication documents). To delete a published source document, a Workplace user must have Owner Control of the source and any publication documents deleted with it. If the user has insufficient access rights for one or more of the deletions, the operation results in an error and no deletions occur.
A style template, created on the Content Engine using the Publishing Style Template Manager, specifies how to translate a document from its original format into HTML or PDF. No special security settings are required as the Transformation Engine takes ownership of each publish request in its queue and assumes that the user has Full Control.