Skip to main content

Release Notes 21-04-2026

Written by Support
Updated today

21-04-2026 April 2026 Quick Release V1

Summary

This release adds a new AI Review Comments feature in Forms, resolves an AI review submission blocker, fixes data display and scoping issues in Documents, and introduces an optional document download proxy for users in restricted-network regions.

Forms

  • AI Review Comments - You can now add a comment on any AI review inside a form to record your thoughts, planned actions, or disagreements with the AI feedback. Each comment is limited to 1,000 characters and one per review, and appears inline with the review as well as in the form's history.

  • AI Review No Longer Blocks Form Submission on Failure - When an AI review on a required question fails, you can now submit the form instead of being locked out. A separate fix also resolves repeated errors during AI review polling for workers assigned to multiple organisations.

Documents

  • Global Documents Dashboard No Longer Shows Stale Documents - Fixed an issue on the Global Documents Dashboard where documents tied to a worker's previous category reappeared after the worker's category was changed. Only documents still actively required by the worker or contractor are now shown for processing.

  • Required By Column Display Fix - Fixed a display issue where the Required By column in the Documents list showed raw HTML tags instead of the organisation names when a worker document was required by three or more organisations. The column now renders correctly with a tooltip showing the full list on hover.

  • Optional Document Download Proxy - A new per-organisation setting lets documents be served through the ComplyFlow app domain instead of Amazon S3 links, so users in regions where S3 is blocked can still open worker, supplier, plant and project documents. The setting is off by default β€” no change for existing organisations.

Security & Code Quality

  • Authorisation Safety Hardening - Eight authorisation checks across audits, documents, worker records and permit types have been hardened so that denied access is always explicitly returned. This improves code safety and static-analysis compliance with no change to who can access what.

Did this answer your question?