|
PROPERTIES - DOCUMENT
This screen displays information about the request displayed in the Request field. The information on this screen may be revised by authorized users when accessed from the Edit Request screen. The fields you can modify are controlled by the Property Update Permissions set by your User Administrator on the User Permissions screen.
INFORMATION ON THIS SCREEN: |
Request |
The Request Type (ADD, MODIFY, COPY, MOVE, RENAME, DELETE, EMAIL OR UNKNOWN) displays preceding one of the following:
Note: If the Request Type is EMAIL or UNKNOWN, it must be changed to one of the other Request Types (ADD, MODIFY, DELETE, COPY, MOVE, or RENAME) before the request can be published or approved to a workflow stage that requires a valid Request Type. |
Request Type |
One of the following request types: ADD, MODIFY, COPY, MOVE, RENAME, or DELETE. Note: If the Request Type displayed in Request (above) is EMAIL or UNKNOWN, you must select these Request Types before the request can be published or approved to a workflow stage that requires a valid Request Type. |
Filename | The path and filename where the content associated
with the request is/will be published. This field is referenced by the following Template variables:
|
Title | The title of the content associated with the request. The text displayed/typed here can be used in WSD templates by referencing the <$title> variable -- for example, to identify the page when it is bookmarked and in Directory Indexes. |
Description | The description of the content associated with the request. If permitted, you may type the description of the new content in this Data Entry box; up to 255 characters. This information may be referenced by the <$description> template variable (Header, Footer, Page Layout, Edit Layout and Directory Indexing templates). |
Keywords | A set of search keywords used in a search index that point to the document. This field is not used by WSD. This field may be referenced by the <$keywords> template variable to create meta-tags. See Template Language for more information. |
Locked By | If the request is locked, this field displays the
name of the user who locked it. If you have "Unlock All Requests" System Permission, you may
unlock the request or change the name of the user to whom the lock is currently assigned. See User Permissions .
Care should be taken before unlocking a 'locked' request to make sure it is not currently being worked on by the locking user. To unlock a locked request, or change the name of the "Locked By" user, select "No Lock" or the name of a user from the drop-down box. |
Author | The Last Name, First Name and User ID of the Author.
The default for this field is set on the System Policy screen. If you are an authorized user, you may
change this field.
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:
|
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:
|
Submitted by | 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:
Note: If you have "Modify Submitter" System Permission, you may change the name of the submitter. See User Permissions. For e-mail requests this information is derived as follows:
|
Next Rev. # | The next revision number of a document that will be assigned when that document is 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. The value in this field will be permanently assigned/recorded when the document is published to the web site. 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 document's position in the directory index list. This field is present only when the "Maintain Directory Index Files" System Policy is turned on. Choices in the drop-down box are: None, First, Last, and Other. For Other, a position number must be entered in the data entry box to the right of the drop-down box. |
Publish Date | The date/time to publish the document
after final approval. The Default Publish Date is set on the System Policies screen. The valid values are:
|
Expiration Date |
This property is used to determine if/when WSD's "Cleanup Database" module should automatically generate and submit a request to Delete or Modify this content. The first selection for this property is as set of radio buttons labelled as follows:
The second element of this property specifies the date on which the automated request will be generated when the Delete or Modify radio button is selected. See the Automated Submission tutorial for more information. |
Header |
This data entry box displays if the content's mime type (based on the file extension) has the "Templates Supported" option enabled. See Edit Mime Type for more information. You may select the Header template for the new content from this drop-down box of available header templates . Warning: If a Page Layout Template will be used to create this content, make sure the values associated with the Header that you select do not adversely affect the format of the Page Layout Template. Use the View Request function to determine if the header you choose is compatible with the Page Layout Template you are using. |
Footer |
This data entry box displays if the content's mime type (based on the file extension) has the "Templates Supported" option enabled. See Edit Mime Type for more information. You may select the Footer template for the new content from this drop-down box of available footer templates . Warning: If a Page Layout Template will be used to create this content, make sure the values associated with the Footer that you select do not adversely affect the format of the Page Layout Template. Use the View Request function to determine if the footer you choose is compatible with the Page Layout Template you are using. |
Page Layout Template |
If you are using a page layout template to create this content, the name of that template is displayed on a drop-down list of available templates. If permitted, you may change the Page Layout Template selection. When you change this value, data previously entered may be lost if the newly selected template does not support the information available in the previously selected template. The template selected here defines the format of the document you are adding. If an Edit Layout template is assigned to a Page Layout template, the online editor will automatically apply the Edit Layout template. |
File Size | The file size of the document in bytes; calculated by the system each time it is displayed. |
Options |
Document contains template commands - When checked, Indicates the content contains template commands. Select this option if you insert one or more template variables in the body of any document that does not use a page layout template. See Template Language . Skip Orphan Document Check - When checked, this content will be ignored by the automated "Orphan Check" process in the "Cleanup Database" module when "Auto Submit Delete for Orphaned Doc" has been set to "Yes" on the System Policy screen. Exclude From Search - When selected, WSD will skip over this document during a search. To Exclude a directory and all documents within the directory searches, see Directory Properties. Document contains template fields - When checked, indicates that one or more template fields have been manually placed into this document. Note: This option is only required for documents containing template fields that have not been created using a Template. |
FUNCTIONS: |
Select this function to display the Version History screen for the document. | |
Select this function to display the Approval History screen for the request. | |
Select this function to display the Approvals Needed screen. If you have "Modify Approvals Needed" system permission (see User Permissions) and have accessed this screen from the Edit Request or Submit New Request screen, you may change the Approval Class and Approvals Needed selections for this Request. | |
LINKS | Select this function to display a list of all documents containing links that point TO this content and a list of all links contained in this document that point at other content. |
UPDATE PROPERTIES | Select this function to save the changes made on this screen, and return to the request processing screen. |
Select this function to return to the request processing screen without updating any of the changes made on this screen. |
Copyright 2000-2005 CyberTeams, Inc., http://www.cyberteams.com All
rights reserved.
|