> 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-9-13.md).
# 3.9.13
Release Date: September 13, 2021
## Store Manager and POS
### Inactive users filtered out in Time Clock
Starting with release 3.9.13, the **Time Clock** only shows active users. This makes it easier to enter time for cashiers. There is also a new **Browse** icon next to the **Cashier** field that you can use to quickly look up a specific cashier.
### Editing Information from purchase orders or transfers in/out
Starting with release 3.9.13, you can edit an item from a purchase order or transfer in/out in Store Manager. When you edit the item in the **Item** dialog, you now have the option to save your changes.
## Store Manager and Central Manager
### Place Order on Release option renamed to Auto Release Order
Starting with release 3.9.13, the order setting option **Place Order on Release** has been renamed to **Auto Release Order**. The functionality of the option has not changed.
### Columns and column names updated for purchase orders and transfers in/out
Starting with release 3.9.13, the **Items** and **Charges** tabs for purchase orders or transfers in/out have the same columns and column headings in both Store Manager and Central Manager.
## Central Manager
### Improved display time performance for Item lists
Starting with release 3.9.13, if you use Central Manager from a remote location to connect to the central database and your network latency is greater than 20ms, you can improve Central Manager performance by adding a line to the **RMH.Central.config** file. The config file is usually located under **C:\ProgramData\RetailHero\RMH Central Manager**.
Add the following line of text anywhere before the closing `` tag:
``
{% hint style="info" %}
The default packetsize value is 8000.
{% 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 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-9-13.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.