EDIT STAGE

This screen allows you to edit the workflow stage selected on the Maintain Workflow Stages screen

INFORMATION ON THIS SCREEN:

Stage Name	The descriptive text that identifies the stage. This name can have up to 40 characters, and may contain any characters that can be displayed in HTML. The Stage Name appears on the WSD Application Desktop, reports, notification message, and other areas of WSD that list or refer to workflow stages. We recommend that you assign a descriptive name to each stage, preferably a name that matches your workflow. For example: Design, Typeset, Editing, Formatting, Policy Review, Author Correction, Author Review, Final Review, etc.
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.
Stage Type	Author - Restricts access to individual requests (content) in this workflow stage to the following: The designated Author, as defined on the Properties screen Any user authorized to "update requests in an Author stage" as defined on a User Permissions screen Other WSD users can be given permission to view and add comments to requests in an Author Stage depending on a policy set on the System Policies screen. Individual - Any WSD user with permission to edit and approve requests in this Stage Type can edit and/or approve any request.  Group - Permissions to edit and/or approve requests in this Stage Type are based on the each user's membership in one or more approval groups required to approve individual requests. Which groups are allowed to approve requests are assigned to a Group stage using the Edit Group screen. Groups required to approve requests within a Group Approval Stage are assigned via the Maintain Approval Classes screen. A user who has been given permission to Modify Approval Needed via the User Permissions screen can add or remove groups from the list of required approvals for specific requests.
Notification E-Mail Template (Author Stages only)	If the Stage Type is Author, this field allows you to choose whether you want designated Authors to receive automatic e-mail notifications when requests are approved or disapproved into this Stage Type. Choose "None" if you do not want WSD to send automatic notifications, else select a specific E-mail  template from the drop-down list.
Required Request Fields	These check boxes determine the information required before a request can be approved to this stage (i.e., the information must be provided in a previous stage). For the Submitter, Author, and Maintainer fields, the name must be selected from a drop-down list of Authorized WSD Users on the each Request's  Properties screen. Filename Path: identifies the path and filename of the content associated with a request when it is published to the public web site. It must be a required field for the Publishing Stage, however, you may make it a required field for any stage preceding the Publishing Stage. The information in the Filename field is referenced by the<$filename>  template variable. [Filename:] on the Properties screen.  Submitter: identifies the person submitting the document. It is recommended that it be a required field for the stage immediately following the Initial Entry stage, so that reviewers and approvers know who submitted the document. [Submitted By:] on the Properties screen.  Author: identifies the author of the request. It must be a required field for all Author stages so that WSD knows which user can modify, approve and disapprove the request. The information in the Author field is referenced by the <$author> template variable. [Author:] on the Properties screen.  Maintainer: identifies the person responsible for updating the request after it is published. The information in the Maintainer field is referenced by the <$maintainer> template variable. [Maintainer:] on the Properties screen.  Request Type: identifies one of the listed request types: Unknown, Email, Add, Modify, Copy, Move, Rename, or Delete. Because Unknown and Email are not valid Publishing request types, the Request Type must be changed to one of the other five types before the request is approved to the Publishing Stage. You may choose to make it a required field for any stage preceding the Publishing Stage. [Request Type:] on the Properties screen. Note: Unknown does not apply to Template requests.  New Filename: identifies the new filename for a COPY, MOVE or RENAME request. It must be a required field for the Publishing Stage, however, you may make it a required field for any stage preceding the Publishing Stage. [New File Path and Name:] on the Copy Request, Rename Request and Move Request screens.  Next Revision Number: identifies the revision number for any asset, beginning with 1.0. This number is automatically incremented by the Version Increment (set on theSystem Configuration screen) each time a request (Add, Modify, etc.) is submitted for that asset; not when the asset is published. While a request is being processed, the revision number can be changed manually, but only to a *larger* number. The information in the Next Revision Number field is referenced by the <$revision> template variable. If you do versioning, this should be a required field. [Next Rev #:] on the Properties screen.

FUNCTIONS:

UPDATE STAGE	Select this function to save the information entered on this screen and return to the Maintain Workflow Stages screen.
CANCEL	Select this function to cancel all information entered on this page and return to the Maintain Workflow Stages screen.