-------------------------------------------------------- Release Notes for MRO Management v 5.2 13 January, 2003 -------------------------------------------------------- 1. Introduction -------------------------------------------------------- This text is stored in a file called UPDATE.TXT. It will be installed into the program directory, so you can read or print it at your convenience. These release notes are provided to help you learn about changes to the software that have occurred too late to include in the on-line manual and help systems. Review the Contents section (next) to see if any of the Release Notes may be of interest to you. 2. Contents -------------------------------------------------------- 1. Introduction (prior section) 2. Contents (this section) 3. Enhancements 4. Fixes 5. Known Issues 6. Post-CD Fixes & Enhancements -------------------------------------------------------- 3. Enhancements -------------------------------------------------------- MAJOR PERFORMANCE ENHANCEMENTS A major performance enhancement was implemented in the Validation process. Network users especially should notice an increased speed when importing, revalidating, and exporting records. PERFORMANCE ON THE MAIN SCREEN HAS BEEN IMPROVED. The new drop-down lists were not optimized to use indexes. We have customized this component to behave much faster! PERFORMANCE OF RESULT EXPORT AUDIT TRAIL IMPROVED A new index was added to the DrugPak Results database (TESTS.DBF) to improve performance of the Result Export Audit Trail report. AUTOMATICALLY REVALIDATING RECORDS New option "Automatically revalidate records when adding to the Work Area". This option forces the system to revalidate records when adding them to the work area. Primarily this serves to streamline the process of adding Pre-Employment participants to DrugPak. DEFAULT SAMPLE TYPE Defaulting specimen type to "Urine" is now optional. See "Preferences | Global Settings | Validation Options" ADD PRE-EMPLOYMENT PARTICIPANT Added "ADD ALL" and "SKIP ALL" buttons to the "Add this participant" dialog during the validation process. This is used only when "Prompt to add" option is selected. It remembers only for the current "Round" of validation... I.E. it does not remember for the entire MRO session. Each time you import, or choose "Validate Current / Filtered / All" it forgets again. MORE INFORMATION IN POP-UP WINDOW When notifying the user that a Specimen is already on file, now the message will identify the Specimen ID value. SECURITY Now only the MASTER user may modify Global Settings (all users may view the Global Settings, without making changes). DELETING RECORDS See "Preferences | Global Settings | General" to control whether all users or only the MASTER user may delete records from the MRO Management work area. The default value is ALL USERS. TOOLS A new item can be found on the main menu "Tools | Special | Undelete Missing Records". This routine will scan the MRO Work file for deleted records (Specimen ID's) which do not exist in either DrugPak or MRO Management, and restore them. The P_SORT2 field will be given a value of RESTORED so you can use the filter P_SORT2='RESTORED' to isolate the restored records. This routine will only work to restore records which have been deleted since the last time the database was packed. VALIDATION OPTIONS "Auto-enter MRO Name and Verification date" options are now stored separately for DOT and non-DOT. See "Preferences | Global Settings | Validation Options". VERIFY NEGATIVES Now the dialog will save the last filter condition used. Now the dialog will have access to all the filters previously used in the work area by the current user. New filters added by the current user in this window will be added to the user's filter list in the main screen. NOTE: The Verify Negatives process is obsolete, if you choose to automatically MRO-Verify results with no exceptions (See "Preferences | Global Settings | Validation Options"). FORBIDDING NUMERIC NAMES A new option "Forbid Numeric Names" will clear the name field during the Validation process, if the name begins with a number. The name will be transferred to the INTERNAL comments field. REQUIRING COC DATE COC date is optionally required. This option may be configured separately for DOT and Non-DOT. See Global Settings | Required Fields. REQUIRING SAMPLE TYPE Sample Type is now optionally a required field. See "Global Settings | Required Fields." -------------------------------------------------------- 4. Fixes -------------------------------------------------------- The following fixes resolved some issues introduced in DP Informer v5.0. LOOKUP WINDOWS Lookup windows would not remember field positions and sizes after shutting down the application. ACCESS VIOLATION Fixed intermittent Access Violation on main screen. EXPORTED AUDIT TRAIL The Export process was using the same field (MROX_DATE) as the DrugPak "Export to MRO" routine to track when the record was exported. This was preventing the "Export to MRO" process from recognizing new results. Henceforth, MRO Management will set the R_ADDED date field, and set the R_ADDEDAPP="M". RAN TEST TYPE The alternative Random test type code was not being used when an open RND test could not be found. Now the user will prompted (as in v.4.0) with the opportunity to change the imported test type from RND to RAN. REPORTING ON BLANK COMPANY ID MRO Worksheet and Result List reports would not print records without a company ID. Now records without a company ID will print if the user chooses to print for All Companies. FIND COMPANY MENU OPTION "Find Company" option on Company Function button menu did nothing. This has been fixed. VALIDATE RECORDS ERROR It was not possible to validate records based on the current filter. The error would appear: "could not find an index order with the specified name." This has been fixed. REPETITIVE CLICKING NEEDED After translating records, if exceptions were found, the user needed to click the green check in the Status window twice before the window would disappear. This has been fixed. VERIFY NEGATIVES Now the "add filter condition" button works. VALIDATION PROCESS The exception "This pre-employment participant is not yet on file" was a common exception found during the translation process. However, this exception really served no purpose, because when records were added to the work area, it would be automatically removed. Therefore this exception will no longer appear when Translating records. COLLECTOR NAMES Fixed a bug that could cause duplicate collector names to be added to the collector name database, and collector names to be added to the wrong collection site. To update and correct your collector name database automatically, see DRUGPAK "Tools | Advanced | Rebuild Collector Names File" CHECKING FOR DUPLICATE SPECIMEN IDS Previously the validation process would only check to see if the Specimen ID was already on file if there were no other exceptions in the record. This meant that the user may spend some time correcting exceptions just to discover that the record was a duplicate. Now it will check even if other exceptions were found. RESULT EXPORT AUDIT TRAIL The Result Export Audit trail report was not properly finding qualifying records. This has been fixed. The Result Export Audit trail report was displaying the wrong value for the Exported date. This has been fixed. -------------------------------------------------------- 5. Known Issues -------------------------------------------------------- You can keep up-to-date with the latest version of DrugPak by visiting our Update page on the web: http://drugpak.com/dp52 HELP FILES The Help Files have not yet been updated to cover the new features in v.5.2. See the "Enhancements" section, above for an overview of what is different in the new software. Call for support if you can't find what you are looking for. -------------------------------------------------------- 6. Post-CD Fixes & Enhancements -------------------------------------------------------- No updates have been released since the release of the latest DrugPak CD. for. -------------------------------------------------------- 6. Post-CD Fixes & Enhancements -------------------------------------------------------- v. 5.2.30526 -------------------------------------------------------- 1. Fixed a flaw in the validation routine which was forcing the DILUTE checkbox to be checked if the SUBSTITUTED checkbox was checked. Now the DILUTE and SUBSTITUTED checkboxes are mutually exclusive. 2. A new option has been added to the MRO Management Global Settings | Validation Options page: "Check INTERNAL comment for DILUTE/SUBSTITUED terminology". If this checkbox is marked ON, then the Validation routine will look in the INTERNAL comments field for the phrase DILUTE or SUBSTITUTED. If either of these words is present, then the corresponding checkbox will be marked ON. This option is turned ON by default. To disable this feature, turn this checkbox OFF. 3. An exception will be reported if DILUTE and SUBSTITUTED are both marked TRUE.