> For the complete documentation index, see [llms.txt](https://knowledge.out-smart.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.out-smart.com/outsmart-knowledge-base/outsmart-knowledge-base-pt/app-movel/ios-outsmart-app/visoes-gerais-dos-modulos/visao-geral/mapa-ad-hoc.md).

# Mapa / Ad hoc

Usar o mapa para localizar registos próximos e ordens de trabalho ad hoc no iOS.

## Mapa / Ad Hoc

Usar o mapa para encontrar clientes, Projetos, Objetos e Ordens de trabalho ad hoc nas proximidades.

O que é mostrado depende dos filtros e das políticas do dispositivo.

### O que se pode fazer

* Mostrar registos nas proximidades no mapa
* Filtrar Tipos de artigo visíveis
* Abrir Ordens de trabalho ad hoc a partir de layouts compactos

### Usar o mapa

{% stepper %}
{% step %}

### Abrir o mapa

Abrir o mapa a partir de **Visão Geral**.
{% endstep %}

{% step %}

### Definir os filtros

Ativar os Tipos de artigo que pretende ver.
{% endstep %}

{% step %}

### Abrir um resultado do mapa

Tocar num marcador para rever os respetivos detalhes.
{% endstep %}

{% step %}

### Abrir Ordens de trabalho ad hoc

Usar o formato compacto **Visão Geral** menu quando for necessário **Ordens de trabalho ad hoc**.
{% endstep %}
{% endstepper %}

### É importante ter em conta

As Ordens de trabalho ad hoc são carregadas separadamente antes de aparecerem no mapa.

O mapa mostra apenas Tipos de artigo permitidos pelas Definições e pela política.


---

# 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://knowledge.out-smart.com/outsmart-knowledge-base/outsmart-knowledge-base-pt/app-movel/ios-outsmart-app/visoes-gerais-dos-modulos/visao-geral/mapa-ad-hoc.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.