OpenText AQM 26.126.125.1 gives release owners group-based approval permissions and configurable re-authentication for electronic-signature actions, making it easier to enforce accountable release decisions. The update also expands reporting, requirements evidence, version control, and reusable baseline capabilities in the Web Client.
Reporting that supports release decisions
Project teams can now generate, preview, and download project reports directly in the Web Client. Business View Excel reports can also be generated and modified in Microsoft Excel, providing a practical route for teams that need governed operational reports alongside executive-ready analysis.
For release management, the value is not simply more reports. It is a clearer and more repeatable path from quality data to decision evidence:
- Produce project-level evidence without depending on desktop-only reporting workflows.
- Export Business View data for controlled analysis and stakeholder distribution.
- Reduce manual collection of status, coverage, and quality information before release reviews.
Report ownership still matters. Organizations should define approved report templates, data refresh expectations, and who may distribute release evidence externally.
Tighter control of coverage and traceability
The Web Client now lets teams add requirement coverage to tests and refine that coverage by test configuration. This makes coverage evidence more specific where a requirement must be validated across platforms, environments, or configurations.
A new site parameter, DISABLE_REQUIREMENT_TEST_COVERAGE, allows administrators to prevent users from adding new requirement-to-test links. This is important for programs where coverage relationships are controlled artifacts: an unauthorized link can make a coverage position appear stronger than the approved test strategy supports.
