> 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-11-7.md). # 3.11.7 Release Date: October 10, 2022 ## **POS** ### Usability change to Login screen in POS Starting with release 3.11.7, if you enter your **User ID** on the **Login** screen and press **Enter**, the cursor moves to the **Password** field instead of submitting the User ID (without a password) for verification. This is a usability improvement that is designed to increase the login success rate. ## **Store Manager and POS** ### Restrict access to the Action button in POS Starting with release 3.11.7, there is a new option **Do not allow to access the Action button** to restrict users from editing line items in a transaction using the Action button in POS. This option is available in Store Manager under **Setup** | **People & Security** | **Users** | **Extended Properties**. ## **Central Manager** ### Usability change to Items tab for purchase orders or transfers in/out Starting with release 3.11.7, on the **Items** tab of purchase orders or transfers in/out, you can sort column data in ascending or descending order by clicking the column header. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.rmhpos.com/releases/old/3-11-7.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.