> 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/gai-shu-yu-ji-chu/release-notes/testing-availability-on-sandbox.md).

# 沙盒环境中的测试可用性

随时了解**沙盒环境**中可供测试的最新功能、修复和配置。此专用环境可用于验证和功能检查

***

## **即将开放测试的更新**

<table data-header-hidden><thead><tr><th width="247"></th><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>功能/更新</strong></td><td><strong>描述</strong></td><td><strong>客户可开始测试的日期</strong></td><td><strong>内部测试日期</strong></td></tr><tr><td>LN 客户和 M3</td><td>按表格行创建税额</td><td>12/13/2024</td><td>12/10/2024</td></tr><tr><td>供应商发票</td><td>顺序工作流</td><td>12/2/2024</td><td>11/29/2024</td></tr><tr><td>组织</td><td>显示所有子组织，以提供统一视图</td><td>12/2/2024</td><td>12/2/2024</td></tr><tr><td>供应商发票 - 导入</td><td>通过 SFTP/FTP 将文件读取为已归档文件</td><td>12/2/2024</td><td>12/2/2024</td></tr><tr><td>供应商发票报告</td><td>Power BI（用于报告的 ClickHouse 数据）</td><td>2024-11-28</td><td>12/1/2024</td></tr></tbody></table>

***

## **如何在沙盒环境中测试**

1. **访问沙盒环境**：
   * 使用现有凭据登录沙盒环境。
   * 确认使用的是正确的沙盒 URL。
2. **测试指南**：
   * 按照各项功能或修复对应的步骤进行操作。
   * 通过 [support.fellowpro.com](https://support.fellowpro.com) 报告任何问题、异常行为或反馈。
3. **测试日志**：
   * 查看系统日志，了解相关测试结果或错误。
   * 记录测试过程和结果，以供审核。

***

## **反馈与支持**

如果在测试期间遇到任何问题或有任何建议，请联系支持团队，或使用沙盒环境中提供的反馈表单。

* **支持联系方式**：<support@fellowpro.com>

***

**注意**：此页面将定期更新，以反映沙盒环境中测试可用性和即将开放测试的更新信息。


---

# 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/gai-shu-yu-ji-chu/release-notes/testing-availability-on-sandbox.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.