> 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-1.md).

# 3.11.1

Release Date: July 18, 2022

## **Central Manager, Store Manager, and POS**

### Synchronize global cashier password changes

Starting with release 3.11.1, when a global cashier changes their password using either POS or Store Manager, the password is synchronized to Central Manager and then to any stores in the store groups to which the cashier has been assigned. Global cashiers are created in Central Manager (**Setup** | **People and Security** | **Store Users**) and assigned to store groups. Cashiers typically change their passwords from the POS login screen, but they can also change their passwords using Store Manager (from either the login screen or from **Setup** | **People & Security** | **Users**).

## **Store Manager, POS, and POS Software Development Kit (SDK)**

### Configure mandatory customer fields and phone number formats

Starting with release 3.11.1, you can configure mandatory fields for new customers. In Store Manager, click **Setup** | **Customer** | **Customer Policy**. On the **Options** tab, select the fields that must be filled out for new customers. If you do not fill out these fields in Store Manager an error message displays. In POS, the Save button is disabled.

You can also configure a required phone number format on the **Mask** tab. For example, you might enter +1-###-###-#### as the phone number format, where +1 is the country code, ### is the three-digit area code, and ###-#### is the seven-digit phone number.

{% hint style="info" %}
If you define a phone number format on the Mask tab, it does not affect existing customer phone numbers in the database. The format requirements only apply to new phone number entries.
{% endhint %}

You can look up the mandatory customer fields using the POS SDK. Refer to the POS SDK documentation for more information. In a typical installation, the POS SDK is saved to **C:\Program Files (x86)\Retail Hero\RMH POS\RMH POS SDK**.

## **Store Manager**

### Prompt to save changes to the physical inventory count batch

Starting with release 3.11.1, if you accidentally click Close before you have saved changes to your physical inventory count batch, Store Manager will display a message asking if you want to save your changes.

### All serial number fields added to the Purchase Order and Transfer In/Out data source

Starting with release 3.11.1, all serial number fields (1, 2, and 3) have been added to the data source used to customize the Purchase Order and Transfer In/Out templates.


---

# 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-11-1.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.