> For the complete documentation index, see [llms.txt](https://support.cregis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.cregis.com/announcement/zh-tw/jul-2026/20260710.md).

# Cregis更新通知 - 版本 \[V3.7.4]

尊敬的Cregis用戶，

您好！我們將於**2026年7月14日 23:00 - 7月15日 1:00（UTC）**推出Cregis的最新版本 **V3.7.4**，此次更新爲**非強制更新**。請您提前安排業務，並於維護完成後按需要升級版本及調整相關權限設定；同時請重新登入相關設備，並啟用自動化配置（自動簽名/ 自動歸集），以確保自動化流程正常運作。

**本次更新包括：**

* 團隊 API 管理上線（僅桌面端）
* WaaS 項目功能優化（僅桌面端）
* AML 服務配置調整
* 修復已知問題

\
感謝您一直以來對Cregis的支持！如有任何疑問，請隨時聯繫我們。

Cregis 團隊\
2026-07-10


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.cregis.com/announcement/zh-tw/jul-2026/20260710.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.