What's new in 2026.2

Here you'll find the latest features and enhancements in Tricentis Vera 2026.2. For a detailed list of resolved issues and known issues, check out the technical release notes.

Public API

We've added a public API so external tools and scripts can access Vera data programmatically:

  • Authenticate with an API key using the X-API-Key header. No interactive login required.

  • Each key is bound to a user and inherits that user's permissions combined with the key's scopes.

  • Keys support optional expiration dates, per-minute rate limit overrides, and IP allowlists.

  • Administrators manage keys from the new API Keys page in the administration area. Create, edit, rotate, and revoke without touching the server.

  • Deploy the new vera-api-public service as part of your 2026.2 upgrade.

SAML 2.0 single sign-on

We've moved SAML SSO management into the Web Portal, so Site Administrators can configure single sign-on without editing YAML files or restarting the server:

  • Register, edit, and delete SAML identity providers from the new Identity Providers page.

  • Upload IdP certificates and update authentication contexts directly in the UI.

  • Validate each IdP before rollout with built-in login and signature SSO tests.

  • Control how Vera identifies itself to your IdP from the new Service Provider page.

Record Integrity

We've added a new admin workspace for sync issues between Vera and connected source systems:

  • Triage potential mismatches from the new Record Integrity queue under Administration > Source Record Management.

  • Run a Check to confirm whether the source system is still out of sync, individually or in bulk.

  • Use Try to fix automatically to push Jira or qTest to the state Vera expects, including a full qTest remediation sequence.

  • Accept intentional differences with status mappings, dismiss explainable mismatches with a required reason, and export the queue to CSV.

  • Decide who gets the email alert from the new Mismatch Notification page: all administrators, a single administrator, or no one.

  • Deploy the new vera.api.recordintegrity and vera.worker.recordintegrity services as part of your 2026.2 upgrade.

GraphQL Console

We've added a read-only GraphQL Console so system administrators can query and export Vera data for compliance and reporting:

  • Query records, approval routes, domains, users, revisions, attachments, and traceability data from the new GraphQL Console under Reports.

  • Start from example queries for common scenarios, such as approval history and non-compliant records.

  • Export results as JSON and download linked attachments through their URLs.

  • Enable the console and query engine as part of your 2026.2 upgrade.

Upgrade to Tricentis Vera 2026.2

For detailed information on how to upgrade, see Upgrade to 2026.2.