> 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/document-processing/e-documents/validation-rules/validation-change-log.md).

# 变更日志

**变更日志**记录验证设置的每次变更。它属于 [电子发票验证](/chinese/guan-li-yu-she-zhi/settings/document-processing/e-documents/validation-rules.md)。只有组织管理员可以查看。

打开 **规则和政策** 旁边的 **变更日志** 选项卡。

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-83d3c72439285d47204337eae89b0dcdadc05a46%2Feinvoice-validation-change-log.png?alt=media" alt="变更日志选项卡，包含 When、Who、Rule、From to To 和 Action 列"><figcaption><p>变更日志包含四条示例记录。用户名已替换为示例名称。</p></figcaption></figure>

| 列             | 显示内容                       |
| ------------- | -------------------------- |
| **When**      | 变更时间。                      |
| **Who**       | 执行变更的用户。                   |
| **Rule**      | 已变更的设置或规则。                 |
| **From → To** | 旧值和新值。                     |
| **Action**    | 变更类型。可打开设置向导中的记录，查看各项具体变更。 |

每页显示 50 条记录。

确认后，[每种文档类型的验证](/chinese/guan-li-yu-she-zhi/settings/document-processing/e-documents/validation-rules/validation-per-document-type.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.docbits.com/chinese/guan-li-yu-she-zhi/settings/document-processing/e-documents/validation-rules/validation-change-log.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.
