If the documents included in an Update Documents Action in a CAPA are not in either Published or in Draft status when the CAPA reaches Implementing Status, then the Action will not be completed until the documents have finalized the Approval Cycle they are currently in and are then pushed through another full approval cycle.
In other words, the documents need to go through a full approval cycle before the action is completed. The action will be marked automatically as closed by the system once this happens, and the document reaches Approved, Not Published status.
Steps According to Document Status at Implementing Status of CAPA
Draft:
If the document is in Draft status, the author can make the necessary updates. Bear in mind that the document must reach Approved, not Published before the task will be marked as closed.
Under Review/Under Signing by Approver/Under Signing by QA>Reject >Draft:
If the document is Under Review/Under Signing by Approver/Under Signing by QA, the responsible person should reject it and push it back to Draft. This way, the author can make the necessary updates. The document must then reach Approved, not Published before the task will be marked as closed.
Approved not Published>Publish>Force Review>Draft:
If the document is in Approved, not Published status, first publish the document. Once the document reaches Published status, select Force Review. This will push the document back to Draft status so the required updates can be made. The document must then reach Approved, not Published status again before the task will be marked as closed.
Published>Draft:
If the document is in Published status, the system will force review the document taking it back to Draft status for the author to make the necessary changes. It will then need to be pushed through the approval cycle for the action to appear as closed. The document must reach Approved, not Published status again before the task will be marked as closed.