<!-- 
	 Copyright 2005-2006 The Kuali Foundation.
 
 
     Licensed under the Educational Community License, Version 1.0 (the "License");
     you may not use this file except in compliance with the License.
     You may obtain a copy of the License at
 
     http://www.opensource.org/licenses/ecl1.php
 
     Unless required by applicable law or agreed to in writing, software
     distributed under the License is distributed on an "AS IS" BASIS,
     WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
     See the License for the specific language governing permissions and
     limitations under the License.
-->
<?xml version="1.0" encoding="UTF-8"?>
<data xmlns="ns:workflow" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="ns:workflow resource:WorkflowData">
	<helpEntries xmlns="ns:workflow/Help" xsi:schemaLocation="ns:workflow/Help resource:Help">
		<helpEntry>
			<helpName>Position Type</helpName>
			<helpText>These are position types defined in Human Resource system. Click the desired entry to select it.</helpText>
			<helpKey>PositionType</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Salary Plan</helpName>
			<helpText>HRMS uses Salary Plans to help identify default Paygroup and Object Codes of an employee for job funding. Salary Plans differentiate employees of a particular Position Type. For instance, the Hourly PERF (HP) salary plan can be found under the Hourly (HR) position type. Select a distinct Salary Plan if you do not want to receive eDocs from all Salary Plans found under a specific Position Type.</helpText>
			<helpKey>SalaryPlan</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Fiscal UPAA</helpName>
			<helpText>Fiscal is the Fiscal Approver. UPAA stands for Unit Personnel Action Agent.</helpText>
			<helpKey>FiscalUPAA</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Fiscal UPAA Delegate</helpName>
			<helpText>The delegate is the person or workgroup who is designated as an alternative approver for either the Fiscal Approver or the Unit Personnel Action Agent (UPAA).</helpText>
			<helpKey>FiscalUPAADelegate</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Chart</helpName>
			<helpText>The name of a top-level University organization unit in the approval chain for financial documents. Expressed as a 2-character code. For example, "IA" for Indianapolis Administrative.</helpText>
			<helpKey>Chart</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Reviewer ID</helpName>
			<helpText>The person or the workgroup to whom this document will be routed for approval. For a person, enter the Network ID username. For a workgroup, enter the Workgroup ID.</helpText>
			<helpKey>ReviewerID</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Org</helpName>
			<helpText>The name of a University organization unit within a specific Chart unit, used in the approval chain for financial documents. Expressed as a 2- to 4-character code. For example, "UNIV" for University level.</helpText>
			<helpKey>Org</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Document Type Group Parent</helpName>
			<helpText>The name of the parent Document Type Group for this Document Type or Document Type Group. Properties of this parent will be inherited automatically.
		      Enter the name of the Document Type Group, or select one in the QuickFinder. Leave the field blank if there is no parent Document Type Group
</helpText>
			<helpKey>DocumentTypeGroupParent</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Document Type Group Name</helpName>
			<helpText>The name of the Document Type Group. 
		      The string includes all parent Document Type Groups, if any, arranged hierarchically and separated by periods. 
		      For example,GrandparentDocTypeGroup.ParentDocTypeGroup.ThisDocTypeGroup.</helpText>
			<helpKey>DocumentTypeGroupName</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Document Type Group Label</helpName>
			<helpText>The display label of the Document Type Group.
		    This text is the label displayed in any reference to the Document Type Group in other documents or applications.</helpText>
			<helpKey>DocumentTypeGroupLabel</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Document Type Group Description</helpName>
			<helpText>Text that describes the common function and properties of the Document Type Group. The description documents the business transactions performed by documents that inherit from this Document Type Group. It is free-form text provided by the Document Type Group authors.</helpText>
			<helpKey>DocumentTypeGroupDescription</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Action Taken ID</helpName>
			<helpText>An internal integer that Workflow creates to unique identify an Action Taken entry.</helpText>
			<helpKey>ActionTakenID</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Action Date</helpName>
			<helpText>The time and date on which the Action was taken, formatted hh:mm:ss xm MM/DD/YYYY.</helpText>
			<helpKey>ActionDate</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Date Finalized</helpName>
			<helpText>The date on which the document was "finalized", i.e., all approvals and acknowledgements are done. The date must be expressed in the MM/DD/YYYY format, e.g., 12/25/2000 for December 25, 2000. The date may also be supplied by clicking the adjacent Calendar icon and selecting a date from the monthly calendar; the value is then automatically loaded into the field. Also, the search may be expanded by selecting either "Before" or "After" from the adjacent pulldown list to find documents finalized before or after the selected date inclusive, respectively. For the selected date only, use the default "Exactly" from the list.</helpText>
			<helpKey>DocSearchDateFinalized</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Viewer</helpName>
			<helpText>The Network ID of anyone who views the document during its routing, i.e., anyone in its RouteLog for a request to acknowledge, approve, complete, or FYI the document. This string must be a valid Network ID. Use the magnifying glass icon to search for people by identifiers such as first and last name, employee id, and network id.</helpText>
			<helpKey>DocSearchViewer</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Document Title</helpName>
			<helpText>The Document Title given to the document when it is created. This string may have been assigned by the Initiator or built automatically from the contents of the document, depending on the document type.</helpText>
			<helpKey>DocSearchDocumentTitle</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Document Route Level</helpName>
			<helpText>The number of a route level in the document. Use the pulldown list to qualify the search to Exactly, After, or Before this Route Level.</helpText>
			<helpKey>DocSearchDocumentRouteLevel</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Date Approved</helpName>
			<helpText>The date on which the document was most recently approved. The date must be expressed in the MM/DD/YYYY format, e.g., 12/25/2000 for December 25, 2000. The date may also be supplied by clicking the adjacent Calendar icon and selecting a date from the monthly calendar; the value is then automatically loaded into the field. Also, the search may be expanded by selecting either "Before" or "After" from the adjacent pulldown list to find documents most recently approved before or after the selected date inclusive, respectively. For the selected date only, use the default "Exactly" from the list.</helpText>
			<helpKey>DocSearchDateApproved</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Document Route Status</helpName>
			<helpText>The current routing status of the document, one of the following: 
                All 		All documents that have been submitted for routing
        		Initiated 	Document is created, but is not yet submitted for routing.
        		Saved 		Document has been saved to complete later.
        		Enroute 	Routing is in progress.
        		Approved 	Document is approved by all required reviewers and is waiting for postprocessing.
        		Disapproved Document is disapproved by a reviewer. Routing has stopped.
        		Canceled 	Document is canceled by a reviewer. No further action can be taken.
        		Processed 	Document is approved, and its postprocessing is completed. It is waiting for acknowledgements, if any. No further action needed.
        		Final 		Document is finalized and all acknowledgements have been received, if any. No changes are allowed.
        		Exception 	A routing exception has occurred, requiring processing.</helpText>
			<helpKey>DocSearchDocumentRouteStatus</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Workgroup Name</helpName>
			<helpText>Name of the workgroup.  May be used to search for the workgroup.</helpText>
			<helpKey>WorkgroupName</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Workgroup Active Indicator</helpName>
			<helpText>This option indicates whether or not the workgroup can be requested of any workflow related actions.</helpText>
			<helpKey>WorkgroupActiveIndicator</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Document Type</helpName>
			<helpText>The Document Type of the documents.  This string must be a Document Type Name or Label previously validated for Workflow. Use the magnifying glass icon to search for document types.</helpText>
			<helpKey>DocSearchDocumentType</helpKey>
		</helpEntry>		
		
		<helpEntry>
			<helpName>Initiator</helpName>
			<helpText>The Network ID of the initiator, i.e., the individual who created the document.  This string must be a valid Network ID. Use the magnifying glass icon to search for people by identifiers such as first and last name, employee id, and network id.</helpText>
			<helpKey>DocSearchInitiator</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Document Id</helpName>
			<helpText>The numeric identification of the document for routing purposes. This number may or may not be the same as the Application Document ID, depending on the type of document. However, it is always an integer unique among all routing "e-Docs". It is displayed in the "Document ID" column of both the Action List and the Document Search channels.</helpText>
			<helpKey>DocSearchDocumentId</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Date Created</helpName>
			<helpText>The date on which the document was created. The date must be expressed in the MM/DD/YYYY format, e.g., 12/25/2000 for December 25, 2000.  The date may also be supplied by clicking the adjacent Calendar icon and selecting a date from the monthly calendar; the value is then automatically loaded into the field. Also, the search may be expanded by selecting either "Before" or "After" from the adjacent pulldown list to find documents created before or after the selected date inclusive, respectively. For the selected date only, use the default "Exactly" from the list.</helpText>
			<helpKey>DocSearchDateCreated</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Document Search Named Search</helpName>
			<helpText>A named search is a group of Workflow Document Search criteria that has been saved for a user under a name supplied by the user. If the user has performed a Document Search and has saved this search criteria as a Named Search, the user can perform this search again by simply selecting the name of the search out of a dropdown list on the Document Search page and this search will be performed using the saved criteria. To save the current search criteria, enter a name to name your search and click the search button. The search criteria will be saved under this name and the name will appear in the Searches dropdown list at the top of the Document Search page. To recall a search, select the search by name from the dropdown list at the top of the Document Search page and click the search button. This will perform the Document Search with the search criteria saved under that name.</helpText>
			<helpKey>DocSearchNamedSearch</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Approver</helpName>
			<helpText>The Network ID of an approver, i.e., anyone who approves the document. This string must be a valid Network ID. Use the magnifying glass icon to search for people by identifiers such as first and last name, employee id, and network id.</helpText>
			<helpKey>DocSearchApprover</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Application Document ID</helpName>
			<helpText>The identification of the document by the application which created it. This value may or may not be the same as the Document ID, depending on the type of document. Applications may use the Document ID supplied by Workflow for their internal Document ID, or they may create a value which becomes this Application Document ID.</helpText>
			<helpKey>DocSearchApplicationDocId</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Date Last Modified</helpName>
			<helpText>The date on which the document was last modified. The date must be expressed in the MM/DD/YYYY format, e.g., 12/25/2000 for December 25, 2000. The date may also be supplied by clicking the adjacent Calendar icon and selecting a date from the monthly calendar; the value is then automatically loaded into the field. Also, the search may be expanded by selecting either "Before" or "After" from the adjacent pulldown list to find documents last modified before or after the selected date inclusive, respectively. For the selected date only, use the default "Exactly" from the list.</helpText>
			<helpKey>DocSearchDateLastModified</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Document Type Active Indicator</helpName>
			<helpText>This option indicates whether or not the application will be allowed to create EDocs of this Document Type. Inheritance on Active Indicator differs from inheritance in all other policies. If the Document Type's Document Type Parent is set to Inactive, then EDocs of this type will not be created by the application, regardless of the inheritance. However, if the Document Type is set to Inactive and the Document Type's Document Type Parent is set to Active, then the Document Type will remain Inactive.</helpText>
			<helpKey>DocumentTypeActiveIndicator</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Document Type Description</helpName>
			<helpText>Text that describes the purpose and function of the Document Type. The description documents the business transactions performed by documents of this Document Type. It is free-form text provided by the Document Type authors.</helpText>
			<helpKey>DocumentTypeDescription</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Document Type Default Approve Policy</helpName>
			<helpText>This option indicates whether EDocs of this Document Type can be put in the Approved state without any Approve Action Request. If this option is set to Yes, then it is equivalent to giving an EDoc of this type implicit approval.  If this option is set to No, then an EDoc of this type must have at least one approve to be put in the Approved state.</helpText>
			<helpKey>DocumentTypeDefaultApprovePolicy</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Document Type Pre Approve Policy</helpName>
			<helpText>This option indicates whether EDocs of this Document Type can have Approval Actions Taken on them before their corresponding Action Requests are generated or activated.</helpText>
			<helpKey>DocumentTypePreApprovePolicy</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Initiator Must Route</helpName>
			<helpText>Initiator Must Route.</helpText>
			<helpKey>InitiatorMustRoute</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Document Type Searchable Attribute Name</helpName>
			<helpText>Name of the Searchable Attribute to be associated with this Document Type. If the Document Type has a Searchable Attribute, this attribute field will display on the Document Search page whenever the corresponding Document Type is selected as a search criterion. The Searchable Attribute field can then be used to provide additional search criteria.</helpText>
			<helpKey>DocumentTypeSearchableAttributeName</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Document Type Route Level</helpName>
			<helpText>This is a number that orders the route levels of a Document Type. The route levels contain route methods (route modules or route templates) that determine how documents of this document type will be routed. Enter a positive integer indicating the order in which the route methods will be run.  The methods are run in ascending order by their numeric Route Level: 1, 2, 3, ... Entries with the same Route Level (but different Route Types) are run concurrently. Two additional entries are required:
  			-1   Exception Route Level
  	 		0   AdHoc Route Level</helpText>
			<helpKey>DocumentTypeRouteLevel</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Document Type  Route Level Name</helpName>
			<helpText>The name of a Route Level for this Document Type. Enter text that describes the business function involved.</helpText>
			<helpKey>DocumentTypeRouteLevelName</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Document Type JNDI Factory Class</helpName>
			<helpText>The name of the Factory Class of the JNDI service for the Document Type. Together with the JNDI URL, it locates the applications which support this Document Type.
  	      
  	      This field is used only if the applications are not coresident with Workflow, and is normally left blank.</helpText>
			<helpKey>DocumentTypeJNDIFactoryClass</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Document Inherit Super User Policy</helpName>
			<helpText>This option indicates whether the Document Type / Document Type Group will inherit the Super User Policy of its parent Document Type Group.
  	      
  	      No partial inheritance is allowed on the Super User Policy. Document Types should have at least one Super User Policy set to Yes, whether through inheritance or directly. This ensures that if there is an unforeseen problem, then the EDoc can be cleared from routing using the Super User Service.</helpText>
			<helpKey>DocumentInheritSuperUserPolicy</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Document Super User Approve Policy</helpName>
			<helpText>This option indicates whether Super User Approve will be allowed on EDocs of this Document Type / Document Type Group.
  	      
  	      This check will occur before the check for authorization with the application's Post Processor.</helpText>
			<helpKey>DocumentSuperUserApprovePolicy</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Document Super User Cancel Policy</helpName>
			<helpText>This option indicates whether Super User Cancel will be allowed on EDocs of this Document Type / Document Type Group.</helpText>
			<helpKey>DocumentSuperUserCancelPolicy</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Document Super User Disapprove Policy</helpName>
			<helpText>This option indicates whether Super User Disapprove will be allowed on EDocs of this Document Type / Document Type Group.</helpText>
			<helpKey>DocumentSuperUserDisapprovePolicy</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Document Super User Route Level Approve Policy</helpName>
			<helpText>This option indicates whether Super User Route Level Approve will be allowed on EDocs of this Document Type / Document Type Group.</helpText>
			<helpKey>DocumentSuperUserRouteLevelApprovePolicy</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Document Disapprove Policy</helpName>
			<helpText>This option indicates the routing behavior when EDocs of this Document Type / Document Type Group are Disapproved:
  	      
  	       Cancel: The EDoc goes into the Disapproved state. Currently supported.
  	       Return to Initiator: A Complete request is sent to the EDoc initiator. NOT SUPPORTED.
  	       Last Approver: A Complete request is sent to the last approver of this EDoc. NOT SUPPORTED.
  	       Inherited: Inherits the Disapprove Policy of the parent Document Type Group. Currently supported.</helpText>
			<helpKey>DocumentDisapprovePolicy</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Document Default Approve Policy</helpName>
			<helpText>This option indicates whether EDocs of this Document Type can be put in the Approved state without any Approve Action Request.
  	      
  	      If this option is set to Yes, then it is equivalent to giving an EDoc of this type implicit approval.
  	      
  	      If this option is set to No, then an EDoc of this type must have at least one approve to be put in the Approved state.</helpText>
			<helpKey>DocumentDefaultApprovePolicy</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Document Pre Approve Policy</helpName>
			<helpText>This option indicates whether EDocs of this Document Type can have Approval Actions Taken on them before their corresponding Action Requests are generated or activated.</helpText>
			<helpKey>DocumentPreApprovePolicy</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Help Name</helpName>
			<helpText>Name of this help entry.</helpText>
			<helpKey>HelpName</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Help Key</helpName>
			<helpText>A unique textual idntifier for this help entry. Help key can't contain quotation mark '.</helpText>
			<helpKey>HelpKey</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Help Text</helpName>
			<helpText>The text for this help entry.</helpText>
			<helpKey>HelpText</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Annotation</helpName>
			<helpText>Notes to be included in the Route Header.</helpText>
			<helpKey>Annotation</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Description</helpName>
			<helpText>Description of the document.</helpText>
			<helpKey>Description</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Entry Priority</helpName>
			<helpText>The priority determines the order this document will be routed within the same route type. The lower the number the greater the priority. The highest priority you can assign is 1.</helpText>
			<helpKey>EntryPriority</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>From Date/To Date</helpName>
			<helpText>The business rule you are defining will be effective during the period of From Date and To Date, inclusive. To Date must be after From Date, and it must be on or after today's date. Both Dates may be left blank. In that case, From Date will be today's date and the To Date will be 100 years from today's date.</helpText>
			<helpKey>FromDateToDate</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Active</helpName>
			<helpText>Business rules that are active are used by the workflow engine to route documents. When a business rule does not apply anymore, it can not be deleted, but can be made inactive.</helpText>
			<helpKey>ActiveIndicator</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Initiator Must Route</helpName>
			<helpText>Initiator Must Route.</helpText>
			<helpKey>InitiatorMustRoute</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Route Template Route Level Name</helpName>
			<helpText>The name of the Route Level for this entry in the Route Template for this Document Type or Document Type Group.
                    
                    Enter text that describes the business function involved.
                    
                    The entries in the Route Template are run in ascending order by their numeric Route Level: 1, 2, 3, ... Entries with the same Route Level (but different Route Types) are run concurrently.
                    
                    Two additional entries are required:
                    
                    -1   Exception Route Level
                    0   AdHoc Route Level
                    
                    They are included automatically when a parent Document Type Group is named.</helpText>
			<helpKey>RouteTemplateRouteLevelName</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Route Template Final Approver Route Type</helpName>
			<helpText>This option indicates that this Route Level will generate the last approval request in the Route Template entry for this Document Type / Document Type Group. If any subsequent Route Level in this template does generate an approval request, then the EDoc will be put in Exception Routing.
              
              This option cannot be selected for the Exception or Ad Hoc Route Levels.</helpText>
			<helpKey>RouteTemplateFinalApproverRouteType</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Route Template Mandatory Type</helpName>
			<helpText>If Yes is selected, then this Route Level must generate an Action Request. Otherwise, this EDoc will be put into Exception Routing.
              
              If No is selected, then normal routing will proceed if no Action Requests are generated in this Route Level for this EDoc.</helpText>
			<helpKey>RouteTemplateMandatoryType</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Route Template Exception Workgroup</helpName>
			<helpText>The Exception Workgroup for this entry in the Route Template of this Document Type or Document Type Group. This Workgroup will respond to any Exception routing.
              
              Enter a valid Workgroup name or choose one in the QuickFinder.
              
              The entries in the Route Template are run in ascending order by their numeric Route Level: 1, 2, 3, ... Entries with the same Route Level (but different Route Types) are run concurrently.
              
              Two additional entries are required:
              
              -1   Exception Route Level
              0   AdHoc Route Level
              
              They are included automatically when a parent Document Type Group is named.</helpText>
			<helpKey>RouteTemplateExceptionWorkgroup</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Route Queue Id</helpName>
			<helpText>The Route Queue Id is the unique id number that identifies a particular queue entry.</helpText>
			<helpKey>RouteQueueId</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Queue Priority</helpName>
			<helpText>This is the priority of the Route Queue entry.</helpText>
			<helpKey>RouteQueuePriority</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Queue Status</helpName>
			<helpText>The Queue Status will be Exception, Queued, or Routing.</helpText>
			<helpKey>RouteQueueStatus</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Queue Date</helpName>
			<helpText>The Queue Date is the date that a Route Queue entry was entered into the queue.</helpText>
			<helpKey>RouteQueueDate</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Retry Count</helpName>
			<helpText>The Retry Count refers to the number of attempts made to route the Route Queue entry. There may be a maximum number of times that attempts will be made such as four attempts.</helpText>
			<helpKey>RouteQueueRetryCount</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>IP Number</helpName>
			<helpText>The IP Number is a network number associated with a certain computer. Route Queue entries have an IP number to guard against one computer system routing entries attributed to another computer system.</helpText>
			<helpKey>RouteQueueIPNumber</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Processor Class Name</helpName>
			<helpText>The Processor Class Name is ...</helpText>
			<helpKey>RouteQueueProcessorClassName</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Processor Value</helpName>
			<helpText>The Processor Value is ...</helpText>
			<helpKey>RouteQueueProcessorValue</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Document Type Name</helpName>
			<helpText>The name of the Document Type.</helpText>
			<helpKey>DocumentTypeName</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Document Type Label</helpName>
			<helpText>The display label of the Document Type. This text is the label displayed in any reference to the Document Type in other documents or applications.</helpText>
			<helpKey>DocumentTypeLabel</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Parent Document Type Name</helpName>
			<helpText>Name of the parent Document Type for this Document Type. Properties of the parent will be automatically inherited. Parent Document Type can be selected from the QuickFinder.</helpText>
			<helpKey>ParentDocumentTypeName</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Super User Workgroup</helpName>
			<helpText>A workgroup whose members are super users for this document/document type.</helpText>
			<helpKey>SuperUserWorkgroup</helpKey>
		</helpEntry>	
		
		<helpEntry>
			<helpName>Blanket Approve Workgroup</helpName>
			<helpText>A workgroup whose memebers can blanket approve the document/document type.</helpText>
			<helpKey>BlanketApproveWorkgroup</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Post Processor Name</helpName>
			<helpText>The name of the "Post Processor" class provided for the Document Type. This processor class responds to each change of Workflow routing status as appropriate for the Document Type. It also completes any post-processing activities after the document has final approval.</helpText>
			<helpKey>PostProcessorName</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Doc Handler URL</helpName>
			<helpText>The URL of the "Doc Handler" application provided for the Document Type. This application displays the document contents in the format appropriate for this Document Type, including any action buttons for the current context. It is also responsible for authorizing access to the document display.</helpText>
			<helpKey>DocHandlerURL</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Document Type JNDI URL</helpName>
			<helpText>The URL of the JNDI service for the Document Type. Together with the JNDI Factory Class, it locates the applications which support this Document Type. This field is used only if the applications are not coresident with Workflow, and is normally left blank.</helpText>
			<helpKey>DocumentTypeJNDIURL</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Advanced Document Search URL</helpName>
			<helpText>A URL where a user can specify more detailed criteria to search for a document.</helpText>
			<helpKey>AdvancedDocumentSearchURL</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Custom Action List Attribute Class Name</helpName>
			<helpText>This is the fully-qualified name of a java class that contains information used to customize an action list. In order to customize an action list, create a java class that implements the CustomActionListAttribute interface. The fully-qualified name of this class will be entered into the Document Type(s) for the documents that will display in the action list with the customization.</helpText>
			<helpKey>CustomActionListAttributeClassName</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Custom Email Attribute Class Name</helpName>
			<helpText>This is the fully-qualified name of a java class that contains information used to customize an action list e-mail notification.  In order to customize an action list e-mail, create a java class that implements the CustomEmailAttribute interface. The fully-qualified name of this class will be entered into the Document Type(s) for the documents that will display in the action lists that are sending out the customized e-mail notifications.</helpText>
			<helpKey>CustomEmailAttributeClassName</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Custom Note Attribute Class Name</helpName>
			<helpText>This is the fully-qualified name of a java class that contains information used to customize a note attached to a workflow document. In order to customize a document note, create a java class that implements the CustomNoteAttribute interface. The fully-qualified name of this class will be entered into the Document Type(s) for the documents that will have notes attached to them.</helpText>
			<helpKey>CustomNoteAttributeClassName</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Document Search Generator Attribute Class Name</helpName>
			<helpText>This is the fully-qualified name of a java class that contains information used to perform a customized document search. In order to customize search for a document type, create a java class that extends the StandardDocumentSearchGenerator class. The fully-qualified name of this class will be entered into the Document Type for the document that will use the search customization.</helpText>
			<helpKey>DocumentSearchGeneratorAttributeClassName</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Workflow Id</helpName>
			<helpText>This is a unique id given to each user of the workflow system.</helpText>
			<helpKey>WorkflowId</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Network Id</helpName>
			<helpText>This is a username used by Indiana University to identify its users.</helpText>
			<helpKey>NetworkId</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Employee Id</helpName>
			<helpText>This is an id used by Indiana University to identify its employees.</helpText>
			<helpKey>EmployeeId</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>UUID</helpName>
			<helpText>This is a unique identifier for Indiana University employees.</helpText>
			<helpKey>UUID</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Display Name</helpName>
			<helpText>This is the name of an individual consisting of the first name, possibly a middle initial or full middle name, and the last name.</helpText>
			<helpKey>DisplayName</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Given Name</helpName>
			<helpText>This is most often an individual's first name, but it may also be a different name by which the individual is known.</helpText>
			<helpKey>GivenName</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Last Name</helpName>
			<helpText>This is an individual's last name or surname.</helpText>
			<helpKey>LastName</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Email Address</helpName>
			<helpText>This is an address where an individual receives electronic mail.</helpText>
			<helpKey>EmailAddress</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Email Notification</helpName>
			<helpText>Action List automatically emails a reminder to you when you have eDocs in your Action List. You can change the timing of these emails as you prefer:
      		Immediate: send an email to you immediately when you get a new eDoc. This setting is the default.
      		Daily: send an email reminder to you each day if you have at least one eDoc to review.
      		Weekly: send an email reminder to you each week if you have at least one eDoc to review.
      		None: do not send any email reminders.</helpText>
			<helpKey>EmailNotification</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Action Requested</helpName>
			<helpText>The action required of the reviewer to take on this document.</helpText>
			<helpKey>ActionRequested</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Action Request ID</helpName>
			<helpText>An internal number that Workflow creates to uniquely identify an Action Request entry.</helpText>
			<helpKey>ActionRequestID</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Action Request Date</helpName>
			<helpText>The time and date on which the Action Request was made, formatted hh:mm:ss xm MM/DD/YYYY.</helpText>
			<helpKey>ActionRequestDate</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Delegator ID</helpName>
			<helpText>Network ID of the delegator.</helpText>
			<helpKey>DelegatorID</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Primary Delegate ID</helpName>
			<helpText>Network ID of the user who was designated as a primary delegate.</helpText>
			<helpKey>DelegateID</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Action Request Workgroup</helpName>
			<helpText>A workgroup that an action can be requested of.</helpText>
			<helpKey>ActionRequestWorkgroup</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Date Last Assigned</helpName>
			<helpText>The date on which the document/action request was assigned to a user. The date must be expressed in the MM/DD/YYYY format, e.g., 12/25/2005 for December 25, 2005.
          
          The date may also be supplied by clicking the adjacent Calendar icon and selecting a date from the monthly calendar; the value is then automatically loaded into the field.</helpText>
			<helpKey>ActionListDateLastAssigned</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Routing Priority</helpName>
			<helpText>An internal integer that Workflow assigns to reviewers to order routing within the same Route Level. The highest priority is 1.</helpText>
			<helpKey>RoutingPriority</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Responsibility</helpName>
			<helpText>The position of responsibility or role within an organization that receives a request for action. Requests are made to organizational roles, which are then subsequently directed to the individuals currently assigned to those roles.</helpText>
			<helpKey>Responsibility</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Responsibility ID</helpName>
			<helpText>An internal number that Workflow creates to uniquely identify an organizational responsibility or role.</helpText>
			<helpKey>ResponsibilityID</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Route Type Name</helpName>
			<helpText>The name of the Route Type.
         
         Enter brief text to describe this Route Type.</helpText>
			<helpKey>RouteTypeName</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Route Type Route Module Name</helpName>
			<helpText>The name of the Workflow Route Module used with the Route Type.
         
         Enter the name of a registered Route Module.</helpText>
			<helpKey>RouteTypeRouteModuleName</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Route Type Activation Policy</helpName>
			<helpText>The Activation Policy for the Route Module.
         
         Select one of the following policies:
         
         Sequence:  Route Type runs in sequence with others
         Parallel:  Route Type runs concurrently, in parallel with others.</helpText>
			<helpKey>RouteTypeActivationPolicy</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Route Type Label</helpName>
			<helpText>The display label for the Route Type.
         
         This text is the label displayed in any reference to this Route Type in other documents or applications.</helpText>
			<helpKey>RouteTypeLabel</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Route Type Route Module JNDI Factory Class</helpName>
			<helpText>The Factory Class of the JNDI service for the Route Type. Together with the JNDI URL, it locates the applications which support this Route Type.
         
         This field is used only if the applications are not coresident with Workflow, and is normally left blank.</helpText>
			<helpKey>RouteTypeRouteModuleJNDIFactoryClass</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Route Type Route Module JNDI URL</helpName>
			<helpText>The URL of the JNDI service for the Route Type. Together with the JNDI Factory Class, it locates the applications which support this Route Type.
         
         This field is used only if the applications are not coresident with Workflow, and is normally left blank.</helpText>
			<helpKey>RouteTypeRouteModuleJNDIURL</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Route Type Active Indicator</helpName>
			<helpText>Active / Inactive choice to enable the Route Type.
         
         Check Yes only if the Route Type should be enabled.</helpText>
			<helpKey>RouteTypeActiveIndicator</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Route Type Description</helpName>
			<helpText>Text that describes the purpose and function of the Route Type. The description documents the business rules exercised by this Route Type. It is free-form text provided by the Route Type authors.</helpText>
			<helpKey>RouteTypeDescription</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Route Method</helpName>
			<helpText>The Route Method of a route level specifies either a route module or route template.
         
         Select either a route module from the pulldown list of existing route modules or use the magnifying glass icon to search for a route template.</helpText>
			<helpKey>RouteMethod</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Route Template Route Level</helpName>
			<helpText>The numeric Route Level for this entry in the Route Template of this Document Type or Document Type Group.
               
               Enter a positive integer indicating the order in which this entry is run.
               
               The entries in the Route Template are run in ascending order by their numeric Route Level: 1, 2, 3, ... Entries with the same Route Level (but different Route Types) are run concurrently.
               
               Two additional entries are required:
               
               -1   Exception Route Level
               0   AdHoc Route Level
               
               They are included automatically when a parent Document Type Group is named.</helpText>
			<helpKey>RouteTemplateRouteLevel</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Workgroup Member</helpName>
			<helpText>A person who is a member of this workgroup.</helpText>
			<helpKey>WorkgroupMember</helpKey>
		</helpEntry>
		
		<helpEntry>
			<helpName>Workgroup Description</helpName>
			<helpText>A description of the workgroup.</helpText>
			<helpKey>WorkgroupDescription</helpKey>
		</helpEntry>
	
	</helpEntries>
</data>