A Task can be Rejected at two different stages of a Change Request:
- During Implementing status
- While in Under Signing By QA status.
Action Approval/Rejection cycle - Implementing Status
The Task Responsible User (John Smith in this example) will be able to perform the assigned Task once the Change Request reaches the Implementing status from his dashboard:
To sign off the Task, the Responsible User will need to click on the Change Request title and:
- Click on the Actions button
- Click on Close Task
On the Update task status window:
- Introduce electronic signature credentials: User and Password
- Submit Remarks
After he/she signs off, the action will be in its Pending Approval status and will not be displayed on the Users dashboard anymore (Only if the User has chosen to only have "Action Required" items displayed in the filters option, otherwise the "Pending Approval" CAPA Action will still be displayed). At this moment, the QA (Kate Peterson in this example) will be requested to Approve or Reject the completed Action:
If the Action is Rejected, it will become available once again as Open on the Action Responsible User Dashboard.
Please note: The requirement for Action Approval from QA while the Change Request is in Implementing status depends on a Module Configuration.
Action Approval/Rejection cycle - Under Signing by QA Status
While the Change Request is in Under Signing by QA status, QA has the option of rejecting specific Actions when rejecting the CAPA and setting it to Implementing status.
From the Change Request Details page, the QA decides to click on Reject as a QA:
In the Reject change request form pop-up, QA will need to:
- Select the Custom Actions to be Rejected
- Provide a Reason
Where can I see the rejection notification?
Going back to John Smith's Scilife dashboard, we can see that the Change Request Task is displaying again. This notification will also be present in the User's e-mail.
This information also becomes available on the Change Request Audit Trail.