DocuBrain TechDoc Acceptance Test Plandocubrain.com/.../documentation/r8/TechDoc8AcceptanceTestPlan.pdf · DocuBrain® TechDoc Acceptance Test Plan. PTI-TD-00003 Revision 8-1 DocuBrain

PTI-TD-00003 Revision 8-1

A DocuBrain® Product By Prevo Technologies, Inc. http://docubrain.com/ http://www.prevo.com/

DocuBrain® TechDoc

Acceptance Test Plan

http://docubrain.com/

http://www.prevo.com/


DocuBrain TechDoc Acceptance Test Plan i

Table of Contents Acceptance Test Plan Overview .......................................................................................... 1

Overview ......................................................................................................................... 1

Intent ............................................................................................................................... 1

General Test Instructions ................................................................................................ 1

Modifications to the Original Test Plan .......................................................................... 1

Testing Environment ....................................................................................................... 2

Notes on Installing a Testing Environment ..................................................................... 2

DM User Testing .................................................................................................................. 4

DM-74 – Add Projects for Associating Documents ......................................................... 5

DM-247 – Document and Generation Attachments ...................................................... 7

DM-473 – Add a new Mass Cancel Document feature for CR 23410 ............................. 8

DM-500 – Update the Look and Feel of the DM............................................................. 9

DM-502 – Allow an Attachment when Casting Vote .................................................... 10

DM-503 – Can't Vote Again to Change Comments if the Type of Vote Doesn't Change....................................................................................................................................... 11

DM-504 – Add support for Office 2010 Differences in the Text Extractors ................. 13

DM-514 – Delete Folder Tree when No Documents in Tree ........................................ 14

DM-515 – Optimize Reports for Documents with Keyword Criteria ............................ 15

DM-517 – Allow Group to be deleted if it has Associations ......................................... 16

DM-532 – Handle Smart Quotes Pasted into Various Input Fields............................... 17

DM-534 – Add Keywords as a Column on Reports ....................................................... 18

DM-535 – Add Search Folders with Selectable Columns .............................................. 19

DM-536 – Add support for Office Open XML Thumbnails that use the EMF Format .. 20

DM-539 – Add a Text Extractor for Visio VSD Files ....................................................... 21

DM-544 – Add a Progress Indicator When Uploading Files.......................................... 22

DM-545 – Add Nonresident URL to Generation ........................................................... 23

DM-546 – Add Navigation Crumbs to the Explorer ...................................................... 24

DM-547 – Add Revision as a Column in the Explorer ................................................... 25

DM-548 – Add an Action Gear to Various Brief Items .................................................. 26

DM-549 – Add Web 2.0 Widgets to TechDoc ............................................................... 27

DM-550 – Add Change Password Feature for Improved Security and Usability .......... 28

DM-551 – Improve Review Vote Request Subject on Email ......................................... 29

DM-552 – Add Support for Visio 2013 Thumbnails ...................................................... 31

DM-553 – Add Support for Visio 2013 Text Extraction ................................................ 32

DM-554 – Add Compose Email to Document, Generation, and Project ...................... 33

DM-555 – Fix Report Problem with Order by and Multiple Virtual Columns ............... 34

DM-560 – Add Document Default Associations to a Folder ......................................... 35

DM-561 – Add Access and Mail List Inheritance for Folders ........................................ 37

DM-562 – Change OK Button for Quick Search on Main Menu to an Image ............... 39

DM-563 – Add Release to a Generation ....................................................................... 40

DM-564 – Add Unrelease to a Generation ................................................................... 41

DM-567 – Rename Lists to Groups ............................................................................... 42


DocuBrain TechDoc Acceptance Test Plan ii

DM Records Manager Testing........................................................................................... 43

DM-456 – Add an RMA Cutoff Date (Retention Start Date) per CR 21419 .................. 44

DM Workflow Manager Testing ........................................................................................ 47

DM-531 – Add BPMN 2.0 Workflow Support to TechDoc ............................................ 48

DM Admin Testing ............................................................................................................ 51

DM-486 – Allow Modify Remote Email with One That Already Exists ......................... 52

DM-491 – Add System Property to define which hyperlinks and generations that Status and Retrieval display .......................................................................................... 54

DM-493 – Update TechDoc to use Tomcat 7 ................................................................ 56

DM-494 – Upgrade DM to use new JRE for TechDoc 8 ................................................ 57

DM-526 – Update the DM Default Authenticator System Property to Document the Impact on SSO ............................................................................................................... 58

DM-533 – Adjust Memory Allocated to Tomcat during DM Installation ..................... 59

DM-556 – Add Ability to get Document Statistics ........................................................ 60

DM-558 – Add Partition Information to File Areas on the DM .................................... 61

DM-577 – Change Default Submit Order on Resubmit All Documents ........................ 62

SM User Testing ................................................................................................................ 63

SM Admin Testing ............................................................................................................. 64

SM-97 – Add Advanced Search and Quick Search to the SM ....................................... 65

SM-98 – Upgrade SM to use new JRE for TechDoc 8.................................................... 66

SM-101 – Update the Look and Feel of the SM ............................................................ 67

SM-105 – Update the SM Default Authenticator System Property to Document the Impact on SSO ............................................................................................................... 68

SM-107 – Adjust Memory Allocated to Tomcat during SM Installation ....................... 69

SM-112 – Fix Cross Site Scripting (XSS) Finding Reported on the SM .......................... 70

SM-113 – Add Partition Information to File Areas on the SM ...................................... 71

SM-114 – Change OK Button for Quick Search on Main Menu to an Image ................ 72

SM-115 – Update Lucene to the Latest Version for TechDoc 8.................................... 73

SM-118 – Add Rebuild Index Command into the SM in Support of Upgrading Lucene 74

SM-119 – Add Optimize Index Command into the SM in Support of Upgrading Lucene....................................................................................................................................... 75

Specialized System Level Testing ...................................................................................... 76

DM-492 – Fix Original PDFbox Temp File Closed Too Early Issue ................................. 76

DM-496 – Make Sure Build Date is always Correct on DM About Screen.................... 76

DM-505 – Add new Interim Certificate Authority that is required by NSSC ................ 76

DM-507 – Add Ability for Folder Shares to Open Documents in New Windows ......... 77

DM-509 – Add Create Date and Non-Resident Support to REST .................................. 77

DM-511 – Add Support for Files Larger than 2GB ........................................................ 78

DM-512 – Add Support to the DM for SQL Server 2012 ............................................... 78

DM-513 – Add the Outlook Mime Type to DM ............................................................ 79

DM-516 – Add Snapshot Isolation to the DM Database ............................................... 79

DM-521 – Add REST Privilege to Restrict Use of TechDoc Client and Other REST-Based Applications................................................................................................................... 79

DM-522 – Update CSS to Deal with Recent Change to IE9 ........................................... 80


DocuBrain TechDoc Acceptance Test Plan iii

DM-523 – Improve SAML to Work on Servers with Multiple Host Names .................. 80

DM-524 – TechDoc Client Doesn't Handle a Server that is Not Configured for SSO .... 81

DM-525 – Modify Cabinet does not work from the TechDoc Client ............................ 81

DM-527 – Change DM TechDoc Tomcat Ports to Avoid Collisions ............................... 81

DM-528 – Update BDL Protocol Authorization to Handle IPv6 .................................... 82

DM-537 – Update TechDoc 8 Installer to Configure IIS to Pass Errors Back to Client . 82

DM-540 – Improve the DM on Servers with Multiple Host Names.............................. 82

DM-541 – Add Temp Folder Checking on DM Start Up ................................................ 83

DM-543 – Update REST Document Search Service to Support All Document Columns....................................................................................................................................... 83

DM-565 – Add New Iterators to Records to Reduce Memory Usage in TechDoc ........ 84

DM-570 – Add Utils from CSV Import Utility to TechDoc 8 for Inclusion with Scan Agent 8 .......................................................................................................................... 84

DM-573 – Add Nonresident Document Support to Scan Agent ................................... 84

DM-574 – Update the VIX API to Support VMware 5.1 ................................................ 84

DM-576 – Modify the Render Task so that Lower Priority Renders Can Be Handled .. 85

DM-584 – Add Deleted File Logging for Replace Document ........................................ 85

SM-96 – Remove Keyword History out of the SM Show History Servlet ..................... 87

SM-99 – Make Sure Build Date is always Correct on SM About Screen ....................... 87

SM-100 – History Display Could Have Problem when IP Address is not set ................ 87

SM-103 – Add Support to the SM for SQL Server 2012 ................................................ 87

SM-104 – Add Snapshot Isolation to the SM Database ................................................ 88

SM-106 – Change SM TechDoc Tomcat Ports to Avoid Collisions ................................ 88

SM-109 – Improve the SM on Servers with Multiple Host Names ............................... 88

SM-110 – Add Temp Folder Checking on SM Start Up ................................................. 89

SM-111 – Increase the Released File Name Length to 255 to Match the DM ............. 89

SM-117 – Remove Clustering from the Remote Host Index on the Documents Table 89

Conclusion ......................................................................................................................... 91


DocuBrain TechDoc Acceptance Test Plan iv

Acceptance Tester Information

Name: Date:

Mail Code or Address: Phone Number:

Comments:


DocuBrain TechDoc Acceptance Test Plan 1

Acceptance Test Plan Overview

Overview

TechDoc is a distributed, document and records management system designed for the management of any type of document or file, such as traditional documents (Word, Excel, PowerPoint, PDF, etc.), CAD drawings, audio, video, etc. TechDoc provides a simple, distributed, and secure way for users to manage and share their documents and records electronically.

Intent This Acceptance Test Plan is intended to demonstrate and verify that the functional capabilities meet general user needs and the application performs as designed by the development team. The test cases included in this plan are specifically targeted to verify capabilities that have either been changed or added with this release of TechDoc.

General Test Instructions

The test has step-by-step instructions you need to follow to execute the test cases accurately. Skipping a step could skew the test results. It might be necessary to return to the start of a test sequence if a step or steps are inadvertently dropped. The following input is requested for each test case:

Done – Optionally, place a check mark in this column to note that each step was performed.

Correct – Circle Y to indicate that the results were correct or N to indicate that the results were incorrect or that an unexpected error occurred.

Initials – Enter your initials to indicate that you completed this test case.

Comments - If N is circled, please explain why here. Also, feel free to provide any additional comments concerning this test case.

Modifications to the Original Test Plan

None, this is the original plan.



Testing Environment

The following requirements must be met in order to perform testing:

Internet connectivity

A TechDoc compatible web browser

Access to a TechDoc test system running TechDoc Release 8 or the latest release candidate of TechDoc Release 8.

A TechDoc User Account on the test system

Notes on Installing a Testing Environment If you are installing a test environment, here is a list of requirements that are expected of the environment in order to allow users to complete the tests. If you are simply a tester, you can skip the remainder of this section.

Install a Document Manager (DM) and a Search Manager (SM). Usually do so on the same server, it will make testing easier for the users as they will only need to know one server name.

On the SM: o Add a couple of Authenticators o Add Network Addresses to allow testers access to the system if necessary o Add a Remote Host for the DM (Note the username and password for use

when setting up the DM) o Modify System Properties:

Set AllowForgotPassword to Yes Set AllowLogInFrom to the appropriate value Set AllowSearchFrom to Global Set CachedFileMode to Yes Set CachedFilesRequireAuthorization to No Set DisableSearching to No Set ExternalBaseUrl to the appropriate value Set SmtpFromAddress if necessary to allow SMTP delivery in your

environment Set SmtpGateway to a Mail gateway accessible by the SM Adjust any other settings to suit your requirements

o Create User Accounts for testers

On the DM: o Add a couple of Authenticators o Adjust Doc Categories if desired

Do not delete NS as it is used in testing o Add a couple of Employers



o Add a couple of Keywords make sure that at least one of them is a date create a private keyword named Private_Keyword

o Add Network Addresses to allow testers access to the system if necessary o Add a couple of Organizations o Add a couple of RMA File Plans that are not permanent o Add some Doc Types o Add a Search Manager Host for the SM

Set the Web Search preferably to Campus so testers can choose any Web Search (besides None) and their documents will get sent to the SM

Set "Send Index Text" to Yes Set "Send Release Files" to Yes The "Send Thumbnails" can be set either way (it doesn't affect

testing) Of course, use the Username and Password that you used when

creating the Remote Host on the SM When given the chance to submit all documents, click OK; It is

important that all current information be sent to the SM o Modify System Properties:

Set AllowAssocRemoteAccess to Yes Set AllowFetchByUsernameFrom to the appropriate value Set AllowForgotPassword to Yes Set AllowLogInFrom to the appropriate value Set AutoDocNumberMask to something if it is blank, we suggest

AUTO-%y-%###### Set ExternalBaseUrl to the appropriate value Set SmtpFromAddress if necessary to allow SMTP delivery in your

environment Set SmtpGateway to a Mail gateway accessible by the DM Set SystemAvailable to Yes Adjust any other settings to suit your requirements

o Create User and Admin Accounts for testers



DM User Testing The following test cases can be performed by a user with Normal privileges on a Document Manager.



DM-74 – Add Projects for Associating Documents

Projects have been added to associate/group documents together. It is very common for multiple documents to be needed while working on a project. Initially, the project will mainly be used for simply associating a group of documents together. In the future, projects will be expanded to provide more functionality based on user feedback.

Steps for Testing Done

1. Start by creating a Project. Click Projects on the Main Menu and click Create Project on the side menu. Give the Project a name and optionally fill in the remainder of the information. Click Next and then OK to create the Project.

2. Now modify the Project and add a Keyword. Click Projects on the Main Menu, select the Project created in the previous step, and then click Modify on the side menu. When the modify Project screen loads, enter a reason and then click Next. Select a Keyword from the New Keyword drop down, click Add to add the Keyword. Enter/select a value for the Keyword and then click OK to modify the Project.

3. Let's add a Document to the Project. First create a test Document and note the Document Number. Now click Projects on the Main Menu, select the Project created for this test, and then select Add Document on the side menu. In the Document Number box, type just the first few letters (3 or 4) of the Document Number. A suggestions box should popup below showing all Documents with Document Numbers that match those first few letters. Select the test Document from the list, type a reason, and then click OK.

4. If you have another non-admin User account available, test associating access to the Project. If another non admin User account is not available, you may skip the remainder of this step. Click Projects on the Main Menu, select the test Project, and then select Assoc Access from the side menu. The Project should default to Local Users with Read access. Give your other User account modify privileges to the Project, log out and then log in with that account and see that you are able to modify the Project. Log out and log back in with your original User account.

5. Test the Compose Email feature by clicking Projects on the Main Menu, selecting the test Project, and selecting Compose Email from the side menu. Using the interface, create a test email and send it to yourself. The To and CC buttons can be used to select Users and Groups to send the email to. Try out some of the text and body formatting options using the toolbar. Select a few of the Include links at the bottom and then click Send. Give the email time to be sent (sometimes may take up to 10-15 minutes). Once you receive the email, verify it appears as it did when you constructed it; the links are correct, etc…



6. Remove the test Document from the Project. Click Projects on the Main Menu, select the test Project, and then select the Project Document you added in the previous example. When the Project Document screen loads, select Remove from the side menu. Click Next, enter a reason, and then select OK. Verify that the Project no longer contains the test Document.

7. You no longer need the test Document, so you may navigate to the Document and delete it.

8. Now Delete the Project. Click Projects on the Main Menu, select the test Project, and then select Delete from the side menu. Click Next, enter a reason, and then click OK to delete the Project.

Results: You were able to Create, Modify, Delete, and Compose Email for the Project. You were also able to Add and Remove a Project Document and Associate Access for the Project.

Correct Initials

Y N

Comments:



DM-247 – Document and Generation Attachments

The ability to upload attachments to a document or one of its generations has been added to TechDoc. Attachments need to appear on the appropriate "Show" pages and the DM status and retrieval page.


1. Create a test Document for this exercise.

2. Navigate to and select the test Document. Click Attachments on the side menu under "Show…" and then click Add on the side menu. Enter a description, a reason, and then click Next. Click the Browse button and select a file to upload as the attachment for this Document. Click OK to create the attachment.

3. Verify that you now see the Document attachment listed, with the correct filename, description, etc.

4. Select the attachment and select Delete from the side menu. Click Next, enter a reason, and then click OK to delete this attachment.

5. Navigate to and select the test Document. This time however, select a generation under the test Document. Click Attachments on the side menu and then click Add on the side menu. Verify that the screen says you are adding an attachment to the Generation. Enter a description, a reason, and then click Next. Click the Browse button and select a file to upload as the attachment for this Generation. Click OK to create the attachment.

6. Verify that you now see the Generation attachment listed, with the correct filename, description, etc.

7. Select the Generation attachment and select Delete from the side menu. Click Next, enter a reason, and then click OK to delete this attachment.

8. Now delete the test Document.

Results: Now you are able to Create and Delete an Attachment on both a Document and a Generation.

Correct Initials

Y N

Comments:



DM-473 – Add a new Mass Cancel Document feature for CR 23410

The ability to mass cancel a large number of documents at once has been added to TechDoc. The user provides the revision, a file, and whether the file should be rendered or not (if applicable). The file is then added to each document as the final generation of the document and then cancelled with the specified revision.


1. Create several test Documents and write down their Document Numbers. It's helpful to name them similar i.e. massCancelTest001, massCancelTest002, etc.

2. Click My Work on the Main Menu and select Mass Cancel Docs on the side menu.

3. Enter the beginning of the Document Number scheme used in step 1 followed by a star. For example if you named the Documents massCancelTest001, massCancelTest002, etc… you could enter massCancelTest*.

4. Click Search and note that your test Documents are displayed as results. If you see your Documents, click Next.

5. Select your test Documents by checking the box next to them and click Next.

6. Now Click Browse and select a file to be uploaded and used as the last Generation for the Documents. Click Next after you have selected a file.

7. Select a Revision from the Revision drop down and just choose No for Render. Click Next to continue.

8. Click Next, enter a reason, and then Click OK.

9. Navigate to each of the Documents and verify that they are canceled with the appropriate Revision and final Generation. After verifying each Document, you can Delete it.

Results: Now you can Mass Cancel Documents. Correct Initials

Y N

Comments:



DM-500 – Update the Look and Feel of the DM

The Look and Feel of TechDoc has been updated. The color schemes and all the icons have been updated. Also, layouts have been changes to allow for more compact display of various items.


1. Navigate to and select a Folder. Now using the side menu, try out a few operations just to see that each of the screens for that operations display correctly, the icons appear appropriately, etc.

2. Repeat step one for a Document.

3. Repeat step one for a Generation.

4. Lastly make a pass through all of the links on the Main Menu (Groups, My Work, Projects, etc…) visiting a few screens in each section to verify everything appears correct.

Results: Now the Document Manager's look and feel is much more modern.

Correct Initials

Y N

Comments:



DM-502 – Allow an Attachment when Casting Vote

The ability to upload an attachment as part of casting a vote has been added. When this is done, the attachment is automatically added to the discussion item that is created for that particular vote. You must have the Review Leader privilege to complete this test.


1. Create a test Document and note its Document Number.

2. Create a test Review for the Document making sure that you are a member of the Review team selected for the Review. Once you have created the Review, start the Review.

3. Click Reviews on the Main Menu, select the Review you created, and then select Vote from the side menu.

4. Fill in the Vote as you normally would. At the bottom, click the Browse button, select a file to upload as an Attachment, and then click OK.

5. Click Reviews on the Main Menu, select the Review you created, and then select Show… Discuss/Votes.

6. Select the Vote you posted and verify there is now a download icon (diskette) next to the info icon.

7. Click the download icon and verify it contains the file you originally uploaded as the Attachment.

8. Now you may now delete the test Review and Document.

Results: Now you can add an Attachment when casting a vote. Correct Initials

Y N

Comments:



DM-503 – Can't Vote Again to Change Comments if the Type of Vote Doesn't Change

Previously, if you re-voted and tried to change the comments but you don't change the type of vote (for example, leaving it Approved), the system would say that nothing has changed and wouldn't record the new comment. This has been corrected so that you can simply change the comments without changing the type of vote. You must have the Review Leader privilege to complete this test.


1. Create a document; none of the settings is important.

2. On the side menu, click Create Review.

3. When creating the review, don't pick a review team, type A for the Revision, choose No for Allow Reserve and Replace, choose No for Allow Open Posting, enter some text for the Voter Instructions, enter a reason, and click OK.

4. On the side menu, click Create Level.

5. When creating level 1, select No for Auto Concur, select No for Auto Promote, leave Max Duration empty, enter All for Votes Needed for Level, enter a reason, and click Next.

6. Click Next to skip the Group selection screen.

7. Select yourself in the Available Users box, click Add to add yourself to the Selected Users box, and click Next.

8. Click OK without adding any remote users.

9. Click Review Info on the side menu.

10. Click Start on the side menu.

11. Enter a reason and click OK.

12. Click Vote on the side menu.

13. Skip the optional account input(s), choose "Concur with Remarks" for Vote, enter a remark for Remarks, and click OK.

14. Click Vote again on the side menu.

15. Skip the optional account input(s), choose "Concur with Remarks" again for Vote, enter a different remark then last time for Remarks, and click OK.

16. You should receive a message that your vote has been registered.

17. You can now delete the review and the document.

Results: You can now recast a vote with the only difference being the remarks.

Correct Initials

Y N



Comments:



DM-504 – Add support for Office 2010 Differences in the Text Extractors

Minor differences are possible with embedded objects between Office 2007 and Office 2010. The Office text extractors have been improved to handle the differences when present so that all text is extract.


1. Using Microsoft PowerPoint 2010, create a PowerPoint presentation. Enter a title on the first slide, and at the bottom of the screen, enter a few words into the "notes" area. Save the PowerPoint and exit.

2. Create a test Document using the PowerPoint presentation created in the previous step. Be sure to use a Document Type that is text searchable and a Document Category with an appropriate web search setting for your Search Manager.

3. Release the Document so it will be sent over to the Search Manager and have its text indexed.

4. Now switch over to the search engine and perform a Text search using one of the words or a phrase entered in the "notes" area in step 1. Remember it can take up to a couple minutes for search index updates to run.

5. Verify that you are able to search and find your PowerPoint presentation using words entered in the "notes" area.

6. Go back to the Document Manager and delete the test Document.

Results: Newer Office 2010 documents can be searched by text in embedded areas such as notes on slides.

Correct Initials

Y N

Comments:



DM-514 – Delete Folder Tree when No Documents in Tree

Delete Folder has been improved to allow a folder tree to be deleted. However, to prevent the large scale deletion of documents accidentally, the folder can contain folders but it and any child folders in the tree cannot contain any documents. This way Mass Delete Document can be used to knowingly remove a large number of documents and Delete Folder can then be used to quickly clean up the folder tree that is left behind.


1. Create a test Folder; the attributes specified do not matter.

2. Now navigate into that test Folder and create another Folder.

3. Continue on navigating deeper into this Folder tree creating empty Folders.

4. Once you have created four or five Folders, navigate back to the original Folder you created at the top and select it.

5. Create a test Document within this Folder.

6. Navigate back to the original Folder, select it, and then select Delete from the side menu. Verify that you are not able to delete the Folder Tree because it contains a Document.

7. Now Delete the Document you just created. Navigate back to the original Folder, select it, and then select Delete from the side menu.

5. Click Next, enter a reason, and then click OK to delete the Folder and all of its empty sub-Folders.

Results: Now you can delete Folder Trees as long as they contain no Documents.

Correct Initials

Y N

Comments:



DM-515 – Optimize Reports for Documents with Keyword Criteria

When running Document reports on systems with large numbers of documents and keywords, it was possible to create reports that take an extremely long time to complete. The issue arises when many keyword criteria are specified on the report. The Reports SQL generator has been improved for this condition and the same queries that were taking hours now complete in seconds


1. Click Reports on the Main Menu, and then select Create on the side menu.

2. Give the Report a Name, Description, and select Documents as the Table. Click Next to continue.

3. On the Choose Data Fields To Show screen, add the Doc Number and a few other fields to the Selected Data Fields. Click Next to continue.

4. On the Choose Data Fields to Order By screen, you can just click Next.

5. Finally on the Choose Data Fields to Limit Results screen, select and add five or six Keywords. Then for those five or six Keywords, just enter/select a value. The Keywords added and the values specified do not matter. Click Next.

6. Now click the Preview As HTML link to view the Report. Verify that the Report loads quickly now, no more than several seconds. The test here is that you are running a Report that is checking several Keywords. Whether or not you match a single Document, this type of a Report used to take a long time to execute.

Results: Now you can create Reports with lots of Keyword criteria that execute quickly.

Correct Initials

Y N

Comments:



DM-517 – Allow Group to be deleted if it has Associations

Groups (formerly list Lists) can now be deleted even if they have associations. A warning is displayed on the Delete Group servlet so that the user will realize associations will be lost.


1. Click Groups on the Main Menu and select Create from the side menu.

2. Enter a name and description, select Shared as the Group Type, select Local Users as the Member Type, enter a reason, and then click Next.

3. On the Member screen, find your user account in the list, select it, and click Add. Click OK to create the Group.

4. Now create a test Document. The information entered for this Document does not matter.

5. Navigate to the Document, select it, and click Assoc Access from the side menu.

6. Enter a reason and click Next. On the Groups screen, select your test Group, choose an access setting of Modify, and then click Add. Click Next. Click Next. Finally click OK to finish the association.

7. Now you have a test Group that is associated to a Document. Click Groups on the Main Menu, select your test Group, and click Delete on the side menu.

8. Verify that you now see a warning telling you the Group has one or more associations.

9. Click Next, enter a reason, and click OK. Verify that you are now able to delete the Group.

10. Navigate to, select, and delete the test Document.

Results: Now you can delete a Group even if it has associations. Correct Initials

Y N

Comments:



DM-532 – Handle Smart Quotes Pasted into Various Input Fields

When copying data from sources like Office products to text boxes in TechDoc, smart quotes and various other Unicode characters can cause errors. Improvements have been made to translate these special characters back to their standard ASCII representation to avoid the errors from occurring.


1. Most of the fields throughout the Document Manager now handle smart quotes and other Unicode characters commonly used in Office products. We'll just touch on a couple of example. Create a Folder and in the description field enter some text and a smart quote. A smart quote can be obtained by typing a quote into a Word document. If smart quotes are enabled you will see your normal quotes replaced with the special forward and backward facing quotes. These quotes can be copy to the clipboard by pressing CTRL + C and pasted into the description field by pressing CTRL + V. If you don't have smart quotes enabled (the default setting in Word), you may simply enter a different Unicode character such as « by holding the ALT key, typing 0171 and then releasing the ALT key.

2. Now create a Document and like the previous example placing a smart quote or other Unicode character in its title.

3. Navigate around the Document Manager and find a few other things to create, maybe a Group or Cabinet, and try these special characters there.

4. Verify that all of the Folders, Documents, and any other things you've created allowed you to enter those special characters.

5. Delete the Folder, Document, and any other things you created for this test.

Results: Now you can use smart quotes and other special characters in input fields.

Correct Initials

Y N

Comments:



DM-534 – Add Keywords as a Column on Reports

A request was received to allow a Keyword to be shown as a column on a Document report. In performing the work required, it was determined that Keywords should be added as columns for Projects, Records, and Record Sets.


1. Click Reports on the Main Menu and then select Create on the side menu.

2. Enter a name and description for the Report and choose Documents for the Table. Click Next.

3. On the Fields To Show screen, add Doc Number and a Keyword from the list at the bottom. The Keywords in the System will be presented as {Keyword} followed by the name of the Keyword. After you've added the Doc Number and a Column, click Next.

4. On the Fields to Order By screen, just click Next.

5. On the Data Fields To Limit Results screen, just enter a bit of search criteria you know will match at least one or more Documents in the system that have Keyword you selected in step 3. An easy way to do this is just add the Keyword and set the value = *. That way you'll make any Document in the system that has the Keyword you specified. Click Next.

6. Now click the Preview As HTML link. Verify the Report shown contains the Doc Number and Keyword columns, and that the Keyword column lists its value for each Document.

7. Close the Report popup window. Now just click Cancel to cancel the creation of the Report. If you have already clicked OK to create the Report, just navigate back to the Report and delete it.

Results: Now you can create Reports that display Keywords as a column.

Correct Initials

Y N

Comments:



DM-535 – Add Search Folders with Selectable Columns

The Search Folder concept from the TechDoc Client has been introduced into TechDoc 8. A user can create a Search Folder with arbitrary document criteria and all matching documents that the user has read access to will appear in the search folder. In addition, the user can decide which columns will be shown when the documents are displayed.


1. Click My Work on the Main Menu, select All of my… Search Folders on the side menu, and then click Create on the side menu.

2. Enter a name and description for the Search Folder and then click Next.

3. On the criteria screen, you are basically just performing an Advanced Search. Choose one or more of the fields to search on, and enter a value. For instance if you wanted to find all the Documents that have a Doc Number that starts with testPlan you would enter testPlan* in the Number field. Make sure that the search you choose will match at least one Document. Click Next.

4. On the Columns to Display screen, select and add one or more columns to be displayed. The columns selected here will be the displayed when you view the Search Folder. Click OK to create the Search Folder.

5. You should now be looking at the Search Folder info screen. Click Search on the side menu.

6. Now the search results matching the criteria of your Search Folder are displayed. Notice the columns you selected are displayed. Note that the Doc Number column is always displayed.

7. Now modify the Search Folder changing the columns and criteria. After you modify the Search Folder, perform the Search again and see that the display and results are what you'd expect.

8. You may now delete the Search Folder.

Results: Now you can create Search Folders and customize their output.

Correct Initials

Y N

Comments:



DM-536 – Add support for Office Open XML Thumbnails that use the EMF Format

Microsoft Office can now use EMF thumbnails in addition to JPG thumbnails that Microsoft Office used previously. The Office Open XML Thumbnail renderer has been updated to look for EMF thumbnails so that thumbnails can be produced for either type of Microsoft Office document. In order to test this functionality, you must have a Microsoft Office 2010 or newer document saved in one of the new OOXML formats (DOCX, XLSX, PPTX, etc.). The difficulty is that we are not aware of any way to force Microsoft Office to produce the thumbnail in EMF format. An example that contains an EMF thumbnail is available at http://docubrain.com/sites/default/files/examples/TechDoc8AcceptanceTestPlanPoem.docx or you may choose to use your own file that meets the requirements.


1. Create a document using a DOCX, XLSL, or PPTX file that contains an EMF thumbnail. Make sure to use a Doc Type that sends thumbnails, set Web Search to Community, and make sure Community has read access to the document.

2. Release the document and choose not to render it (if given the option).

3. Wait a couple minutes for the update to make it to the SM.

4. Go to the SM and search for your document.

5. On the search details screen, the thumbnail should be displayed.

Results: Office documents that have EMF thumbnails should now display on the SM.

Correct Initials

Y N

Comments:

http://docubrain.com/sites/default/files/examples/TechDoc8AcceptanceTestPlanPoem.docx

http://docubrain.com/sites/default/files/examples/TechDoc8AcceptanceTestPlanPoem.docx



DM-539 – Add a Text Extractor for Visio VSD Files

A TechDoc text extractor has been created that specifically handles Visio VSD files. In the past, TechDoc used the fallback text extractor that simply attempts to extract any strings of text that appear in the file whether they are valid or not. In order to test this functionality, you must have a Microsoft Visio document saved in the VSD format. An example that can be used is available at http://docubrain.com/sites/default/files/examples/TechDoc8AcceptanceTestPlanPoem.vsd or you may choose to use your own file that meets the requirements. The example flowchart contains the poem "Do Not Go Gentle into That Good Night" by Dylan Thomas broken into different shapes.


1. Create a document using a Visio file with the VSD extension that contains some text. Make sure to use a Doc Type that sends text, set Web Search to Community, and make sure Community has read access to the document.



4. Go to the SM and search for your document using different words or phrases.

Results: Visio VSD text extraction is now more reliable with a text extractor written specifically for VSD files than the old fallback extractor.

Correct Initials

Y N

Comments:

http://docubrain.com/sites/default/files/examples/TechDoc8AcceptanceTestPlanPoem.vsd




DM-544 – Add a Progress Indicator When Uploading Files

As part of improving the DM look and feel under issue DM-500, the Dojo toolkit has been incorporated into TechDoc. The Dojo toolkit made it easier to add a progress indicator when uploading files. Also, there has been a long standing issue we with the Previous and Cancel button on a file upload screen. When either one of them is pressed, TechDoc would still have to upload the file (if one had been chosen), before the button press could be handled. This issue has been addressed.


1. For this test we'll just be creating a Document. First you'll need to find a decent sized file; something around 1MB to 20MB in size. You don't need a huge file, but you do want something large enough so you can see the progress bar update a few times. A small file will just complete instantly.

2. Now that you have a file, navigate to a folder and start to create a Document.

3. For the first screen, enter a number, title, etc… the info entered here is not important. Click Next.

4. On the Keywords screen, just click Next.

5. Now on the file screen, click Browse and locate your test file. After you've selected it, click Open.

6. Next you'll click the OK button. Verify that you are presented with a progress bar that shows you the status of the file upload. Keep in mind, if your network connection to the Document Manager has a lot of band width, your upload may appear to complete almost instantly. If this happens and you wish to see the progress bar in action, create another Document with a larger file.

7. Delete your test Document.

Results: Now you can see the progress when uploading files. Correct Initials

Y N

Comments:



DM-545 – Add Nonresident URL to Generation

Nonresident Generations can now have a Nonresident URL assigned to them. DM's and SM's now use this Nonresident URL as the fetch URL so that the Generation can be fetched from its non-TechDoc location.


1. Navigate to a Folder and start to create a Document. On the first screen, you can enter any info you want, but set Resident Document to No. Enter a reason and click Next.

2. On the Keywords screen, just click Next.

3. Now on the last screen, enter a URL to a file somewhere else. The URL can be a link to a PDF file on another website, an image on another website, it's up to you. If you cannot think of a URL to use, you may use the URL from the previous test item. http://docubrain.com/sites/default/files/examples/TechDoc8AcceptanceTestPlanPoem.vsd Once you have entered a URL, click OK.

4. Now you should be looking at the Document. Verify that the Generation's title is the URL you entered during the create process. Try to click on the URL and see it loads the page or content you'd expect.

5. Now select the Generation and click Modify on the side menu.

6. Change the URL to be something else. Again it can be an image, PDF, it's up to you. Once you have modified the Generation, click OK.

7. Again you should be looking at the Document. Verify that the Generation's title now displays the new URL. Also make sure when you click on the URL, it loads the content you'd expect.

8. You may delete your test Document.

Results: Now Nonresident Generations have a URL that can be used to fetch the Generation from a non-TechDoc location.

Correct Initials

Y N

Comments:





DM-546 – Add Navigation Crumbs to the Explorer

Navigation crumbs have been made available in the Explorer. The full path to the Cabinet, Folder, or Document is still displayed in the heading, but now TechDoc makes all the components in the full path clickable (similar to the portions of the path being clickable in the Windows Explorer). Also, when focused on a generation, TechDoc now displays the parent folder above the document. It only takes up one line and but make navigate back to the parent folder easier.


1. To test this item, you'll just want to navigate around in the Explorer. First navigate to the root of the Document Manager and see that only a / is displayed in the navigation crumbs.

2. Click into a Cabinet. Now the crumbs should display / and the name of the cabinet. Click on the / crumb.

3. Now you should again be at the root of the Document Manager. Navigate into a Cabinet and down into a Folder. Verify that the crumbs display a /, the name of the Cabinet, and the name of the Folder. Click on the Cabinet name crumb.

4. Now you should be in the Cabinet you clicked on the crumbs.

5. Click around a bit more navigating deeper and deeper into Folders and use the crumbs to jump back to the top. Verify that each time you click a crumb that you end up focused on the correct Cabinet or Folder.

Results: Now you can use navigation crumbs to navigate easier and quicker and the Explorer.

Correct Initials

Y N

Comments:



DM-547 – Add Revision as a Column in the Explorer

By popular demand, the Revision column has been added in the explorer. With the new changes for the action gear, it really makes sense to be able to see the revisions on documents and generations.


1. Navigate to a Folder and create a Document.

2. After creating the Document, you should be focused on it. Click the action gear next to the info icon and select Release.

3. Select the Generation to release, enter a revision, enter a reason, and then click Next. Click OK to release the Document.

4. Again you should be focused on the Document. Verify that the Rev column now contains the revision you entered when releasing the Document. Also notice that the revision is displayed on the Generation.

Results: Revision now appears as a column in the Explorer. Correct Initials

Y N

Comments:



DM-548 – Add an Action Gear to Various Brief Items

Action gears have been added to various brief items. The purpose of an action gear is to query the system at the time the user click on it and display a popup menu of available actions the user can perform on the item the action gear belongs to.


1. For this test, we won't create or modify any Cabinets, Folders, or Documents. Instead we will just navigate around a bit and see what all you can do with the action gear. Navigate to a Cabinet and select it. Once selected, click the action gear and choose an option from the menu.

2. Verify you were taken to the operation you clicked. Now click the back button on your browser.

3. You should be focused on the same Cabinet again. Click a Folder in that same Cabinet to navigate into it.

4. You should now be focused on that Folder. Notice how the gear still appears next to the Cabinet. Click the gear next to the Cabinet and choose an operation.

5. Verify that you were taken to the operation you selected. Notice that the operation is also targeted at the Cabinet. Unlike the side menu that only targets the currently selected item, the gear targets the Cabinet, Folder, or Document that it appears next to. The action gear makes navigation much quicker and a lot simpler.

6. Navigate around in the Explorer a bit more and test out a few more operations on the action gear menus.

Results: Now you can use the action gears to quickly perform operations without having to navigate to and select the target item.

Correct Initials

Y N

Comments:



DM-549 – Add Web 2.0 Widgets to TechDoc

Web 2.0 widgets have been added to TechDoc to improve usability. Examples include: Date and Date/Time widgets, Editable Combo Boxes for searching items by wildcard or drop down selection, and email widgets (which are tested under another issue).


1. Create a test resident Document; the information entered is not important. After creating the Document, release it.

2. Navigate to and select the Document. Select the Generation under the Document and then click Modify Release Date on the side menu.

3. Verify that the old release date matches the preset new release date.

4. Using the Date/Time widgets, set a new date and time. Verify that you can both enter numbers into the field and also click the down arrows to select from the calendar or time list. After entering a new release date, enter a reason and click OK.

5. You should now be focused on the Generation. Click the info icon next to the Generation.

6. Verify the release date matches that which you entered in the previous step.

7. You may delete the test Document.

8. Click Advanced Search on the Main Menu.

9. You should now be looking at the Advanced Document Search. Scroll down to the bottom and select a Keyword to add. The Keyword added should be a Drop Down Keyword with a Number, String, or URL data type.

10. Now that you've added the Keyword, verify that you can just click into its value field and start typing. Verify that you can also click the down arrow to view the available choices for that drop down. This gives a bit more flexibility when searching. Say for instance that you had 1000 entries in the list that were company names. You knew the company started with "gra" but you didn't know for sure which company in the list was the right one. Using this new feature you could just enter "gra*" to search all the companies starting with "gra" since you are no longer forced to just select one from the list.

Results: Now you can use the Web 2.0 widgets to navigate a bit easier and leverage a little more flexibility when searching.

Correct Initials

Y N

Comments:



DM-550 – Add Change Password Feature for Improved Security and Usability

For improved security, locally authenticated users can change their password without having to first enter their current password. The password changing logic in the "Modify Myself" servlet has been removed and a new "Change Password" servlet has been added which requires the old and new passwords to be entered before the change can take place. If your account is not locally authenticated by TechDoc, you can skip this test.


1. Click My Work and click Change Password on the side menu.

2. On the Change Password screen, enter the old password for your test account.

3. Now enter a new password and then verify it in the New Verify box. Be sure you remember the password!

4. Now click OK to complete the password change.

5. Click Log Out on the Main Menu.

6. Now log in using your new password and verify that your old one no longer works.

Results: Now on your own, you can easily change your password. Correct Initials

Y N

Comments:



DM-551 – Improve Review Vote Request Subject on Email

The subjects have been improved on emails that are sent to voters to be more user-friendly. Here are examples of the four email subjects that have been improved: Your vote is requested on the review of PHOTO-123, Rev A, "Test Photo" Voting has been paused on the review of PHOTO-123, Rev A, "Test Photo" Voting has resumed on the review of PHOTO-123, Rev A, "Test Photo" Your vote is no longer needed on the review of PHOTO-123, Rev A, "Test Photo" You must have the Review Leader privilege to complete this test.


1. Create a document; none of the settings is important.

2. On the side menu, click Create Review.

3. When creating the review, don't pick a review team, type A for the Revision, choose No for Allow Reserve and Replace, choose No for Allow Open Posting, enter some text for the Voter Instructions, enter a reason, and click OK.

4. On the side menu, click Create Level to create level 1.





9. On the side menu, click Create Level again to create level 2.





14. Click Review Info on the side menu.

15. Click Start on the side menu, enter a reason, and click OK.

16. Click Pause on the side menu, enter a reason, and click OK.

17. Click Resume on the side menu, enter a reason, and click OK.

18. Click Promote on the side menu, enter a reason, and click OK.

19. You can now delete the review and the document.



20. Use your email client to review the emails sent by this test to see that the subjects of the emails are now formatted similar to the subjects shown at the beginning of the test.

Results: The subjects on the review emails are now more user-friendly.

Correct Initials

Y N

Comments:



DM-552 – Add Support for Visio 2013 Thumbnails

Visio 2013 has introduced a new XML format (VSDX) that finally compares to the XML formats introduced by other Office products in previous versions. Thumbnail support has been added for this new format. In order to test this functionality, you must have a Microsoft Visio 2013 document saved in the VSDX format that has a preview thumbnails embedded in it. An example that can be used is available at http://docubrain.com/sites/default/files/examples/TechDoc8AcceptanceTestPlanPoem.vsdx or you may choose to use your own file that meets the requirements.


1. Create a document using a Visio 2013 VSDX file that contains a thumbnail. Make sure to use a Doc Type that sends thumbnails, set Web Search to Community, and make sure Community has read access to the document.



4. Go to the SM and search for your document.

5. On the search details screen, the thumbnail should be displayed.

Results: Correct Initials

Y N

Comments:

http://docubrain.com/sites/default/files/examples/TechDoc8AcceptanceTestPlanPoem.vsdx




DM-553 – Add Support for Visio 2013 Text Extraction

Visio 2013 has introduced a new XML format (VSDX) that finally compares to the XML formats introduced by other Office products in previous versions. Text extraction support has been added for this new format. In order to test this functionality, you must have a Microsoft Visio 2013 document saved in the VSDX format. An example that can be used is available at http://docubrain.com/sites/default/files/examples/TechDoc8AcceptanceTestPlanPoem.vsdx or you may choose to use your own file that meets the requirements. The example flowchart contains the poem "Do Not Go Gentle into That Good Night" by Dylan Thomas broken into different shapes.


1. Create a document using a Visio 2013 file with the VSDX extension that contains some text. Make sure to use a Doc Type that sends text, set Web Search to Community, and make sure Community has read access to the document.



4. Go to the SM and search for your document using different words or phrases.

Results: Visio VSDX text extraction is now supported by TechDoc. Correct Initials

Y N

Comments:





DM-554 – Add Compose Email to Document, Generation, and Project

A new Compose Email capability has been added to the Document, Generation, and Project. The feature also allows easy selection of users and groups, rich text editing, and inclusion of various hyperlinks applicable to the item that the email is being created for.


1. Create or navigate to and select a Document. After selecting the Document, click Compose Email on the side menu.

2. Using the Compose Email screen, send yourself an email. Be sure to click and try out the To… and CC… buttons. Also try out some of the editor's features; try out the clipboard, text formatting, alignment, etc… Select a few of the links at the bottom of the screen and then click Send.

3. Verify that you receive the email and it appears formatted as you composed it. Note that it can several minutes to receive the email if your network is busy.

4. Optionally, navigate to a Generation, click Compose Email on the side menu, and compose an email for the Generation.

5. Optionally, create or navigate to a Project, click Compose Email on the side menu, and compose an email for the Project.

Results: You are now able to compose an email for a Document, Generation, or Project using a Web 2.0 email widget.

Correct Initials

Y N

Comments:



DM-555 – Fix Report Problem with Order by and Multiple Virtual Columns

If a user specified multiple virtual columns to display, a non-virtual column to display, and then ordered on the non-virtual column, it resulted in a SQL error. TechDoc only has a couple of tables that even have more than one virtual column. Now that individual Keywords can be added as virtual columns to a Document report, it's very easy to test.


1. Click Reports on the Main Menu and then click Create on the side menu.

2. Enter a name and description for the Report. Select Documents for the Table and then click Next.

3. Select and Add ID, Keywords, and few of the individual Keywords from the bottom of the list. Click Next.

4. On the Order By screen, select ID and click Add. Click Next

5. On the Limit Results screen, enter a bit of criteria to limit results returned and then click Next.

6. On the Preview/Save screen, click the Preview As HTML link.

7. Verify that the report looks as though you'd expect and then close that popup window.

8. You should still be focused on the Preview/Save screen. Just click Cancel to cancel the creation of the Report. If you have already clicked OK to create the Report, just navigate to the Report and delete it.

Results: Now you can create Reports with virtual and non-virtual columns ordering by virtual columns without issue.

Correct Initials

Y N

Comments:



DM-560 – Add Document Default Associations to a Folder

Document default associations can now be applied to a folder. These associations are then automatically added to documents when they are created. In addition, when document default associations are changed on a folder, the user can decide to change the current associations on documents under the folder; they are also given options about how the changes should be applied (merged, overridden, or completely replaced).


1. Create a test Folder. The information entered for the Folder does not matter.

2. Now navigate to the Folder, select it, and select Doc Default Access on the side menu.

3. Enter a reason and click Next.

4. On the Groups screen, click Next.

5. On the Users screen, select a User, check the Modify box, and then click Add. Click Next.

6. Finally click OK to complete the association.

7. You should be focused on your test Folder now, click Create Folder on the side menu.

8. For this sub Folder, enter any information you want and then Click OK.

9. You should now see a message saying Folder successfully created.

10. Navigate to the Folder you just created, select it, and then select Show… Associations on the side menu.

11. Verify that this Folder was automatically given the Document Default Access setting for the User you selected with Modify access.

10. Navigate to the first Folder your created, select it, and then select Doc Default Access on the side menu.

11. This time, for the Folder Inheritance setting, select "Replace child folder…", enter a reason, and then click Next.


13. On the Users screen, remove the User you gave access to previous and add a different User with Delete access. Click Next.

14. Click OK to complete the association.

15. Navigate to the sub Folder you created, select it, and then click Show… Associations on the side menu.

16. Verify that the Document Default Access on this folder has been replaced and the previous User is now gone and the new User is present with Delete access.

17. Now create a Document in this Folder; the information entered for the Document is not important.

18. Navigate to and select the Document, and then click Show… Associations on the side menu.



19. Verify that the User you selected in the previous with Delete access was set for you by default.

20. Finally, navigate to and select the original Folder. Select Doc Default Access on the side menu.

21. This time, for the Document Inheritance field, select "Replace child documents…" Enter a reason and then click Next.


23. On the Users screen, select the User you added in the previous step and remove them from the list. Click Next.


25. Now navigate to the Document you created, select it, and select Show… Associations on the side menu.

26. Verify that User that was present before with Delete access is now gone because you replaced all of the child Document associations on the parent Folder.

27. View the servlet help for Document Default Access and test the other inheritance fields in the same manner we've described here. See how the Override and Merge settings work.

28. Delete your test Folders and Documents.

Results: Now you set Document Default Associations on a Folder and have child Documents automatically receive those settings.

Correct Initials

Y N

Comments:



DM-561 – Add Access and Mail List Inheritance for Folders

When a folder is created inside of a parent cabinet/folder, it inherits all of the parents associations. When associations are changed on a cabinet/folder, the user is now given the option to apply the changes to the children below it. If they wish to make changes to the children below; they are also given options about how the changes should be applied (merged, overridden, or completely replaced).


1. Create a test Folder. The information entered for the Folder does not matter.

2. Now navigate to the Folder, select it, and select Assoc Access on the side menu.

3. Enter a reason and click Next.


5. On the Users screen, select a User, check the Modify box, and then click Add.

6. Finally click OK to complete the association.

7. You should be focused on your test Folder now, click Create Folder on the side menu.

8. For this sub Folder, enter any information you want and then Click OK.

9. You should now see a message saying Folder successfully created.

10. Navigate to the Folder you just created, select it, and then select Show… Associations on the side menu.

11. Verify that this Folder was automatically given the Access setting for the User you selected with Modify access.

10. Navigate to the first Folder your created, select it, and then select Assoc Access on the side menu.

11. This time, for the Folder Inheritance setting, select "Replace child folder…", enter a reason, and then click Next.


13. On the Users screen, remove the User you gave access to previously and add a different User with Delete access.


15. Navigate to the sub Folder you created, select it, and then click Show… Associations on the side menu.

16. Verify that the Access on this Folder's access has been replaced and the previous User is now gone and the new User is present with Delete access.

17. View the servlet help for Associate Access and test the other inheritance fields in the same manner we've described here. See how the Override and Merge settings work. Also perform these same tests for the Associate Notification servlet.

18. Delete the rest of your test Folders created during this test.



Results: Now you can set the Access and Mail settings on a Folder for child Folders to inherit.

Correct Initials

Y N

Comments:



DM-562 – Change OK Button for Quick Search on Main Menu to an Image

Multiple reports were received of people mistakenly clicking the OK button for the Quick Search on the Main Menu bar instead of clicking on the OK button inside the main content area. The Quick Search OK button has been changed to use an image instead.


1. For this test, you can be on any screen in the Document Manager.

2. In the Quick Search field, select Document and then enter the Document Number of a Document you know exists.

3. Click the arrow image next to the search field and verify that it takes you to the Document just as the old OK button would.

Results: Now the Quick Search's button does not look like a normal OK button.

Correct Initials

Y N

Comments:



DM-563 – Add Release to a Generation

A release option has been added to a generation's side menu. Users have complained that it is annoying to have to navigate back to the document to release the generation. Also, a generation's action menu will have the feature too (when appropriate).


1. Create a test resident Document; the info entered for the Document does not matter.

2. After creating the Document, you should be focused on the Document. Click the Generation listed below the Document.

3. Now that the Generation is selected, click Release on the side menu.

4. Complete the Release process and verify that you are now able to release a Generation using the side menu while being focused on the Generation you want to release.

5. If you plan to perform the next test (DM-564), do not delete this test Document as you will need it. If you do not plan to continue testing any further, you may delete the Document.

Results: Now you are able to release a Generation from its side menu.

Correct Initials

Y N

Comments:



DM-564 – Add Unrelease to a Generation

An unrelease option has been added to a generation's side menu. Users have complained that it is annoying to have to navigate back to the document to unrelease the generation. Also, a generation's action menu will have the feature too (when appropriate).


1. If you kept the test Document from DM-563, skip to step 2. If you do not have the test Document from DM-563, create and release a resident Document. The information entered for the Document does not matter.

2. Navigate to and select your test Document.

3. Click the Generation listed under the Document to select it.

4. Now click Unrelease on the side menu and complete the unrelease process.

5. Verify that you are able to now unrelease a Generation by selecting the Generation you want to unrelease and using the Generation side menu.

6. Delete your test Document.

Results: Now you are able to unrelease a Generation from its side menu.

Correct Initials

Y N

Comments:



DM-567 – Rename Lists to Groups

Lists have been renamed to groups to match the terminology of most other systems. The word List has been very confusing for users because everyone thinks of the term as a generic list of things.


1. Click Groups on the Main Menu.

2. Verify that you are taken to the "Groups" area of the Document Manager.

3. Verify that all of your former Lists appear exactly the same (with the only change being that they are now referred to as Groups).

4. Create and modify a couple test Groups and see that the process is still the same.

8. Delete any test Groups you created.

Results: Lists are now referred to as Groups. Correct Initials

Y N

Comments:



DM Records Manager Testing The following test cases can only be performed by a user with the Records Manager privilege on a Document Manager.



DM-456 – Add an RMA Cutoff Date (Retention Start Date) per CR 21419

Prior to TechDoc 8, TechDoc always used the Release Date of a document as a hardcoded cutoff date. Flexible Cutoff column support has been added to the RMA File Plan to determine what column or keyword should be used as the Cutoff Date. In addition, an optional Cutoff Trigger keyword has been added to the RMA File Plan. If specified, the specified keyword and optionally the value must be present in addition to the Cutoff Date being set to trigger the fact that retention should actually be started.


1. Click Records on the Main Menu and select RMA Keywords under Show…

2. Look for a Keyword called Incident_Date. If it does not exist, click Create on the side menu, enter Incident_Date for the name, enter "The date the incident occurred." without the quotes for the description, choose Free Form for the Input Type, choose Date for the Data Type, enter a reason, and click OK.

2. Look for a Keyword called Incident_Closed. If it does not exist, click Create on the side menu, enter Incident_Closed for the name, enter "Has the incident been closed." without the quotes for the description, choose Drop Down for the Input Type, choose String for the Data Type, enter a reason, click OK, enter Yes for New Valid RMA Keyword Value, click Add, enter No for New Valid RMA Keyword Value, and click OK.

3. Click Records on the Main Menu and select RMA File Plan under Create…

4. Enter a name, identifier, and description, select No for Permanent Records and Vital Records, leave Review Period empty, enter 5 years for Retention Period, select Doc Create Date for the Cutoff Date Source, enter a reason, and then click Next.

5. Leave Cutoff Trigger Source set to None and click Next.

6. Click OK and take note of the name of the RMA File Plan that you created.

7. Click Explorer on the Main Menu, navigate to a place where you wish to make a Folder (if necessary), and then click Create Folder on the side menu.

8. Enter a name, description, select your RMA File Plan in the dropdown, enter a reason, and click OK.

9. Click OK to leave the access as is.

10. Optionally, click Set Default on the side menu to make this folder your default folder during testing. This will make navigation easier.

11. Now create two or three documents in the folder that you just created; none of the attributes is important.

12. Release one of the documents and choose not to render it (if given the option).



13. Click on the "i" icon for the folder to show its information, click on the hyperlink for the RMA Record Set listed in the info, and then click Show Records on the side menu.

14. Note that each Document has an RMA Record and that all of the RMA Records have a cutoff date and retention date.

15. Click Show Info on the side menu, click on the hyperlink for RMA File Plan listed in the info, and click on Modify.

16. Change the Cutoff Date Source to Doc Release Date, enter a reason, click Next, click Next, and click OK.

17. Navigate back to the folder, show the info on the folder, click on the hyperlink for the RMA Record Set listed in the info, and then click Show Records on the side menu.

18. Note that each Document has an RMA Record but only the released Document has a cutoff date and retention date now.

19. Click Show Info on the side menu, click on the hyperlink for RMA File Plan listed in the info, and click on Modify.

20. Change the Cutoff Date Source to Record Set Keyword Date, enter a reason, and click Next.

21. Choose Incident_Date for the Cutoff Date Keyword, choose Record Set Keyword for Cutoff Trigger Source, and click Next.

22. Choose Incident_Closed for the Cutoff Trigger Keyword, enter Yes for the Cutoff Trigger Value, and click OK.

23. Navigate back to the folder, show the info on the folder, click on the hyperlink for the RMA Record Set listed in the info, and then click Show Records on the side menu.

24. Note that each Document has an RMA Record but none of them has a cutoff date or retention date now.

25. Click Modify on the side menu, enter a reason, and click Next.

26. Choose Incident_Date for the New RMA Keyword, and click Add.

27. Enter a date other than today for Incident_Date, make note of the date you used, and click OK.

28. Click Show Records on the side menu and note that each Document has an RMA Record but none of them still has a cutoff date or retention date.

29. Click Modify on the side menu, enter a reason, and click Next.

30. Choose Incident_Closed for the New RMA Keyword, and click Add.

31. Choose Yes for Incident_Closed and click OK.

32. Click Show Records on the side menu and note that each Document has an RMA Record, the cutoff date is the date that you used for Incident_Date, and the retention date is the cutoff date plus 5 years.

33. You can now delete the documents, the folder, and the RMA File Plan that you used for this test (in that order). There is no need to delete the RMA Keywords you possibly created for this test.



Results: TechDoc now has RMA Cutoff Date support with an optional trigger and you can see the effect it has on the cutoff and retention dates.

Correct Initials

Y N

Comments:



DM Workflow Manager Testing The following test cases can only be performed by a user with the Workflow Manager privilege on a Document Manager.



DM-531 – Add BPMN 2.0 Workflow Support to TechDoc

A BPMN 2.0 workflow engine has been added to TechDoc. The workflow engine can automate business processes that don't even involve document management. Many TechDoc-specific service tasks have been added to support document management workflows. In addition, workflows can be triggered by specific commands. A WYSIWYG BPMN 2.0 editor has been adapted to work with TechDoc to allow users to graphically create a workflow and then deploy it to TechDoc.


1. Before testing Workflow support, first make sure you have the Workflows privilege. The easiest way to tell if you have the Workflows privilege is to log into the Document Manager and see if you have a Workflows link on the Main Menu. If you do not, you will need to skip this test or request this privilege to perform this test.

2. The first step in Workflow is creating a process. The creation of a Workflow process is very involved and requires in depth knowledge of the BPMN 2.0 specification and use of BPMN design tools. To make this a bit easier, we have created an example workflow process that can be downloaded from http://docubrain.com/sites/default/files/examples/TechDoc8AcceptanceTestPlanWorkflowExample.bar Download the example workflow process.

3. The file you downloaded is a BAR file, which stands for Business Archive. It is simply a renamed zip file that contains one or more Workflow process .bpmn files. To get the example process into TechDoc, log into the Document Manager, click Workflows on the Main Menu, and click Create Deployment on the side menu. Enter a Deployment name, reason, and click Next. Now click the Browse button, navigate to the BAR file you downloaded, and click OK. Now click OK to create the Deployment.

4. Now you've deployed the BAR's Workflow processes to the Document Manager. You should be looking at the Workflow Deployment info screen displaying the process definition TD8AcceptanceTestExample. This is the example process we're going to be testing with. Verify that this example process is listed on the Workflow Deployment info screen.

5. In order to actually run the Workflow process, you need to create a Workflow Process Trigger. Triggers are the way that processes are executed. Triggers can be set to execute a particular process in many ways… when a Document is created that contains a particular keyword, when a Document is modified, etc… There are many ways. What we want to do is create a Trigger that just says I'm going to start the process manually when I'm ready. Click Workflows on the Main Menu, and then click Create Process Trigger on the side menu. Give your Trigger a name, choose for the command Start Process (meaning you'll just start it when you're ready), select the example process

http://www.omg.org/spec/BPMN/2.0/

http://www.omg.org/spec/BPMN/2.0/

http://docubrain.com/sites/default/files/examples/TechDoc8AcceptanceTestPlanWorkflowExample.bar

http://docubrain.com/sites/default/files/examples/TechDoc8AcceptanceTestPlanWorkflowExample.bar



from the drop down (it should be labeled something like TD8AcceptanceTestExample: and some numbers), enter a reason, and then click OK.

6. Now you have a deployed Workflow process and created a trigger to start it. The next step is to create a test Document to run the Workflow against.

7. After the Document is created, view its info and verify all if its information. Note that it is not reserved.

8. Now while the Document is selected, click Start Process from the side menu. This command is used to say that you want to execute a process against the current Document. When the Start Workflow Process screen displays, select the Process Trigger you created in step 5, enter a reason, and click OK.

9. You should be looking at the Show Workflow Process Instance Info screen. This screen will display to you the currently running process, the process diagram, etc. Most of the time however, for short processes you will be presented with a message saying the Process Instance has already been completed.

10. After the Process has completed, navigate back to the Document and verify that it is now reserved. The example Workflow Process is very simple; it simply takes the current Document and Reserves it. Workflow Processes can be very complex and perform a huge array of operations, but for this test we chose to keep it simple.

11. You may now navigate to, select, and then delete the test Document.

12. Click Workflows on the Main Menu and then click Show… Process Triggers. Select and Delete the Process Trigger you created.

13. Click Workflows on the Main Menu and then click Show… Deployments. Select the Deployment you created and delete it.

Results: TechDoc now supports BPMN 2.0 workflows. Correct Initials

Y N

Comments:





DM Admin Testing The following test cases can only be performed by a user with the Admin privilege on a Document Manager.



DM-486 – Allow Modify Remote Email with One That Already Exists

Modify Remote Email has been enhanced to allow a remote email to be specified that already exists in the system. This would allow the following situation to be handled: Consider that a DM has the remote emails [email protected] and [email protected] used. Both emails were considered valid and referred to the same person. However, now you want to decommission the first email and have it replaced everywhere it occurs by the second email. This change allows the remote emails to be "merged" into one.


1. Create a test Folder, the information entered does not matter.

2. Navigate to and select the Folder, then click Assoc Notif on the side menu.

3. Enter a reason and click next.

4. On the Groups screen, click Next. On the Users screen click Next.

5. On the Remote Emails screen, enter a test email address and then click Add. The email address entered does not have to be a real address.

6. After adding the first address, enter a second email address and click Add. It may be helpful to use a similar address as the first address. For example, if you entered [email protected] you may want to enter [email protected] to distinguish the two.


8. Click Admin on the main menu and then click Remote Emails under the Miscellaneous column.

9. Verify that both of the email addresses entered in steps 5 and 6 are listed. Click the first email address entered and then click Modify on the side menu.

10. In the modify box, enter the "new" email address (the second email you entered in step 6) and then click OK.

11. Verify that you receive a message telling you the two addresses cannot be merged unless the option is checked. Now check the "Allow email address…" checkbox and then click OK.

12. Verify that you receive a message saying the two addresses have been merged. Click Admin and click Remote Emails under the Miscellaneous column.

13. Verify that only the newer email (from step 6) is now listed and the original email (from step 5) is gone.

14. Navigate to and select your test Folder. Click Show… Associations on the side menu. Verify that now only the newer email is listed as an Association.

15. You may delete your test Folder.

Results: Now you have the ability to merge Remote Emails. Correct Initials

Y N

mailto:[email protected]

mailto:[email protected]



Comments:



DM-491 – Add System Property to define which hyperlinks and generations that Status and Retrieval display

The ability to change what the Status and Retrieval servlet will display has been added to avoid potential ISO audit findings. A new drop down system property called "StatusRetrievalFetch" has been added to limit what generations of a document are shown on the screen.


1. Create a test Document, the information entered does not matter.

2. Now Reserve and Replace the Document to create an additional Generation.

3. Finally Release the Document. If asked to Render the Generation, choose no.

4. Navigate to the Status and Retrieval display by navigating to and selecting the Document, and then clicking Show… Links on the side menu. On the Document Links screen, click GO on the Show Status/Retrieval link.

5. On the Document Status screen, look at the bottom and see that all of the links for the Generations you've created are listed.

6. Open another browser tab and navigate into the Document Manager. Click Admin on the Main Menu, and then click System Properties under the Miscellaneous column.

7. Scroll down to the StatusRetrievalFetch property to see its current setting. The setting defaults to "All Fetchable and Shown" to say just show you all of the Generation links. Change this setting to "Latest Release Fetchable, No Others Shown" and then scroll to the bottom, enter a reason and click OK.

8. Switch back to your other browser tab that should still be on the Document Status screen and perform a refresh (usually done by clicking a reload button or pressing F5).

9. Verify that now only the latest Generation is shown and the other is not.

10. Flip back to the System Properties screen on the other tab and select a different option for the StatusRetrievalFetch property and save it. Then flip back to the Document Status tab, refresh and see that the links listed correspond to the setting you picked.

11. Navigate back to the System Properties screen and set the StatusRetrievalFetch property back to what it was originally.

12. Navigate to and delete your test Document.

Results: Now you can use the StatusRetrievalFetch System Property to define the hyperlinks and generations shown on the Status and Retrieval display.

Correct Initials

Y N



Comments:



DM-493 – Update TechDoc to use Tomcat 7

TechDoc has been updated to use Tomcat version 7. TechDoc was using Tomcat 5.5, which will not be supported for much longer.


1. Click Admin on the main menu.

2. Click System Info in the Miscellaneous menu.

3. Scroll down to the Servlet Engine Information section.

4. Note that the Engine Info shows Apache Tomcat/7.0.40.

5. Note that TechDoc appears to be functioning well on previous tests.

Results: TechDoc is running the new version of Tomcat and appears to be functioning well.

Correct Initials

Y N

Comments:



DM-494 – Upgrade DM to use new JRE for TechDoc 8

The JRE (Java Runtime Environment) used by TechDoc has been upgraded to support 64-bit. This allows TechDoc to take advantage of automatic performance improvements and larger memory support.




3. Scroll down through the Java System Properties section.

4. Note that the os.arch property shows amd64.


Results: TechDoc is running the 64-bit version of Java and appears to be functioning well.

Correct Initials

Y N

Comments:



DM-526 – Update the DM Default Authenticator System Property to Document the Impact on SSO

The description on the DM's DefaultAuthenticator system property has been updated to make it obvious that choosing an SSO (Single Sign-On) authenticator such as the SAML authenticator will cause the DM to automatically use SSO for log in requests.



2. Click System Properties in the Miscellaneous menu.

3. Scroll down to the DefaultAuthenticator system property.

4. Note the description mentions the impact on SSO.

5. Scroll to the bottom and click Cancel.

Results: Now, the DM's DefaultAuthenticator system property describes the impact on SSO.

Correct Initials

Y N

Comments:



DM-533 – Adjust Memory Allocated to Tomcat during DM Installation

As TechDoc moves to 64-bit environments and larger systems, Tomcat needs to automatically take advantage of the larger resources available. Starting with TechDoc 8, the installer attempts to allocate reasonable memory limits to Tomcat based on available resources rather than assigning a small "should run" everywhere setting.




3. Look in the System Specific Information section.

4. Note the size shown for the JVM Max Memory setting. Prior to TechDoc 8, the setting would always be 512 MB unless manually changed by a system administrator. Most servers will show a value larger than that now.

Results: The installation process now tries to calculate a reasonable size for the maximum memory that Java is allowed to use. Most systems will have a size larger than 512 MB now.

Correct Initials

Y N

Comments:



DM-556 – Add Ability to get Document Statistics

Many requests have been received to find out how many documents, how many generations, or how much space is being taken by documents with various characteristics. A new Document Statistics feature has been added that can quickly allow Admins to determine these types of usage statistics.


1. Click Admin on the Main Menu and then click Doc Statistics under the Miscellaneous column.

2. On the Document Statistics screen, you are basically performing a search. For instance, if you have created some Documents on this machine, click the Owner drop down, select yourself, and then click Get Stats.

3. Look at the Document Search Results to see how many Documents and Generations you own, and the total amount of disk space they take up.

4. Try a few other searches and look over their output. Maybe search for all of the Documents of a specific Document Type or Organization.

Results: Now you have the ability to get Document Statistics. Correct Initials

Y N

Comments:



DM-558 – Add Partition Information to File Areas on the DM

Partition information has been added to the File Area displays. Previously, a TechDoc Admin would usually have to contact systems people to see how large the partition is where the File Area is stored.


1. Click Admin on the Main Menu and then click File Areas under the Show… column.

2. There should be at least one File Area listed, click it.

3. On the File Area Info screen, verify that you can see the Available Space, Reserved Space and now also the Partition Free Space and Total Space.

Results: Now you can also see the Partition Free Space and Total Space.

Correct Initials

Y N

Comments:



DM-577 – Change Default Submit Order on Resubmit All Documents

The default order on the Resubmit All Documents to an SM command has been changed. Previously, they were resubmitted in whatever order they are returned from the database. Now the "Newest Documents First" order is the default, which seems to make since for most use cases. Also, while making this change, the language for the "are you sure" messages was strengthened so that the requester better understands the impact of their actions. Do NOT click OK during this test! There is no need to actually perform the resubmit all.


1. Click Admin on the Main Menu and then click Resubmit All Documents under the Search Manager column.

2. On the Resubmit All Documents screen, read over the message and see that it has been restructured so the user will better understand that impact of their actions.

3. Click the Order drop down and see that you now have the choice to say Resubmit newer Documents first or older Documents first.

4. After you have verify, everything on the Resubmit screen, click Cancel so you do *NOT* perform a resubmit all.

Results: Now Resubmit All Documents has a stronger message and defaults to submitting newer documents first.

Correct Initials

Y N

Comments:



SM User Testing This release of TechDoc does not have any test cases that would be performed by a normal user only using the normal search pages on the search manager.



SM Admin Testing The following test cases can only be performed by a user with the Admin privilege on a Search Manager.



SM-97 – Add Advanced Search and Quick Search to the SM

While working on the SM Admin Help, it was noticed that some SM history was not discoverable because of the lack of Advanced Search like the DM has. Advanced Search has been added to the SM. Also, to allow for the same look and feel to the screens between the DM and the SM, Quick Search was added to the SM as well. In this release, the SM's Quick Search will only provide quick searches for users.


1. Log into the Search Manager and click Advanced Search on the Main Menu.

2. Verify that you are taken to the Advanced Search screen and then click History on the side menu.

3. Perform a History Search. Select a Target Type of User, enter your username for the Target Name, and then click OK.

4. You should see the History Results for your username and all of the actions you have performed. If you just logged into the Search Manager and went straight to Advanced Search, you should see a Logged In Action close to the top. Click on a few of the History Results listed and see their output.

5. On the Main Menu, in Quick Search, select User. Enter your username and then click the button to perform a Quick Search.

6. Verify since usernames are unique, if just finds a single result and shows the User Info for your account.

8. Try a few other Quick and Advanced Searches and review their output.

Results: Now the SM has Advanced Search and Quick Search functionality.

Correct Initials

Y N

Comments:



SM-98 – Upgrade SM to use new JRE for TechDoc 8

The JRE (Java Runtime Environment) used by TechDoc has been upgraded to support 64-bit. This allows TechDoc to take advantage of automatic performance improvements and larger memory support.




3. Scroll down through the Java System Properties section.

4. Note that the os.arch property shows amd64.


Results: TechDoc is running the 64-bit version of Java and appears to be functioning well.

Correct Initials

Y N

Comments:



SM-101 – Update the Look and Feel of the SM

The Look and Feel of TechDoc was very out dated. The color schemes and all the icons have been updated. Also, layouts have been changes to allow for more compact display of various items.


1. Log into the Search Manager. Verify that the Admin screen is presented in the same format as before only now in a more modern blue color scheme.

2. Click File Areas under the Show… column. Verify that a new icon is displayed.

3. Back up to the Admin screen and click Users on the Show… column. Verify that Users now have new icons as well.

4. Click around through the Search Manager and explore some of the screens. Only the look and feel has been updated, functionality and the location of everything have stayed the same.

Results: Now the Search Manager's look and feel is much more modern.

Correct Initials

Y N

Comments:



SM-105 – Update the SM Default Authenticator System Property to Document the Impact on SSO

The description on the SM's DefaultAuthenticator system property has been updated to make it obvious that choosing an SSO (Single Sign-On) authenticator such as the SAML authenticator will cause the SM to automatically use SSO for log in requests.



2. Click System Properties in the Miscellaneous menu.

3. Scroll down to the DefaultAuthenticator system property.

4. Note the description mentions the impact on SSO.

5. Scroll to the bottom and click Cancel.

Results: Now, the SM's DefaultAuthenticator system property describes the impact on SSO.

Correct Initials

Y N

Comments:



SM-107 – Adjust Memory Allocated to Tomcat during SM Installation

As TechDoc moves to 64-bit environments and larger systems, Tomcat needs to automatically take advantage of the larger resources available. Starting with TechDoc 8, the installer attempts to allocate reasonable memory limits to Tomcat based on available resources rather than assigning a small "should run" everywhere setting.




3. Look in the System Specific Information section.

4. Note the size shown for the JVM Max Memory setting. Prior to TechDoc 8, the setting would always be 512 MB unless manually changed by a system administrator. Most servers will show a value larger than that now.

Results: The installation process now tries to calculate a reasonable size for the maximum memory that Java is allowed to use. Most systems will have a size larger than 512 MB now.

Correct Initials

Y N

Comments:



SM-112 – Fix Cross Site Scripting (XSS) Finding Reported on the SM

A possible Cross Site Scripting (XSS) finding was reported for "Show Lookup List" on a NASA security audit. The issue appears to be that an invalid host name can be added to the Title element of the HTML output without being encoded. In testing, the title does not appear to actually enable an XSS attack. But to remove the possibility that a future browser might allow it, the title is always encoded now to ensure that it can't happen.


1. Enter the following URL https://your.sm.hostname.here/servlet/sm.web.ShowLookUpList?table=organizations&host=%3ctest%3e into your browser change the host name in the URL to match the host name of your SM.

2. Notice that the title of the page shows as: <TEST> Organizations.

3. Notice that the body of the page is: No Organizations for <test> found!

Results: The title of the page now properly encodes special characters like angle brackets and quotes when outputting the title so that they are displayed rather than being processed by the browser as tags.

Correct Initials

Y N

Comments:

https://your.sm.hostname.here/servlet/sm.web.ShowLookUpList?table=organizations&host=%3ctest%3e

https://your.sm.hostname.here/servlet/sm.web.ShowLookUpList?table=organizations&host=%3ctest%3e



SM-113 – Add Partition Information to File Areas on the SM

Partition information has been added to the File Area displays. Previously, a TechDoc Admin would usually have to contact systems people to see how large the partition is where the File Area is stored.


1. Click Admin on the Main Menu and then click File Areas under the Show… column.

2. There should be at least one File Area listed, click it.

3. On the File Area Info screen, verify that you can see the Available Space, Reserved Space and now also the Partition Free Space and Total Space.

Results: Now you can also see the Partition Free Space and Total Space.

Correct Initials

Y N

Comments:



SM-114 – Change OK Button for Quick Search on Main Menu to an Image

Multiple reports were received of people mistakenly clicking the OK button for the Quick Search on the Main Menu bar instead of clicking on the OK button inside the main content area. The Quick Search OK button has been changed to use an image instead.


1. For this test, you can be on any screen in the Search Manager.

2. In the Quick Search field, Users should already be selected (other options may be added in the future). Enter the username of a User you know exists.

3. Click the arrow image next to the search field and verify that it takes you to the User.

Results: Now the Quick Search's button does not look like a normal OK button.

Correct Initials

Y N

Comments:



SM-115 – Update Lucene to the Latest Version for TechDoc 8

The Lucene search engine used by TechDoc has been updated to the latest version to improve performance and reduce memory consumption.




3. Scroll down through the Search Engine Information section.

4. Note that the Search Engine property shows Lucene V4.3.0.


Results: TechDoc is now using Lucene V4.3.0. Correct Initials

Y N

Comments:



SM-118 – Add Rebuild Index Command into the SM in Support of Upgrading Lucene

A Rebuild Index command has been added to the SM to automate rebuilding of the index when we upgrade Lucene. In the past, an Admin was required to perform a manual process to upgrade the index. By adding the Rebuild Index command, an Admin can manually request that the index be rebuilt from the UI but it also provides the ability to queue the command as part of the upgrade process. Due to the impact on the server and the length of time this command can take on a server with a large number of documents, only one Admin should perform this test when time is available for the test to complete after hours.



2. Click Rebuild Search Index in the Miscellaneous menu.

3. Click Next.


5. Show Pending Updates can be used to see if the command is still running.

6. After completed, you can look at the TechDoc log file and search for "Rebuild of SM search index" to see when it started and when it completed.

Results: The SM index can now be rebuilt inside of TechDoc from the web interface.

Correct Initials

Y N

Comments:



SM-119 – Add Optimize Index Command into the SM in Support of Upgrading Lucene

An Optimize Index command had been added to the SM to automate optimizing of the index. In the past, an Admin to perform a manual process to upgrade the index. By adding the Optimize Index command, an Admin can manually request that the index be optimized from the UI but it also provides the ability to queue the command as part of the upgrade process. Due to the impact on the server, only one Admin should perform this test when time is available for the test to complete after hours.



2. Click Optimize Search Index in the Miscellaneous menu.

3. Click Next.


5. Show Pending Updates can be used to see if the command is still running.

6. Normally, optimization will run very quickly. You can look at the TechDoc log file and search for "Optimization of SM search index" to see when it started and when it completed.

Results: The SM index can now be optimized inside of TechDoc from the web interface.

Correct Initials

Y N

Comments:



Specialized System Level Testing The following tests require that your DM and/or SM be installed a certain way or require testing that is difficult for most users to perform. These items have been regression tested by the development team. If you wish to test them, you will need to setup your own server(s) accordingly.

DM-492 – Fix Original PDFbox Temp File Closed Too Early Issue

An issue was identified that existed in the original PDFbox library. Some of the parser objects accept a handle to a temporary file and then attempt to close it in their finalize method. This should not be done and has been corrected. There is no user level testing for this change.

DM-496 – Make Sure Build Date is always Correct on DM About Screen

While working on DM-491, the build date on the About screen of the DM was found to be incorrect. Update 27 to Java 6 changed behavior that caused TechDoc to sometimes load the incorrect build properties file. Changes have been made to TechDoc to ensure that the correct build properties file is always interrogated for the build date. At the time of this writing, the official build was not finalized yet. If you know what the build date should be, you can go to the About page on the DM and verify that the build date is correct.

DM-505 – Add new Interim Certificate Authority that is required by NSSC

NSSC recently installed a new certificate on their AP Pooling SM. Once they installed it, the DM started having trouble sending updates to the SM. The issue is the new interim certificate authority that the certificate was signed by. TechDoc has incorporated the new interim certificate authority into the TechDoc 8 stack so that it will automatically be available. In order to test this functionality, you must have an SM that has an SSL certificate issued by the intermediate issuer "VeriSign Class 3 Public Primary Certification Authority - G5". If so, you can log onto the DM as an Admin, click on Admin on the main menu, click on



"Search Manager Hosts *", click on the icon for the SM with this type of certificate, and click Test on the side menu. The test should successfully complete.

DM-507 – Add Ability for Folder Shares to Open Documents in New Windows

A request was made to have Folder Shares open Documents in a new browser window. The reason is when viewing a Folder Share in a SharePoint web part, it would be very desirable if the document would open in a new window because normally web parts are not very large so viewing the document in the web part itself is very constraining. In order to test this functionality, you must have a SharePoint server with TechDoc Web Parts installed on it. You need to create a Folder Share on TechDoc, add the TechDoc Folder Share Web Part to a SharePoint site, view the SharePoint site, navigate to a document within the web part, click on the document, and observe that the document opens in a new window.

DM-509 – Add Create Date and Non-Resident Support to REST The REST protocol was missing two features that were needed when REST was being used in TechDoc 7 for a migration effort. First, an optional create date needs to be supported by Create Document. When missing, the current date and time will automatically be used to maintain backward compatibility. Second, the client needs to support non-resident documents. These two capabilities have been added to TechDoc. In order to test this functionality, you must have software that implements the REST protocol. To test the new create date feature, call the Create Document REST service on the target DM (https://example.com/service/rest/RestCreateDocument) with a typical Create Document message body but additionally pass the new CreateDate parameter like so: CreateDate=08/01/2013 10:15:32 Verify that you are able to create a document now specifying the create date. Now delete that document in the Document Manager. Now repeat the test using the same message body leaving the create date out. Verify that you are able to create the document and it has the current date and time for the create date. Now delete the document in the Document Manager. In order to test the Non-Resident support on Create Document, perform a Create Document similar to the previous test. You may use the same message body with a



couple minor changes. Remove the FileName and File parameters because they are not allowed when creating a Non-Resident document since there is no file. Now specify the document as Non-Resident using the parameter Resident=No. Perform the Create Document and see that the document is created as Non-Resident in the Document Manager. You may now delete the document. Additionally, if you wish to specify a URL for the Non-Resident document you may specify NonresidentURL=http://www.example.com/some/resource/here. The Non-Resident URL is handy when you are creating a Non-Resident document to represent say a document in another system that must remain there for security or contractual reasons. This way you have tracking of the document in TechDoc and a link to the official file.

DM-511 – Add Support for Files Larger than 2GB

TechDoc now supports files larger than 2GB. Note that most browsers have trouble uploading files this large. However, the TechDoc Client can easily handle this with its use of chunked encoding. In addition, the TechDoc Client is many times faster at uploading files than a browser is anyway. In order to test this functionality, you must have a TechDoc server with at least one file area that has more than 2 GB of free space. Using the TechDoc Client installed on a PC, create a document using a file larger than 2 GB, verify that the document is uploaded, and then delete the document.

DM-512 – Add Support to the DM for SQL Server 2012

TechDoc 8 includes an updated SQL Server 2012 JDBC driver that can take full advantage of SQL Server 2012. TechDoc 8 officially supports SQL Server 2008 and SQL Server 2012. The Microsoft driver no longer supports SQL Server 2000 at all. In order to test this functionality, you must have SQL Server 2012 installed, locally or remotely. Upgrade your existing SQL Server to 2012 or migrate the database from an older version SQL Server to a 2012 SQL Server. Test various features on the DM to verify that TechDoc works under SQL Server 2012.



DM-513 – Add the Outlook Mime Type to DM

The Mime Type for Outlook messages has been added to the DM and the IMAP/IMAPS services used by Outlook and other email clients has been updated to default to assigning that Mime Type to uploaded email messages. Prior to 7b, TechDoc defaulted to always assigning "message/rfc822" as the Mime Type for emails. The problem with that is that when a user attempts to view the email from TechDoc using IE, IE attempts to view the email but always displays an empty page. By setting emails to the Outlook Mime Type, IE will use Outlook to view the email and then the contents of the email will be correctly displayed. In order to test this functionality, you must have IMAP configured on the server and have an Outlook client configured on a PC to connect to the TechDoc server. From the Outlook client, copy an email from a local Outlook folder to one of the TechDoc folder shown in the Outlook client. Now access TechDoc from a web browser, navigate to the Mailboxes cabinet, navigate to the user folder where the file was copied to using the Outlook client, click on the document, click on the generation, and click on Show Info. Note that the MIME type is application/vnd.ms-outlook. You should now be able to click on the Fetch link and have the email open in Outlook and see the full content.

DM-516 – Add Snapshot Isolation to the DM Database

Since TechDoc 8 requires a minimum of SQL Server 2008 R2, we can now enable to use snapshot isolation to eliminate read locking from the database. This became apparent after seeing an issue with a long running report on a server at KSC. Enabling snapshot isolation will prevent this from happening. There is no specific testing for this functionality. You can test various features within the DM to verify that they still work.

DM-521 – Add REST Privilege to Restrict Use of TechDoc Client and Other REST-Based Applications

The REST privilege to restrict which users can use the TechDoc Client and other REST-based applications has been added to TechDoc. This was added due to how easy it is to upload large amounts of data to TechDoc using the Client. In order to test this functionality, you must have a TechDoc Client installed on a PC. Simply add the REST privilege to a user to see that they can connect using the TechDoc Client. Then remove the REST privilege from the user to see that they can no longer connect using the TechDoc Client.



DM-522 – Update CSS to Deal with Recent Change to IE9

Changes to IE9 caused a rendering of the new look and feel that was not quite right under IE9. The output still looked fine under Firefox, Safari, Chrome, and Opera. Adjustments were made so that the output looked fine in all browsers. In order to test this functionality, you must have access to an IE9 browser and another browser such as Chrome or Firefox. Open the DM home page on each browser and note that the output is nearly identical. Next, log into the DM using each browser, navigate to a cabinet or folder that contains multiple child folders and/or documents, and note that the output is nearly identical. IE9 had issues with the main menu area displaying oddly and with the child items of a folder or cabinet being displayed oddly (sometimes the horizontal line dividing two children would be missing or thicker than other horizontal lines).

DM-523 – Improve SAML to Work on Servers with Multiple Host Names Prior to TechDoc 8 and 7b, SAML (used for NASA's eAuth system) may not work well on a server that has multiple host names assigned to it. The method used to determine the server's host name could potentially return any one of the host names causing SAML to have problems logging users in. TechDoc now uses the ExternalBaseUrl system property (when present) to determine the host name to use when communicating with SAML identity providers. In order to test this functionality, you must have a SAML authenticator configured on the DM that you wish to test. Your server does not need to have multiple host names to perform the test as long as the DM is accessible view the web using localhost. Using localhost is guaranteed to generate the same problem that could occur with multiple host names. Log onto the Windows Server where the DM is running. Open a web browser and access the DM using the URL http://localhost/servlet/dm.web.HomePage. Log into the DM as an Admin, click on Admin on the main menu, click on "Authenticators *", click on the icon for a SAML authenticator, click Test on the side menu, and then click the Test button to use Single Sign-on. The test should successfully complete.

http://localhost/servlet/dm.web.HomePage



DM-524 – TechDoc Client Doesn't Handle a Server that is Not Configured for SSO

Prior to TechDoc 8 and 7b, the TechDoc Drag and Drop Client had an issue when you configured the Client to use SSO but the Server was not configured for SSO. An improvement has been made in TechDoc that allows the user to receive a message informing them that SSO cannot be used with that particular server. In order to test this functionality, you must have a TechDoc Client installed on a PC and the DM must not have an SSO-enabled authenticator (SAML) configured. Attempt to connect to the DM using the TechDoc client. Make sure to set the connection to use Single Sign-on. With this update, the TechDoc Client will display a meaningful message that SSO cannot be used with the DM.

DM-525 – Modify Cabinet does not work from the TechDoc Client

An improvement was made to the REST protocol used by the TechDoc Client so that cabinets can be modified. Prior to TechDoc 8 and 7b, a user could modify folders but they could not modify cabinets. Of course, the user must still have the appropriate privilege and access to modify a cabinet. In order to test this functionality, you must have the TechDoc Client installed on a PC, "Modify Cabinet" or Admin privileges on the DM, and Modify or Owner access to a cabinet on the DM. Using the TechDoc client, connect to the DM, right click on the cabinet, click Modify, and then attempt to modify the description by adding something to the end of it. Modify the cabinet again and change the description back to what it was. The test should successfully complete.

DM-527 – Change DM TechDoc Tomcat Ports to Avoid Collisions

The Tomcat port numbers have been changed on the DM. Numerous issues with the port numbers have occurred because they are the default port number for Tomcat and more products are embedding Tomcat. By moving them, TechDoc is less likely to run into conflicts with other Tomcat-based applications. In order to test this functionality, you must be able to log onto the Windows server where the DM is running. Open a command prompt and execute the command: netstat –aon | more You should see host 127.0.0.1 listening on TCP ports 17973 and 17974.



DM-528 – Update BDL Protocol Authorization to Handle IPv6

A problem has been corrected that prevented a remote application from using the BDL (Bulk Document Loader) protocol when the remote server is running on IPv6. The authorization element no longer requires the IP address to be passed. The Version 1 authorization type can now be used with any hardcoded IPv4 address since it is ignored (such as 127.0.0.1). A new Version 2 authorization type has been added that does not require any IP address to be specified at all. In order to test this functionality, you must have an application that is written to use the BDL protocol, the client machine running the application must be using IPv6, and the server running the DM must be using IPv6. Issue a BDL command using a Version 2 authorization type to see that it completes successfully.

DM-537 – Update TechDoc 8 Installer to Configure IIS to Pass Errors Back to Client Due to issues experienced on newer versions of IIS, the TechDoc 8 installer has been updated to ensure that the error handling setting on IIS web sites where TechDoc is installed is set to pass through mode. This allows TechDoc errors to be passed through to callers even when surface hardening their IIS servers. There is no user level way to test this. However, if you have IIS manager access to the TechDoc web site, you have view the setting to verify that it has been changed. The attribute existingResponse under section system.webServer/httpErrors should be set to Pass Through.

DM-540 – Improve the DM on Servers with Multiple Host Names

Servers running TechDoc are starting to be set up with multiple host names. Different parts of the DM (email, logging, etc.) might display different host names. The system has been updated to always use the ExternalBaseUrl system property (when present) to determine the host name. In order to test this functionality, you must have a DM whose IP host name in DNS is one the users don't normally see and a DNS alias server name that users normally access the DM with. Log into the DM as an Admin and make sure that the ExternalBaseUrl system property is set correctly. Send an email using Email Users on the Admin menu in



TechDoc. For the user type, choose Admin. Use your normal email client to view the email and see that the host name is correct in the body of the email.

DM-541 – Add Temp Folder Checking on DM Start Up

If the temp folder used by Java is missing, the DM can experience numerous problems that Java does not report as errors. In the rare event that the temp folder is missing, the DM will now attempt to create that folder on startup. In order to test this functionality, you must be able to log onto the Windows server where the DM is running. When no users will be interrupted stop the Tomcat service. Now use a Windows Explorer to navigate to the \TechDoc\tomcat folder on the drive that TechDoc was installed to. Delete the temp folder located in \TechDoc\tomcat. Start the Tomcat service. After a few seconds, the temp folder should reappear (you may have to refresh the explorer to see it). Also, you can go to \TechDoc\logs, open the log dated for today, scroll to the bottom of the log, and see warning that the temp folder was missing but recreated.

DM-543 – Update REST Document Search Service to Support All Document Columns

Prior to TechDoc 8 and 7b, the REST Document Search Service used by the TechDoc Client only supported a select number of Document columns to be specified. In order to improve performance of a couple operations and enable more functionality in the future, the service can now return all Document columns. In order to test this functionality, you must have software that implements the REST protocol. To test the feature, call the Search Documents REST service on the target DM (https://example.com/service/rest/RestSearchDocuments) with any of the following new columns that were added:

CreateDate, DocCategoryID, DocTypeID, FileName, LastModifyDate, MetricFrequency, MetricOrganizationID, MetricPOCID, MetricReportingLagDays, MetricResponsibleOfficialID, OrganizationID, PointOfContact, ReleaseDate, Resident, and WebSearch



DM-565 – Add New Iterators to Records to Reduce Memory Usage in TechDoc

TechDoc continues to strive to reduce memory usage wherever possible, especially as document counts continue to grow. With new features available to TechDoc 8 by using Java 7, new record iterators can easily be used to replace other methods that consume more memory. Additional focus will be placed on continuing this work in TechDoc 8a. There is nothing specifically testable for this issue other than to note that no unusual problems are encountered during testing.

DM-570 – Add Utils from CSV Import Utility to TechDoc 8 for Inclusion with Scan Agent 8

While performing imports for the CAPPS closeout at KSC, many utility functions for processing of data were needed. These utility functions could be very handy for anyone to use. This Utils class has been imported into the td script package so all JavaScript-enabled applications can take advantage of it. This will be especially useful for Scan Agent. In order to test this functionality, you have to use the Scan Agent. For more details on all the new utils functions that are now available, consult the JavaScript Objects section of the Scan Agent Guide, Revision 8.

DM-573 – Add Nonresident Document Support to Scan Agent Scan Agent 8 now allows uploading of non-resident documents as requested. Previously, only resident documents could be uploaded via the Scan Agent. In order to test this functionality, you have to use the Scan Agent. For more details on all the new utils functions that are now available, consult the JavaScript Objects section of the Scan Agent Guide, Revision 8.

DM-574 – Update the VIX API to Support VMware 5.1

The VIX API used by TechDoc to control a Render VM running under VMware has been updated to version 12 to add support for VMware 5.1. In order to test this functionality, you must have a Render VM running on VMware 5.1. Log on to the Windows Server running the Document Manager as a user with



Administrator rights. Start a Command Prompt that is "run as Administrator" and type the following command: tdvmctrl status RenderVM You should receive a message that starts with "Success:"

DM-576 – Modify the Render Task so that Lower Priority Renders Can Be Handled

While working on a large migration, it became apparent that it would be very advantageous to have the render task allow lower priority renders to be queued that do not hold up interactive users. Changes have been made to support this. There is no user level way to test this. In the future, Admin functionality will be added that can exercise this feature.

DM-584 – Add Deleted File Logging for Replace Document Sometime ago, logging of deleted files was added to TechDoc to make it possible for System Admins to recover files from backups when users inadvertently delete them. Unfortunately, deleted file logging was overlooked on Replace Document, which can delete a generation if the user clicks the Overwrite option. In addition, the Sys Admin guide has a new subsection specifically about how to recover deleted files. It is suggested that you review that section before attempting to test this item. To test this item, the tester must have a TechDoc Admin account and a Windows Admin account on the server that the DM is running on. The test will be performed without using backup tapes as that would greatly complicate trying to perform this test. Also, we suggest that you use a text file when creating documents because it makes it easier to validate the contents of the file as most DM's will not have Office or other desktop products installed on them to open the test file with. To test a non-encrypted file, log into the DM as a TechDoc Admin, go to the Admin screen, and click on Doc Categories under Show… Then look for a Doc Category that has "Store Encrypted" set to "No". In a default configuration, the Doc Category "NS" is set this way. Create a document using an unencrypted Doc Category. Once the document has been created, explore to the generation on the document that was just created and click on the Show Info link or icon. Note the "File Path" of the generation and that "Encrypted" is set to "No". Now log into Windows and copy (do not CUT) the generation file specified by the "File Path" to another location on the computer. View the copy of



the file and see that it is the correct file. Next, go back into TechDoc, navigate to the Document, reserve it, and then replace it with the "Overwrite generation" option checked on. Next, go to the Admin screen, click on Log Files under Miscellaneous, and click on the TechDoc log dated for today and view it. Scroll to bottom of the log and look for a TechDoc message about the deleted file. Note that the file path should agree with the "File Path" you noted above. To test an encrypted file, log into the DM as a TechDoc Admin, go to the Admin screen, and click on Doc Categories under Show… Then look for a Doc Category that has "Store Encrypted" set to "Yes". In a default configuration, the Doc Category "ITAR" is set this way. Create a document using the encrypted Doc Category. Once the document has been created, explore to the generation on the document that was just created and click on the Show Info link or icon. Note the "File Path" of the generation and that "Encrypted" is set to "Yes". Now log into Windows and copy (do not CUT) the generation file specified by the "File Path" to another location on the computer. Attempt to view the file and see that it does not display correctly because it is encrypted. Next, go back into TechDoc, navigate to the Document, reserve it, and then replace it with the "Overwrite generation" option checked on. Next, go to the Admin screen, click on Log Files under Miscellaneous, and click on the TechDoc log dated for today and view it. Scroll to bottom of the log and look for a TechDoc message about the deleted/encrypted file. Note that the file path should agree with the "File Path" you noted above. Also, note the long hexadecimal value (the decryption key) inside the parentheses in the log message. Now open a command prompt on the server where the DM is running and change to the directory where you made the copy of the encrypted generation file. Let's assume that the generation file name is 12550.txt and that the decryption key in the log message is 0123456789ABCDEF. If that were the case, you would enter the following command in the command prompt window: TechDocDecryptFile.exe 0123456789ABCDEF 12550.txt decrypted.txt Upon running the command, you will be prompted for a valid Admin username and password for the DM before the command will attempt to decrypt the file. If successful, you could then view the file decrypted.txt and see the original contents. Of course, you would need to change the decryption key and file name in the command to the correct values for this test to work. In normal operation, the file specified by the "File Path" would already have been deleted by the time you looked in the log file. To recover the file, you would inform your backup operator of the "File Path" and the date/time of the log entry. Your backup operator would then go to the appropriate backup tape/device prior to the date/time of the log entry and restore the file specified by "File Path" to a location where you could access it.



SM-96 – Remove Keyword History out of the SM Show History Servlet

While working on SM Admin Help, it was discovered that the Show History servlet has sections in it to support Keywords. However, there is no history for Keywords. This support was removed from the Show History servlet to remove the unnecessary code and prevent confusion in the future. There is no user level way to test this.

SM-99 – Make Sure Build Date is always Correct on SM About Screen

While working on DM-491, the build date on the About screen of the DM was found to be incorrect. Update 27 to Java 6 changed behavior that caused TechDoc to sometimes load the incorrect build properties file. Changes have been made to TechDoc to ensure that the correct build properties file is always interrogated for the build date. At the time of this writing, the official build was not finalized yet. If you know what the build date should be, you can go to the About page on the SM and verify that the build date is correct.

SM-100 – History Display Could Have Problem when IP Address is not set A display issue was found when an SM history record has an IP address that has not been set. The issue was introduced when IPv6 support was added. The issue was handled on the DM but was not handled on the SM. The issue can occur much more frequently on a DM then an SM because an SM rarely creates history records with null IP addresses. There is no user level way to test this.

SM-103 – Add Support to the SM for SQL Server 2012

TechDoc 8 includes an updated SQL Server 2012 JDBC driver that can take full advantage of SQL Server 2012. TechDoc 8 officially supports SQL Server 2008 and SQL Server 2012. The Microsoft driver no longer supports SQL Server 2000 at all. In order to test this functionality, you must have SQL Server 2012 installed, locally or remotely. Upgrade your existing SQL Server to 2012 or migrate the database from an



older version SQL Server to a 2012 SQL Server. Test various features on the SM to verify that TechDoc works under SQL Server 2012.

SM-104 – Add Snapshot Isolation to the SM Database

Since TechDoc 8 requires a minimum of SQL Server 2008 R2, we can now enable to use snapshot isolation to eliminate read locking from the database. This became apparent after seeing an issue with a long running report on a server at KSC. Enabling snapshot isolation will prevent this from happening. There is no specific testing for this functionality. You can test various features within the SM to verify that they still work.

SM-106 – Change SM TechDoc Tomcat Ports to Avoid Collisions The Tomcat port numbers have been changed on the SM. Numerous issues with the port numbers have occurred because they are the default port number for Tomcat and more products are embedding Tomcat. By moving them, TechDoc is less likely to run into conflicts with other Tomcat-based applications. In order to test this functionality, you must be able to log onto the Windows server where the SM is running. Open a command prompt and execute the command: netstat –aon | more You should see host 127.0.0.1 listening on TCP ports 17973 and 17974.

SM-109 – Improve the SM on Servers with Multiple Host Names

Servers running TechDoc are starting to be set up with multiple host names. Different parts of the SM (email, logging, etc.) might display different host names. The system has been updated to always use the ExternalBaseUrl system property (when present) to determine the host name. There is no user level way to test this. If you have an SM whose IP host name in DNS is one the users don't normally see and a DNS alias server name that users normally access the SM with, when an alert does occur, view the email and notice that the host name is correct in the body of the email.



SM-110 – Add Temp Folder Checking on SM Start Up

If the temp folder used by Java is missing, the SM can experience numerous problems that Java does not report as errors. In the rare event that the temp folder is missing, the SM will now attempt to create that folder on startup. In order to test this functionality, you must be able to log onto the Windows server where the SM is running. When no users will be interrupted, stop the Tomcat service. Now use a Windows Explorer to navigate to the \TechDoc\tomcat folder on the drive that TechDoc was installed to. Delete the temp folder located in \TechDoc\tomcat. Start the Tomcat service. After a few seconds, the temp folder should reappear (you may have to refresh the explorer to see it). Also, you can go to \TechDoc\logs, open the log dated for today, scroll to the bottom of the log, and see warning that the temp folder was missing but recreated.

SM-111 – Increase the Released File Name Length to 255 to Match the DM In a previous version of TechDoc, the DM increased the allowed Generation file name to be 255 characters. However, a corresponding file name length was not changed in the SM. The length of a released file name on the SM has been increased to 255 characters to prevent index problems on a caching SM when the released file name is larger than 128 characters. In order to test this functionality, you must have a caching SM. Create a file on your PC using Word, Notepad, etc., add a line or two of text so that it won't be empty, and save it to a file name that is longer than 128 characters but less than 256 characters in length. Log into a DM and create a document using this file with the really long name. Ensure that you set the attributes on the document so that the file will be pushed to the caching SM. Release the document and wait for a couple minutes for the document to be pushed to the caching SM. Go to the SM, search for the document, and click the revision to download the file. Previously, the document would fail while attempting to push it to the SM.

SM-117 – Remove Clustering from the Remote Host Index on the Documents Table

In working on a problem at KSC, it appeared that the issue could be tied to a clustering index on the Documents table in the Search Manager. In examining the index, it was felt that the index shouldn't be a clustering index anyway. The clustering has been removed from the Remote Host Index in TechDoc 8.



There is no user level way to test this. However, if you have DBO access to the SM's database, you can use SQL Server Management Studio to review the Documents table to ensure that there is no clustering index any more.



Conclusion

This concludes testing of TechDoc Release 8.

Be sure to fill out the Acceptance Tester Info on page iv and return it to your TechDoc Testing Coordinator.

Thank you for your time and assistance in monitoring the quality of our product.