[Web-erp-svn] SF.net SVN: web-erp:[7122] trunk

[<dai...@us...>]

Revision: 7122
          http://sourceforge.net/p/web-erp/reponame/7122
Author:   daintree
Date:     2015-02-04 08:22:52 +0000 (Wed, 04 Feb 2015)
Log Message:
-----------
finish adding Andrews quality documentation

Modified Paths:
--------------
    trunk/ProductSpecs.php
    trunk/QATests.php
    trunk/doc/Manual/ManualOutline.php
    trunk/doc/Manual/ManualQualityAssurance.html

Modified: trunk/ProductSpecs.php
===================================================================
--- trunk/ProductSpecs.php	2015-02-04 08:12:21 UTC (rev 7121)
+++ trunk/ProductSpecs.php	2015-02-04 08:22:52 UTC (rev 7122)
@@ -4,7 +4,7 @@
 include('includes/session.inc');
 $Title = _('Product Specifications Maintenance');
 $ViewTopic= 'QualityAssurance';// Filename in ManualContents.php's TOC.
-$BookMark = 'QA';// Anchor's id in the manual's html document.
+$BookMark = 'QA_ProdSpecs';// Anchor's id in the manual's html document.
 include('includes/header.inc');
 
 if (isset($_GET['SelectedQATest'])){

Modified: trunk/QATests.php
===================================================================
--- trunk/QATests.php	2015-02-04 08:12:21 UTC (rev 7121)
+++ trunk/QATests.php	2015-02-04 08:22:52 UTC (rev 7122)
@@ -3,6 +3,8 @@
 
 include('includes/session.inc');
 $Title = _('QA Tests Maintenance');
+$ViewTopic= 'QualityAssurance';// Filename in ManualContents.php's TOC.
+$BookMark = 'QA_Tests';// Anchor's id in the manual's html document.
 include('includes/header.inc');
 
 if (isset($_GET['SelectedQATest'])){

Modified: trunk/doc/Manual/ManualOutline.php
===================================================================
--- trunk/doc/Manual/ManualOutline.php	2015-02-04 08:12:21 UTC (rev 7121)
+++ trunk/doc/Manual/ManualOutline.php	2015-02-04 08:22:52 UTC (rev 7122)
@@ -237,7 +237,15 @@
                                  'Work order issues',
                                  'Closing work orders'),
      'QualityAssurance' =>array('Quality Assurance',
-							'Overview'),
+								'Overview',
+								'Tests Maintenance',
+								'Product Specifications',
+								'Copying Specification',
+								'Print Product Specification',
+								'Logging Samples',
+								'Entering Test Results',
+								'Print Certificate of Analysis',
+								'View Historical Results'),
     'MRP'               => array('Material requirements planning',
                                  'MRP Overview',
                                  'Base data required',

Modified: trunk/doc/Manual/ManualQualityAssurance.html
===================================================================
--- trunk/doc/Manual/ManualQualityAssurance.html	2015-02-04 08:12:21 UTC (rev 7121)
+++ trunk/doc/Manual/ManualQualityAssurance.html	2015-02-04 08:22:52 UTC (rev 7122)
@@ -10,7 +10,7 @@
 <p>All menu options for Quality are found under Manufacturing. Your menus may look differnet based on your permissoins. The menus are shown below.</p>
 <img src="images/QA_Menus.png" alt="QA Menu options screen" />
 
-<h2>QA Tests Maintenance</h2>
+<h2><a id="QA_Tests">QA Tests Maintenance</a></h2>
 <p>This is where all tests that will be performed are defined. Other specification related information can be captured here that isn’t tested but describes in more detail the product specification. An example of this would be Processing Conditions for your product that you wish for your customers to understand. A specification is made up of any number of tests. The test defines outer tolerances but the specification allows the upper and lower bounds of the test to be specified.</p>
 <img src="images/QA_Tests.png" alt="QA Tests screen" />
 
@@ -30,7 +30,7 @@
 	<li>Active: once a test has results entered against it delete is no longer allowed. This flag can be used to
 inactivate it and not use it on future product specifications.</li>
 </ul>
-<h2>Product Specification</h2>
+<h2><a id="QA_ProdSpecs">Product Specification</a></h2>
 <p>Product Specifications are a collection of QA Tests that come together to define how a Product Data Sheet is built, what we test for and what we certify our results to. These are loosely tied to Items (Stocks). If a Product Specification is named the same as a stock ID then the Product Description will be used in printed paperwork and screens. If it is not a stock id then it is considered a generic product specification that can be used to hold any type of test results in your system. This also allows cascading templates to be created for faster product specification definition. In the future I foresee there may also be a loose connection to Fixed Assets. A Product Specification is added as soon as a test is added to it.
 To start a new specification, go to the Product Specification Screen, Type in a specification Name or stock id and click Submit.</p>
 <img src="images/QA_ProductSpecificationMaintenance.png" alt="QA Product specification maintenance screen" />