Users can submit defects 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 | Image RemovedImage Added |
Default Role(s) | Defect Manager, Tester |
Record Type(s) | Defects |
Starting Workflow State(s) | For Defect Manager: New, Open, Ready to Verify, Deferred For Tester: Ready to Verify |
Ending Workflow State | Routing for Approval |
Special Rule(s) | - The GxP field must by Y.
- The Category field must not be blank.
- The Analysis field must not be blank.
- The Verification Evidence field must not be blank.
- The Resolution field must not be blank.
- The Resolution Type must be one of: Code Change, Configuration Change, Documentation Update, Externally Resolved, User Training, Workaround Implemented, or Other. (See Below)
- The record will become locked against editing.
- The Approval Route field will be updated with the new route information.
- The Pending Tasks field will be updated with the Level 1 task information.
- The Rejection Reason field will be cleared when the route is started.
- The record will automatically transition to Closed after the route is complete. The Approved field will be updated to Y at this time.
- The record will automatically transition to Rejected if the route is rejected.
- First-level task assignee's will receive an email notification.
|
...