> 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/design-steps-are-not-getting-synchronized.md).

# Design Steps are not getting synchronized

### Description

The user has configured an integration between **Test Plan** entity of Micro Focus ALM/QC and any entity of the target system. The field **Design Steps** of the Test Plan entity has been mapped to the relevant field entity in the target system; however, they aren't getting synchronized.

### Cause

A probable reason for this behavior can be a missing value of **Database Schema Name** and/or **Proxy URL** in the system configuration form for Micro Focus ALM/QC.

### Solution

* To synchronize the **Design Steps** with Micro Focus ALM/QC, a user needs to mention **Database Schema Name** and/or **Proxy URL** in the system configuration form for specific versions of Micro Focus ALM/QC.
* To determine which particular field (Database Schema Name and/or Proxy URL) is required for a particular version of Micro Focus ALM/QC to synchronize Requirement Traceability, please refer [System configuration in Micro Focus ALM/QC](/v7.237/connectors/micro-focus-alm-qc.md#system-configuration).

> **Note**: To configure proxy, please refer [Proxy Configuration](/v7.237/connectors/micro-focus-alm-qc.md#proxy-configuration-steps).

> **Note**: To configure System, please refer [System Configuration](/v7.237/integrate/configure-integrations/system-configuration.md). design-steps-are-not-getting-synchronized


---

# 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/design-steps-are-not-getting-synchronized.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.