Trns port SiteManager 3.9b Maintenance Release Summary of Changes

Transcription

1 Trns port SiteManager 3.9b Maintenance Release Summary of Changes The following is a summary of the Trns port Modification Requests (TMRs) included in this release. Each item listed has the number followed by a brief explanation of the problem and the resolution. This Maintenance release corrects 25 maintenance TMRs, one warranty TMR and one minor enhancement. SiteManager Software Development Environment for 3.9b The following software was used in the development of the AASHTO SiteManager 3.9b application: Design Software 1. PowerBuilder 11 Build 3050 Databases 1. Oracle 10g DB SQL Anywhere 11.0 (local database only) Online Help 1. RoboHelp 7 Installation 1. InstallShield Due to the way InstallShield 2009 handles uninstalling applications, the setup program can no longer uninstall the application from the same setup program that installs the application. Therefore, the SiteManager setup was divided up into a main setup program that gathers all the information and uninstalls the selected application if it existed previously. You will notice differences during the installation of the client application and also the cd structure. The following are new directories under SM-Appl directory: Setup_Training_SMAdmin Setup_Training_SMAPP Setup_Training_SMBatch Training (SM-Train) is divided up similarly, except the names of the subdirectories are: Setup_Training_SMAdmin Setup_Training_SMAPP Setup_Training_SMBatch KEY NOTES: PLEASE THOROUGHLY READ THE NEW SITEMANAGER INSTALLATION GUIDE FOR INSTRUCTIONS ON HOW TO INSTALL THIS RELEASE. THIS GUIDE IS THE SOLE SOURCE OF INFORMATION ON NEW AND UPGRADE INSTALLATIONS FOR SITEMANAGER. The summary of the functional changes for this product update release are as follows: TMR P/S Type field on Maintain Sample Information window Description: The Producer/Supplier Type field on the Maintain Sample Information window displays the code value, not the actual description from the code table which is not consistent with other areas of SiteManager. Code values are difficult to interpret for end users. Resolution: The maintain sample window was modified so that the P/S type field now displays the description instead of the code. 1

2 TMR Change Order approval uses the User's Name instead of User ID Description: When approving a Change Order whose approval rules are overridden, and the user has two or more User IDs in the system, it uses the first User Name in the database that matches that User ID. This can cause the wrong User ID to be associated with an approval. Example: User1 John Doe User2 John Doe User is logged in using ID 'User2'. User2 approves a Change Order, but the system shows the Change Order being approved by User1. System should go by User ID and not the user name associated to an ID Resolution: The Change Order Approval Dialog window was modified. The User ID dropdown was changed to show both User Name and User ID. TMR Adjustment description contradiction Description: Noticed that for some of the adjustments that have been added to the system (i.e. ASPH, Asphalt) they do not have a description appearing in the top datawindow on the Line Item Adjustment window. Data is embedded in the top datawindow and a code table is used for the drop down on the bottom datawindow, ADJTYP. SiteManager is not using the ADJTYP code table for both datawindows Resolution: The Line Item Adjustment window now uses the ADJTYPE code table to display the adjustment type description in the Price Adj. Type field. TMR Existing Plant ID Can Be Unprotected, Changed, and Saved Description: An existing Plant ID can be unprotected, changed, and saved. In an existing Producer/Supplier record that has plants, click to the Plants tab. Select a plant. Click the Address button. Click the New button. Close the Address bubble by clicking the Address button. The Plant ID field has become unprotected. Make changes and click Save. The changes have been saved. Resolution: The code was modified so that on the Plant tab within the Producer/Supplier window, the plant id field will only be editable when a new plant is added. TMR Plant Can Be Deleted by User With Inquiry Access to Producer/Supplier Window Description: A user with Inquiry access to the Producer/Supplier window can delete a plant from the Plants tab. Open an existing Producer/Supplier record and click to the Plants tab. Select a Plant. Click the Address button. Click the New button and notice that the Delete button is activated. Click the Address button to close the Address box. Click the Delete button to delete the selected Plant. The user is prompted, Do you wish to delete this plant record. Click Yes. The Plant record is deleted. Click the X to close the Producer/Supplier window. The user is prompted, Save changes? Click Yes and the window will close. Reopen the Producer/Supplier window (reselect the same Producer/Supplier record if necessary) and click to the Plants tab. Notice that the Plant has been deleted and those changes were saved. Resolution: The code was modified so that on the Plant tab within the Producer/Supplier window, the delete button will only be available when a new plant is added and is active only when the focus is on the new plant row. 2

3 TMR Receive Sample at Lab Unit - Remarks indicator not displayed properly Description: Receive Sample at Lab Unit. 1) Enter remarks for all of the samples in the Queue for a Lab Unit. (The Remarks bubble will have lines indicating that there are remarks for the sample) 2) Sort any column for the rows/samples displayed. 3) The Remarks bubble for the 1st row displayed does not have the lines indicating that there are remarks and the row is NOT highlighted in blue; only the column is highlighted and the color is black. If any other row is selected it is highlighted properly and the Remarks bubble has the lines indicating that there is a remark. Resolution: The Receive Sample at Lab Unit was modified so the scrolling was corrected after sorting. Now, selecting and setting the appropriate row focus works so the correct rows are highlighted and the remarks are linked to the correct row. TMR LIMS application terminates restart message program already running Description: If the LIMS application terminates abnormally and the user tries to access LIMS from SiteManager they receive the following message: "An instance of the LIMS program is already running. Please close that first. This prevents LIMS from starting even though no instance of LIMS is actually running. Resolution: The LIMS application was modified so that LIMS will no longer prevent/allow another instance of LIMS from running by checking to see if the lims.dat file is present. This was causing a problem when LIMS aborted. The file that should have been deleted when LIMS closed was not deleted. Subsequent attempts to run LIMS failed since the application thought another instance of LIMS was running. Now the application checks directly to see if another instance of LIMS is running via Windows API calls. SiteManager was also modified so only a single instance can run at once. There used to be code to prevent multiple instances of SiteManager from running. This function had stopped working with a newer version of Windows Now the application checks to see if another instance of SiteManager is running via Windows API calls. LIMS was also modified to include version checking between the client and the database. TMR Tests do not display when user is assigned to only 1 lab Description: Tests do not display when a user is assigned to just one lab unit. 1) Assign a User to just one Lab Unit 2) After sample is received at Destination Lab and Lab Unit, navigate to Maintain Test Queue 3) If radio button for Select a Lab Unit is selected, no Tests for the Lab Unit are displayed. 4) If radio button for All My Lab Units is selected, all Tests for the one Lab Unit are displayed. 5) If you use the drop down the select the Lab Unit, the all Tests for the one Lab Unit are displayed. Resolution: The code was modified so that if the user has only a single lab associated to their user id, the lab unit dropdown on the Manage Test Queue window will work correctly. TMR Denied Change Order Items show as Pending on the Contract Item table Description: When a Change Order is created where it adds a new item (an extra work Change Order) and the Change Order is subsequently denied, what is supposed to happen in the t_cont_itm table? There are some denied changed orders that added new items and when the Change Order was denied the items are still in the t_cont_itm table with a pending status. This creates several problems...one is that when the 3

4 status of the Contract is changed from Active to Complete; SiteManager gives the message that it can not be changed because all items are not complete. Resolution: The code was modified to set item status to "DENY" when change order is denied. In addition, the code was changed to remove denied items from selection on DWR templates, subcontracts, and contract item funding. Denied is now not allowed for item status selection on the contract item window. TMR Instructs to enter mm/dd/yy but you must enter mm/dd/yyyy Description: In the SiteManager LIMS View Only Sample Information window, the Open sample criteria window displays the filter criteria and instructs to enter date in mm/dd/yy format but when you enter the date in that format, it displays an error message. The date value is accepted in the mm/dd/yyyy format. Resolution: The drop down list labels for the Field Open Sample Records dialog on the View-Only Sample Information window now reflects the correct date format that the system uses (mm/dd/yyyy). TMR Incorrect labels and dropdown list Description: On the LIMS Alternative Workflow window, the column header Lab Unit should be labeled To Test Status. On the same window, the Filter Criteria dropdown list includes field names that are data style (e.g., lims_alt_test_workflow_tst_meth) instead of label (e.g., Test Method). The sort order for the list is not alpha by name or by default column order on the screen (left to right). Resolution: On the LIMS Alternate Workflow window, the column headers and filter criteria dropdown field names were corrected. The corresponding search screens were also altered to match similar search screens in SiteManager where possible. TMR Tests that were requeued are removed from the queue on Review Test Description: On the Review Tests window, tests that were requeued are removed from the queue. However, when comparing multiple test results (templates) in the lower zone, if the test status is changed to 'Requeue' the comparison is no longer possible. If no template is available for comparison the template for the next test method is displayed. At this point, the application generates an error - Invalid fn_compare_all_columns if no template results are entered. Resolution: If a test template did not have any data stored in the database, the system would crash trying to read values from the database. Now it will display an empty template to the user if there is no data saved in the database. TMR Search window causes NULL Reference error when closed with the "X" Description: When choosing a Test Method or other fields that use the Search feature in the Test Trigger Events or Alternative Test Workflow window in LIMS, a NULL Reference error will occur and the application will crash when the Test Method search window is closed with the "X" in the upper right hand corner instead of the Cancel button. Resolution: The search window was modified to use the same exit logic whether the user clicks on the Cancel button or the X button on the control menu to exit the search window. TMR Material short description displayed instead of material code Description: On the Assign Test window, the material code field is showing the material short description instead of the material code. 4

5 Resolution: The field on the Assign Test window was changed to show the material code instead of the material short description. TMR Can not add or remove multiple users on Maintain Lab Users Description: When associating users to labs, you can not select multiple users (ctrl+click or shift+click) and then use the Add or Remove buttons. Resolution: In LIMS, the Maintain Lab User window was modified so that the 'Available Users' and 'Lab Users' datawindows now allow multiple selections, i.e. multiple users can be added or removed from the lab via ctrl and shift clicking. TMR View-Only Sample errors for Remarks when no Tests assigned Description: On the View-Only Sample Information window the application terminates when clicking on the Remarks when the Sample viewed does not have any Tests associated. 1) Display a Sample that does not have any Tests associated (i.e. a voided Sample) 2) Click on the Test Status tab 3) Click on the Remarks icon 4) PowerBuilder Application Execution Error (R000006) is displayed: Error: Invalid Data Window row/column specified at line 38 in function f_remarks of object t_tab_viewonly_sampleinfo_dot. Resolution: The View-Only Sample Information window was changed so that it will not read the remarks id and display it when the user is viewing a sample that has no tests assigned in LIMS. TMR Test Template Computed Field returning String Value generates PowerBuilder error Description: Review Tests - When you click on a template with a computed field that returns a string value you receive the PowerBuilder Application Execution Error (R0012) message window. Message is 'Application Terminated. Error: Data Window column type does not match GetItem type at line 25 in function fw_compare_all_columns of object w_test_result.' Note that this error occurs only if the computed field is defined as an attribute (F1, F2, F3... etc.) on the template creation window within SiteManager. Computed fields defined in PowerBuilder that return string values (e.g. displaying sample id, material code, etc.) will not cause this error. Resolution: The template functionality was modified so that the function will now return the value of a column whose type is determined at run time (including string values). TMR Group Security window names inconsistent with icon names Description: On the LIMS windows, the icon and the window header say "View-Only Sample Information". These are available on the LIMS panel or the View-Only panel. In LIMS Group Security window, these are labeled as "Sample Information Views" for both the LIMS panel and the View-Only panel. The name for the window in the Window Privileges zone in Group security is inconsistent with the name of the window shown to the users. The name should be consistent throughout the application. Resolution: Database scripts were created to modify the names of the View-Only Sample Information window and tab descriptions for the Group Security window to make them consistent. 5

6 TMR Assign Products & Maintain Product Users not in LIMS group security Description: Assign Products and Maintain Product Users are not available in the LIMS Group Security window/pick list. Resolution: Maintain Product Users and Assign Products were added into the LIMS tables for Group Security. TMR Two Date fields are not aligned on View-only Sample window Description: On the View-Only Sample Information window on the Test Status tab, the charge date and start date field information fields are not aligned with the other fields on the window. Resolution: The alignment was reset and resized for all columns on the window. TMR Services>Copy Tests should not appear on Assign Product Window menu Description: On the Assign Product Window the menu option Services>Copy Tests should not appear. This function results in Test Methods being added to the SiteManager Material Details window, Test Tab. Resolution: The Default Products Assigned window and the Default Test Assignment window were modified so the copy test menu item was removed from the Services menu. The Services menu was also removed since no options were provided under it. TMR Testers dropdown has userids not assigned to the Lab Unit. Description: UserIds appear in Testers dropdown who are not assigned to the Lab Unit. The User has authority for the Test type but not the Lab Unit that is being displayed for the sample/test. Resolution: Changes were made to the Tester dropdown on the Maintain Test Queue within LIMS. The dropdown will now only show users who have been qualified to run the tests (test methods) and have been added to the appropriate lab (the lab id on the selected row). Note: In order for the user to have this correction, changes were necessary for the installation process. For users using the SiteManager with LIMS client, the limsmisc folder stores window preferences specific to the user (for example, column orders, widths, single labs vs. all labs, and so on) for various LIMS datawindows. Upon upgrading the SiteManager with LIMS client, the installation process deletes the limsmisc folder. The first time LIMS needs to write to this directory, it re-creates it. The installation must delete this folder to ensure all changes to table structure are applied. Example: While using LIMS, users may have rearranged columns in the Review Tests window to match the order of how they preferred to see the data presented. After an update to the LIMS application which deletes the limsmisc folder the users preferences are restored to the system default. Users will have to recreate their preferred arrangement after the update. TMR Add Run Button, Maintain Test Queue, should not copy entire record Description: The Add Run button on the Maintain Test Queue screen copies the entire record from the existing test, to a new test record, with a new run number. This includes the Start and End dates. This is incorrect. These dates should remain empty, until the test is actually started/completed, at which point, the system will stamp in the appropriate date. Resolution: The 'add run' functionality on the Maintain Test Queue window was modified so that the start and complete dates will not be copied. The dates will be set to zero. 6

7 TMR Conversion Factor on Stockpiled Materials gets reset if description is changed Description: On the Stockpiled Materials window if the description field is changed then the Conversion Factor field gets reset to the default of " ". Resolution: On the Stockpiled Materials window, the Conversion Factor will not be changed when the description field is changed. TMR SM LIMS - Canceling a test - Maintain Test Queue Description: The act of canceling a test in LIMS should ensure the test reportable indicator is set to N, so cancelled tests do not get shown in queues such as Sample Review. The cancelled tests for a sample are appearing in Sample Review queue, with no data since the test was cancelled, and it may be a source of confusion for some users. Resolution: A new updateable "Reportable" column was added on the Maintain Test Queue window and a new "Test Status" column was added on the Review Sample window. The new Reportable checkbox on Maintain Test Queue allows users to indicate whether a test is reportable or not when they cancel a test. (If the reportable box is checked, the cancelled test will appear on the Review Samples window.) TMR Inability to add multiple instances of a test at time of sample entry with LIMS Description: The ability for Samplers and Testers to add multiple instances of the same test to a sample at the time of sample-entry has been possible in SiteManager prior to and including version 3.9a. However, this is only possible in LIMS as supervisor-level functionality in the Maintain Test Queue window (add test) and Review Tests window (order retest). Resolution: A new field was added to SiteManager called test_runs. The value of this field represents the number of test runs required when the test is assigned to a sample. In SiteManager, the Assign Sample Tests window was modified to include the new test_runs field. When tests are saved, the system will generate the number of records identified in the test_runs field. If the default test is required, the new test_run field cannot be modified. In LIMS, the Test Assignment Information window was modified to include the new test_runs field on the default tests datawindow. This value is required and must be an integer between 1 and 9. TMR Rounding Issue in Item Price Adjustments (Estimate Generation) Description: While generating an estimate, the fuel and material adjustments are never right. After extensive research, it was discovered a rounding error that caused this. Resolution: The base price structure and variables used in calculating line item adjustments during an estimate were increased to decimal(5). This change increased the accuracy of the adjustment amount. Some internal variables only stored values to 3 and 4 decimals. 7