> 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-50-15.md).

# 3.50.15

Release Date: January 12, 2024

## **Store Manager**

### Add new tasks to the Advanced Item Wizard

Starting with release 3.50.15, the following tasks have been added to the **Advanced Item Wizard**:

* Task 200: Make Item Active
* Task 210: Make Item Inactive
* Task 1010: Change "May not be placed on Purchase Order" value
* Task 1070: Change "Accept food stamps for items" value
* Task 1080: Change "Item is not discountable at POS" value
* Task 1190: Change "Quantity entry at POS not allowed" value
* Task 1200: Change "Price must be entered at POS" value
* Task 1220: Change "Item is taxable" value
* Task 1230: Change "Item is available on web site" value

## Central Manager

### New Force Install Tables executable

Starting with release 3.50.15, you can run Force Install Tables as an executable in Command Prompt or PowerShell. This allows you to update or repair the Central database without opening Central Administrator or Central Manager. To use the Force Install Tables executable, open Command Prompt or PowerShell and enter the following:

`"C:\Program Files(x86)\Retail Hero\RMH Central Manager\ForceInstallTables.exe" & exit /b`

The executable displays either a success or failure message. Detailed results are saved to a log stored in the following folder: C:\ProgramData\RetailHero\RMH Central Manager\Force Install Tables.

### New retry settings for failed jobs

Starting with release 3.50.15, in Central Server and Central Client you can set the maximum number of attempts that will be made to process a job (and the time interval between attempts) before the system identifies a job as failed.

<div align="left"><figure><img src="https://2921455087-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjgsd9U4TRO2qgcIBegi7%2Fuploads%2F8U51lZ4EB8A2dCJjEzpc%2F3-50-15-central-server-retry-settings.jpg?alt=media&amp;token=f14f5dd1-eac4-461d-9b17-e0f20b220684" alt=""><figcaption></figcaption></figure></div>

{% hint style="info" %}
Failed jobs are more common on the Central Server side, so the best practice is to select a longer retry interval and to keep failed jobs for 15 days before deleting them. This allows more time for detecting and troubleshooting failed jobs.
{% 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-50-15.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.