HFT Release Notes

Release 1.3, May 15, 2005
GENERAL NOTES AND QUESTIONS:
  1. Contents: This release contains the requested fixes and enhancements based on release 1.2.
Feedback Results:
  1. Re:1) Please make it so a second click on the radio button under Hydrants w/Tests/City un-selects the button.
    That radio button is part of the group of radio buttons above it. One of the buttons must always be selected for the query to function correctly. To cause that specific button to "unselect" itself would not conform to proper HTML behavior. However, we did add a Reset button next to the Query button to reset the form to its original state. We think this better meets your goal.
  2. Re: 2) On the query results, if it doesn’t slow things down too much, please make all of the columns sortable.
    The default initial sort is by city, street, building number, intersection, pressure zone, map, and test. Clicking on any column header causes that column to be sorted first, followed by the default sort sequence. Note: The "Bldg" column cannot be sorted numerically because there are non-numeric entries in that column (ex: 104A, 106K, etc.).
  3. Re: 3) When only one row is returned as a result of a query, it goes straight to the detail page where there is no "e" button to edit the hydrant info, please add one there too.
    The Detail page now has an "e" button next to the I/O button.
  4. Re: 4) When I try to enter a hydrant in/out of service, I get this error message: ORA-04063: view "HFT.HYDNT_SERV_CURR_VU" has errors. Following are Dave’s comments regarding this error:

    The error is the result of installing the Oracle 9.2.0.6 patch to our database. Under this release, Oracle has tightened its allowable SQL syntax [...]
    We do not have version 9.2.0.6 of Oracle, but this same error occurred when we compiled the view on a 10g database. We fixed the problem by changing the HYDNT_SERV_DATA table to an in-line view. It compiles correctly on 10g, so we expect it will on 9.2.0.6 as well. Let us know if it does not.
  5. Re: 1) Please add city to the query options so users can query for a hydrant number in a certain city
    We have added a City code poplist to the General Query section to limit results to that city. This applies only to the 5 query types in the General Query section since the other queries are more narrowly defined than a city.
  6. Re: 2) On the Pressure Zone and Pipe Extension Links on the details (or on the query results), please make them open in a new window.
    These links now open in a new browser window.
  7. Re: 3) When there is only one hydrant returned as a result of a query (this is an amendment to item #3 below), please display the ONE ROW as if it were a list. So, no need to add the e-button here, now. Hilary thinks this will make it more clear that no tests exist (when no tests exist).
    The one row now displays, rather than jumping to the details page. The "e" button was added to the details page anyway just to be consistent (since it already had an I/O button on it).
  8. Re: 4) Can you add a button similar to the E and I/O buttons to show status history for a particular hydrant. When you click on it, it would show Hydrant IN service on 10/1, OUT of Service on 12/3, back IN service on 12/4, etc. Similar to the "hftqserv" form in the forms app.
    Both the query results and details pages now have an "H" button to show the In/Out history of the hydrant.
OTHER THINGS WE DID ON OUR OWN:
  • Nothing to report.

KNOWN BUGS (FUTURE FIXES) AND REQUESTED ENHANCEMENTS:
  • Requested Enhancements and Problem Reports
    • Nothing to report.

Prior Release Notes: 0.1 1.0 1.1 1.2