> For the complete documentation index, see [llms.txt](https://documentation.efalia.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.efalia.com/produit/acropolis/fiches-pratiques/fp-007-gestion-version-document.md).

# FP-007 : gestion des versions de document

## Objectifs

* Mettre à disposition maîtrisée une version de document opérationnelle
* Préparer la prochaine version
* Informer sur les différentes versions et sur les liens inter version
* Mettre en œuvre la nouvelle version

{% hint style="danger" %}
Conserver la version précédente en veillant à interdire ou à limiter son accès
{% endhint %}

* Archiver éventuellement (voir fiche Archivage)

## Schéma fonctionnel

<figure><img src="https://3557286639-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcnnXLnfB61CBUw4H9Fho%2Fuploads%2Fgit-blob-965ee6626e0a252142bcc60470ba0846598ded38%2Ffp-fp-007-gestion-version-document-01.webp?alt=media" alt=""><figcaption></figcaption></figure>

## Fonctions sollicitées

* Copie d'un document avec lien de version
* Conversion éventuelle de document en format PDF
* Modification d'un document :
  * Evolution du code ‘ETAT’
  * Evolution du code indice
  * Limiter l'accès en lecture ou avec mot de passe
  * Conversion PDF
  * Changement chrono
* Automatisation possible du processus défini par la réalisation d'un assistant


---

# 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://documentation.efalia.com/produit/acropolis/fiches-pratiques/fp-007-gestion-version-document.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.
