Approval Route Information

Viewing Current Approval Route Progress

An entity that has been routed for approval will display the status of that route in the Approval Route field. The field displays the name of the approval route, the current status of each task group (i.e. levels), and the current status of each approval task.

Figure: Approval Route Field Example

Pending Approvers

The pending approvers for each record are identified in two fields: Pending Tasks and Approval Route. The Pending Tasks field can be used in filters and reports to easily show the records waiting for a user's approval.
Users can use the Entity Grid View to easily filter on their user name or approval role to see their pending approval tasks.

Figure 25: Grid View Filtered for a User's Pending Approval Tasks

Figure: Grid View Filtered for an Approval Role's Approval Tasks

Rejection Reason

If an entity is rejected, the Rejection Reason field will be populated with the rejection reason entered by the user who rejected the entity. The field will be cleared when the entity is routed for approvals again.

Figure: 'Rejection Reason' field after a record was rejected.

Signature

The Signatures field contains all signatures applied to the current revision of an entity. Each signature contains the following information at a minimum:

• The user's full name
• The user's ID
• The date/time stamp of when the signature was created
• The signature's meaning (e.g. Content Originator, Technical Approval)
• The type of approval route the signature is associated with (e.g. approval, pre-execution approval)
• The format version of the signature. (This field is used to identify changes to signature formats as new versions of VERA are released.)

Figure: 'Signatures' field with two signatures

Approved Records

Approved records are records that have completed an approval route and have received all required electronic signatures. In most workflows, once a record is approved, it cannot be further edited or reworked unless it is revised. If the record type does not support revisions (ex. test runs and defects), then the record will be permanently locked against further changes.