Release Notes 20.09

Release Notes
Bidding
Bug
Fixed an issue which would prevent you from creating new quote templates if an existing template had a ' character in the title, "John's Template", for example
G1083
20.09.02
Bug
The 'Check Flags' message has been improved for reverting a quotes status'.
F4764
G1090
20.09.03
Billing and Invoicing
Feature
We've added the option of viewing "no charged" billings to the billing row assignment page, and removed no charged rows from it, by default.
This new screen will allow you to toggle the no charge status from a costing row if it is inaccurate.
F3046
G841
20.09.01
Company and Contact
Bug
Fixed issue where selecting a Country would clear the Town and City fields on the Company details page.
F4718
G1077
20.09.01
Jobs
Bug
Fixed issue with Jobs where the client attending details would not load into the Client Attending dialog.
G1088
20.09.03
Feature
Added the Resource Information icon to the 'Action' column on the Job Schedule tab. Requires the 'showResource' permission.
F4695
G1085
20.09.02
Projects
Bug
Fixed issue where you received an 'Invalid Entity' message when trying to delete a comment from the Project 'Comments' tab.
G1086
20.09.02
Reporting and Dashboard
Bug
Fixed some 404 errors when opening the Dashboard (likely no noticeable problem to the user).
G1073
20.09.01
Bug
Fixed issue with the 'Bid Revenue by Line Item' Dashboard report where the end dates in the search criteria didn't take time into account so some records may not be returned in certain timezones.
G1089
20.09.03
Feature
Fixed issue with the 'Bid Revenue By Line Item' dashboard report where the ordering on the Date columns would be alpha numeric rather than by the actual date.
F4525
G1074
20.09.01
Security
Bug
Attempting to log in using a Locked account will now report the correct reason for login failure - previously would say 'Invalid credentials'.
G1075
20.09.01
Bug
Password is no longer mandatory when saving a User, if using Okta authentication method for login.
G1076
20.09.01
Bug
We fixed an issue that was causing the Spectrum API to create hundreds of Session records in the database. The API no longer requires any sessions and relies completely on the token for users to access its resources. This change is invisible to the end user - other than increasing the speed of all API calls slightly.
G138
20.09.01
Robert Salmeron