> 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-5.md).
# 3.10.5
Release Date: May 9, 2022
## Store Manager
### New cashier property to prevent returns or voids
Starting with release 3.10.5, you can prevent cashiers from returning or voiding entries from a transaction by selecting the **Do not allow to return or void entries from transaction** option. This option is available under **Setup** | **People & Security** | **Users** on the **Extended Properties** tab.
When this option is selected, the cashier will see the message "You do not have the privilege to return or void entries from the transaction" if they attempt to return or void an item.
### Changes to Formula button
Starting with release 3.10.5, you will see the following changes to purchase orders and transfers in/out:
* On the **Items** tab, the existing **Formula** button will be renamed to **Discount**. Only the button name is changing; the underlying functionality remains the same.
* On the **Items** tab, if you click in the **Cost** or **New Price** columns a new button named **Formula** is enabled. You can use this button create a basic formula to calculate a Cost or New Price for items.
## **Central Manager and Store Manager**
### Spanish translations
Starting with release 3.10.5, the Spanish translations of the Central Manager and Store Manager interfaces were updated.
---
# 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-5.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.
