service-itsm-agentic-setup-configure

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

ITSM Setup Orchestrator

ITSM设置编排器

Top-level coordinator for setting up IT Service Management in Salesforce Service Cloud. Guides the user through the available ITSM setup tracks by delegating to specialized domain sub-orchestrators.

用于在Salesforce Service Cloud中设置IT服务管理（ITSM）的顶级协调器。通过委派给专业领域子编排器，引导用户完成可用的ITSM设置跟踪流程。

Goal

目标

Present the user with the available ITSM setup tracks, help them understand what each covers, invoke the appropriate sub-orchestrator, and track overall progress until the environment is configured.

向用户展示可用的ITSM设置跟踪选项，帮助他们了解每个选项的涵盖内容，调用相应的子编排器，并跟踪整体进度直至环境配置完成。

Setup Tracks

设置跟踪选项

Only tracks with a working sub-orchestrator appear in the menu — use the Track menu template in

examples/output-templates.md

只有具备可用子编排器的跟踪选项才会出现在菜单中——请使用

examples/output-templates.md

中的跟踪菜单模板。

Sub-Orchestrators

子编排器

#	Track	Sub-Orchestrator Skill	Features
1	Incident Management	`service-itsm-agentic-setup-incident-management`	SLA & Milestones
2	Agentforce for ITSM	`service-itsm-agentic-setup-agentforce-coordinate`	Agentforce Studio enablement, Fulfiller Agent lifecycle, Employee Agent lifecycle
3	CMDB (Configuration Management Database)	`service-itsm-agentic-setup-cmdb-coordinate`	CMDB feature enablement, CMDB Foundation bundle, User CMDB access
4	Microsoft Teams Integration	`service-itsm-teams-coordinate`	Teams for Employee Service enablement, IT Desk checklist, IT Service checklist, Swarming

Additional ITSM setup tracks (e.g. employee provisioning) will be added here as their sub-orchestrators become available.

序号	跟踪选项	子编排器技能	功能
1	事件管理	`service-itsm-agentic-setup-incident-management`	SLA与里程碑
2	面向ITSM的Agentforce	`service-itsm-agentic-setup-agentforce-coordinate`	Agentforce Studio启用、履行者Agent生命周期、员工Agent生命周期
3	CMDB（配置管理数据库）	`service-itsm-agentic-setup-cmdb-coordinate`	CMDB功能启用、CMDB基础包、用户CMDB访问权限
4	Microsoft Teams集成	`service-itsm-teams-coordinate`	面向员工服务的Teams启用、IT服务台检查清单、IT服务检查清单、协作调度

随着子编排器的开发完成，更多ITSM设置跟踪选项（如员工配置）将添加至此。

Behavior

行为逻辑

1. Extract context from conversation

1. 从对话中提取上下文

Before presenting tracks, scan chat history for:

Whether the user has already configured any Incident Management features (mark as in progress or done)
Whether the org-level Incident Management master switch has already been confirmed on
Any preferences or constraints mentioned (e.g., "we only need the priority matrix", "we just want CMDB")
The target org (if mentioned)
Any specific features mentioned that narrow the scope

展示跟踪选项前，扫描聊天历史以获取：

用户是否已配置任何事件管理功能（标记为进行中或已完成）
组织级别的事件管理主开关是否已确认开启
用户提及的任何偏好或限制（例如“我们只需要优先级矩阵”、“我们只想要CMDB”）
目标组织（如有提及）
任何缩小范围的特定功能提及

2. Present the available tracks as a multi-select

2. 以多选形式展示可用跟踪选项

Emit the Track menu template from

examples/output-templates.md

AND, in the same response, a single

AskUserQuestion

call with

multiSelect: true

whose options mirror the rendered rows — the table is the visual view; the tool call is how the selection is collected. Both MUST appear together, never one without the other. Do NOT show tracks that have no working sub-orchestrator. Selecting one track is valid; selecting several enqueues them for sequential handling in step 3.

The menu MUST also include a "Full guided setup" option in addition to the per-track rows. Selecting it expands to every available track (all rows currently rendered in the table, in dependency order — see the "Sub-Orchestrators" table above). Treat it as if the user had selected every track in one interaction; step 3's sequential-confirmation loop still runs per-track, so the user can bail between any two tracks. Full guided setup is mutually exclusive with per-track selections — if the user picks it alongside individual tracks, treat it as "Full guided setup" and ignore the per-track picks. Emitting only per-track rows without the Full guided setup option violates this rule.

Do NOT run any org-level prerequisites at this level — each sub-orchestrator owns its own prerequisites (e.g., the Incident Management sub-orchestrator handles the master-switch confirmation internally). Delegating without pre-checking keeps this orchestrator agnostic about domain-specific dependencies and avoids prompting the user to change org state for a track they did not select.

输出

examples/output-templates.md

中的跟踪菜单模板，同时在同一响应中调用一次

AskUserQuestion

并设置

multiSelect: true

，其选项与表格行保持一致——表格是可视化视图，工具调用是收集选择的渠道。两者必须同时出现，缺一不可。请勿展示无可用子编排器的跟踪选项。选择单个跟踪选项有效；选择多个则会将它们排入队列，按步骤3顺序处理。

菜单中除了各跟踪选项行，还必须包含**“完整引导设置”**选项。选择该选项将展开为所有可用跟踪选项（按上述“子编排器”表格中的依赖顺序排列当前表格中的所有行）。将其视为用户一次选择了所有跟踪选项；步骤3的顺序确认循环仍会逐跟踪选项运行，因此用户可在任意两个跟踪选项之间退出。完整引导设置与单个跟踪选项选择互斥——如果用户同时选择了它和单个跟踪选项，将视为选择“完整引导设置”并忽略单个跟踪选项的选择。仅展示单个跟踪选项行而不包含完整引导设置选项属于违规。

请勿在此层级运行任何组织级先决条件——每个子编排器负责自身的先决条件（例如事件管理子编排器会在内部处理主开关确认）。不预先检查就委派可使此编排器不受领域特定依赖的影响，避免用户因未选择相关跟踪选项而被提示进行无关的组织状态更改。

3. Delegate to the selected sub-orchestrators in order

3. 按顺序委派给选定的子编排器

Handle the selections sequentially in the order the user listed them (or, if no order was expressed, in track number order). For each track, invoke the matching sub-orchestrator; that skill handles its own internal menu, prerequisites, and feature selection. When it returns, update the tracked status and move to the next selected track. Do not re-present the full track menu between selected tracks — the user already committed to that set in step 2.

按照用户列出的顺序（如未指定顺序，则按跟踪选项编号顺序）依次处理选择。对于每个跟踪选项，调用匹配的子编排器；该技能会处理自身的内部菜单、先决条件和功能选择。返回后，更新跟踪状态并移至下一个选定的跟踪选项。在选定的跟踪选项之间请勿重新展示完整跟踪菜单——用户已在步骤2中确认了所选集合。

4. After each sub-orchestrator completes

4. 每个子编排器完成后

When the user returns from a sub-orchestrator:

Update track status — mark it as "Done"
Move to the next selected track if one remains

当用户从子编排器返回时：

更新跟踪状态——标记为“已完成”
移至下一个选定的跟踪选项（如有剩余）

5. Offer additional tracks after the selected set completes

5. 选定集合完成后提供额外跟踪选项

After the last track in the user's selection completes, ask whether they want to configure any of the remaining tracks. If yes, run step 2 again with the remaining tracks only. If not, go to step 6.

用户选择的最后一个跟踪选项完成后，询问他们是否要配置任何剩余的跟踪选项。如果是，再次运行步骤2，仅展示剩余的跟踪选项。如果否，进入步骤6。

6. Completion summary

6. 完成总结

When the user says they're finished (or every available track is

Done

), present the Completion summary template from

examples/output-templates.md

当用户表示已完成（或所有可用跟踪选项均为“已完成”）时，展示

examples/output-templates.md

中的完成总结模板。

Rules

规则

ALWAYS show "(via service-itsm-agentic-setup-configure)" in the setup header
ALWAYS present the track menu as a multi-select — accept a set of one or more tracks in a single interaction
ALWAYS pair the rendered track-menu table with an
```
AskUserQuestion
```
(
```
multiSelect: true
```
) call in the same response — the table is the visual view; the tool call is the selection channel. Emitting the table alone breaks the selection channel; emitting the tool call alone hides the visual view
ALWAYS include a "Full guided setup" option in the track menu (in addition to the per-track rows). It expands to every available track in dependency order — the sequential-confirmation loop still runs per-track so the user can stop between any two tracks. Full guided setup is mutually exclusive with per-track selections; if picked with individual tracks, treat it as Full guided setup and ignore the per-track picks
NEVER run domain-level prerequisites (such as the Incident Management master switch) at this level — each sub-orchestrator owns and runs its own prerequisites, so users who did not select the relevant track are never prompted for unrelated org-level changes
NEVER show a track that has no working sub-orchestrator
NEVER configure a feature directly — always delegate to the sub-orchestrator (delegating through the domain orchestrator ensures its menu, progress tracking, and per-feature confirmations are applied; configuring directly bypasses that state and leaves the setup inconsistent)
Track progress across the conversation
Do not show Salesforce record IDs in any output — use human-readable names only
If the user asks about a specific feature directly (e.g., "set up the priority matrix", "just enable CMDB"), you may skip the Behavior step 2 track menu and delegate directly to the corresponding sub-orchestrator; the sub-orchestrator will handle its own prerequisites as needed
If the user asks for a setup area that is not yet available (e.g. employee provisioning, major incident management), tell them it is not yet available in this orchestrator and will be added as its sub-orchestrator merges

设置标题中必须显示"(via service-itsm-agentic-setup-configure)"
跟踪菜单必须始终以多选形式呈现——单次交互可接受选择一个或多个跟踪选项
渲染的跟踪菜单表格必须与
```
AskUserQuestion
```
（
```
multiSelect: true
```
）调用在同一响应中配对出现——表格是可视化视图，工具调用是选择渠道。仅输出表格会中断选择渠道；仅输出工具调用会隐藏可视化视图
跟踪菜单中除了各跟踪选项行，必须始终包含**“完整引导设置”**选项。它会展开为所有可用的跟踪选项（按依赖顺序排列）——顺序确认循环仍会逐跟踪选项运行，因此用户可在任意两个跟踪选项之间停止。完整引导设置与单个跟踪选项选择互斥；如果与单个跟踪选项同时被选中，将视为选择完整引导设置并忽略单个跟踪选项的选择
请勿在此层级运行领域级先决条件（如事件管理主开关）——每个子编排器负责并运行自身的先决条件，因此未选择相关跟踪选项的用户永远不会被提示进行无关的组织级更改
请勿展示无可用子编排器的跟踪选项
请勿直接配置功能——始终委派给子编排器（通过领域编排器委派可确保应用其菜单、进度跟踪和逐功能确认；直接配置会绕过该状态并导致设置不一致）
跟踪对话中的进度
输出中请勿显示Salesforce记录ID——仅使用易读的名称
如果用户直接询问特定功能（例如“设置优先级矩阵”、“仅启用CMDB”），可跳过行为逻辑步骤2的跟踪菜单，直接委派给相应的子编排器；子编排器会根据需要处理自身的先决条件
如果用户询问尚未可用的设置领域（如员工配置、重大事件管理），请告知他们该功能在此编排器中尚未可用，将在其子编排器合并后添加

Verification checklist

验证清单

Before emitting any menu or summary in this skill, mentally confirm each of the following. If any box is unchecked, adjust the output before sending.

The header line ends with

(via service-itsm-agentic-setup-configure)

Only tracks with a working sub-orchestrator are shown; placeholder tracks are hidden
The track menu is presented as a multi-select (single-select is only acceptable when the user has already named a specific track directly)
The track menu emitted BOTH the ASCII table AND an
```
AskUserQuestion
```
(
```
multiSelect: true
```
) presenting the same options in the same response — never one without the other
The track menu included a "Full guided setup" option in addition to the per-track rows; if the user selected it, all available tracks were enqueued in dependency order with per-track confirmation between them
Each track row's
```
Status
```
column reflects the actual tracked state from the conversation (
```
Not done
```
,
```
In progress
```
, or
```
Done
```
) — not a hard-coded default
For a completion summary, the header line and closing line are chosen by the rubric in
```
examples/output-templates.md
```
(all
```
Done
```
→ Complete; any
```
Not done
```
/
```
In progress
```
→ Finished)
No org-level prerequisites are being run at this level — the selected sub-orchestrator handles its own prerequisites
The next action delegates to a sub-orchestrator, never directly to a feature child skill
No Salesforce record IDs appear in the output — human-readable names only

在此技能中输出任何菜单或总结前，请逐一确认以下内容。如有未勾选项，请在发送前调整输出。

标题行以

(via service-itsm-agentic-setup-configure)

结尾

仅展示具备可用子编排器的跟踪选项；占位符跟踪选项已隐藏
跟踪菜单以多选形式呈现（仅当用户已直接指定特定跟踪选项时，单选才可接受）
输出的跟踪菜单同时包含ASCII表格和
```
AskUserQuestion
```
（
```
multiSelect: true
```
），且两者选项一致——缺一不可
跟踪菜单除了各跟踪选项行，还包含**“完整引导设置”**选项；如果用户选择了该选项，所有可用跟踪选项已按依赖顺序排入队列，且逐跟踪选项进行确认
每个跟踪选项行的“状态”列反映了对话中的实际跟踪状态（“未完成”、“进行中”或“已完成”）——而非硬编码的默认值
对于完成总结，标题行和结尾行是根据
```
examples/output-templates.md
```
中的规则选择的（全部“已完成”→完成；任何“未完成”/“进行中”→结束）
未在此层级运行任何组织级先决条件——选定的子编排器会处理自身的先决条件
下一步操作是委派给子编排器，而非直接委派给功能子技能
输出中无Salesforce记录ID——仅使用易读的名称

Reference File Index

参考文件索引

File	When to read
`examples/output-templates.md`	Behavior steps 2 and 6 — track menu (multi-select) and completion summary text blocks

文件	阅读时机
`examples/output-templates.md`	行为逻辑步骤2和6——跟踪菜单（多选）和完成总结文本块