> For the complete documentation index, see [llms.txt](https://docs.opshub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opshub.com/v7.237/help-center-index/faqs/hp-faqs/present-comment-sync-to-target-system.md).

# Updated comment in Micro Focus ALM/QC is added as a new comment in the target system

### Description

For integration from Micro Focus ALM/QC to any other target system, if Comments synchronization is enabled, the new comments \[Added with 'Add Comment'] on Micro Focus ALM/QC entity will be synchronized/added to a target system. But if an already added comment is edited in Micro Focus ALM/QC, then it will be added as a new comment in the target system.

### Cause

In Micro Focus ALM/QC, for the comment field, if the user made an update to an already added comments then the revision about this updation is not maintained. The entire text present in the comment field of the entity of Micro Focus ALM/QC gets synchronized to the target system.

### Solution

When the comments are mapped from Micro Focus ALM/QC to any target system and the user updates the comment in Micro Focus ALM/QC for the synchronized entity, then to know the behavior for updating the comment in the target, please refer [Micro Focus ALM/QC Comments](/v7.237/connectors/micro-focus-alm-qc.md#micro-focus-alm-comments).

> **Note**: To know how to map comments in <code class="expression">space.vars.OIM</code>, please refer mapping [Comments](/v7.237/integrate/configure-integrations/mapping-configuration.md#comments) in the documentation.


---

# 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://docs.opshub.com/v7.237/help-center-index/faqs/hp-faqs/present-comment-sync-to-target-system.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.