Topics:
⚠️ Important: Action May Be Required After This Update
As part of our recent update to improve clarity and consistency across compliance records and reporting, some field and column names have changed.
Because of this, you may notice:
Previously saved table views (e.g., Assemblies or Locations) are missing columns — these will need to be reconfigured using the new field names.
Dashboard Widgets - If a user previously had a table dashboard widget set up with one of the updated columns, that column will no longer be displayed. It will need to be readded.
Familiar fields may appear under different names — you’ll need to search for them using their updated terminology.
These changes help make SwiftComply more intuitive and accurate, but we recommend reviewing and updating your saved views to ensure everything appears as expected.
Read on for a full breakdown of what’s changed and how it may affect your workflows.
Compliance Updates
What is Changing in the Compliance Record?
We’ve updated how compliance records are managed when a test report is accepted, to ensure that the information shown is always accurate and up to date:
Automatic Updates Based on Test Date:
When a test report is accepted, if the Tested On Date is later than the current Last Tested On date in the compliance record, the following fields will be updated:Last Tested On → updated to match the Test Date
Last Test Result → updated to match the Test Result from the accepted report
These updates will happen regardless of the Preserve Date or Allowable Window Days (AWD) settings, making the compliance record the most reliable source for the latest accepted report details.
Update Next Test Due Date Logic Remains Unchanged:
The Update Next Test Due date will not update if the Test Date falls outside the AWD or the overall result is noncompliant. This is consistent with current behavior and ensures that scheduling remains aligned with jurisdictional rules.No Updates for Older Reports:
If the accepted report has a Test Date earlier than the current Last Tested On date, no changes will be made to the compliance record. This prevents overwriting newer data with outdated information.
These changes improve the accuracy of the compliance record and ensure it reflects the most recent, valid test report data, supporting more reliable reporting and easier decision-making.
Resetting Accepted Reports
What Happens When a Report is Reset to In Progress?
If an accepted test report is reset to In Progress, and that report was the latest one based on the Reported On date, the system will automatically update the compliance record using the next most recent accepted report.
Here’s how it works:
The system looks for the accepted report with the next highest Tested On date.
The Last Tested On, Update Next Test Due, and Last Test Result fields in the compliance record will be updated to reflect that report.
This logic ensures the compliance record always reflects the most up-to-date accepted report.
Important Note:
Manual changes made directly to the compliance record (outside of accepted reports) will not be retained if a report is reset. The system only considers data from accepted test reports when determining compliance record values.
Clearer Labels, Headers, and Filters
We’ve updated field labels, column headers, and table filters to make them easier to understand and ensure they’re aligned with the same underlying data.
These improvements help eliminate confusion and make it simpler to interpret what you’re seeing, whether you're viewing a compliance record, running a report, or filtering results. The updated terminology reflects how customers use the system and supports a more intuitive, consistent experience across SCBF.
Updated Field Labels
Updated Column Names - Assemblies
Note: Renaming these fields will reset them in your user preferences, meaning the affected columns may need to be re-added to your custom views.
Overall Compliance:
This status shows whether an assembly is currently compliant by evaluating both the Last Test Result and the Update Next Test Due date. An assembly must have a passing test result and not be overdue to be considered compliant.
Assembly Compliance Updates
Updated Column Names - Location
Note: Renaming these fields will reset them in your user preferences, meaning the affected columns may need to be re-added to your custom views.
Overall Compliance:
Indicates whether a location is compliant by checking both the Last Survey Result and the Update Next Survey Due date. To be considered compliant, the location must have a passing survey result and not be overdue for the next survey.
Location Compliance Updates
Updated Filter Names
Updated Tables
Test Table
These fields help you understand how and when the Update Next Test Due date is affected by accepted test reports.
Possible Update Next Test Due
Shows the date the Update Next Test Due field would update to if the test is accepted and meets all criteria for updating the field.
Update Update Next Test Due
Indicates whether accepting the test actually updated the assembly’s Update Next Test Due date. (Blank if the test is not accepted.)
Update Next Test Due At Acceptance
Displays the value of the Update Next Test Due field at the moment the test was accepted.
(Blank if the test is not accepted.)
Survey Table
These fields help explain how the Update Next Survey Due date is calculated and updated when a survey is accepted.
Possible Update Next Survey Due
Displays the date the Update Next Survey Due field would update to if the survey is accepted and meets the update criteria.
Update Update Next Survey Due
Indicates whether accepting the survey updated the location’s Update Next Survey Due date.
(Blank if the survey is not accepted.)
Update Next Survey Due At Acceptance
Shows the value of the Update Next Survey Due field at the time the survey was accepted.
(Blank if the survey is not accepted.)
Updated Reporting
