OSPINSIGHT Integrity 8.0 - Release Notes 9/6/2018
Added Integrity Test 115 (Check for spans that are missing sequential information.)
Added Integrity Test 131 (Find ductbanks that might be missing a relationship to a span)
Added Integrity Test 162 (Check for termination types or span types that have more than 4095 ports or strands)
Added Integrity Test 163 (Check for orphan patches.)
Added Integrity Test 164 (Check for gaps in the port table.)
Added Integrity Test 165 (Check for gaps in the strand table.)
Added Integrity Test 166 (Check for gaps in the spanlength table.)
Added Integrity Test 336 (Check for num values out of sequence in a link for strands.)
Added Integrity Test 337 (Check for link records with strands from multiple cable spans.)
Added Integrity Test 338 (Check for num values out of sequence in a link for ports.)
Added Auto Fix to Test 129
OSPIntegrity database is automatically added when first pointing to the SQL server
Added Run History
Fixed Integrity Setup adding folders in incorrect locations
Fixed ‘ExecuteNonQuery requires an open and available Connection. The connection’s current state is closed’ error when setting up
Integrity on a new computer.
Fixed deleting from database error ‘Value cannot be null’
Fixed deleting database from database setup error.
Test 187 no longer shows cached routes during the test.
Fixed Test 186 from freezing Integrity during Group Tests.
Fixed ‘Violation of PRIMARY KEY constraint 'pk_strand'.’ Error
Checked the setup.mdb corruption issue on installation.
ODBC’s should be setup automatically when ran as an administrator.
Fixed first startup error messages.
Fixed "The keyword Object cannot be translated because the table is not mappable."
Fixed "File IntegrityTestCAB.DAT not found.”
Fixed error with Test 186 autofix.
Sometimes removing databases from Integrity ‘Run box’ will not remove them from Integrity
On first open, the Individual Details and Test Run History columns will be squished. Double clicking on them will re-align them.
On first open, when integrity is first minimized it will size to a tiny window.
When running tests from Run History, it only runs the oldest copy of the database that is listed in Run History.