Edit Tests Module

The Edit Tests module allows the user to edit two specific fields in the TEST table. Edit Tests behaves slightly differently from the other three test modules. First, only one test can be operated upon at a time. Second, database changes cannot be uploaded from the main test selection and search window. Instead, clicking on the “EDIT TEST” button opens a new window where changes are made and then saved to the database (Fig. 22).

Figure 22. Edit Test Entry Screen.

In the Edit Tests entry screen, only two parameters may be changed, Instrument and Test Comment:

·	Instrument is selected from a pull-down menu (and should never be set to null).
·	Test comment is a text entry field up to 150 characters.
·	Add comments to existing comments; do not remove old comments.
·	Do not use single or double quotes or special characters in the comments.

An audit trail reason (5–150 characters) must be entered before the “UPDATE of a selected test” button becomes active. Clicking the “NO CHANGE” button returns the user to the search screen and to the previous state (no change occurs).

User Account Privileges

The privileges for the Edit Tests function are defined by analysis code. A user may be given analysis code = ALL, in which case their account can operate on all analyses (typically restricted to the technical staff). Alternatively, the user may be given privilege for specific analysis codes only (e.g., GRA, MS, and PWAVE_L for someone working with the WRMSL).

Procedure

1.	Perform a search as described in “Search Functions.” This query returns only active tests.
2.	Select one test (and only one test) to be edited. The “EDIT TEST” button becomes active.
3.	Click the “EDIT TEST” button.
4.	Edit the desired fields.
5.	Enter an audit reason in the audit field.
6.	Click the “UPDATE of a selected test” button, or the “NO CHANGE” button to abort.

Note that no separate popup window for the audit reason appears—this is different behavior than all of the other modules.