> For the complete documentation index, see [llms.txt](https://interfacing.gitbook.io/interfacing-help-files/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://interfacing.gitbook.io/interfacing-help-files/interfacing-help-files-fr/document-control/gerer-le-cycle-de-vie-de-la-documentation/managing-a-data-harmonization-cycle.md).
# Managing a Data Harmonization Cycle
Review and confirm changes to associated documentation when updates occur.
The **data harmonization** cycle controls how changes to associated objects are synchronized. You decide whether updates to related content are applied automatically or require review.
In this cycle, users review updated associated documentation to confirm whether it is still relevant or should be replaced. This helps keep information current while preserving approved relationships between objects.
{% hint style="warning" %}
Data harmonization is **optional** and can be configured per object, allowing control to be applied only where needed. Some documentation may require strict oversight, while others can be updated automatically.
{% endhint %}
***
## What are the Data Harmonization Controls?
There are three degrees of control:
1. **High Control**
No updates are applied automatically. User must review every change to associated objects.
2. **Medium Control** \
Minor version updates to associated objects are applied automatically. \
Major version updates cause the object to be marked “**Out of Sync**,” requiring users to review and confirm whether the association is still relevant before updating.
3. **Low Control** \
All updates, major and minor, are automatically applied. Users are not prompted to review associations before they are updated.
{% hint style="warning" %}
When an object is marked as **High** or **Medium Control**, its associations are **frozen** upon a status change (e.g., **Sent for Review,** **Approved**, **Published**).
This ensures that published content always points to the approved version of its associated objects.
{% endhint %}
***
## How to Configure & Manage a Data Harmonization Cycle
In **Phase 1**, governance cycle management is not yet available in the platform. All setup and administration must be performed in EPC.
For detailed instructions on managing data harmonization cycles in EPC, refer to the following topics:
* [Setting the Data Harmonization Control Level Per Documentation Item](https://www.manula.com/manuals/interfacing-technologies/epc10-webapp/15.4/en/topic/12-1-6-4-object-association-strictness-control-level)
* [Enabling or Disabling Data Harmonization in Your System](https://www.manula.com/manuals/interfacing-technologies/epc10-webapp/15.4/en/topic/10-9-1-3-enable-data-association-harmonization)
***
## Completing Data Harmonization Tasks
While you cannot manage data harmonization cycles in the platform, you *can* complete data harmonization tasks assigned to you. See the guide below to get started:
---
# 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://interfacing.gitbook.io/interfacing-help-files/interfacing-help-files-fr/document-control/gerer-le-cycle-de-vie-de-la-documentation/managing-a-data-harmonization-cycle.md?ask=&goal=
```
`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.
