> 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/upcoming-release/help-center-index/faqs/hp-faqs.md).

# Micro Focus ALM/QC

* [In an integration where Micro Focus ALM/QC is the source system, a specific field in the target system is not getting updated as per the updates in the source system](/upcoming-release/help-center-index/faqs/hp-faqs/field-not-updated-hp-source.md)
* [Updated comment in Micro Focus ALM/QC is added as a new comment in the target system](/upcoming-release/help-center-index/faqs/hp-faqs/present-comment-sync-to-target-system.md)
* [How to create a folder structure in Micro Focus QC/ALM based on the hierarchy in the source system?](/upcoming-release/help-center-index/faqs/hp-faqs/folder-structure-on-information-from-source-system.md)
* [Requirement Traceability is not getting synchronized](/upcoming-release/help-center-index/faqs/hp-faqs/requirement-traceability-is-not-getting-synchronized.md)
* [Design Steps are not getting synchronized](/upcoming-release/help-center-index/faqs/hp-faqs/design-steps-are-not-getting-synchronized.md)
* [Getting error: "The Web server is configured to not list the contents of this directory" while accessing the proxy for Micro Focus QC/ALM](/upcoming-release/help-center-index/faqs/hp-faqs/getting-error-the-web-server-is-configured-to-not-list-the-contents-of-this-directory-while-accessin.md)
* [Getting error: "The requested content appears to be a script and will not be served by the static file handler" while accessing the proxy for Micro Focus QC/ALM](/upcoming-release/help-center-index/faqs/hp-faqs/getting-error-the-requested-content-appears-to-be-script-and-will-not-be-served-by-the-static-file-h.md)


---

# 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/upcoming-release/help-center-index/faqs/hp-faqs.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.