> 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/admin/printing/print-service-queue/print-service-queue-fields.md).

# Print Service Queue Fields

### Overview:

The Print Service Queue provides header-level options, search filters, and grid columns that allow users to track and manage print jobs efficiently. It acts as a monitoring hub for all print-related activities within the system.

### Header Level Options

The following options are available under the **Options** menu in the Print Service Queue. These options allow users to manage and control print jobs efficiently.

* **Batch Delete:** Allows users to delete selected print jobs from the queue. This is useful for removing unwanted, failed, or duplicate print requests.
* **Reprint:** Allows users to resend selected print jobs to the printer. This is useful in cases where a print job failed, was missed, or needs to be printed again.

### Header Level Search Fields

These fields allow users to filter and locate specific print jobs.

| Field         | Description                                             |
| ------------- | ------------------------------------------------------- |
| Printer       | Filters print jobs based on the selected printer.       |
| Print Service | Filters print jobs based on the selected print service. |

### Header Level Icons

These features provide quick actions for managing and viewing print jobs:

* **Navigation Controls:** Allow users to move between pages within the grid.
* **Refresh:** Refreshes the print queue to display the latest job statuses.
* **Save:** Preserves user interface settings such as column preferences.
* **Search:** Allows quick searching of print jobs.
* **Advanced Search:** Enables detailed filtering using conditions like column name, operator, and value.
* **Download:** Exports print queue data in formats such as CSV, Excel, or PDF.
* **Columns:** The Print Service Queue displays the following columns to provide visibility into print job details:

| Field           | Description                                                                             |
| --------------- | --------------------------------------------------------------------------------------- |
| Job Id          | Displays the unique identifier for each print job.                                      |
| Printer         | Displays the printer assigned to the print job (e.g., Print 1).                         |
| Print Service   | Displays the print service used to process the job.                                     |
| Status          | Indicates the current status of the print job (e.g., Waiting, Sent to Printer).         |
| Entity Type     | Displays the type of entity from which the print job was generated (e.g., Sales Order). |
| Create Datetime | Shows the date and time when the print job was created.                                 |
| Create Source   | Displays the user who initiated the print request.                                      |
| Entity Ref#     | Displays the reference number of the source document (e.g., Sales Order numbers).       |
| Error Message   | Displays any error message associated with the print job, if applicable.                |


---

# 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/admin/printing/print-service-queue/print-service-queue-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.