Setting up a test configuration in your current GainSeeker database

The following instructions will help you create a test configuration and user in your current GainSeeker database. This configuration can be used to make and test changes before moving them into your production environment.

  1. Using the System Administration module of GainSeeker, copy a configuration from production and give it a new name. Submit the changes using the Submit button.

 

  1. In the new configuration, open the Tables and File Paths dialog. Append _DEV to several table names to create new tables for this configuration.

  1. Data tables: VDATA, VDAT_AUX, VNOTE, DDATA, DDAT_AUX, DNOTE, VMON, VMON_AUX

  2. Inspection tables: INSPECTIONUID, HSISCRIPTS, SCRIPTARCHIVE

  3. Report tables: HSIRPT, and optionally DDT, DPRI_DT, DASHDT, DASHRET, DASHSW, DESKTOP, VPRI_DT, REPORT

  4. Data Entry tables: optionally TEMPLATE, SCHFILE, PLAN_VAL, PLAN_AUX, SESSIONLIST

  5. Control table: HSICT

  1. It is highly recommended that you share the following tables with the production environment but you can create new tables if wanted. Creating new tables will require loading tables with default values and copying supporting text files. It will also require any updates to the tables to happen in both environments.

  1. Traceability tables: TRACEMST, TRPRIMST, TRACE1, TRACE2, TRACE3, TRACE4, TRACE5, TRACE6

  2. ECAT tables: ACTION, CAUSE, EVENT, EVENTCA

  3. Standards tables: VSTDS, DSTDS, VPRI, DPRI, DPROC, DPROCDL, DMDL

  4. Filter tables: FILTER, DFILTER, SFILTER, STATLIST, DSTATS, MFILTER

Note: If you choose not to share these tables, you must update both environments when changes occur, such as creating new Standards.

  1. Set all paths for this configuration to a new folder, e.g., “Development”. Add two sub folders named "Copy to Dev" and "Copy from Dev" for exported items to move between configurations.

  2. From  the Tables and File Paths dialog, click the Check for Tables button. After saving changes, you will get a Table Test Results dialog. Click the Run TC Utility... button and then the Start button on the Table Creation Utility screen.

  3. On the Users tab of the System Administration module, create a new user with the new Development configuration.

  4. At this point, you can export/import non-shared data between the Development and Production environments. It may also be useful to create a Python script to refresh the development data tables with current data from production (last 30 days).