> 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/es/releases/old/3-50-12.md).
# 3.50.12
Fecha de lanzamiento: 17 de noviembre de 2023
## **Administrador de la tienda**
### Agregar nuevas tareas al Advanced Item Wizard
A partir de la versión 3.50.12, se han agregado las siguientes tareas a la **Asistente avanzado de artículos**:
* Tarea 110: Cambiar precios de artículos
* Tarea 120: Cambiar límites de precio de artículo
* Tarea 130: Cambiar el costo del artículo
* Tarea 180: Cambiar los precios de venta del artículo
* Tarea 1060: Cambiar la descripción del artículo
* Tarea 1150: Cambiar la subdescripción del artículo
* Tarea 1240: Cambiar la descripción ampliada
### Eliminar las plantillas de recibos heredadas
A partir de la versión 3.50.12, las plantillas de recibos heredadas se han eliminado de **C:\Program Files (x86)\Retail Hero\RMH Store Manager\ReceiptTemplates**. Esto facilitará la selección de la plantilla de recibo correcta al configurar los formatos de recibo y los registros para las tiendas. Consulte [**Formatos de recibo**](/es/store-manager/configure-pos-and-store-manager/registers-and-receipts/setting-up-receipt-formats.md) y [**Registros**](/es/store-manager/configure-pos-and-store-manager/registers-and-receipts/setting-up-registers.md) para obtener más información.
---
# 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/es/releases/old/3-50-12.md?ask=&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.
