Ideagen Audit Quality v2.3.0 - v2.3.1 release notes
Who is this article for?
Administrators interested in learning more about solution updates.
No special access or permissions are required.
Versions 2.3.0 and 2.3.1 make Queries generally available, lay the groundwork for upcoming API access to query results, improve data layouts for analytics tools, and strengthen audit scope handling, risk reporting, and overall reliability across assessments, views, attachments, and Office Online collaboration.
This article outlines the full changes, enhancements, and fixes that have been implemented in this release, available from 23 April 2026.
1. Features
Queries
Queries are used to define saved data extracts. You choose which information to include (fields), how to order it (sorts), and how to narrow it (filters), using perspectives that match how assessment and risk data is structured - including related records where the product supports sub-queries (for example, linked detail under a parent record).
Each definition can be run on demand. A run produces structured data (JSON) that you can download. This means that the same definition can feed spreadsheets, BI tools, or other systems without rebuilding the logic each time.
Queries are now fully available to users so teams can build, save, and run structured extracts with confidence. You can retrieve saved query results through a JSON export for tools such as Power BI or Excel. Exported data is easier to use in analytics tools: information is laid out in a flatter, more consistent way, including custom fields and roles, so imports need less manual reshaping. The query experience also supports a wider set of record types and relationships, making more of your assessment and risk data addressable in one place.
Smarter scope management
Continuing the work from the previous release, this release refines how scope and the assessment universe stay aligned when plans change, with clearer prompts and safeguards so teams can manage scope safely and predictably - including stricter rules where location must be part of scope in certain configurations.
Documents and collaboration
Attachments linked into assessment work cannot be removed while still in use, supporting a defensible audit file. Office Online improvements address co-authoring when others are editing, and lock messaging when documents are hard-locked, so teams understand who can edit and when.
Guidance and clarity
Locations and service line registers include clearer on-page guidance to help people use them correctly. Where views use rich text on standard fields, you'll see an appropriate warning when it matters. Assessment methods can no longer be added in ways that clash with methods already fixed by the relevant record type.
2. Fixes
We've resolved issues across the solution, including:
- File uploads (including clearer messaging for certain file names)
- Attachment handling in the UI
- Assessment views (terminology on audit trail, planned risks appearing reliably, process changes on audit work items)
- Lists for limited roles
- Multi-select row counts on registers
- Creating multiple locations or service lines