> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/chinese/guan-li-yu-she-zhi/settings/global-settings/document-types/layout-manager/save-and-apply-changes.md).

# 保存和应用更改

## 保存并应用在 Layout Manager 中所做的更改，是确保布局自定义设置在文档处理工作流中有效应用的重要步骤。

### 以下是保存和应用更改的步骤：

#### 保存更改：

* 在 Layout Manager 中完成所需的自定义设置后，请找到“Save”按钮以保存更改。
* 点击此按钮，在 Layout Manager 中保存更改。此操作会备份您的布局自定义设置，并确保您以后仍可编辑这些设置。

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-52087b95b42eed09d38641d8415278afe97f13b5%2Fimage%20(257).png?alt=media" alt=""><figcaption></figcaption></figure>

#### 将更改应用于文档处理工作流：

* 在 Layout Manager 中保存更改后，这些更改通常会自动应用于使用相应文档类型的文档处理工作流。
* 根据此模板创建的新文档会继承更新后的布局设置。这意味着新文档将包含您在 Layout Manager 中添加的新组、字段或其他布局自定义设置。
* 使用此模板创建的现有文档可能会因软件和配置而采用不同的处理方式。在某些情况下，更改会自动应用于现有文档；在其他情况下，可能需要手动调整，才能使现有文档符合更新后的布局设置。

#### 测试更改：

* 在保存布局更改并将其应用于文档处理工作流后，建议测试这些更改，以确保其按预期运行。
* 创建新的测试文档或检查现有文档，确保更新后的布局设置已正确应用，并且数据已按预期采集和显示。

按照这些步骤，您可以有效地在 Layout Manager 中保存更改，并将其应用于文档处理工作流。这有助于将布局自定义设置顺利集成到文档创建和处理流程中。


---

# 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.docbits.com/chinese/guan-li-yu-she-zhi/settings/global-settings/document-types/layout-manager/save-and-apply-changes.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.
