Viewing Record Detail

VERA contains a robust log of all VERA-related activities. It tracks details, transitions, electronic signatures, and route activities that occurred on the record itself. Users have the option to view or print a detailed report. Designated users can "Approve" or "Reject" within each section when applicable. 

Viewing Records Details

The record Details vary by record type, but they will contain a VERA Details section, a source system section (e.g., Jira Details or qTest Details), and an Approval Route section.

VERA Details

The VERA Details section includes the record definition.

AttributeDescription
SystemThe record source system
Record IDThe record source system identifier is also a hyperlink back to the record in the source system
Record TypeThe classification of the item in the VERA
Item TypeThe classification of the item in the source system
RevisionRevision is an optional field by record type.  When configured, the revision number starts at one. It is iterated when an approved record is revised
AuthorThe author field is configured as the individual who routed the record for approval or by a field value on the source record. The area is not displayed if an author is not configured for a record type. If the author field is configured for a record type, but the Author is blank, it will display as "Unknown."
Record Status

The status of the record in the VERA workflow

Routing for Approval - record status when a record is routed for approval and the approval route status is In Progress

Rejected - the record status when an approval task in the associated approval route was rejected and the approval route status is Rejected.

Approved - the record status when the approval tasks in an approval route are approved, and the approval route status is Complete.

Draft - the record status when an approved record is revised, and a new revision is created

Domain NameThe VERA domain associated with the source system project.

Source System Details

The source system details section is displayed below the VERA Details section. This section contains record-specific data fields from the source system.  The fields displayed are based on individual configurations. These source system data fields are verified along with associated signatures (see Signature Verification Failure Report for more details).

Source record fields stored in VERA can be modified by configuring the Record Management Policy.

Jira Details

The following fields are displayed in the Jira Details section.  

AttributeDescription
Issue TypeJira Issue Type
DescriptionJira Issue Description
SummaryJira Issue Summary

HTML Formatting and Styles

  • Vera will display the plain text from the source Jira record.  We do not support Jira formatting at this time.  
  • For Xray user defined user lists, Vera will display the User ID (Ex: 6242b67adb7e006aa388b4), not the Username (John Doe).  


qTest Details

The following fields are displayed in the qTest Details section. 

AttributeDescription
Project NameSource record's qTest project name
Project IDSource record's qTest project ID
qTest Version IDqTest Test Case Version ID
DescriptionqTest Test Case Description
Linked DefectsDefects linked to qTest Test Case
AttachmentsAttachments linked to qTest Test Case
Step NameqTest Test Case Step #
Step DescriptionqTest Test Case Step Description
Expected ResultqTest Test Case Step Expected Result
Attachments (Step)Attachments linked to qTest Test Case Step
Linked Defects (Step)Defects linked to qTest Test Case Step
Test Case IDqTest Test Case ID of Test Run
Status (Test Run)qTest Test Run Execution Status
Attachments (Test Run)Attachments linked to qTest Test Run
Linked Defects (Test Run)Defects linked to qTest Test Run
Execution Log NameqTest Test Execution Log #
Test Case NameName of qTest Test Case used to create Execution Log
Test Case VersionqTest Test Case version used to develop Execution Log
Status (Execution Log)qTest Execution Log Execution Status
Executed StartqTest Execution Log Start date and time
Executed EndqTest Execution Log End date and time
Execution Log NotesqTest Execution Log Comments
Attachments (Execution Log)Attachments linked to qTest Execution Log
Linked Defects (Execution Log)Defects linked to qTest Execution Log
Actual ResultsqTest Execution Log Step Actual Result
Status (Execution Log Step)qTest Execution Log Step Actual Execution Status
ExecutedqTest Execution Log Step Execution date and time
TesterPerson who executed the qTest Log Step 
Linked Defects (Execution Log Step)Attachments linked to qTest Execution Log Steps
Step Attachments (Execution Log Step)Defects linked to qTest Execution Log Steps.

HTML Formatting and Styles

When handling previously formatted source text, there can be minor discrepancies between the source display and the display in Vera.  The following are some such differences that users may encounter:

  • When data is copied from Microsoft Word into qTest, and the qTest item is routed for approval, Word formatting tags are displayed in the Vera record.  Although word tags are not visible in either Word or qTest, they are retained as part of the original source data inside of qTest.  They are then rendered by Vera as part of the original source data that is passed via the qTest API.  Ex.<o:p></o:p>.
  • When images are embedded in qTest, they are displayed in Vera as download links, not thumbnails.
  • Tables created directly in qTest using the editor are displayed in Vera as formatted columns and rows, but table outlines are not displayed.  qTest table outlines are not part of the HTML that is available via the qTest API and therefore cannot be rendered in Vera.
  • Some background styles are not available in print view.  If background style is relevant to the detail or meaning of a test step value, users are advised to find another way to meaningfully represent the data.
  • Supported HTML tags are: <address>,<article>,<aside>, <blockquote>, <header>,<hgroup>, <footer>,<h1>, <h2>, <h3>, <h4>, <h5>, <h6>, <section>, <div>, <li>, <ol>, <p>, <pre>, <ul>, <a>, <b>, <br>, <cite>, <em>, <i>,<main>, <nav>, <s>, <span>, <strong>, <u>, <caption>, <col>, <colgroup>, <table>, <tbody>, <td>, <tfoot>, <th>, <thead>, <tr>
    <figcaption>, <figure>, <hr>, <abbr>, <bdi>, <bdo>, 'code', 'data', 'dfn', <kbd>, <mark>, <q>, <samp>, <small>, <sub>, <sup>, <time>, <var>, <wbr>, <nav>, <img>.

In general, where qTest either sanitizes or does not render HTML, Vera will handle this in one of the following ways:

1. If the raw HTML is available via the qTest API, we will display the raw HTML; or

2. If the qTest API does not make the html available, we will show a blank step in Vera.


Approval Route

The approval route section displays the approval route and approval tasks associated with the demonstrated VERA record.  Approve and Reject options are shown if there is a pending approval task and the user is authorized to complete the approval task (see Approving Records and Rejecting Records for more details)

The following fields are displayed in the approval route

AttributeDescription
NameThe approval route name is associated with the record status 
Status (Approval Route). 

The status of the approval route

In Progress - approval route status when one or more approval tasks are pending approval. Approvers can complete approval tasks

Stopped - approval route status when an approval task in the associated approval route is Rejected

Canceled - approval route status when the record author withdraws or cancels approval

Complete - approval route status when all associated approval tasks are complete. 

LevelThe approval route level is the approval order.  The previous level approval tasks must be completed before starting the next level approval tasks. 
Approval TaskApproval tasks represent the approval roles needed to approve the associated record.  The approval task also determines the meaning of the signature.
Status

The status of the VERA approval task.

Pending - waiting for the approver to complete approval tasks

Canceled - pending approval task is canceled when the approval route is canceled 

Not Started - waiting for previous approval route level completion

Complete - approver completed approval task

ReviewerThis field contains the approval role on Pending and Not Started approval tasks.  The approver's full name and username are displayed on the Completed and Rejected approval tasks 
DateThe date field indicates the date and time when the approval task was Completed or Rejected in UTC time

Activity History

The Activity History section displays the events associated with the VERA record.  Each event includes the record values at the time of activity.

The following activities are captured in history:

ActivityDescription
Record createdThe initial creation of the record when it was routed for approval and created in VERA
Route StartedThe record state is set to Routing for Approval. The Approval Route is created.
Electronic SignatureAn Approval Task is approved, and Completed.
RejectionThe record state is set to Rejected Record.  
Transition to RejectedOne or more approval tasks have been rejected,  The record state is set to Rejected
Record UpdatedThe record updates on subsequent Route for Approval activities after the record is created
Route CancelledThe Approval Route is Cancelled or withdrawn 
Transition to ApprovedThe record state is set to Approve when the Approval Route is Complete
Transition to Draft An Approved record is revised. A new revision of the VERA record is created with a Draft state transition
Transition to SupersededA revised record is approved, and the previously approved record status is set to Superseded.
  • For Jira Cloud, Vera will display the Jira User ID (Ex. ug:20b7f3dd-cf98-42b8-99a0-2e5872258a6c), not the username (Ex. John Doe).


Approval Routes

The Approval Route section displays the event history associated with the demonstrated VERA record. The approval routes section displays every Approval Route created for this record when it was routed for approval.

The following fields are displayed in the approval route section

AttributeDescription
RouteThe approval route name is associated with the record status status
Status (Approval Route). 

The status of the approval route

In Progress - approval route status when one or more approval tasks are pending approval. Approvers can complete approval tasks

Stopped - approval route status when an approval task in the associated approval route is Rejected

Canceled - approval route status when the record author withdraws or cancels approval

Complete - approval route status when all associated approval tasks are complete

OwnerRoute owner from the source system, the user who routed the test for approval started the started the
StartedThe date field displays the date and time when the approval route was created in UTC 
EndedThe date field indicates the date and time when the approval route was Completed, Stopped or Cancelled in UTC time 
Approval TaskApproval tasks represent the approval roles needed to approve the associated record.  The approval task also determines the meaning of signature status
Status (Approval Task)

The status of the VERA approval task.

Pending - waiting for the approver to complete approval tasks

Canceled - pending approval task is canceled when the approval route is canceled 

Not Started - waiting for previous approval route level completion

Complete - approver completed approval task

ReviewerThis field contains the approval role on Pending and Not Started approval tasks.  The approver's full name and username are displayed on the Completed and Rejected approval tasks 
DateThe date field indicates the date and time when the approval task was Completed or Rejected in UTC time

Revision History

The Revision History section displays if the record has revisions.

The following fields are displayed in the revision history section

AttributeDescription
RevisionThe VERA revision number.  Other revisions are listed with hyperlinks for the record revision.
Status

The status of the record in the VERA workflow

Routing for Approval - record status when a record is routed for approval and the approval route status is In Progress

Rejected - the record status when an approval task in the associated approval route was rejected and the approval route status is Rejected

Approved - the record status when the approval tasks in an approval route are approved and the approval route status is Complete

Draft - the record status when an approved record is revised, and a new revision is created approval

Approval DateThe date field displays the date and time when the approval task was Completed in UTC time

The revision History tab will only appear if there is more than one revision.

Print View (Record Detail Report)

The Print View section displays the details and history from VERA Details, Signatures, and Source System Details in the browser with an option to Print or Save to PDF. This print view displays the Record Detail Report.

Details

The details of the Record Detail Report are the same data as the Details page but formatted to be printer-friendly. See VERA Details for definitions of fields included in the Record Detail Report. The sections will be separated into VERA Details, Signatures, and Source System Details.

A Rejection Details section will be visible only if the record has a rejection. This section will contain a table with the following information: rejection reason, full reviewer name with reviewer username, the meaning of the approval task, and the date/time in UTC format that the rejection occurred. The Rejection Details section will not display once a record is fully approved, even if it previously had a rejection, because it is considered resolved.

Attachments

Image attachments are displayed inline at their original upload size. Non-image attachments are indicated with hyperlinks to the attachment in VERA.

Print Preview Details of Record Detail Report

Upon clicking the Print button, a print preview will display with additional information not seen on the Print View page.

  • Timestamp of when the Record Detail Report was generated
  • Footer name for VERA Record Detail Report
  • URL to the VERA record 
  • Page number out of total pages
  • End of Document marker
  • Conditional watermark based on record status
VERA StatusRecord Detail Report Watermark
Routing for ApprovalDraft
RejectedRejected
SupersededSuperseded
ApprovedApproved VERA records will not have a watermark on the Record Detail Report

Table of Contents