Query and export Vera data

The GraphQL Console lets system administrators query Vera data directly from the Web Portal. Use it to build repeatable exports for compliance reporting, traceability, and user access reviews. These reports previously required manual MongoDB exports or support requests.

The console is read-only. You can retrieve records, approval routes, domains, users, revisions, attachments, and traceability data, but you can't change Vera data through GraphQL.

Before you start

To open the GraphQL Console, you need:

• The system administrator role.

• The console enabled for your deployment. To enable it, check out Enable the GraphQL Console.

What you can query

The GraphQL Console gives you access to the following data:

Data	What you can retrieve
Records	Filter by status, record type, release, domain, and other fields. Includes approval signatures and revision history.
Routes	Approval history, task groups, approver names, and timestamps.
Domains and users	Domain ownership, role assignments, time zones, and related metadata.
Record revisions	Full revision history with linked approval routes for a record or a set of records.
Attachments	Download links for files linked to records and to records in linked sub-records, such as execution logs on a test run.
Requirements traceability	Requirement-to-test-to-run hierarchies for document generation and RTM-style reporting, with approval and execution timestamps where configured.

Important considerations

Keep the following in mind:

Behavior	What to expect
Read-only access	The console blocks mutations and subscriptions. If you run a mutation, the console returns an error.
Field aliases on ID fields	If you alias certain identifier fields, such as syncId, your query may fail. Alias display fields such as status or name instead.
Session timeout	If your portal session expires while the console is open, queries may return an authorization error until you reload the page or sign in again. The inactivity prompt may not appear inside the embedded console frame.
Supported queries	Tricentis documents a set of example queries for common customer scenarios. Use those as starting points; ad hoc queries beyond the documented patterns may not be supported.

Open the GraphQL Console

To open the console, follow these steps:

1. Sign in to the Tricentis Vera Web Portal with a system administrator account.

2. Open Site Administration.

3. In the left navigation, expand Reports and select GraphQL Console.

Run a query

To run a query, follow these steps:

1. In the query editor, enter or paste a GraphQL query. Name the query after the query keyword, for example query ApprovedRecords { ... }, so you can identify it later.

2. Select Run, or use the keyboard shortcut shown in the console toolbar.

3. Review the results in the response panel. Expand nested objects to inspect signatures, linked records, attachments, and other fields.

To browse available fields and filters, use the schema explorer in the Documentation panel. The console supports standard GraphQL features such as field aliases. For example, if you want to rename status to recordStatus in the result.

Export results

To export results, copy the JSON from the response panel into a spreadsheet tool, script, or BI connector. For large exports, run focused queries that filter by release, status, or date. Don't pull entire collections at once or you might receive a timeout error.

Download attachments

When a query returns attachment metadata, each attachment includes a url field. To download the file, open that URL in a new browser tab while you're signed in to Vera. If you're not signed in, Vera prompts you to authenticate before the download starts. GraphQL results don't return embedded images inline, so use the attachment URL to download the file.

What's next

Check out Example GraphQL queries for Vera data export to build common compliance and reporting exports.