TEAAS 2.0 Release Notes

  1. TEAAS_2_0 Deployment.html was created.
  2. Status bar has been added to the TEAAS Client Application Browser, which indicates the last window that was started.
  3. The Intersection and Strip Analysis Report UIs will now allow searches on Study Name, County, Location Text, Log No., and Tip No.
  4. A Reports section including a Features Report button has been added to the Intersection, Boundary, Structure, Mile Marker and Railroad Crossing UIs.
  5. Highest Order Segment Gap Report has been added as the last component of the TEAAS Client Application Browser’s Generate Report function.
  6. An error involving the display of Y-line feet from saved studies has been fixed on the Intersection and Strip Analysis Report UIs.
  7. A database structure error that prevented 3 digit municipality codes from being saved in FTV_USER_REPORT has been corrected.
  8. The comparison for the Y-line (converted to miles) on Fiche, Intersection Analysis and Strip Analysis Reports has been changed to 3 decimal precision.
  9. Intersection and Strip Analysis Reports have a new Criteria Summary Section at the beginning of both reports that lists the County, Municipality, and Location Text.
  10. The memory leak problem on the Server has been fixed. This has amounted to drastic changes on all the server components requiring a complete testing.
  11. An error that allowed new, overlapping HO Segments has been corrected.
  12. Intersection and Strip Analysis Report UI’s were not validating yline field, if it were left empty. This has been corrected. (Raised during UT by Tom on 1/31/2000 – Corrected by Vish on 1/31/2000).
  13. When the generate button is pressed with an incorrect value in the yline field in Intersection and Strip Analysis Report UI’s, an error dialog pops up. When the error dialog is closed, the Study Tab is not displayed, even though the focus is in the yline field. This has been corrected on both the report UI’s. (Raised during UT by Tom on 1/31/2000 – Corrected by Vish on 1/31/2000).
  14. Strip Analysis Report UI was not validating County Combo box upon depressing the Generate Fiche and Generate Study buttons. This has been corrected. (Raised during UT by Tom on 1/31/2000 – Corrected by Vish on 1/31/2000).
  15. Remove the following TEAAS privileges from the Public Query User

Uncoded Roads Report,

Uncoded Municipalities Report,

Ordinance Exception Report: On Road/HO Route,

Ordinance Exception Report: Overlap,

Ordinance Exception Report: No Milepost,

Highest Order Segment Gap Report.

(Requested by Kevin Lacy during System/User Test 2/1/2000 - Completed)

  1. A new user id called TEAAS_REPORT for reports has been created in all the database environments. The new id has a read only access on the TEAAS and CRASH tables. Since the report id is kept in the TEAAS Client program files, a new id with restricted access has been created.
  2. Added version number to the WelcomeUI.
  3. Label on Strip and Intersection Reports for "Total Vehicle Exposure" changed to read "Total Vehicle Exposure (per Million)". This data item does not correspond to the heading and should be moved to the section above in the next release.
  4. A ":" was removed from the "Vehicle Exposure Statistics" section of the Public and Technical versions of the Intersection Report.
  5. The "Property Damage" data element was right aligned in the Public and Technical Strip reports.
  6. A new index has been created on the CNTY_NBR column of the MVC_LOCATION table to improve performance of the queries.
  7. The queries for Fiche (List, Summary and Detail), Intersection and Strip reports have been modified to make sure that the driving table is MVC_LOCATION so as to use the new index created.
  8. Remileposting has been modified to run continuously with parameterized daily start-time.
  9. New UI and server components developed for Item Mileposting. Tables required for storing milepostable items created on the database.