> For the complete documentation index, see [llms.txt](https://doc.sysdevmobile.com/mss-release-history/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.sysdevmobile.com/mss-release-history/release-history/database-version/version-17.md).

# Version 17

{% hint style="success" %}
Data de disponibilização pública: 26/10/2022
{% endhint %}

* Adicionado novo campo à tabela BOERPMSUSR: **USRSynchronizationGroup VARCHAR(120)**
* Adicionada nova tabela de configurações de grupos de sincronização: **BOERPGRPGroups**
* Adicionada nova tabela de configurações de tabelas a sincronizar por grupo de sincronização: **BOERPGRPTables**
* Adicionada nova tabela de definição de polígonos: **MSPOL** 
* Adicionada nova tabela de coordenadas de polígonos: **MSPOC**
* Adicionada nova tabela de grupos de artigos: **MSGRA**
* Adicionada nova tabela de artigos por grupo: **MSGAA**
* Adicionada nova tabela de grupos de clientes: **MSGRC**
* Adicionada nova tabela de clientes por grupo: **MSGCC**


---

# 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://doc.sysdevmobile.com/mss-release-history/release-history/database-version/version-17.md?ask=<question>&goal=<endgoal>
```

`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.