> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/xoroerp-1/manufacturing/quality-issue-code/quality-issue-code-centre/quality-issue-code-centre-fields.md).

# Quality Issue Code Centre Fields

### Overview

The **Quality Issue Code Centre** provides visibility into available quality issue codes, their status, and configuration details. These quality issue codes are applied during workstation logging when reporting quarantined quantities, ensuring consistent defect categorization and structured quality tracking across production processes.

### Header Level Options

The following options are available under the **Options** menu in the Quality Issue Code Centre. These options allow users to perform actions on selected quality issue code records.

* **Batch Delete:**\
  This option allows users to delete multiple selected quality issue code records at once. Deleted records cannot be used for quality issue reporting in manufacturing processes.

### Header Level Search Fields

The **Header Level Search Fields** allow users to filter and locate specific quality issue code records quickly. 

| **Field** | **Description**                                                                       |
| --------- | ------------------------------------------------------------------------------------- |
| Name      | Allows users to search quality issue codes by entering the name of the quality issue. |
| Code      | Allows users to search records using the unique code assigned to the quality issue.   |

### Header Level Icons

These features provide users with flexible navigation, search refinement, and data management capabilities while working in the Quality Issue Code Centre.

* **Navigation Controls:**\
  Allow users to move between records or pages within the grid.
* **Refresh:**\
  Refreshes the grid data based on selected search criteria to display the most recent information.
* **Save:**\
  Saves any updated user interface (UI) settings, ensuring a consistent viewing experience in future sessions.
* **Advanced Search:**\
  Allows users to perform detailed searches by specifying criteria such as column name, operator, and value for precise record filtering.
* **Download:**\
  Enables users to export data in multiple formats such as CSV, TXT, MS Word, MS Excel, PDF, and Excel (.xlsx) for reporting or analysis.
* **Columns:**\
  Allows users to customize visible grid columns. Available options may change based on selected search criteria.

### Quality Issue Code Centre Columns

The Quality Issue Code Centre displays the following columns to provide visibility into quality issue code details.

| **Field**  | **Description**                                                                                                  |
| ---------- | ---------------------------------------------------------------------------------------------------------------- |
| Name       | Displays the name of the quality issue that identifies the type of defect or production issue.                   |
| Code       | Displays the unique identifier assigned to the quality issue code for reference and tracking.                    |
| Is Active? | Indicates whether the quality issue code is active and available for use in manufacturing and quality reporting. |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.xorosoft.com/xoroerp-1/manufacturing/quality-issue-code/quality-issue-code-centre/quality-issue-code-centre-fields.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.