add in help files from philip@ktdms.com.

Might want to move to non-space-named files. git-svn-id: https://kt-dms.svn.sourceforge.net/svnroot/kt-dms/trunk@5336 c91229c3-7414-0410-bfa2-8a42b809f60b

add in help files from philip@ktdms.com.
Might want to move to non-space-named files. git-svn-id: https://kt-dms.svn.sourceforge.net/svnroot/kt-dms/trunk@5336 c91229c3-7414-0410-bfa2-8a42b809f60b
bshuttle
1 parent 2af87afd
Showing 45 changed files with 560 additions and 155 deletions
kthelp/ktcore/EN/admin/admin-mode.html
kthelp/ktcore/EN/admin/archived documents.html
kthelp/ktcore/EN/admin/authentication sources.html
kthelp/ktcore/EN/admin/automatic workflows.html
kthelp/ktcore/EN/admin/control units.html
kthelp/ktcore/EN/admin/deleted documents.html
kthelp/ktcore/EN/admin/document checkout.html
kthelp/ktcore/EN/admin/document fieldsets.html
kthelp/ktcore/EN/admin/document types.html
kthelp/ktcore/EN/admin/dynamic conditions.html
kthelp/ktcore/EN/admin/help administration.html
kthelp/ktcore/EN/admin/link type management.html
kthelp/ktcore/EN/admin/manage groups.html
kthelp/ktcore/EN/admin/manage permissions.html
kthelp/ktcore/EN/admin/manage plugins.html
kthelp/ktcore/EN/admin/manage users.html
kthelp/ktcore/EN/admin/role administration.html
kthelp/ktcore/EN/admin/saved searches.html
kthelp/ktcore/EN/admin/system information.html
kthelp/ktcore/EN/admin/workflow.html
 <html>
-<head><title>Administrator Mode</title></head>
+<head>
+   <title>Administrator Mode</title>
+</head>
+
+
 <body>
-<h2>Administrator Mode</h2>
  
-<p class="descriptiveText">Administrator mode allows for users who have system administrator
-rights, or unit administrators within their unit, to see folders and
-documents in the browse mode that they otherwise would not see due to
-permissions.</p>
+<h2>Administrator Mode</h2>
+<p>
+There are instances where systems administrators may be denied access to certain documents in the repository - management level documents containing classified information, for example.
+</p>
+<p>
+However, because problems with these documents in the repository will also need to be fixed, administrators must be granted a way of overriding the controls in an audited manner that protects this information. 
+</p><p>
+Enabling Administrator mode allows system and unit administrators to view and manage all documents in the system, including those documents where they are normally denied access. 
+</p>
 </body>
-</html>
 \ No newline at end of file
+</html>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+   <title>Archived Documents</title>
+</head>
+<body>
+<h2>Archived Documents</h2>
+This page lets you restores a document that has previously been archived.
+<br></br><br></br>
+Note: By default, documents are restored to the folder location where they were originally archived. If that folder no longer exists on the system, the document is restored to the root directory in the repository.
+</body>
+</html>
+
+
+
+
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+   <title>Authentication Sources</title>
+</head>
+
+
+<body>
+<h2>Authentication Sources</h2>
+KnowledgeTree allows you to control access to the DMS for the users and groups in its database, using KnowledgeTree's own default authentication method - Database Authentication.
+<br></br><br></br>
+However, KnowledgeTree also allows you to add external authentication sources where your organization maintains its own list of users and groups that require controlled access to the DMS.
+<br></br><br></br>
+You can also modify or delete the details of external authentication sources and authentication provider information.
+<br></br><br></br>
+Note: You need to add the credentials of each user to KnowledgeTree (see Managing Users and Managing Groups) to allow the system to retrieve their details, even if you're using an external authentication source. 
+
+For more detail, please refer to the Administrator Manual.
+
+</body>
+</html>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+   <title>Automatic workflows</title>
+</head>
+<body>
+<h2>Automatic workflows</h2>
+
+<p>
+Automatic workflows allow you to define the conditions for automatically assigning a
+specific workflow to a document.</p><p>
+Workflow assignment may occur on a per folder basis or on a per document type
+basis. Only one mode may be selected for a particular system.</p>
+
+</body>
+</html>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+   <title>Unit Administration</title>
+</head>
+<body>
+<h2>Unit Administration</h2>
+<p>KnowledgeTree provides Units as a means of organizing groups. Units may be used to model your organization's business units.</p>
+<p>
+<strong>Note:</strong> By default, each time a new Unit is created on the system, a Unit folder is created in the Organization (root) directory.</p> 
+</body>
+</html>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+   <title>Deleted Documents</title>
+</head>
+
+
+<body>
+<h2>Deleted Documents</h2>
+<p>
+This page allows you to restore or expunge documents that have been deleted in the KnowledgeTree repository.
+</p><p>
+<strong>Note:</strong> Expunging saves disk space by permanently deleting documents that are no longer useful or required.
+</p><p>
+<strong>Note:</strong> By default, documents are restored to the folder location where they were originally deleted. If that folder no longer exists on the system, the document is restored to the root directory in the repository. 
+</p>
+</body>
+</html>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+
+<html>
+<head>
+   <title>Document Checkout</title>
+</head>
+
+
+<body>
+<h2>Document Checkout</h2>
+<p>
+This page lets you override the currently checked out status of a document and forces the document to be checked back in to the repository.
+</p><p>
+Forced check ins are used where a checked out document is urgently required back in the repository so that another user can check it out.
+</p><p>
+<strong>Note:</strong> The document is checked back in to the repository without saving any changes that may have been made to it while it was checked out.
+<p>
+</body>
+</html>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+   <title>Document Fieldsets</title>
+</head>
+<body>
+<h2>Document Fieldsets</h2>
+<p>
+Document Fieldsets allow you to associate custom metadata with documents in the
+repository.
+</p>
+<p>
+There are two types of document fieldsets:
+<ul>
+<li><strong>Normal</strong> - users are allowed to edit normal fieldsets only if they have been
+   associated with the document type that is being edited.</li>
+<li><strong>Generic</strong> - users may add and edit generic fieldsets to any document type in
+   KnowledgeTree.</li>
+</ul>
+</p>
+<p>   
+<strong>Note:</strong> KnowledgeTree auto-generates an editable system name (namespace) for every
+fieldset. Plug-ins use this namespace to call the fieldset, and to control how the fieldset works.
+For more information on developing Plug-ins for KnowledgeTree, see the KnowledgeTree Wiki
+at <a href ="http://support.ktdms.com/confluence/">http://support.ktdms.com/confluence/</a>
+</p>
+
+<h2>Document Fields</h2>
+<p>
+KnowledgeTree uses fields to group sets of related information into predefined
+fieldsets. The custom fieldsets are then associated with specific document types, to
+define the information (metadata) that should be included on documents of that
+type.</p>
+<p>
+There are three classes of custom fields in KnowledgeTree:
+<ul>
+<li><strong>Normal</strong> - stores text metadata, such as invoice code</li>
+<li><strong>Lookup</strong> - used to allow users to select from a predefined set of options</li>
+<li><strong>Tree</strong> - used to allow users to select a metadata value by browsing a tree structure</li>
+</ul>
+</p>
+<h3>Managing Tree Fields</h3>
+
+<p>
+Trees can have multiple sub-categories and levels. You need to add sub-categories at
+each level in order to organize the options into a 'tree'.</p>
+<p>
+The top level of the tree is called the root. The root, which holds all the top level
+items, is not shown to the user, but it provides a single 'parent' to the top level items.</p>
+<p>
+For example, let's say you create a tree of the countries in the world. In this case, the
+actual countries would be keywords - e.g. South Africa, England, Singapore, etc. And
+the highest group of categories (the top level or 'root') would be continents - e.g.
+Africa, Europe, Asia etc. The sub-categories, which fall below the top level 'continents'
+could be 'regions' - e.g. Sub-Saharan Africa, Western Europe, South East Asia.</p><p>
+KnowledgeTree allows you to create more sophisticated tree fields on the Edit
+Lookup Tree page.</p>
+
+</body>
+</html>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+   <title>Archived Documents</title>
+</head>
+<body>
+<h2>Archived Documents</h2>
+<p>
+Document Types are used to group together documents that have a similar function.
+They also allow you to associate custom fieldsets for specific information that must be
+included with a particular document type.
+</p>
+Let's say you create a document type called 'Invoice', and you want to ensure that
+all documents of the type 'Invoice' contain the following fields: invoice number,
+customer name, delivery address. You can group these fields in a fieldset called
+Invoice Details, for example. And then you may want to create another fieldset for
+the monetary values in the invoice, which you could call 'Amount'. The fieldset
+Amount may include the following fields: Nett Item Value, Tax, Discount, and
+Total Due.
+<p>
+There are two ways you can configure the document type - Invoice - and the
+fieldsets you want to associate with this document type.
+</p>
+
+<p>
+1. You can first create the document type in the Document Types section, and then
+create one or more custom fieldsets in the Document Fieldsets section. The
+collection of fieldsets you define are automatically listed in the Document Type
+editing page. Having created the fieldset(s), you need to edit the document type you
+created in order to to add (associate) the fieldset(s) you want to use in this document
+type.
+</p>
+<p>
+2. Alternatively, you can first create a set of custom fieldsets in the Document
+Fieldsets section, and then create the document type. Having added the document
+type, KnowledgeTree automatically opens the Document Type editing page, where
+you can select the fieldsets out of the collection of fieldsets you have pre-defined in
+Document Fieldsets, and which now display on the Document Type editing page.
+</p>
+<p>
+<b>Note:</b> Document types cannot be deleted in KnowledgeTree; they can only be disabled. Since a document type may be associated with a large amount of documents, deleting a document type may cause the loss of required metadata.
+</p>
+</body>
+</html>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+   <title>Dynamic Conditions</title>
+</head>
+<body>
+<h2>Dynamic Conditions</h2>
+<p>
+You use KnowledgeTree's Dynamic Conditions feature to set up the rules that will determine the permissions that may be applied to documents within a folder.These rules may be applied to a document's metadata, to its contents, or to its transactional information. Dynamic Conditions are applied on a per folder basis, and may be set up in the folder's Folder permissions page.
+</p><p>
+Having created a new dynamic condition, you need to assign it to a folder. You can also unassign dynamic conditions when they're no longer useful for the folder. </p><p>
+
+<strong>Note:</strong> Dynamic Conditions are configured in the same way as Saved Searches.
+</p><p>
+<strong>Note:</strong> Having defined a dynamic condition, you cannot delete it because that may change permission  assignments.
+<p>
+</body>
+</html>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+   <title>Help Administration</title>
+</head>
+<body>
+<h2>Help Administration</h2>
+
+<p>
+The KnowledgeTree Document Management System contains several built in system
+help files.
+</p>
+<p>
+You can open a help file anywhere in the system by clicking this help page icon:(?)
+</p>
+<p>
+The help file that displays is relevant to the location of the icon. For example, in the
+image below, you click the help page icon on the right of the page to view help for
+Browse Documents.
+</p>
+</body>
+</html>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+   <title>Link Type Management</title>
+</head>
+<body>
+<h2>Link Type Management</h2>
+
+Document links allow users to establish associations between documents in the
+repository. When creating a document link, you should specify the type of relationship that the
+link implies between the linked documents - i.e. 'associated with', or 'duplicated by'.
+
+</body>
+</html>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+   <title>Manage Groups</title>
+</head>
+<body>
+<h2>Manage Groups</h2>
+<p>
+Only a <b>User</b> that has been assigned to a <b>Group</b> is allowed to access the KnowledgeTree Document Management System.
+</p>
+<strong>Note:</strong> Groups can be members of other groups, and can have other groups as members.  These memberships pass the permissions set on to the parent group to user members of the member groups, possibly along a few chains.
+
+<h3>Example:</h3>
+
+<p>Let's say you create a new Group called Testers. Having created the Testers Group, you must assign the it to a Unit. You can name the Unit 'Quality Assurance'. So, the group named Testers is part of the unit Quality Assurance.
+</p>
+<p> 
+Group: Testers<br>
+Unit: Quality Assurance
+</p>
+</body>
+</html>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+   <title>Manage Permissions</title>
+</head>
+<body>
+<h2>Manage Permissions</h2>
+KnowledgeTree 3 provides several default (core) permissions - <b>Read</b>, Write</b>, <b>Add Folder</b>, <b>Manage Permissions</b>, <b>Delete</b> - but it also allows you to create your own permissions.
+<br></br><br></br>
+You can create permissions for controlling user and group access for plug-ins, or create permissions to use as Guard Permissions for workflow transitions.
+</body>
+</html>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+   <title>Manage plugins</title>
+</head>
+<body>
+<h2>Manage plugins</h2>
+<p>
+Plug-ins allow you to add new features to your implementation of the KnowledgeTree Document Management System.
+</p>
+ 
+<p>
+<strong>Note:</strong> Go to <a href="http://support.ktdms.com/confluence/x/xg">our Wiki </a> to view a list of the plug-ins that have been developed by the KnowledgeTree community. 
+</p>
+<p>
+You use <strong>Manage Plugins</strong> to:
+</p>
+<ul> 
+<li>re-read the plug-ins list for new plug-ins that you copy to the plug-in directory</li>
+<li>enable plug-ins</li>
+<li>disable plug-ins</li>
+</ul>
+</body>
+</html>
+
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+   <title>Manage Users</title>
+</head>
+<body>
+<h2>Manage Users</h2>
+<p>
+You use the <b>Manage Users</b> section of <b>Users</b> and <b>Groups</b> to add or remove users from the KnowledgeTree Document Management System. You can also search for user details, or view a list of all the users that exist in the system.
+</p>
+<p>
+The system uses the information you specified when you added the user or group, to retrieve their details from the authentication source. This allows verification of the user or group's login rights, and of the permissions they have for accessing information in the repository. 
+</p>
+
+</body>
+</html>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+   <title>Role Administration</title>
+</head>
+<body>
+<h2>Role Administration</h2>
+Roles include, for example, a document creator, a document reviewer, a document publisher, or writer, editor, developer, secretary, and so on.
+<br></br><br></br>
+Workflow actions - e.g. review, or publish - are typically assigned to a specific role. The role is granted permissions for working with the document, based on the type of tasks their role performs - e.g. reviewers need read and write permissions.
+<br></br><br></br>
+User Groups are allocated to Roles on a per-directory basis, and are inherited from the root folder of the DMS. 
+</body>
+</html>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+   <title>Saved Search</title>
+</head>
+<body>
+<h2>Saved Search</h2>
+KnowledgeTree's Saved Search feature allows you to pre-save useful, advanced searches, in order to save time on commonly used searches.
+</body>
+</html>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html>
+<head>
+   <title>System information</title>
+</head>
+<body>
+<h2>System information</h2>
+
+<p>
+KnowledgeTree provides a Support and System Information page in the Miscellaneous section of DMS Administration, which helps you identify and fix problems with your system.The Support and System Information page displays the output of a php_info command in a scrollable window. You may be asked to copy and send this information to the KnowledgeTree support staff if you require assistance with your problem.
+</p>
+<p>
+Clicking the Download PHP Information link on this page automatically runs <strong>phpinfo</strong> and prints the results to the KnowledgeTree Document Management System.
+</p>
+<p>
+<strong>Note:</strong> If you believe that distributing this information represents a security risk for your organization, we recommend that you sanitize the output before copying and sending it. Alternatively, please enquire about sending the information directly to the developer dealing with your issue. 
+<p>
+ 
+<p>
+You can also click the direct link to the KnowledgeTree Issue Tracker, where you can:
+</p>
+<ul> 
+<li>report bugs</li> 
+<li>view known issues</li> 
+<li>find out whether fixes have already been applied for your problem in a new version of KnowledgeTree</li>
+</ul>
+</body>
+</html>
+<html>
+<head>
+<title>Workflow</title>
+</head>
+
+<body>
+
+<h2>Workflow</h2>
+<p>Workflow may be defined as the process a document goes 
+through to serve its purpose in an organization. For example, an invoice is 
+created, distributed, then paid; a report may be created, reviewed, edited, and 
+distributed. </p>
+<p>Some documents, such as tenders, may have complex 
+workflows, requiring input from several people within and outside of your 
+organization before the work is complete. </p>
+<p>The KnowledgeTree administrator defines and manages 
+document workflows in DMS administration, and any KnowledgeTree user may be 
+involved in a document workflow. </p>
+<p>Workflows in KnowledgeTree involve three key areas:</p>
+<ol>
+	<li>Assigning workflows</li>
+	<li>States and Transitions</li>
+	<li>Workflow effects (Actions)</li>
+</ol>
+<h3><a name="assign"></a>Assigning workflows</h3>
+<p >A document in the repository can have 
+only one workflow attached to it at any given time. By default, workflows are 
+not automatically attached to new documents when theyre added to the 
+repository. However, the administrator may configure the system to assign 
+workflows when new documents are created, or to assign workflows only to 
+specific documents. Users are also allowed to select and assign workflows to the 
+documents they are working with  provided they have the permissions to do so. 
+</p>
+<h3><a name="states"></a>States and Transitions</h3>
+<p >Workflows consist of states and 
+transitions. A state may be defined as a stage in a documents lifecycle, such 
+as billed or draft. Each workflow has a starting state, which is the initial 
+state for any document in a workflow.</p>
+<p >Transitions, which may be defined as the 
+way in which documents move between states, are an essential part of the 
+workflow. Each state can have one or more transitions, depending on how the 
+administrator has created the workflow.</p>
+<p >Transitions point to the next step in 
+the workflow, such as send to client or review, which effectively changes the 
+state of the document. Transitions represent the actions that may be performed 
+on a document. For example, an invoice starts in the generated state; then it is 
+sent to client, before it is marked as billed.  Transitions are said to be 
+guarded  not all users are allowed to access them. In a publication workflow 
+for example, only users with the role reviewer would be allowed to review a 
+document, and to move it from draft to published.</p>
+<h3><a name="effects"></a>Workflow effects (Actions)</h3>
+<p >Workflows are more than just states and 
+transitions. Users and administrators use workflows to restrict, deny or grant 
+access to documents in the repository, based on the documents position in the 
+workflow. For example, a state can restrict both actions and permissions on a 
+document  only reviewers may be allowed to discuss draft documents for 
+instance, while clients will be disallowed from viewing unbilled invoices, and 
+published documents will be prevented from being checked in or checked out of 
+the repository. Additionally, users in specified Roles or Groups can be notified 
+when a document reaches a certain state in a workflow. These notifications 
+display on the Dashboard and are emailed to users with specified email accounts.</p>
+
+</body>
+</html>
@@ -5,139 +5,15 @@
 <body>
  
 <h2>Browse Documents</h2>
-<p>You use the Browse Documents section to navigate the 
-repository  either by folder, by document type, or by lookup value  the 
-default is browse by folder.</p>
-<h3>Folder Actions</h3>
-<p>You use the Folder Actions buttons to:</p>
-<ul>
-	<li>Add new folders.</li>
-	<li>Add multiple documents to the repository at once  
-	either by uploading a zip file (bulk import), or by specifying a server path 
-	(bulk upload) to a location to upload all the documents and files at that 
-	location to the repository.</li>
-</ul>
-<h4>Subscriptions</h4>
-<p>Subscribing to a folder allows you to receive notifications 
-that tell you when that folder is modified. An email notification is sent to you 
-if you have provided your email address when subscribing. Your alerts and 
-notifications are also displayed on the Dashboard. </p>
-<h4>Search</h4>
-<p>KnowledgeTree provides three versatile search options  
-simple (quick) search, advanced search, and saved searches. Search is 
-permissions-based, so the system only returns items that the logged in user is 
-allowed to access. </p>
-<p> </p>
-<h5>Simple (quick) search</h5>
-<p>Specify a search term to search all text - including 
-document metadata and the contents of the following file types (if your 
-administrator has configured these options): MS Word, MS Excel, MS PowerPoint, 
-Adobe PDF, and Plain Text files.</p>
-<h5>Advanced Search</h5>
-<p>Define criteria to launch a detailed Boolean search of the 
-repository. This search allows more detailed search requests (using document 
-metadata). For example, you can search for all MS Excel documents containing the 
-word 'Invoice'.</p>
-<h5>Saved search</h5>
-<p>The saved search function allows KnowledgeTree 
-administrators to pre-save useful advanced searches. For example, you may want 
-to save a search that shows all documents in a completed state of a workflow. 
-Saved searches save time on commonly used searches. </p>
-<h3>Document Actions</h3>
-<p>The Document Detail screen summarizes key information about 
-the currently selected document. The Document Actions pane on the left of the 
-screen provides a set of buttons for working with the document. </p>
-<h4>Download</h4>
-<p>You can download a file to open it, or to save it, without 
-checking it out of the repository. </p>
-<h4>Check-in / Check-out</h4>
-<p>Check out a document to temporarily remove it from the 
-repository while you update it. While its checked out, other users cant check 
-it out to make changes. The version is incremented when the document is checked 
-in  a metadata version snapshot is created.</p>
-<p>An administrator can override the checked out status of a 
-document if the user has failed to check-in a document. In this case, the user 
-needs to check-out the document again and redo their changes.</p>
-<h4>Metadata</h4>
-<p>Metadata is the information about a document that describes 
-how, and when, and by whom, a particular set of data was collected, and how the 
-data is formatted.</p>
-<p>KnowledgeTree groups metadata fields into fieldsets. A 
-fieldset is a set of related information, which can be attached to a 
-document.  For example, lets say we specify a Project fieldset as follows:</p>
-<p><b>Project</b></p>
+
 <ul>
-	<li>Project Name</li>
-	<li>Division</li>
-	<li>Cost Estimate</li>
-	<li>Implementation Status</li>
+<li><a href="user/portlets/Document Actions.html"> Document Actions</a></li>
+<li><a href="user/portlets/Folder Actions.html">Folder Actions</a></li>
+<li><a href="user/portlets/Browse By.html">Browse By</a></li>
+<li><a href="user/portlets/Search.html">Search</a></li>
+<li><a href="user/portlets/Subscriptions.html">Subscriptions</a></li>
 </ul>
-<p>This project fieldset can be attached to any document type 
-that relates to a project; and all members of that fieldset (i.e. project name, 
-division, cost estimate, implementation status) would apply. A plug-in could be 
-written, which uses the information in the Project fieldset, to provide 
-reporting information on a project level, or on a project-based hierarchy of 
-documents.</p>
-<h4>Delete</h4>
-<p>Deleted documents remain in the repository (in DMS 
-Administration) until the KnowledgeTree administrator either expunges them or 
-restores them. </p>
-<p>See Administration  Document Storage  Restore or Expunge 
-Deleted Documents</p>
-<h4>Move</h4>
-<p>Only users with the required permissions for a folder are 
-allowed to move an item to another location in the repository. </p>
-<h4>Transaction History</h4>
-<p>This feature provides a record of all transactions 
-performed on the document: create date, uploads, downloads, check-out, check-in 
-and the previous deletion of the document if it has been restored.</p>
-<h4>Version History</h4>
-<p>This feature provides a record of all past and current 
-versions of a document. A new document version is created whenever a document is 
-checked-out then subsequently checked-in again. The version history feature 
-allows you to download older documents and compare them with more recent 
-versions.</p>
-<h4>Links</h4>
-<p >Document links allow you to establish 
-associations between documents in the repository. Your KnowledgeTree 
-administrator needs to create the Document Link Types that you use to link 
-documents. When creating a document link, the administrator specifies the type 
-of relationship that the link implies between the 
-linked documents  i.e. associated with, or duplicated by. </p>
-<h4>Version Control</h4>
-<p>KnowledgeTree has powerful document version control 
-features, which ensure that the editing and versioning of documents is done in a 
-controlled and auditable manner. Newly created documents are assigned as version 
-0.1. The first time you check it out for editing and then check it back in 
-again, the version number increments to version 1. Each subsequent check out / 
-check in causes the version number to increment by 1. </p>
-<p>A document may only be checked out for editing by a single 
-user at a time. When a document is checked back in, you need to specify the 
-changes you made.</p>
-<p>Users and groups who have read or write access to a 
-document are allowed to download it for viewing only  you can choose to open 
-the document in your Web browser or save it to your local computer.  You can 
-view a version history of all changes to the document, and you can download 
-previous versions for comparison. </p>
-<p>Any changes you make to the document you downloaded won't 
-display in the version in the repository unless you check out the document, and 
-then check it back into the repository with your changes.</p>
-<p>Any user that logs in to KnowledgeTree can view the list of 
-documents they have checked out (if any) in the Checked-out documents section of 
-the Dashboard. </p>
-<h4>Permissions</h4>
-<p >Permissions in KnowledgeTree are 
-folder-based  permissions that have been allocated for a specific folder apply 
-to all the documents in that folder.</p>
-<p >There are four default types of 
-permissions: Read, Write, Add Folder, and Manage Permissions. </p>
-<p >Users that have only Read permission on 
-a document can view the document and its metadata, but are not allowed to change 
-it. Users that have Read and Write permissions are allowed to change the 
-contents of a document, as well as its metadata. </p>
-<p >Users with the Add Folder permission are 
-allowed to create and edit sub-folders within their group folder. </p>
-<p >Users with the Manage Permissions 
-permission are able to edit permissions within their group folder.</p>
+
+
 </body>
 </html>
@@ -3,18 +3,27 @@
    <title>Dashboard</title>
 </head>
 <body>
+<h2>Dashboard</h2>
+The Dashboard displays items relevant to the logged in user, such as a list of the documents you have checked out, and items requiring your attention.
  
  
-<h2>Dashboard</h2>
-<p>The Dashboard displays information relevant to the logged 
-in user. It lists the documents you have checked out, and it displays items 
-requiring your attention, which may include:</p>
-<ul>
-	<li>Pending documents  documents that need to be approved</li>
-	<li>Subscription alerts and Notifications  documents 
-	youre subscribed to that have been added, deleted, or modified. This 
-	section also lists document requiring your input in the workflow cycle.</li>
+<h3>Items that require your attention</h3>
+
+<p>This section may include links to the following types of documents in the repository:</p>
+
+ <ul>
+<li>Pending documents - documents in an approval workflow that need to be approved</li>
+
+<li>Subscription alerts and Notifications - documents that you have subscribed to, and which have been added, deleted, or modified. This section also lists documents requiring your input in the workflow cycle.</li>
+
+<li>Orphaned folders - orphaned folders are sub folders of parent folders where you do not have the appropriate view or other permissions. You have permissions for accessing the orphan folder, but you are not allowed to access the parent folder. The dashboard provides a direct link to the orphaned folder in the repository. This is because you do not have permissions to navigate to the folder through its' parent folder.</li>
 </ul>
  
+<h3>Your Checked-out Documents</h3>
+
+This section lists the documents - if any - that the logged in user currently has checked out of the repository. You can click the link provided to go directly to the document in the repository, where you can download the document to view it, check the document back in, or cancel the document check out. 
+
+
+
 </body>
 </html>
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+<html>
+<head>
+
+	
+  <title>Workflow Overview</title>
+</head>
+
+<body>
+<h2>Workflow Overview</h2>
+<p>Workflow allows you to assign a series of steps to the document creation and
+management process.  For example, a "News" workflow might have documents which
+go from <strong>Research</strong> to <strong>Draft</strong> to <strong>Under Review</strong>
+to <strong>Published</strong>,
+with different people participating in the document's
+lifecycle at each stage. &nbsp;Naturally, not all documents have the
+same needs in terms of workflow: &nbsp;Invoices (which must be <span style="font-weight: bold;">drawn up</span>, <span style="font-weight: bold;">maile</span>d, and then marked as <span style="font-weight: bold;">paid</span>) are very different from Marketing documents.&nbsp;</p>
+<p>To facilitate this, KnowledgeTree&trade; allows the Administrator to
+define a number of different workflows, each of which can be applied to
+different documents as their organisation requires.</p>
+
+</body>
+</html>
@@ -914,7 +914,7 @@ class KTDocumentWorkflowAction extends KTDocumentAction {
     var $sName = 'ktcore.actions.document.workflow';
     var $_sShowPermission = "ktcore.permissions.write";
  
-    var $sHelpPage = 'ktcore/workflow.html';    
+    var $sHelpPage = 'ktcore/user/workflow.html';    
  
     function getDisplayName() {
         return _kt('Workflow');
@@ -56,7 +56,7 @@ class KTArchiveTitle extends TitleColumn {
 }
  
 class ArchivedDocumentsDispatcher extends KTAdminDispatcher {
-
+    var $sHelpPage = 'ktcore/admin/archived documents.html';
     function do_main () {
         $this->aBreadcrumbs[] = array('url' => $_SERVER['PHP_SELF'], 'name' => _kt('Archived Documents'));
  
@@ -33,7 +33,7 @@ require_once(KT_LIB_DIR . &quot;/search/savedsearch.inc.php&quot;);
  
 class KTConditionDispatcher extends KTAdminDispatcher {
     var $bAutomaticTransaction = true;
-
+    var $sHelpPage = 'ktcore/admin/dynamic conditions.html';
     function check() {
         $this->aBreadcrumbs[] = array('url' => $_SERVER['PHP_SELF'], 'name' => _kt('Conditions Management'));
         return true;
@@ -36,6 +36,7 @@ require_once(KT_LIB_DIR . &quot;/widgets/fieldWidgets.php&quot;);
 require_once(KT_LIB_DIR . "/templating/kt3template.inc.php");
  
 class DeletedDocumentsDispatcher extends KTAdminDispatcher {
+var $sHelpPage = 'ktcore/admin/deleted documents.html';
     function do_main () {
         $this->aBreadcrumbs[] = array('url' => $_SERVER['PHP_SELF'], 'name' => _kt('Deleted Documents'));
  
@@ -33,7 +33,7 @@ require_once(KT_LIB_DIR . &#39;/templating/kt3template.inc.php&#39;);
 require_once(KT_LIB_DIR . '/documentmanagement/DocumentTransaction.inc');
  
 class KTCheckoutAdminDispatcher extends KTAdminDispatcher {
-
+    var $sHelpPage = 'ktcore/admin/document checkout.html';
     function check() {
         return true;
     }
@@ -44,6 +44,7 @@ require_once(KT_LIB_DIR . &#39;/plugins/pluginutil.inc.php&#39;);
 class KTDocumentFieldDispatcher extends KTAdminDispatcher {
     var $bAutomaticTransaction = true;
 	var $bHaveConditional = null;
+    var $sHelpPage = 'ktcore/admin/document fieldsets.html';
  
     function check() {
         $this->aBreadcrumbs[] = array('url' => $_SERVER['PHP_SELF'], 'name' => _kt('Document Field Management'));
@@ -31,6 +31,7 @@ require_once(KT_LIB_DIR . &#39;/widgets/fieldWidgets.php&#39;);
 require_once(KT_LIB_DIR . '/documentmanagement/LinkType.inc');  // a horrible piece of work.
  
 class KTDocLinkAdminDispatcher extends KTAdminDispatcher {
+    var $sHelpPage = 'ktcore/admin/link type management.html';
  
    // Breadcrumbs base - added to in methods
     function check() {
@@ -38,6 +38,8 @@ require_once(KT_LIB_DIR . &quot;/templating/kt3template.inc.php&quot;);
  
 class KTDocumentTypeDispatcher extends KTAdminDispatcher {
  
+    var $sHelpPage = 'ktcore/admin/document types.html'; 
+
    // Breadcrumbs base - added to in methods
     function do_main () {
  
@@ -42,6 +42,7 @@ require_once(KT_LIB_DIR . &quot;/authentication/builtinauthenticationprovider.inc.php
  
 class KTGroupAdminDispatcher extends KTAdminDispatcher {
     // {{{ do_main
+    var $sHelpPage = 'ktcore/admin/manage groups.html';
     function do_main() {
 		$this->aBreadcrumbs[] = array('url' => $_SERVER['PHP_SELF'], 'name' => _kt('Group Management'));
 		$this->oPage->setBreadcrumbDetails(_kt('select a group'));
@@ -40,6 +40,7 @@ require_once(KT_LIB_DIR . &quot;/templating/kt3template.inc.php&quot;);
 class ManageConditionalDispatcher extends KTAdminDispatcher {
     var $ru;
  
+
     function ManageConditionalDispatcher() {
         parent::KTAdminDispatcher();
         global $default;
@@ -38,6 +38,9 @@ require_once(KT_LIB_DIR . &quot;/dispatcher.inc.php&quot;);
 require_once(KT_LIB_DIR . "/templating/kt3template.inc.php");
  
 class ManageHelpDispatcher extends KTAdminDispatcher {
+
+    var $sHelpPage = 'ktcore/admin/help administration.html';
+
     function do_main() {
         return $this->getData();
     }
@@ -33,6 +33,7 @@ require_once(KT_LIB_DIR . &quot;/templating/kt3template.inc.php&quot;);
 require_once(KT_LIB_DIR . "/widgets/fieldWidgets.php");
  
 class ManagePermissionsDispatcher extends KTAdminDispatcher {
+    var $sHelpPage = 'ktcore/admin/manage permissions.html'; 
     function do_main() {
         $this->oPage->setTitle(_kt('Manage Permissions'));
         $this->aBreadcrumbs[] = array('url' => $_SERVER['PHP_SELF'], 'name' => _kt('Manage Permissions'));
@@ -38,6 +38,7 @@ require_once(KT_LIB_DIR . &quot;/templating/kt3template.inc.php&quot;);
  
 class KTPluginDispatcher extends KTAdminDispatcher {
     var $bAutomaticTransaction = true;
+    var $sHelpPage = 'ktcore/admin/manage plugins.html';
  
     function check() {
         $this->aBreadcrumbs[] = array(
@@ -31,6 +31,8 @@ require_once(KT_LIB_DIR . &#39;/widgets/fieldWidgets.php&#39;);
 require_once(KT_LIB_DIR . "/roles/Role.inc");
  
 class RoleAdminDispatcher extends KTAdminDispatcher {
+
+    var $sHelpPage = 'ktcore/admin/role administration.html';
     function check() {
         return true;
     }
@@ -34,6 +34,7 @@ require_once(KT_LIB_DIR . &quot;/search/savedsearch.inc.php&quot;);
  
 class KTSavedSearchDispatcher extends KTAdminDispatcher {
     var $bAutomaticTransaction = true;
+    var $sHelpPage = 'ktcore/admin/saved searches.html';
  
     function check() {
         $this->aBreadcrumbs[] = array(
@@ -33,6 +33,7 @@ require_once(KT_LIB_DIR . &quot;/search/savedsearch.inc.php&quot;);
  
 class KTSupportDispatcher extends KTAdminDispatcher {
     var $bAutomaticTransaction = true;
+    var $sHelpPage = 'ktcore/admin/system information.html';
  
     function check() {
         $this->aBreadcrumbs[] = array('url' => $_SERVER['PHP_SELF'], 'name' => _kt('Support and System information'));
@@ -41,6 +41,7 @@ require_once(KT_LIB_DIR . &quot;/foldermanagement/folderutil.inc.php&quot;);
 require_once(KT_LIB_DIR . "/permissions/permissionutil.inc.php");
  
 class KTUnitAdminDispatcher extends KTAdminDispatcher {
+    var $sHelpPage = 'ktcore/admin/control units.html';
     var $bAutomaticTransaction = true;
  
     function check() {
@@ -42,6 +42,7 @@ require_once(KT_LIB_DIR . &quot;/authentication/authenticationproviderregistry.inc.ph
 require_once(KT_LIB_DIR . "/authentication/builtinauthenticationprovider.inc.php");
  
 class KTUserAdminDispatcher extends KTAdminDispatcher {
+var $sHelpPage = 'ktcore/admin/manage users.html';
     function do_main() {
         $this->aBreadcrumbs[] = array('url' => $_SERVER['PHP_SELF'], 'name' => _kt('User Management'));
         $this->oPage->setBreadcrumbDetails(_kt('select a user'));
@@ -53,7 +53,7 @@ require_once(KT_LIB_DIR . &#39;/roles/Role.inc&#39;);
  
 class WorkflowNavigationPortlet extends KTPortlet {   
     var $oWorkflow;
-
+    var $sHelpPage = 'ktcore/admin/workflow.html';
     function WorkflowNavigationPortlet($sTitle, $oWorkflow = null) {
         $this->oWorkflow = $oWorkflow;
         parent::KTPortlet($sTitle);
@@ -81,7 +81,7 @@ class WorkflowNavigationPortlet extends KTPortlet {
  
 class KTWorkflowDispatcher extends KTAdminDispatcher {
     var $bAutomaticTransaction = true;
-    var $sHelpPage = 'ktcore/admin/workflow/overview.html';
+    var $sHelpPage = 'ktcore/admin/workflow.html';
     var $aWorkflowInfo;
     var $oWorkflow;
  
@@ -34,7 +34,7 @@ require_once(KT_LIB_DIR . &#39;/widgets/fieldWidgets.php&#39;);
  
 class KTAuthenticationAdminPage extends KTAdminDispatcher {
     var $bAutomaticTransaction = true;
-
+    var $sHelpPage = 'ktcore/admin/authentication sources.html';
     function check() {
         $res = parent::check();
         $this->aBreadcrumbs[] = array('name' => _kt('Authentication'), 'url' => $_SERVER['PHP_SELF']);
@@ -35,6 +35,7 @@ require_once(KT_LIB_DIR . &#39;/util/ktutil.inc&#39;);
 class KTWorkflowAssociationPlugin extends KTPlugin {
     var $sNamespace = "ktstandard.workflowassociation.plugin";
     var $sFriendlyName = null;
+    var $sHelpPage = 'ktcore/admin/automatic workflows';
  
     function KTWorkflowAssociationPlugin($sFilename = null) {
         $res = parent::KTPlugin($sFilename);
@@ -33,6 +33,7 @@ require_once(KT_LIB_DIR . &#39;/widgets/fieldWidgets.php&#39;);
  
  
 class WorkflowAllocationSelection extends KTAdminDispatcher {
+    var $sHelpPage = 'ktcore/admin/automatic workflows.html';
     var $bAutomaticTransaction = true;
     var $sSection = 'administration';