> 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-10-4.md). # 3.10.4 Release Date: April 25, 2022 ## **Store Manager** ### Worksheet Inventory menu renamed Purchasing Tasks Starting with release 3.10.4, the **Worksheet Inventory** menu has been renamed **Purchasing Tasks**. ### Select customer Ship To Address on purchase orders Starting with release 3.10.4, when you create a new purchase order and choose **Ship To Customer**, you can now look up the customer's shipping address and add it to the **Ship To Address** field. ### Include item Price in purchase order or transfer in/out templates Starting with release 3.10.4, it is now possible to customize purchase order and transfer in/out templates to include item **Price**. To add this column to templates, open a purchase order or transfer in/out in print preview and then click **Edit**. ## **Central Manager** ### New column added to Central Users screen Starting with release 3.10.4, when you go to **Setup** | **People and Security** | **Central Users**, you will see a new **Central User Roles** column where you can see the role assigned to specific users. ## **Loyalty** ### Customer account number now displays on Customer Management tab Starting with release 3.10.4, in Store Loyalty and Central Loyalty, the customer's account number now displays on the Customer Management screen when you look up a customer. --- # 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-10-4.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.