September 2024 Release Notes

Here is an overview of enhancements and bug fixes to the Clearstory platform for the month of September

This month, we launched The T&M Hours chart in Customer Insights and Contractor Insights. This chart allows users to view and export the count of each type of labor hour recorded on T&M Tags over daily, weekly, and monthly timelines.

Users who are associated with only one office will now see the “Offices” column on the Manage Users page, allowing them to easily identify their office when needed.
Users can now sort their COR Logs by Procore Change Event.
Contract Settings are now available for accounts with a Professional License. Users have the option to prevent Contractors from editing certain COR details, restrict them from submitting revisions on CORs outside the Revise & Resubmit stage, and limit their ability to add individuals to a Project.

Fixed an issue where the account name was used instead of the Business Name on No Cost Impact emails.
Fixed an issue where deleting a Change Notification failed if all the Contractors have been removed from the Change Notification.

We fixed an issue with the Vista integration for Received CORs that would remove the PCO # and replace it with Unassigned in the COR log, if the sending contractor updated the COR.
We fixed the issue where the Contract Name was displayed instead of the Business Name in the Change Notification Details page.
We fixed an issue where line breaks in the description of a Change Notification were removed in the email sent to contractors.
We fixed the issue with importing projects for the HCSS integration, users can now import projects upon integration setup.

We have removed the ‘T&M Hours’ Tab from the Contractor Insights page due to some data discrepancies that we discovered when calculating Labor Hours and assigning them to certain dates.
Fixed an issue where empty Analytics report exports had code-strings in the cells instead of being empty cells.
Fixed an issue where users were unable to create new contracts due to the ‘Create New Contract’ form stating that a field is required but not filled in, even though the user had filled it in with valid information.