12/24/2020 Hot Fix
- Made adjustments to the validation flag sync after we discovered yesterday that HUD's changes to fix the duplicate flag bug on the E-Tool website broke our ability to synchronize flags.
- Please be aware that while this was tested to make sure it works, we should probably still be on the look out for cases where it doesn't synchronize correctly. If you find cases of the sync not working right, please put in a service desk ticket. And make sure to keep a backup of the flag report.
Improvements
Interface Screen
Adjusted the Assessed RUL fields so that you cannot enter more than 99 for an ARUL.
- ARULs greater than 99 cause errors in the E-Tool, and we felt that we should really never have an ARUL greater than 99.
Added validation on save on the Interface and the Export Screen on Exporting to check for ARULs greater than 99 to stop saving and/or exporting in cases where ARULs greater than 99 managed to get into the data (most likely from improting old projects).
We ran an update on the database to remove all ARULs greater than 99 for everyone. Most of the ones we found looked like cases where someone entered 100 instead of 1 by accident.
HUD E-Tool Export Service / Tool
Added more descriptive errors for:
Login failures (I.E. Bad credentials).
User doesn't have permission to update an assessment (it isn't in the needs assessor's posession).
User attempts to perform an action they are not allowed to do period (shouldn't happen normally but just to be on the safe side).
Cleaned up formatting on normal error messaes returned from the site (I.E. Building is missing data, etc).
Adjusted the export to stop exporting when a step fails so that it does not waste time trying to continue other steps.
- Continuing on Error has been found to not be an ideal behavior for the Export since it causes the export to waste time on steps that can fail due to previous failures and it also floods the error log with misleading errors.
Other Changes
Versa will no longer send "informational" errors to the Visual Studio App Center on Azure.
- This was causing computers that had errors to send messages for problems that are not actually problems (I.E. Bad URL for an E-Tool, etc.)
- This should reduce bandwith consumption for people who have metered and slow internet connections in some circumstances.
Cleaned up a lot of the code for the HUD API Client (the library we use for interacting with HUD's website).
- This does provide some negligable performance improvements but the overall goal of this is to make the software more maintainable down the road.
Bug Fixes
Fixed a bug that caused the TCO to be calculated incorrectly for Interface Line Items when export usages was enabled.
- This was a combination of mistakes in the code and also leftovers from the Companion where we were using the incorrect formula.
With the above, we also fixed a bug that caused UL-0003 not to get assigned correclty to components / interface line items when running pre-validation flag reports.
- This may need additional work, so if anyone notices UL-003s showing up when they should not or vice versa, please let Stevie & Jacob know.
Adjusted the calculating of the estimate period recap on the export screen so that it doesn't sometimes cause an error to occurr in the background.
Also adjusted the way the uninflated and inflated totals are calculated on the export screen so that it doesn't have to calculate the reserves twice.