> 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/arquivo.md).

# Arquivo

Ver ordens de trabalho e tarefas antigas a partir do arquivo iOS.

## Arquivar

Usar **Arquivar** para rever os mais antigos **Ordens de trabalho** e **Tarefas**.

Permanece separado da Visão Geral ativa.

### O que se pode fazer

* alternar entre Ordens de trabalho e Tarefas arquivadas
* pesquisar Ordens de trabalho mais antigas
* abrir registos históricos para referência

### Abrir e utilizar **Arquivar**

{% stepper %}
{% step %}

### Abrir **Arquivar**

Abrir o menu de mais opções a partir de **Visão Geral** em layouts compactos.

Tocar **Arquivar**.
{% endstep %}

{% step %}

### Escolher o tipo de registo

Alternar entre **Ordens de trabalho** e **Tarefas**.
{% endstep %}

{% step %}

### Encontrar o registo certo

A pesquisa deve ser usada quando for necessária uma Ordem de trabalho mais antiga.
{% endstep %}
{% endstepper %}

### É importante ter em conta

O título do arquivo pode variar entre layouts compactos e normais.


---

# 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/arquivo.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.