We’ve introduced updated password security requirements to better protect user accounts and align with industry security standards.
Passwords are now required to meet the following criteria:
At least 12 characters
At least one number
At least one special character
These requirements are enforced server-side to ensure they cannot be bypassed.
New and updated passwords
The new requirements apply to:
New user registrations
Password resets
Password changes
Any new password created must meet the updated security standards.
Existing users
If your current password does not meet the new requirements:
You’ll be prompted to update your password after logging in
A message will explain why the update is required
You’ll be guided to the existing password reset flow to complete the update
This ensures all accounts meet the same security baseline.
This update strengthens account security across your organization by protecting against unauthorized access — especially important for clients managing sensitive environmental and compliance data.
We’ve improved how photos are displayed when printing Findings Reports to ensure a more consistent, readable layout and to reduce wasted space.
Photos attached to findings are now laid out using a standardized grid-based format when printed.
Updated photo layout behavior:
Up to 4 photos per finding will appear on the same page as the finding details, whenever possible.
Photos are arranged in a consistent 2×2 grid when 3–4 photos are present.
Photo sizes automatically adjust to fit the page while preserving their original aspect ratios.
Page breaks occur only when a finding includes more than 4 photos.
Findings with more than 4 photos:
Photos 1–4 appear on the same page as the finding details.
Photos 5–8 start on the next page.
Additional photos continue in groups of 4 on subsequent pages.
This update resolves issues where:
Photos appeared inconsistently stacked or side-by-side
Images spilled onto new pages unnecessarily
Large blank spaces appeared in printed reports
We’ve improved how legend items are positioned on site maps to ensure they stay correctly aligned—even when a map image is replaced or resized.
Legend item placement is now stored in a resolution-independent format, allowing positions to scale correctly with different image sizes.
This means:
Replacing a site map image no longer causes legend items to shift or misalign
Legend placement remains consistent across image uploads, replacements, and resizes
Existing maps continue to render exactly as expected
Legend positions now adapt automatically to the current map image size
Placement is calculated relative to the map dimensions instead of fixed pixels
When older maps are opened, existing placements are preserved with no user action required
If a replacement site map has a significantly different aspect ratio, the system will display a warning so users can confirm alignment after replacement.
With this update:
Legend items stay visually aligned when maps are replaced
Image resizing no longer breaks legend placement
Map history and existing projects remain unaffected
No changes are required from users—this improvement applies automatically.
We’ve enhanced the Compliance Report to make it easier to identify aging risk and overdue issues across projects.
A new column, Oldest Open Finding, has been added to the Compliance Report table.
The column appears immediately to the right of the existing “Open Findings” column
It shows the age (in days) of the oldest currently open finding for each project
For each project:
The system looks at all open findings
Identifies the earliest created (date initiated) finding
Displays the number of days since that finding was created
If a project has no open findings, the column will display:
“—”
The Oldest Open Finding column is available in:
The on-screen Compliance Report
Exported reports (Excel / CSV)
The column can also be:
Shown or hidden using the column selection filter
Sorted by clicking the column header
This update helps teams:
Quickly spot projects with long-running open issues
Prioritize follow-up and escalation
Assess compliance risk at a glance without drilling into individual findings
No configuration changes are required—this column is available immediately.
We’ve updated how legend items behave on previous (historical) versions of site maps to improve data integrity and ensure maps accurately reflect the conditions at the time they were created.
For projects using Inspections
Legend items on previous map versions are now locked.
Their size and location can no longer be edited.
You can still:
Add new legend items
Remove existing legend items
If you need to modify an existing legend item (size or placement), this must be done on the most recent version of the map.
This ensures historical map versions remain an accurate record of past inspections while still allowing updates to current work.
For projects using the Map Editor only (no inspections)
Once a legend item is added:
Its size and location cannot be changed
You can still:
Remove legend items if needed
This behavior helps maintain consistency across map versions when inspections are not part of the workflow.
Locking legend item placement on historical maps helps:
Preserve inspection accuracy
Prevent unintentional changes to past records
Ensure a clear and reliable map history
If you have questions about how this impacts your workflow, please reach out to support.
We’ve fixed an issue that could cause duplicate findings to be created if the Save Finding button was clicked multiple times before the initial save completed.
In some cases, users could unintentionally create multiple findings by clicking Save Finding more than once while the system was still processing the original request. Each click resulted in a separate finding being created, leading to:
Duplicate records
Inflated finding counts
Additional manual cleanup
This behavior could occur when creating findings from:
The Findings page
The site map editor
The finding creation flow has been updated to prevent duplicate submissions:
The Save Finding button is now disabled while a save is in progress
Additional clicks are ignored until the save completes or fails
Only one finding is created per user action
If a save fails, the button is re-enabled and an error message is shown
These safeguards apply consistently across all areas where findings can be created.
With this update:
Duplicate findings can no longer be created by rapid or repeated clicks
Finding counts and reports remain accurate
The saving experience is clearer and more predictable
Data integrity is preserved, even under slow network conditions
No action is required—this fix is applied automatically.
Back to Release Notes