> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/dineplan/backoffice/printer/printer-job.md).
# Printer Job
### **Overview**
The Printer Job section is used to manage the print jobs configured in the system. You can add new print jobs, edit existing print jobs, delete print jobs, and change the order in which print jobs are displayed.
### **Screen Elements**
| **Screen Element** | **Description** |
| ------------------ | ---------------------------------------------------- |
| Print Job List | Displays the print jobs configured in the system. |
| Search | Used to search for a specific print job. |
| Add Print Job | Used to add a new print job. |
| Edit Print Job | Used to modify the details of an existing print job. |
| Delete Print Job | Used to remove a selected print job. |
| Change Sort Order | Used to change the display order of the print jobs. |
| Close | Closes the Printer Job section. |
### **Working**
#### **Add Print Job**
1. Select "Add Print Job".
2. Enter the "Print Job Name" and "Group".
3. Select the required option under "Printing Content".
4. Configure "Always Exclude Tax" and "Negative" as required.
5. Under "Print Mapping", select "Add" to add a mapping.
6. Select the required "Product Group", "Product", "Printer", "Printer Template", and "DepartmentID".
7. Add additional mappings as required.
8. Select "Save" to add the print job.
#### **Edit Print Job**
1. Select the required print job from the Print Job List.
2. Select "Edit Print Job".
3. Update the required print job details.
4. To add a new mapping, select "Add" under "Print Mapping" and select the required items.
5. To remove an existing mapping, select the required mapping and select "Delete".
6. Select "Save" to save the changes.
#### **Delete Print Job**
1. Select the print job you want to remove.
2. Select "Delete Print Job".
3. In the confirmation message, select "Yes" to delete the print job.
#### **Change Sort Order**
1. Select "Change Sort Order".
2. Adjust the order of the print jobs as required.
### **Use Case**
* Configure specific print jobs for different types of content that need to be printed from the POS.
* Route different product groups or individual products to the appropriate printer based on the configured requirements.
* Direct kitchen-related products to a kitchen printer while routing other products to their respective printers.
* Configure separate print jobs for different departments when printing requirements vary between operational areas.
* Apply different printer templates when the format or content of printed output needs to vary.
* Control how tax information is handled in printed output using the available printing options.
* Maintain multiple print mappings within a single print job when different products or groups need to be routed to different printers.
* Update or remove print mappings when products, printers, departments, or printing requirements change.
### **Notes**
* Select the required print job before using "Edit Print Job" or "Delete Print Job".
* Enter the Print Job Name before saving a new print job.
* Configure the print mapping details as required for the print job.
* Verify the selected print job before deleting it.
* Deleting a print job requires confirmation.
* Use "Change Sort Order" to organize the print job list according to your requirement.
---
# 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://help.rbsgo.com/dineplan/backoffice/printer/printer-job.md?ask=&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.
.png?alt=media)
