quality module and carry an nc-prefixed internal ID plus the user-facing nonConformanceId. See the quality overview for broader module context.
Create an issue from the issue list, MES, or Slack. Alforse can also create one automatically when an inbound inspection rejects a lot. All sources use the same lifecycle.
The lifecycle
AnonConformanceStatus has three values. A new issue defaults to “Registered”; “Closed” is terminal and locks the record.
quality update permission: “Start” (Registered → In Progress), “Complete” (In Progress → runs closeIssue), and “Reopen” (In Progress or Closed → Registered). The reopen path is why Closed isn’t a dead end. It just re-opens the record for more work.
Header fields
Every issue carries a small set of classification fields. Type and location are required; the rest have defaults or are optional.Workflows: the 8D and its cousins
A workflow is a reusable template, not a state machine. It defines initial rich-text content, priority, source, required actions, and approval requirements. Selecting a workflow copies those values into the new issue. Alforse models as a workflow whose required actions cover the eight disciplines. 8D behavior is not hard-coded; custom workflows use the same action model.Required actions and their system categories
Each issue references a set of required actions (requiredActionIds), and the moment the issue is set up, Alforse materializes one action task (nonConformanceActionTask) per required action, numbered by sort order. Those tasks are the checklist the team works through.
A required action can carry a systemType that classifies what kind of action it is. There are five:
The five system actions (Containment Action, Corrective Action, Preventive Action, Verification, Customer Communication) are seeded per company and protected: a database trigger blocks deleting them or changing their systemType, and each is unique per company. Any action you add yourself has no systemType and is fully editable.
Working the tasks
Action tasks run their own small lifecycle: “Pending” → “In Progress” → “Completed”, with “Skipped” as an off-path exit. Tasks start Pending and do not auto-start. Completing a task stamps its completed date. A completed or skipped task can be reopened back to Pending. Tasks can be reordered, given due dates, and tied to specific processes, and a supplier-facing action task can be shared externally as a SCAR (Supplier Corrective Action Request) report. The SCAR is a private, login-free link the supplier opens to respond. They see the non-conformance details, the current status, and the action tasks assigned to them — not the rest of the issue: dispositions, approvals, and closure stay internal. For each task the supplier can update the status and write notes in an editor that auto-saves as they type; entering notes on a “Pending” task promotes it to “In Progress” automatically. Once the issue is “Closed”, the SCAR locks and the supplier can no longer make changes. Whoever holds the URL can open it, so send it only to the supplier contact.Approvals and the Material Review Board
Beyond actions, an issue can require approvals. The only approval requirement Alforse ships is . Adding it materializes an approval task and, when MRB is newly required, seeds two reviewers with titles “Engineering” and “Quality”. Remove MRB and those seeded reviewers are cleared; reviewers you added by hand are left alone. A reviewer is just a title on the issue. You manage the list inline on the issue.Dispositions: deciding the material’s fate
Closing an issue is where the affected material gets resolved. EachnonConformanceItem row carries a — the decision about what to do with that material. The database enum has more values than the UI exposes; the active picker is a deliberate subset of five: