Record Issue
Record Issue Task
- Overview
- The Deviation shall be initiated at this step of the workflow.
- Sections
- These sections Equipment/Instrument, Customers, Suppliers, Product, Process/Operations are not visible initially but users have to choose which sections that are relevant to the Deviation and enable them in Scope section.
Sections |
Visible |
Editable |
Deviation Details |
✔ |
✔ |
Immediate Actions |
✔ |
✔ |
Scope of the Problem |
✔ |
✔ |
Impact Assessment |
✔ |
✔ |
Implementation Actions |
✔ |
✔ |
Equipment/Instrument |
✔ |
✔ |
Customers |
✔ |
✔ |
Suppliers |
✔ |
✔ |
Product |
✔ |
✔ |
Process/Operations |
✔ |
✔ |
Summary of Implementation |
❌ |
❌ |
- Routing
- Please refer to the diagram in the Overview section to see an end-to-end workflow.
- A Deviation can only be routed forward to the Approval step.
- Entering Record Issue Task
- The Record Issue task is entered after starting a new Deviation.
- Submitting Record Issue Task
- Submitting Record Issue Task will follow the standard routing process. Please refer to the routing process in the introduction module of this guide for more details.
.