> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/releases/old/3-50-18.md).

# 3.50.18

Release Date: March 15, 2024

## Store Manager

### Add new tasks to the Advanced Item Wizard

Starting with release [3.50.18](https://support.rmhpos.com/hc/en-us/articles/27439716276243-RMH-3-50-18-Flash-Release), the following tasks have been added to the Advanced Item Wizard:

* Task 5050: Change Tag Along Item and Quantity
* Task 5070: Change Parent Item and Quantity

### Display On Order and Committed columns on Items tab of purchase orders

Starting with release [3.50.18](https://support.rmhpos.com/hc/en-us/articles/27439716276243-RMH-3-50-18-Flash-Release), you can display the **On Order** and **Committed** columns on the **Items** tab for purchase orders. (The On Order and Committed columns are read-only and usually display in the **Ordering Guidance** panel.) These columns are not automatically displayed on the Items tab. To display them, click **Layout**, select the columns, and click **OK**. You can also click **Memorize** to save the layout.

### Export only visible columns from Items tab of purchase orders

Starting with release [3.50.18](https://support.rmhpos.com/hc/en-us/articles/27439716276243-RMH-3-50-18-Flash-Release), if you click **Export** on the **Items** tab of purchase orders, only the visible columns will be exported to a tab delimited or comma delimited file that you can edit in Microsoft Excel. This does not apply to transfers in/out.

To import data back into the purchase order, the import file must contain the Code, Qty on Ord, and Cost columns. To avoid import issues, make sure these columns are visible when you export.


---

# 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.rmhpos.com/releases/old/3-50-18.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.
