Properties (View Only from Version History) Help

PROPERTIES (View Only)

This screen displays version history information about the content selected on the Version History screen. The information on this screen may not be changed.

INFORMATION ON THIS SCREEN:

Request Type The request type for the version - ADD, MODIFY, COPY, MOVE, RENAME or DELETE.

Filename The path and filename of the published content. This field may be referenced by the following Template variables:

<$filename> - The Directory Path and Document Filename.
<$fname> - Document Filename without the Directory Path.
<$dir> - Directory Path in URL format using "/" as a separator.
<$dirpath> - Directory Path in operating system format, using "/" as a separator for Unix servers and "\" as a separator for Windows servers.
<$dirname> - Directory Name where content is stored without the full path.
<$dirdesc> - Directory Description, available only when set in Directory Properties.
<$dirsection> - Directory Section Name available only when set in Directory Properties

See Template Language for more information.

New Filename Displayed only when the properties displayed are for a Copy, Move, or Rename Request.

Title The title of the content.This information may be referenced by the <$title> template variable (Header, Footer, Page Layout, Edit Layout, E-mail, and Directory Indexing templates).

Description The content's description.This information may be referenced by the <$description> template variable (Header, Footer, Page Layout, Edit Layout, E-mail, and Directory Indexing templates).

Keywords A set of keywords used in a search index that point to the content. This information is not used by WSD. This field is referenced by the <$keywords> template variable to create meta-tags. See Template Language for more information

Author The Last Name, First Name and User ID of the Author. The default for this field is set on the System Policies screen.
When template variables are used, this field may be used to record a "by line" when the originating author has to review the completed composition. For e-mail requests from a non-WSD authorized user, this name can be assigned to any authorized WSD user. Different components of this field are referenced by the following Template variables:

<$author> or <$authorlogin> - Author's WSD Username for login
<$authorname> - Author's First and Last Name
<$authorfirstname> - Author's First (given) Name
<$authorlastname> - Author's Last Name (surname)
<$authoremail> - Author's Display E-mail Address
<$authorurl> - Author's URL. Must have been entered on Edit User Info screen.

See Template Language for more information.

Maintainer The Last Name, First Name and User Name of the WSD-authorized user allowed to disapprove documents in workflow stages to which the user does not normally have access. When template variables are used, this field is an alternative method of recording a "by line" naming the maintainer instead of the author of the prose, when your site uses "Author" to refer to individuals creating presentation content. Maintainer-related information can be referenced using the following template variables:

<$maintainer> or <$maintainerlogin> - Maintainer's WSD Username for login.
<$maintainername> - Maintainer's First and Last Name.
<$maintainerfirstname> - Maintainer's First (given) Name
<$maintainerlastname> - Maintainer's Last Name (surname)
<$maintaineremail> - Maintainer's Display E-mail Address.
<$maintainerurl> - Maintainer's URL. Must have been entered on Edit User Info screen.
See Template Language for more information.

Submitter The WSD-authorized user who submitted the request into the workflow process. The Last Name, First Name and User Name if the submitter is a WSD-authorized user. Not all of this information may be available for requests submitted via e-mail. Submitters may be allowed to disapprove documents in workflow stages to which they do not normally have access. When template variables are used, this field can be used to retrieve the following submitter-related information:

<$submitterlogin> - Submitter's WSD Username for login.
<$submitterfirstname> - Submitter's First (given) Name
<$submitterlastname> - Submitter's Last Name (surname)
<$submitteremail> - Submitter's Display E-mail Address.

Note: For e-mail requests this information is derived as follows:

from authorized WSD users, this name is derived from the submitter's e-mail address.

from non-WSD authorized users, the e-mail address in this field must be assigned before the document is approved to a workflow stage requiring "Submitter" as a "Required Request Field."

Revision The revision number of the content; assigned when this version of the content was published. This number begins with 1.0, and is automatically incremented by 0.1 or the default "Version Increment" assigned on the System Config screen. While a request is being processed, the revision number can be changed manually, but only to a *larger* number. This number may not be less than 1.0, and must be larger than the most recently published version. This field is referenced by the <$revision> template variable. See Template Language for more information..

Index Position The content's position in the directory index list if the "Maintain Directory Index Files" System Policy is turned on.

Submit Date The date the version was submitted.

Publication Date The date the version was published.

Header Template The name of the header template file.

Footer Template The name of the footer template file.

Layout Template The name of the Page Layout template used to create the content.

Options
When present, may contain any/all of the following values:

Document contains template commands -- WSD will perform template command processing for this document
Skip Orphan Document Check -- Indicates this content will be ignored by the automated "Orphan Check" process in the "Cleanup Database" module if "Auto Submit Delete for Orphaned Doc" has been set to "Yes" on the System Policies screen.
Note: The Cleanup Database module is typically scheduled as an Overnight Process by System Administrators
.

FUNCTIONS:

RETURN Select this function to return to the Version History screen.

Copyright 2000-2005 CyberTeams, Inc., http://www.cyberteams.com All rights reserved.
CyberTeams and WebSite Director are registered trademarks of CyberTeams, Inc. All other marks are the property of their respective owners.

Request Type	The request type for the version - ADD, MODIFY, COPY, MOVE, RENAME or DELETE.
Filename	The path and filename of the published content. This field may be referenced by the following Template variables: <$filename> - The Directory Path and Document Filename. <$fname> - Document Filename without the Directory Path. <$dir> - Directory Path in URL format using "/" as a separator. <$dirpath> - Directory Path in operating system format, using "/" as a separator for Unix servers and "\" as a separator for Windows servers. <$dirname> - Directory Name where content is stored without the full path. <$dirdesc> - Directory Description, available only when set in Directory Properties. <$dirsection> - Directory Section Name available only when set in Directory Properties See Template Language for more information.
New Filename	Displayed only when the properties displayed are for a Copy, Move, or Rename Request.
Title	The title of the content.This information may be referenced by the <$title> template variable (Header, Footer, Page Layout, Edit Layout, E-mail, and Directory Indexing templates).
Description	The content's description.This information may be referenced by the <$description> template variable (Header, Footer, Page Layout, Edit Layout, E-mail, and Directory Indexing templates).
Keywords	A set of keywords used in a search index that point to the content. This information is not used by WSD. This field is referenced by the <$keywords> template variable to create meta-tags. See Template Language for more information
Author	The Last Name, First Name and User ID of the Author. The default for this field is set on the System Policies screen. When template variables are used, this field may be used to record a "by line" when the originating author has to review the completed composition. For e-mail requests from a non-WSD authorized user, this name can be assigned to any authorized WSD user. Different components of this field are referenced by the following Template variables: <$author> or <$authorlogin> - Author's WSD Username for login <$authorname> - Author's First and Last Name <$authorfirstname> - Author's First (given) Name <$authorlastname> - Author's Last Name (surname) <$authoremail> - Author's Display E-mail Address <$authorurl> - Author's URL. Must have been entered on Edit User Info screen. See Template Language for more information.
Maintainer	The Last Name, First Name and User Name of the WSD-authorized user allowed to disapprove documents in workflow stages to which the user does not normally have access. When template variables are used, this field is an alternative method of recording a "by line" naming the maintainer instead of the author of the prose, when your site uses "Author" to refer to individuals creating presentation content. Maintainer-related information can be referenced using the following template variables: <$maintainer> or <$maintainerlogin> - Maintainer's WSD Username for login. <$maintainername> - Maintainer's First and Last Name. <$maintainerfirstname> - Maintainer's First (given) Name <$maintainerlastname> - Maintainer's Last Name (surname) <$maintaineremail> - Maintainer's Display E-mail Address. <$maintainerurl> - Maintainer's URL. Must have been entered on Edit User Info screen. See Template Language for more information.
Submitter	The WSD-authorized user who submitted the request into the workflow process. The Last Name, First Name and User Name if the submitter is a WSD-authorized user. Not all of this information may be available for requests submitted via e-mail. Submitters may be allowed to disapprove documents in workflow stages to which they do not normally have access. When template variables are used, this field can be used to retrieve the following submitter-related information: <$submitterlogin> - Submitter's WSD Username for login. <$submitterfirstname> - Submitter's First (given) Name <$submitterlastname> - Submitter's Last Name (surname) <$submitteremail> - Submitter's Display E-mail Address. Note: For e-mail requests this information is derived as follows: from authorized WSD users, this name is derived from the submitter's e-mail address. from non-WSD authorized users, the e-mail address in this field must be assigned before the document is approved to a workflow stage requiring "Submitter" as a "Required Request Field."
Revision	The revision number of the content; assigned when this version of the content was published. This number begins with 1.0, and is automatically incremented by 0.1 or the default "Version Increment" assigned on the System Config screen. While a request is being processed, the revision number can be changed manually, but only to a larger number. This number may not be less than 1.0, and must be larger than the most recently published version. This field is referenced by the <$revision> template variable. See Template Language for more information..
Index Position	The content's position in the directory index list if the "Maintain Directory Index Files" System Policy is turned on.
Submit Date	The date the version was submitted.
Publication Date	The date the version was published.
Header Template	The name of the header template file.
Footer Template	The name of the footer template file.
Layout Template	The name of the Page Layout template used to create the content.
Options	When present, may contain any/all of the following values: Document contains template commands -- WSD will perform template command processing for this document Skip Orphan Document Check -- Indicates this content will be ignored by the automated "Orphan Check" process in the "Cleanup Database" module if "Auto Submit Delete for Orphaned Doc" has been set to "Yes" on the System Policies screen. Note: The Cleanup Database module is typically scheduled as an Overnight Process by System Administrators .