Skip to content

Commit cd15c8b

Browse files
committed
docs: clarify Dingtalk app publishing flow
1 parent ca9b1b0 commit cd15c8b

2 files changed

Lines changed: 14 additions & 6 deletions

File tree

en/on-call/integration/instant-messaging/dingtalk.mdx

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -119,6 +119,10 @@ If you need AI SRE, also confirm that all [AI SRE required permissions](#aisre-p
119119

120120
![2025-09-18-15-20-36](https://docs-cdn.flashcat.cloud/images/png/4417440194002a011e2feca5fa5c9469.png)
121121

122+
<Note>
123+
If you need to continue configuring War Room, publish the custom app once first. After the app is published, you can select it from the **Available Apps** list in Scene Groups. See [App Publishing and Usage](#publish) for the publishing path.
124+
</Note>
125+
122126
## 2. Configure War Room
123127

124128
<Tip>
@@ -168,7 +172,7 @@ Fill in group bot configuration. **Message Callback URL**, **Message Callback To
168172

169173
2. Configure **Group Template**. Select **Group Template** in the left menu, click **Create Group Template**.
170174

171-
Set **Enterprise Type** to `Internal`, set **Available Apps** to the custom app created in previous steps. Then fill in template information in the next step.
175+
Set **Enterprise Type** to `Internal`, and set **Available Apps** to the published custom app created in previous steps. Then fill in template information in the next step.
172176

173177
**Template Name**, **Icon**, **Description**, **Text Introduction**, **Template Description**, **Image Introduction** and other descriptive information won't affect group template functionality—you can configure any values that meet requirements.
174178

@@ -206,7 +210,7 @@ Only one IM integration can have War Room enabled at a time. If you've already e
206210

207211
## 3. App Publishing and Usage
208212

209-
After completing the above steps, go to App Publishing → **Version Management & Publishing**, create a new version and publish.
213+
After completing the above steps, confirm that the custom app has been published with the latest version. If it has not been published yet, or if you changed app settings after publishing, go to App Publishing → **Version Management & Publishing**, create a new version, and publish it.
210214

211215
<Note>
212216
To ensure everyone can use the app, adjust the app **Visibility** to all employees before publishing.

zh/on-call/integration/instant-messaging/dingtalk.mdx

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -120,6 +120,10 @@ keywords: ["钉钉", "即时消息", "告警通知", "IM集成", "钉钉机器
120120

121121
![2025-09-18-15-20-36](https://docs-cdn.flashcat.cloud/images/png/4417440194002a011e2feca5fa5c9469.png)
122122

123+
<Note>
124+
如果需要继续配置作战室,请先发布一次自建应用。应用发布后,才能在场景群的 **可选应用** 列表中选择该应用。发布路径请参考 [应用发布与使用](#publish)
125+
</Note>
126+
123127
## 二、配置作战室
124128

125129
<Tip>
@@ -159,17 +163,17 @@ keywords: ["钉钉", "即时消息", "告警通知", "IM集成", "钉钉机器
159163
| 简介 | Flashduty |
160164
| 消息预览图 | [Flashduty 官方 icon](https://download.flashcat.cloud/flashcat_logo_circular.png) |
161165
| 详细描述 | Flashduty 消息推送机器人。 |
162-
| 消息回调地址 | `https://flashcat.cloud/` |
166+
| 消息回调地址 | `http://flashcat.cloud/` |
163167
| 消息回调 token | `token` |
164-
| 信息来源网站 | `https://flashcat.cloud/` |
168+
| 信息来源网站 | `http://flashcat.cloud/` |
165169

166170
完成配置后,点击 **创建**,然后点击 **审批**。右上角弹出 “提交成功” 后,钉钉已自动完成群机器人的审批。
167171

168172
![2025-09-18-15-22-05](https://docs-cdn.flashcat.cloud/images/png/75e853ae6c420d69916e17f5d8922945.png)
169173

170174
2. 配置 **群模板**。在左侧菜单栏中选择 **群模板**,点击 **创建群模板**
171175

172-
**企业类型** 设置为 `企业内部`,将 **可选应用** 设置为先前步骤创建的自建应用。然后,在下一步骤中填写模板信息。
176+
**企业类型** 设置为 `企业内部`,将 **可选应用** 设置为先前步骤中已发布的自建应用。然后,在下一步骤中填写模板信息。
173177

174178
**模板名称****图标****描述****文案介绍****模板描述****图片介绍** 等介绍性信息不会影响群模板功能的使用,您可选择任意满足要求的值进行配置。
175179

@@ -207,7 +211,7 @@ keywords: ["钉钉", "即时消息", "告警通知", "IM集成", "钉钉机器
207211

208212
## 三、应用发布与使用
209213

210-
完成上述步骤后,前往 应用发布 → **版本管理与发布**,创建新版本并发布。
214+
完成上述步骤后,请确认自建应用已发布最新版本。若尚未发布,或发布后又调整了应用配置,请前往 应用发布 → **版本管理与发布**,创建新版本并发布。
211215

212216
<Note>
213217
为了确保所有人可以使用应用,需将应用 **可见范围** 调整为全部员工,再进行应用发布。

0 commit comments

Comments
 (0)