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

# 3.11.14

Release Date: February 22, 2023

## **Central Manager**

### New Item Filter option for all worksheets except 261

Starting with release 3.11.14, if you use **Item Filter** to add items to worksheets, you can build a filter based on the **MSRP** of the items. This new Item Filter option is available for all worksheets except 261.

### Changes to functionality of the Store Group Wizard

Starting with release 3.11.14, the **Store Group Wizard** will continue to create records for items in the GlobalCatalog table of the Central Manager database, but it will no longer create any jobs to synchronize items to stores. You should use **Worksheet 261: Download Items** to synchronize items (and their properties) to stores instead of the Store Group Wizard.

## **Central Manager and Store Manager**

### New columns available for the Items list view

Starting with release 3.11.14, you can choose to display **Date Created** and **Last Updated** columns in **Items** list view. To display these columns, click **Merchandising** | **Items** | **Layout** and select Date Created or Last Updated. By default, these columns are not visible in the Items list view.

### New filter option for items in the Items list view

Starting with release 3.11.14, you can choose to filter items by **Date Created** or **Last Updated** in the **Items** list view. To use this filter, click **Merchandising** | **Items** | **Filter** and select Date Created or Last 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-11-14.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.
