> 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.md).
# 布局管理器
#### 概述
布局管理器允许管理员通过设置文档中各种数据字段和分组的属性，以可视化方式配置和修改文档类型的布局。此界面有助于确保提取模型和手动数据录入位置与扫描或上传到 Docbits 的文档结构精确匹配。
#### 关键组件
1. **分组和字段**：
* **分组**：文档类型中的组织单元，用于对相关字段进行分类（例如，发票详情、付款详情）。这些分组可以展开或折叠，也可以调整顺序，使其与实际文档中的逻辑分组保持一致。
* **字段**：每个分组中的独立数据项（例如，发票号码、付款条款）。可以自定义每个字段的数据采集、显示和处理方式。
2. **属性面板**：
* 此面板显示所选字段或分组的属性，可进行详细配置，例如：
* **标签**：字段在用户界面中显示的标签。
* **字段名称**：系统中使用的技术标识符。
* **元素宽度（百分比）**：字段相对于文档布局的宽度。
* **Tab 索引**：控制导航时的 Tab 键顺序。
* **更改时运行脚本**：字段值发生变化时是否执行脚本。
* **左侧显示标签**：标签显示在字段左侧还是上方。
* **是否为文本区域**：指定字段是否应为文本区域，以容纳较长文本。
* **选择模型类型**：选择用于处理此字段提取的模型类型。
* **字段长度**：此字段可接受数据的最大长度。
* **禁止使用的关键词**：字段中不允许出现的关键词。
3. **模板预览**：
* 根据当前布局配置实时预览文档的显示效果。这有助于确认布局是否符合实际文档结构，对于测试和优化文档处理设置至关重要。
{% @jira/embed url="" %}
---
# 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.md?ask=&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.
