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

# 3.10.0

Release Date: February 28, 2022

## **Store Manager and POS**

### Add unit of measure to pole display

Starting with release 3.10.0, for stores that have Weights and Measures (WAM) functionality enabled, the unit of measure (UOM) defined for a weighted item will automatically display on the pole display if pole display is set up for POS.

{% hint style="info" %}
The quantity of a weighted item cannot be displayed as a whole number. The quantity will always include a decimal point. If the quantity is 1, it will display as 1.0.
{% endhint %}

## **Store Manager and Central Manager**

### New custom item properties fields

Starting with release 3.10.0, you can set up custom item properties fields for items in Store Manager or Central Manager. You can set up these custom fields to capture data that is unique to the types of items you sell.

{% hint style="info" %}
For stores managed by Central Manager, you must set up the custom item properties fields and enter values for those fields in Central Manager. The custom fields and their values are synchronized to the stores when you save. You cannot edit the values on the item's Extended Properties tab in Store Manager.
{% endhint %}

### New database table and column for custom item properties fields

Starting with release 3.10.0, there is a new **ItemCustomProperty** table in both the Store Manager and Central Manager databases to support the set up of custom item properties fields under **Setup** | **Miscellaneous** | **Item Properties**. The **ItemExt** table was also updated. It has a new column **ItemCustomPropertyXmlData** to store any values entered into the custom item properties fields (under **Merchandising** | **Items** on the **Extended Properties** tab).

## **Loyalty**

### Change to permissions required to use Loyalty Manager

Starting with release 3.10.0, you will not be prompted to enter an administrator user name and password when you start Loyalty Manager. Any person with access to the computer where Loyalty Manager is installed will be able to start the application and set up a loyalty program.

{% hint style="info" %}
Administrator privileges are still required to install or uninstall RMH Loyalty.
{% endhint %}


---

# 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-0.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.
