GLOSSARY OF WEBSITE DIRECTOR TERMS This document attempts to provide descriptions for terms you will see in the WebSite Director (WSD) tutorials, Help Files, and Application Screens. Other Internet-related terms have been included for your convenience. Please send comments or requests for additions or changes to this glossary via e-mail to support@cyberteams.com with a subject line of "Requested Glossary Update." Absolute URL -  A web content reference that completely identifies the location of the content. There are 2 forms for this type of reference. The most common is in the form "http://<domain>/<directory-path>/<content-name>.<extension> (for example, http://www.cyberteams.com/company/contact.html). The other form is used within HTML source to specify locations for content stored on the same server as the HTML content containing the reference. This specifies the pathname relative to the root directory of this server in the form "/<directory-path>/<content-name>.<extension> (i.e. "/company/content.html").  Any URL that does not begin with  "/" or "http" is a "Relative URL". Approval Class - Approval Classes define a series of specific steps that a content management request will follow from the time it is submitted into the workflow process until it is approved and published to your public web site or staging server. Each step references an individual workflow stage or, for Group Stages, one or more associated groups. WSD users will, based on their individual user permissions, be required to edit and/or approve each request. Approving a request moves that request through the Approval Class towards publication. Disapproving a request moves it backwards in the workflow process towards the request's originator or into the WSD Trash Bin.   For example, you may want your press releases to be submitted into a "Content Authoring" stage, then moved to the Editing stage, a Review stage and finally an Approval/Publishing stage. See Setting Up Your Workflow Tutorial.      Approval History - A record of each time a request is Edited, Approved or Disapproved, or the "Approvals Needed" for a request are modified, beginning with the time a request is submitted until it is published. Each entry contains the date and time of the event, a description of the event, and which WSD user performed the event. The Approval History screen is accessed from the request's "Properties" screen. Approvals Needed - The specific approvals required between the time a request to add or update content is submitted and the time the content is published. For any single request, these are associated with the Approval Class assigned to a request. A request's "Approvals needed" can be modified by any WSD user who has permission to modify Approvals needed. Users can see and, based on their permissions, change Approvals Needed using a request's Approvals Needed screen .  Author - The WSD-authorized user responsible for creating the initial content. This User category can also be used to record a "by line" when the originating author has to review the completed composition. When an e-mail request to add content is received from  a non-WSD authorized user, this name can be assigned to any authorized WSD user on the request's Properties screen.  Within HTML source, Author-related information can be referenced using the following template variables: <$prop:author$> - Author  <$prop:authorname$> - Author's First and Last Name  <$prop:authoremail$> - Author's Display E-mail Address  <$prop:authorurl$> - Author's URL.  If a request's Author only has "Access" permission (View-Only) for a workflow stage, he/she can disapprove the request to a stage where he/she has Edit/Approval permission. Author Notify E-mail Template - The E-mail Template that will be used by the WSD Notification Module to send a notification to an Author. These notification are sent when a request is approved into an Author workflow stage and the Author is responsible for creating or maintaining the content associated with that request.  See the " System Configuration " screen. Also see the E-mail Templates tutorial. Author Stage  -  One of the three types of workflow stages (steps) supported by WSD. The user designated as the content's "Author" can review, edit and approve their own content in this type of stage unless the user has "Update Documents in Author Stages" System Permission. Based on user permissions, other WSD users may be able to view and/or record comments to content in an Author stage. See the Setting Up Your WebSite Director Workflow tutorial for information on setting up Author Stages. Check-In/Check-Out - See "Lock/Unlock" below. Cookies - Cookies are a general mechanism which server-side programs (such as CGI programs) can use to both store and retrieve information on the client side of the connection. This means that applications can leave information on your workstation for later use to "remember" information that may be specific to your use of the application from that workstation. See Cookies. Creation Date -  the date/time the first version of any type of content is published. Database Publishing - Database Publishing allows WSD users to update selected information in any database that can be accessed by WSD. This allows site owners to selectively add workflow to database updating for dynamic content and other types of information stored in SQL databases. The current WSD Database Publishing feature does not support the retrieval of dynamic content directly from the SQL database. A directory structure on the web site (usually hidden from public view) mirrors the specific content stored in the database you have chosen to update using WSD. WSD uses Page Layout Templates to update database content. See Database Publishing  tutorial. Default Workflow Stage - This stage is assigned on the Approval Class screens, and designates the FIRST  stage into which new requests will be submitted. See Maintain Approval Classes. Description (Directory) - The directory description text entered on the Create Directory or Directory Properties screen; is returned by WSD when it encounters the <$prop:dirdesc$> template language command reference. Description (Content & Templates) - The description entered on the Content/Template Properties screen. This field is referenced by the <$prop:description$> template variable. Directory Index Filename - This is the filename, defined on the " System Configuration " screen, that WSD will create/maintain for each directory that is being indexed. The format of the directory's index is determined by Directory Index Templates. That template defines the layout and listings of all subdirectories and files managed by WSD within each indexed directory. Directory Indexing must have been turned on by selecting "Yes" for the Maintain Directory Index Files field on the " System Policies " screen. Directory Index Template - When the Maintain Directory Index Files System Policy is turned on, WSD generates a directory index file each time content is published to a directory you told WSD to index.  WSD uses Directory Index Template commands to format the directory index HTML file. See the " System Configuration " screen. See the Directory Index Templates tutorial. Directory Indexing  - Directory Indexing is a method used by WSD to create site maps for your web site or individual site segments. You must select each directory you want to be indexed by setting that property using the "Maintain Web Site" function. This feature allows you to either index individual directory content or link subdirectories into a composite map for those directories that you want to integrate into a site map.  See Directory Indexing. Directory Template Restrictions - Selecting "Templates" when setting Directory Properties in "Maintain Web Site" allows System Administrators to restrict availability of templates (Header, Footer, Layout and Index) for any WSD directory. Only "Available " templates will be displayed to content contributors when they submit a new request to add content. This limitation also applies to the template selections listed on the  "Properties" screen for individual requests within the workflow. Document Number - The unique, sequential number assigned by WSD to *new* content (i.e., text, graphic files, binary files, etc.) that has been added (via an ADD request) and published to the web site. This number is for your use when referring to document-related information using your own SQL queries and not the internal document number used by WSD. Modifying the content does not change this number. Deleting the content will not decrement this number. The number may be manually updated (for instance, to skip to a new series on a new year), but can not exceed nine digits in length. Does not apply to Templates. See the System Configuration screen. Document Publication Notice - An e-mail message sent by WSD immediately after content is published. These e-mails are automatically sent to content authors. Your System Administrator may also request immediate notification to a specific list of users for individual sub-directories from the "Directory Properties" screen in "Maintain Web Site." Document Submission Notice - An e-mail message, sent by WSD immediately after a new request is submitted into WSD. These e-mails are sent to a specific list of users as defined for and associated with individual sub-directories by your System Administrator from the "Directory Properties" screen in "Maintain Web Site." Dynamic Content - Dynamic content is any web content that is processed by the web server and/or web server helper processes (server applets) before sending the results to a site visitor's web browser. In contrast, static content is content which is sent to the browser without modification. Common forms of dynamic content are Active Server Pages (ASP), Java Server Pages (JSP), Cold Fusion (CF), and HyperText Processor (PHP) pages. WSD allows you to use any of the above-mentioned dynamic content servers and other well-known systems like WebLogic and ATG Dynamo.   See the Dynamic Content tutorial. Edit Layout Templates - Edit Layout Templates allow WSD administrators to provide complete control over the data entry form used in the Create/Edit Online screens when Page Layout Templates are used. This allows template designers to create data entry formats that are different from the layouts used when the content is actually published to the web site. See Edit Layout Templates Tutorial. Editor Permissions - Allows you to establish policies regarding use of WYSIWYG tools when editing requests regarding content in a directory. See the Directory Properties screen. E-mail Notifications - E-mail Notifications allow you to send e-mail messages to WSD users when various events occur. For example,  when content or templates are published to the web site, when requests to add or modify content or templates are submitted to WSD, when requests associated with work-in-progress are approved or disapproved between Workflow Stages, when requests have been left unattended in a workflow stage longer than the time specified on the System Configuration screen, and/or scheduled request status e-mails for individual workflow stages, as selected by a WSD user.     Except for scheduled status e-mails, all notification messages are sent immediately following the completion of the associated event. E-mail Submission - You may submit requests to add new content or make changes to existing content via an e-mail message addressed to an e-mail address monitored by WSD's content submission process. See the E-mail Submissions tutorial for more information. E-mail Template - A document containing a combination of user-defined text and WSD e-mail template variables used to reference request and content meta data. WSD uses e-mail templates to send e-mail notifications either periodically or when specific events have been completed. See the E-mail Template tutorial.  Expiration Date - WSD provides this property at the Request level to allow users to indicate if/when WSD's "Cleanup Database" module should automatically generate and submit a request to Delete or Modify the selected content. Default selection is Never. The second element of this property allows you to specify the date on which the automated request will be generated if the selected option is Delete (a delete request will be generated on the specified date) or Modify (a Modify Request will be generated on the specified date). Filename - The path and filename where content/templates associated with a specific request is/will be published. The following list shows some examples of how  template variables can be used to reference filename-related information: <$prop:filename$> - the Document Root-relative  Directory Path and Content Filename  <$prop:fname$> - the Content Filename without the Directory Path  <$prop:dirpath$> - the Document Root-relative Directory Path in filesystem format <$prop:dirurl$> - the Document Root-relative Directory Path in URL format <$prop:dirname$> - the Document Root-relative Directory Name without the filename portion <$prop:dirdesc$> - the Directory Description (see Directory Maintenance for more information) <$prop:dirsection$> - the Directory Section Name (see Directory Maintenance for more information) WSD provides additional variables to allow your template developers independent references to parent directories associated with content to be published, including the ability to determine how deeply a page is nested within the directory tree of your web site. Additional information is provided in the Template Language Tutorial. Footer Template - A grouping of HTML code and WSD template variables that define content that may be appended to HTML/text documents by WSD when that template is assigned to specific content by WSD users. These templates are normally used to define standard navigation and page "look and feel" to content on a selective basis. See Header & Footer Templates below. Group Approval Stage  -  Content in a Group Approval Stage needs to be approved by one or more groups. See Maintain Groups and the Setting Up Your WebSite Director Workflow  tutorial. Group ID - The internal Group ID used by template designers and application developers. It is displayed here for their use in most of the external API commands that refer to WSD groups, in the "group= " Layout Template attribute, and the "groupmember" template conditional tag. See < /FONT> < /FONT> Edit Group . Groups - Workflow Groups allow you to distribute approval responsibilities to multiple members of the same organization (for example, a company policy committee or the Legal Department). To prevent approval bottlenecks caused by serialized approvals, any group member with Approval permission can represent the entire group, and multiple Groups may approve content in any order within the same Group Approval Stage. Header & Footer Templates - Header and Footer Templates allow you to design and customize the look and feel of your web site. They also allow you to standardize navigation for your site and site segments. Content contributors and Page Layout Template designers can assign specific headers and footers to content published to your site. WSD adds assigned header and footer templates to your content body when the content is approved and published. It does this by generating the final content from the combination of Header template, content body or Page Layout template, and Footer template. Also, whenever you view or preview content in process, WSD displays the content with the assigned Header and Footer templates exactly as they will be generated when finally published to the web site. See the Header and Footer Templates Tutorial. Header Template - A grouping of HTML code and WSD template variables that define content that may be prepended to HTML/text documents by WSD when that template is assigned to specific content  by WSD users. These templates are normally used to define standard navigation and page "look and feel" to content on a selective basis. See Header & Footer Templates above. Index Position - The content's position in the directory index list. This field is present on the Properties screen only when the "Maintain Directory Index Files" System Policy is turned on. See Directory Indexing Tutorial  for more information. Individual Stage  - A workflow stage in which any user may Edit, Approve, and/or Disapprove any request assigned to that stage, based on that user's individual permissions. Unlike Author Stages,  any user may work on any request. This type of workflow stage is ideal for mixed permission processes, like Editing, where any Junior Editor may modify content, but only Senior Editors are allowed to approve content. See the Setting Up Your WebSite Director Workflow tutorial. Keywords - a set of search keywords used in a search index that point to the content. This field is entered/displayed on the request's Properties screen. This field is not used by WSD, but is accessible using the <$prop:keywords$> template variable. its primary use is in building Header Templates. Links Processing - WSD provides a Links screen to help you determine what other content has links to and from your documents. Links *FROM* a particular document are only processed and shown for those documents whose Mime Type has the Process Links option enabled (see Add Mime Types ). When Links is selected from the Properties screen for published content or from a request associated with the content, WSD performs Links processing for the Mime Type assigned to the content. The list displays a list of all links in the document that point at content on this site or other sites (Links FROM this document) as well as a list of documents on this site that point TO this document (Links TO this document). Local Domain Name - The name of the local Internet domain containing all requests submitted through WSD (for example, "company.com"). When WSD sends an e-mail message, the SMTP mail server needs to know where the message originated. See the System Configuration  screen. Lock/Unlock - When a user is working on a request to add or modify content, WSD locks (checks out) the request to prevent anyone else from editing it until the person editing the request unlocks (checks in) the request or de-selects the "Leave Request Locked" check-box. WSD automatically locks a request (sets the check-box value to "Leave Request Locked") when a user downloads it to their local machine and unlocks a request (resets the check-box value) when a user uses "Browse/Upload" to associate new content with a request. WSD remembers the Lock/Unlock setting when a user edits a locked request.  Locked By - The name and e-mail address of the authorized WSD user who has locked a request. Locked Request - A request may be locked because another user is currently working online and is in Edit Request, a user has checked out the request to work off-line, or a user may have forgotten to unlock the request. Also, the system default may have been set to "Default Leave Request Locked" on the System Policies screen. See Locked Request Tutorial . Maintainer - The WSD-authorized user responsible for ongoing changes to the content. This field is an alternative method of recording a "by line" naming 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: <$prop:maintainer$> - Maintainer  <$prop:maintainername$> - Maintainer's First and Last Name  <$prop:maintaineremail$> - Maintainer's Display E-mail Address  <$prop:maintainerurl$> - Maintainer's URL If you give a Maintainer only the "Access" permission (View-Only) in a workflow stage, he/she can disapprove any request in that View-Only stage into a stage for which he/she has Edit/Approval permission. MIME Type (Multimedia Internet Mail Extensions) - A standard for multi-part, multimedia electronic mail messages and World-Wide Web hypertext documents on the Internet. MIME provides the ability to transfer non-textual data, such as graphics, audio and fax. It is defined in RFC 2045, RFC 2046, RFC 2047, RFC 2048, RFC 2049, and BCP0013. WSD uses MIME Type definitions to identify dynamic server environments. MiniSQL Database - WSD currently supports the MiniSQL (usually referred to as "mSQL") database engine on all server platforms. Note: Most of the long-term information stored in WSD is kept in a database on the web server or, in a database on a server connected by a LAN to the web server.  See the Database Maintenance  tutorial. Multiple Installations of WSD for the same Document Root  - Multiple copies of WSD may be installed on the same server for the same Document Root where each copy of WSD will manage a different site segment. This allows you to give control and responsibility for content maintenance to individual groups (i.e. Engineering, Marketing, Human Resources, etc.) within your organization. When a WSD installation manages only a portion of a server, the parent directory that defines its management space is called its "Working Directory." The installation program provides a "Working Directory" field that must be completed for any WSD installation that manages only a portion of a web site.  See the Directory Maintenance  tutorial for more information. You must purchase a license for each copy of WSD you are going to install. CyberTeams provides an 80% discount for additional licenses purchased for use on the same server. The license with the largest user community is always considered the first/primary license. Multiple Installations of WSD for different web sites on the same server- Multiple copies of WSD may be installed on the same server for different domains, where each copy of WSD will manage a different web site. You must purchase a license for each copy of WSD you are going to install. CyberTeams provides an 80% discount for additional licenses purchased for use on the same server. The license with the largest user community is always considered the first/primary license. MySQL Database - WSD currently supports the MySQL database engine on all server platforms. Note: Most of the long-term information stored in WSD is kept in a database on the web server or, in a database on a server connected by a LAN to the web server.  See the Database Maintenance  tutorial.   New Account Request Address - The e-mail address to which requests for a new WSD Username should be sent. These requests are submitted to WSD when you implement a a web page allowing your users to request new accounts on-line. CyberTeams provides a sample recommended WSD Main Entrance Page. See the System Configuration  screen. Next Document Number - See Document Number.  Next Revision Number - The next revision number that will be assigned when content is revised and published. This number begins with 1.0, and is automatically incremented by an increment defined on the System Configuration screen (default is 0.1) each time a request to add or modify content is submitted; not when it is published. While a request is being processed, the revision number can be changed manually, but only to a *larger* number. This number displays and may be changed on the request's Properties screen. However, it may not be less than 1.0. Notify E-mail Template - The E-mail Template to be used by the WSD Notification Module when it sends out scheduled request status notification messages to users. See the System Configuration  screen. Also see the E-mail Templates  tutorial. Notify From Address - The "From" address to be used by the SMTP mail server when WSD sends an e-mail notification message. This address may be overridden by using "From: <e-mail address>" in the E-mail Template for the notification message. See the System Configuration  screen. Also see the E-mail Templates  tutorial. ODBC Data Source - WSD supports ODBC for Windows and UNIX to provide access to, and use of, a wide range of SQL databases. Windows provides ODBC drivers for all supported databases. For UNIX, you must purchase your ODBC drivers independently. WSD has been tested with drivers  from Openlink Software ( www.openlinksw.com). Orphaned Documents - Those content elements of any MIME-type that are not linked to BY another document. The System Policies screen provides the ability to enable the "Cleanup Database" module to perform a check to identify orphaned documents. All identified documents are submitted as Delete requests using the "Submitted By" source identified via the "Auto Delete/Modify Submitter" option on the System Configuration screen.   Note:  Content in directories with the "Skip Auto Delete" flag set and individual documents with the Request or Document "Option" Property "Skip Orphan Document Check" set will be ignored by the Cleanup Database module. Page Layout Templates - Page Layout Templates allow you to populate web pages that have a predefined format by specifying which portions of content can be created/edited by content contributors. WSD provides two types of on-line editing: WYSIWYG editors, and a browser-based HTML/Text Editor for those who are familiar with HTML code. You also have the option of uploading a template from your local computer, or downloading the template so you can use any third-party application like Adobe GoLive or Macromedia Dreamweaver to manipulate your template content. Pending Requests - See Submissions Stage. Private Directory - Private directories are used to prevent access to segments of a site for one or more of the following reasons: the segment is being maintained by other copies of WSD; the segment is being maintained by some other content-management method; the segment contains information unique to another application running on the web server, and is maintained by that application and not any content management method. These segments are visible only to those users who have System Administration permission (assigned on the Add User and Edit User Info screens) using the Maintain Web Site screen. Directories are designated as private by selecting the "Private Directory" flag on the "Create Directory" and "Directory Properties" screens. WebSite Director (WSD) will not manage any content in a Private Directory.     Publication Date - The date/time, following final approval into the Publishing workflow stage, that you want WSD  to publish a request to add or modify content. This field value can be modified from the system default using the request's Properties screen. The default publication date for WSD is set on the System Policies  screen. This field is referenced by the <$prop:publishdate$> template variable.  Publish Notifications - See Document Publication Notice. Publishing Status - Requests that have been approved for publication, but have not yet been processed by the publication module are listed on the Publishing Status  screen by System Administrators.  RCS - Acronym for "Revision Control System." This is a Unix-based standard for maintaining information regarding multiple published instances of individual files stored in the file system. WSD uses RCS-based versioning because of its efficiency. RCS stores only the most recently published version in its entirety, recording the differences from that version to later re-create previously published versions. RCS libraries are provided automatically for all Unix platforms. WSD includes a Windows-based RCS library in its Windows NT and Windows 2000 installation packages. Relative URL - A directory path relative to the publishing location of the current web page. Any URL that does not begin with either "http" or "/" is a Relative URL. Relogon  -  The Relogon function allows users who are logged on to WSD to log on with a different Username and Password (or with the same Username and Password) without first closing all open browser windows and then opening a new browser instance. See Relogon. Reminder Age (in days) - The number of days that a request can remain in the same stage before a Reminder e-mail message is sent to users responsible for editing/approving content in   that stage. This includes users who have turned off the notification message option for the stage. This is set on the " System Configuration " screen. Reminder E-mail Template - The E-mail Template to be used by the WSD Notification Module when it sends out a Reminder notification message. Reminder messages are sent to users that have requests waiting for their review/approval longer than the time limit entered in Reminder Age (in days) on the " System Configuration " screen.  Also see the E-mail Templates  tutorial. Request - This term describes the container used to manage requests to create new or manage existing content on your web site. This container, created by WSD, is used to describe user-related and content-related meta data and includes a "working copy" of the content that will be published following final approval. Requests are not visible to site visitors because WSD manages them outside your Document Space. Requests are archived in the Version History following publication of the associated content, including comments and all other associated properties. Requests can be submitted via e-mail, from other server processes via WSD's external API, WSD's Live Submit feature, or through the WSD Submit New Request screen. See the  Submit Request tutorial. Request Category - The type of request to add or modify content that you are submitting. Types are Documents (including text, graphics, binary files, etc.) or Templates. Default setting when creating a new request is Documents. Request History Age (in days) - The length of time the version history of published content will be retained before the WSD Overnight Cleanup module deletes it from the WSD version history repository. See the System Configuration  screen. Request Type - One of the following request types: E-mail, Add, Modify, Move, Copy, Rename, and Delete.  The "Move" request type is not available for Templates. Scheduled Processes- WSD provides access to five independently executable programs that perform functions we recommend for overnight processing. These are: content publishing, e-mail notification for reminders and request status, pending (abandoned) requests and dynamic content preview cleanup, database integrity checking, and content repository access permission verification. The Check Permissions module should also be scheduled to run overnight to perform an analysis, check directory and file permissions on the web server and produce the Server Permissions Check report. In addition to scheduling these processes for overnight execution, you can also execute any or all of these modules immediately from the System Administration  screen. For more information, see the Overnight Processes  tutorial. Section Label - The directory's label text  as entered on the " Create Directory " or " Directory Properties " screen. This text is returned by WSD when it encounters the <$prop:dirsection$> template language command reference. See Directory Indexing Templates  tutorial. SetProperty - "SetProperty" commands allow Page Layout Template designers to specify which/whether Header and Footer Templates are to be automatically assigned to content created using Page Layout Templates. In addition to declaring Headers, Footers, and Edit-Layout templates, template designers can use "SetProperty" commands to preset any valid document property such as author, title, description, etc. All properties declared by a "SetProperty" command are automatically set when a Page Layout Template is used to create new content.  The format of the SetProperty command is:  SetProperty <property>= <value> and each SetProperty command must be the first and only entry on a line within the Page-Layout template. Site Name - This field allows you to enter a value to be "pre-pended" to all WSD screen "Title Bars" and to the footer on the "Application Desktop" screen. This will allow you to differentiate between browser instances accessing multiple web sites for the same organization. It also makes it easier to quickly identify which web site is being accessed by multiple WSD browser windows on a user's desktop. This value is set on the System Configuration  screen. SMTP Host Name - This field designates the name of the machine running the SMTP mail server that WSD will communicate with. When WSD sends an e-mail message, it contacts the SMTP mail server specified in this field. This value is set on the System Configuration  screen. SQL Journal File - WSD has the option of maintaining a journal file of all SQL update commands issued against the WSD database. This journal file can be used to recover a WSD database completely even if the database files themselves are corrupted and have to be restored from an older backup.  See the Database Maintenance  tutorial. Stage ID - The internal Stage ID is used by application developers. It is displayed here for their use in most of the external API commands that refer to WSD Stages. See Edit Stage . Stages - Workflow stages allow you to define and customize each step (stage) of your WSD workflow to match the same policies, checks, and balances that you have in place for your manual paper publishing processes, or steps you want to use for your web content publishing process. See Maintain Stages  and Setting Up Your WebSite Director Workflow  tutorial. Submissions Stage - Each user's private workflow stage where requests can be submitted and worked on before being submitted into the workflow process. Requests may be Saved into this stage instead of Submitted into the workflow process defined by the Approval Class associated with a request. WSD will also place requests into the Submission stage when processing is terminated (due to system failure or your use of your browser's Back button) before a request has been submitted into a workflow stage. See Maintain Submissions. Submit Notifications - Allows your System Administrator to define a list of WSD users who will be notified immediately after a new request associated with content in a given directory has been submitted to WSD. See the Directory Properties screen. Submitted by - The Properties screen field where the WSD-authorized user submitting content into the workflow process is assigned and displayed. For e-mail requests from authorized WSD users, this name is derived from the submitter's e-mail address. For e-mail requests from non-WSD authorized user, this name must be assigned on the request's Properties screen. Submitter - the WSD-authorized user responsible for creating a request to add or modify content. Submitter-related information presently can not be referenced using template variables. If you give a Submitter only the "Access" permission (View-Only) in a workflow stage, he/she can disapprove any request in that View-Only stage into a stage for which he/she has Edit/Approval permission. System Policies - A series of settings representing "system-wide policies" regarding WSD behavior. These policies are selected on the System Policies  screen. Temp File Cleanup Age (in days) - WSD creates temporary copies of content that is being added and edited.  If these requests are abandoned (not Saved or Submitted), the WSD Overnight Cleanup module uses the value in this field to identify how long these temporary files should remain before deleting them. This option is set on the System Configuration  screen. Template Publication Notice - An e-mail message sent by WSD immediately after a template is published. These e-mails are automatically sent to template authors. Template Variables  - These are references in the form <$prop:variable$>, where "variable" is the name of a specific WSD meta data (User/document-related information) Property, or <$field:fieldname$>, where "fieldname" is the name of a specific WSD template field defined in the Page Layout Template being used. During View Request, Preview, and Publishing, WSD replaces the <$prop:variable$> or <$field:fieldname$> reference with the actual data value recorded for the named "variable" or "fieldname" in the WSD database or content. If no property or field value is available for a <$prop:variable$> or <$field:fieldname$> reference, WSD suppresses the associated reference text in the template.  See Template Language . Title - The title of the content associated with a request. May be changed on the request's Properties screen. This field is referenced by the <$prop:title$> template variable. This variable is most often used in Header Templates. Trash Bin - Contains all requests that have been disapproved to the Trash Bin. See Maintain Trash Bin. Unlocking a Request - See Lock/Unlock above. User - an individual who is assigned a username and password to logon to WSD. A user can also be a server process, using the external API to access WSD. Depending on the permissions a user has, he/she can manage content and/or perform administration functions (like template administration, user administration, etc.).  Also see the User Administration tutorial. User Directory Permissions - Allows you to create restricted directories where you can define a list of users who are either specifically allowed or disallowed to submit content management requests for content in a directory. See the Directory Properties screen Version File -  The name of the file that contains the RCS-based version information for each version of content published by WSD. This information is maintained by WSD in the <installdirectory>/versions subdirectory. The most recently published version  is retrieved when a request is submitted via the "Submit New Request" screen. When retrieved, WSD compares this file against the version published on the web site. If they are not the same, an error messages displays giving you the choice of using the WSD history version, using the version published on the web site, or canceling the request. Note: When displaying Properties from the "Maintain Web Site" screen this field may contain the value "N/A" indicating the content was not published by WSD. Click Update Properties. WSD will create a version history record as if the content had been published by WSD. This makes the candidate content eligible for Indexing. Version History - The Version History for content published by WSD is maintained in a database record that contains the original author, version numbers, dates, and authors of each version of the asset. WSD gets this information from its RCS (Revision Control System) files. Each time an asset is updated, it is "checked in" to the WSD repository and its version number is updated by the increment set on the System Configuration screen (0.1 is the default increment). The Version History screen, accessed from the Properties screen, provides access to the Version Update History and allows you to revert back to a previous version. To revert to a previous version of an asset, select and submit that version on the Version History screen by clicking the Submit as New Update button. The version will be submitted into the regular WSD workflow for review, approval and publishing. Workflow - Any well-defined process which controls the progression of work between specific business processes. WSD uses workflow, as defined by "Approval Classes" assigned to individual subdirectories, to control access to and progression of content management requests between selected Individual, Author, and Group Approval stages. Workflow Administration is performed using your web browser and requires no programming. For additional information, see the Setting Up Your WebSite Director Workflow tutorial. Working Directory -  The highest (parent) subdirectory (virtual root directory) of the portion of your web server's entire Document Root being maintained by WSD. Within User Permissions under User Administration, this term is used to refer to the  highest (parent) subdirectory (virtual root directory) identifying the document space to which a specific user will be restricted when creating new requests.