> 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-9-17.md).

# 3.9.17

Fecha de lanzamiento: 8 de noviembre de 2021

## **Store Manager y POS**

### Establecer un nuevo precio de venta y un nuevo tipo de venta usando el Asistente de artículos avanzado

A partir de la versión 3.9.17, podrá usar **Asistente avanzado de artículos** en Store Manager para establecer precios de venta que estarán vigentes durante un período o programación especificados. Usted establece los precios de venta en la **Nuevo precio de venta** columna. En la **Nuevo tipo de venta** columna, puede seleccionar **Período** o **Programación**.

### Más tablas actualizadas en la base de datos sin conexión mediante los informes Z, ZZ y de cierre ciego

A partir de la versión 3.9.17, cuando ejecute informes Z, ZZ o de cierre ciego, las siguientes tablas se actualizarán en la base de datos sin conexión:

* RMH\_POSProfile
* RMH\_WAM\_PresetTare
* RMH\_WAM\_PresetTareDetails
* RMH\_WAM\_TareConfig


---

# 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-9-17.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.