Start Post Execution Approval Routes

Owned by Henry Farris (Unlicensed)
Last updated: Mar 02, 2022 by Tim Hartman
2 min read

Testers can submit test runs for approval by starting an approval route. Reference Starting an Approval Route and Configuring an Approval Route of this user guide for more information about starting and configuring approval routes.

Action Menu Button

Default Role(s)

Tester

Record Type(s)

Test Runs

Starting Workflow State(s)

Draft

Ending Workflow State

Routing for Approval

Special Rule(s)

  1. The Execution Status must be either Passed, Failed, or N/A.
  2. The record will become locked against editing.
  3. The Approval Route field will be updated with the new route information.
  4. The Pending Tasks field will be updated with the Level 1 task information.
  5. The Rejection Reason field will be cleared when the route is started.
  6. The Attachment History field is populated. See Section 10.2.
  7. The record will automatically transition to Approved after the route is complete.
  8. The record will automatically transition to Rejected if the route is rejected.
  9. First-level task assignee's will receive an email notification.
Runs can be routed for approval on an individual basis from the Test Runs module or on a multiple-Run basis from the Test Lab Module.


Warning: The default workflow includes a Tester Approval as the Level 1 approval for Runs. This will require any users listed in the Testers field to approve the Run. If a user listed in the Testers field has been removed from the project (deleted from the Project Users list in Customization), the approval will be skipped. If none of the Testers exist in the project, all Tester approvals will be skipped and the Run will progress directly to Level 2 approvals.