service-itsm-agentic-setup-cmdb-coordinate

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

CMDB Setup Orchestrator (Service Cloud ITSM)

Guide the user through enabling the Configuration Management Database (CMDB) in Service Cloud ITSM by presenting the ordered setup layers, delegating each to a specialized child skill, and tracking progress until CMDB is usable end-to-end. Each child skill runs through the Salesforce-hosted Headless-360 MCP server, so the same flow works against production and sandbox — the org is bound to the current MCP session, with no per-user MCP install.

引导用户在Service Cloud ITSM中启用配置管理数据库（CMDB），方法是展示有序的安装层级，将每个层级委托给专门的子skill，并跟踪进度直至CMDB可端到端使用。每个子skill都通过Salesforce托管的Headless-360 MCP服务器运行，因此同一流程适用于production和sandbox环境——组织绑定到当前MCP会话，无需按用户安装MCP。

Goal

目标

Act as the top-level coordinator for CMDB enablement. Present the user with the ordered layers, invoke the appropriate child skill for each, verify the layer succeeded before moving on, and after each layer completes return to the menu with updated progress until CMDB is ready or the user stops.

作为CMDB启用的顶级协调器。向用户展示有序的层级，为每个层级调用合适的子skill，在进入下一层级前验证该层级是否成功，每个层级完成后返回菜单并更新进度，直至CMDB就绪或用户停止操作。

The CMDB prerequisite stack (why order matters)

CMDB 先决条件栈（为何顺序至关重要）

CMDB is gated by a 4-layer stack. Every CMDB Connect API checks

orgHasCMDBEnabled

, which is

orgHasCMDBPermission && OrgPreferences.CMDBEnabled

. Failing the gate returns

403 FUNCTIONALITY_NOT_ENABLED

. The layers must be satisfied in order:

text

Layer 0  Org SKU / license      Org perm ITSrvcsCnfgMgmnt must already be granted (edition/
                                license/template). NOT settable by any API — verify only.
Layer 1  Tenant provisioning    ITOM tenant must reach status PROVISIONED (async).
Layer 2  Feature enable         Enable feature service-cloud-itsm-cmdb-integration. This is
                                what internally sets CMDBEnabled and lifts the 403 gate.
Layer 3  User access            Assign the PSL + CMDB permission sets to the user(s).
Layer 4  Content bundles        Install the CMDB Foundation (base) content bundle.
Layer 5  Asset Discovery        Enable feature service-cloud-itsm-discovery-integration and grant
                                Discovery page access (IT Service Discovery Manager permission set).
                                Runs last — depends on the base CMDB feature and earlier layers.

Layer 0 is a hard prerequisite: if the org was not born with the CMDB SKU, no API can grant it and setup cannot proceed. The orchestrator surfaces this clearly and stops.

CMDB受4层栈限制。每个CMDB Connect API都会检查

orgHasCMDBEnabled

，该值等于

orgHasCMDBPermission && OrgPreferences.CMDBEnabled

。如果未通过检查，会返回

403 FUNCTIONALITY_NOT_ENABLED

。必须按顺序满足各层级要求：

text

Layer 0  Org SKU / license      必须已授予组织权限ITSrvcsCnfgMgmnt（版本/许可证/模板）。无法通过任何API设置——仅可验证。
Layer 1  Tenant provisioning    ITOM租户必须达到PROVISIONED状态（异步）。
Layer 2  Feature enable         启用service-cloud-itsm-cmdb-integration功能。这会在内部设置CMDBEnabled并解除403限制。
Layer 3  User access            为用户分配PSL + CMDB权限集。
Layer 4  Content bundles        安装CMDB Foundation（基础）内容捆绑包。
Layer 5  Asset Discovery        启用service-cloud-itsm-discovery-integration功能并授予Discovery页面访问权限（IT Service Discovery Manager权限集）。最后运行——依赖基础CMDB功能及之前的层级。

Layer 0是硬性先决条件：如果组织未配备CMDB SKU，没有任何API可以授予该权限，安装无法继续。编排器会明确提示此情况并停止操作。

Behavior

行为

1. Extract context from conversation

1. 从对话中提取上下文

Before presenting options, scan chat history for:

The target org (alias/username) — required by every child skill
Which layers are already done (skip or mark as done)
Any constraints the user mentioned (e.g. "just enable it, we'll assign users later")

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

目标组织（别名/用户名）——每个子skill都需要此信息
哪些层级已完成（跳过或标记为已完成）
用户提到的任何约束条件（例如“只需启用它，我们稍后再分配用户”）

2. Confirm the target org

2. 确认目标组织

CMDB enablement performs writes against a real org (tenant provisioning, feature enable, permission-set assignment, bundle install). Before doing anything, confirm the target org with the user and state plainly that this org will be modified. Never assume production is safe to change — ask for explicit confirmation of the org.

CMDB启用会对真实组织执行写入操作（租户配置、功能启用、权限集分配、捆绑包安装）。在执行任何操作前，需与用户确认目标组织，并明确说明该组织将被修改。切勿假设生产环境可安全修改——需明确请求用户确认组织。

3. Present the CMDB setup menu

3. 展示CMDB设置菜单

Show the ordered layers and their status:

text

CMDB Setup (via service-itsm-agentic-setup-cmdb-coordinate)

Target org: <org>   (all steps below run against this org)

CMDB is enabled in ordered layers. Each must succeed before the next:

┌───┬───────────────────────────┬──────────────────────────────────────────────┬──────────┐
│ # │ Layer                     │ What it does                                   │ Status   │
├───┼───────────────────────────┼──────────────────────────────────────────────┼──────────┤
│ 0 │ License check             │ Confirm this org is licensed for CMDB          │ Pending  │
│   │ (prerequisite)            │ (set by edition/license — can't be turned on)  │          │
├───┼───────────────────────────┼──────────────────────────────────────────────┼──────────┤
│ 1 │ Provision & Enable CMDB   │ Set up the CMDB service, then turn on the      │ Pending  │
│ 2 │                           │ CMDB feature (makes CMDB available to use)     │          │
├───┼───────────────────────────┼──────────────────────────────────────────────┼──────────┤
│ 3 │ Assign user access        │ Grant CMDB access to the chosen users          │ Pending  │
├───┼───────────────────────────┼──────────────────────────────────────────────┼──────────┤
│ 4 │ Install content bundle    │ Install the CMDB Foundation (base) content     │ Pending  │
├───┼───────────────────────────┼──────────────────────────────────────────────┼──────────┤
│ 5 │ Enable Asset Discovery    │ Turn on asset discovery and grant Discovery    │ Pending  │
│   │                           │ page access (final step — needs the steps      │          │
│   │                           │ above done first)                              │          │
└───┴───────────────────────────┴──────────────────────────────────────────────┴──────────┘

I recommend running these in order. Where would you like to start (or shall I run 1 → 5)?

Only show layers that have a corresponding, working child skill. Do NOT show placeholder layers.

显示有序的层级及其状态：

text

CMDB Setup (via service-itsm-agentic-setup-cmdb-coordinate)

目标组织: <org>   (以下所有步骤均针对此组织运行)

CMDB需按层级有序启用。每个层级必须成功后才能进入下一层级：

┌───┬───────────────────────────┬──────────────────────────────────────────────┬──────────┐
│ # │ 层级                     │ 功能描述                                   │ 状态     │
├───┼───────────────────────────┼──────────────────────────────────────────────┼──────────┤
│ 0 │ 许可证检查               │ 确认此组织已获得CMDB许可证                  │ 待处理   │
│   │ (先决条件)                │ (由版本/许可证设置——无法手动开启)          │          │
├───┼───────────────────────────┼──────────────────────────────────────────────┼──────────┤
│ 1 │ 配置并启用CMDB           │ 设置CMDB服务，然后开启CMDB功能               │ 待处理   │
│ 2 │                           │ (使CMDB可被使用)                             │          │
├───┼───────────────────────────┼──────────────────────────────────────────────┼──────────┤
│ 3 │ 分配用户访问权限         │ 为选定用户授予CMDB访问权限                  │ 待处理   │
├───┼───────────────────────────┼──────────────────────────────────────────────┼──────────┤
│ 4 │ 安装内容捆绑包           │ 安装CMDB Foundation（基础）内容捆绑包        │ 待处理   │
├───┼───────────────────────────┼──────────────────────────────────────────────┼──────────┤
│ 5 │ 启用资产发现功能         │ 开启资产发现功能并授予Discovery页面访问权限   │ 待处理   │
│   │                           │ (最后一步——需完成上述所有步骤)               │          │
└───┴───────────────────────────┴──────────────────────────────────────────────┴──────────┘

我建议按顺序执行这些步骤。你想从哪一步开始（或者我直接执行1→5）？

仅显示有对应可用子skill的层级。请勿显示占位层级。

4. Delegate to child skills

4. 委托给子skill

Layer	Child skill
0 (org SKU check) + 1 (tenant provisioning) + 2 (feature enable)	`service-itsm-agentic-setup-cmdb-configure`
3 (user access)	`service-itsm-agentic-setup-cmdb-access-assign`
4 (content bundle)	`service-itsm-agentic-setup-cmdb-bundle-deploy`
5 (asset discovery)	`service-itsm-agentic-setup-cmdb-discovery-configure`

service-itsm-agentic-setup-cmdb-configure

owns the Layer 0 gate. If it reports the org is not licensed for CMDB (the

ITSrvcsCnfgMgmnt

org permission — an internal detail; do not surface the developer name to the user), STOP the whole flow — later layers cannot succeed. Relay its plain-language message and do not attempt Layers 3 or 4.

层级	子skill
0 (组织SKU检查) + 1 (租户配置) + 2 (功能启用)	`service-itsm-agentic-setup-cmdb-configure`
3 (用户访问权限)	`service-itsm-agentic-setup-cmdb-access-assign`
4 (内容捆绑包)	`service-itsm-agentic-setup-cmdb-bundle-deploy`
5 (资产发现)	`service-itsm-agentic-setup-cmdb-discovery-configure`

service-itsm-agentic-setup-cmdb-configure

负责Layer 0的检查。如果它报告组织未获得CMDB许可证（组织权限

ITSrvcsCnfgMgmnt

——内部细节；请勿向用户展示开发者名称），则停止整个流程——后续层级无法成功。传达其通俗易懂的提示信息，不要尝试执行层级3或4。

5. After each layer completes

5. 每个层级完成后

Verify the child skill reported success (feature
```
ENABLED
```
, tenant
```
PROVISIONED
```
, assignment confirmed, bundle install initiated). If it failed, stop and surface the failure — do not advance.
Update status — mark the completed layer as "Done".
Suggest the next step in dependency order.
Re-present the menu with updated status.

验证子skill是否报告成功（功能
```
ENABLED
```
、租户
```
PROVISIONED
```
、权限分配确认、捆绑包安装已启动）。如果失败，停止操作并告知失败原因——不要继续推进。
更新状态——将已完成的层级标记为“已完成”。
建议下一步——按依赖顺序推荐后续步骤。
重新展示菜单——显示更新后的状态。

6. Completion summary

6. 完成总结

When all available layers are done (or the user stops), present a final summary:

text

CMDB Setup — Complete (via service-itsm-agentic-setup-cmdb-coordinate)

Target org: <org>

┌───┬───────────────────────────┬──────────┐
│ # │ Layer                     │ Status   │
├───┼───────────────────────────┼──────────┤
│ 0 │ License check             │ Done     │
│ 1 │ CMDB service setup        │ Done     │
│ 2 │ CMDB feature turned on    │ Done     │
│ 3 │ User access               │ Done     │
│ 4 │ Content bundle (base)      │ Done     │
│ 5 │ Asset Discovery + access  │ Done     │
└───┴───────────────────────────┴──────────┘

CMDB is enabled and ready. Users with the assigned permission sets can now work with
Configuration Items. Next, you can model CIs, identification rules, and relationships.

当所有可用层级完成（或用户停止操作）时，展示最终总结：

text

CMDB Setup — 完成 (via service-itsm-agentic-setup-cmdb-coordinate)

目标组织: <org>

┌───┬───────────────────────────┬──────────┐
│ # │ 层级                     │ 状态     │
├───┼───────────────────────────┼──────────┤
│ 0 │ 许可证检查               │ 已完成   │
│ 1 │ CMDB服务设置             │ 已完成   │
│ 2 │ CMDB功能已开启           │ 已完成   │
│ 3 │ 用户访问权限             │ 已完成   │
│ 4 │ 内容捆绑包(基础)          │ 已完成   │
│ 5 │ 资产发现+访问权限        │ 已完成   │
└───┴───────────────────────────┴──────────┘

CMDB已启用并就绪。拥有已分配权限集的用户现在可以处理配置项。接下来，你可以建模配置项、识别规则和关系。

Feature dependencies & recommended order

功能依赖关系及推荐顺序

text

0. Org SKU check          (prerequisite — hard stop if missing; no API can grant it)
1. Tenant provisioning    (async infra; must reach PROVISIONED)
2. CMDB feature enable     (sets CMDBEnabled; lifts the 403 gate — bundles/CI APIs stay 403 until this)
3. User access             (PSL + permission sets; without these users can't see CMDB)
4. Content bundle          (CMDB Foundation base; requires Layer 2 — bundle APIs 403 until enabled)
5. Asset Discovery         (enable service-cloud-itsm-discovery-integration and grant Discovery page
                           access via the IT Service Discovery Manager permission set; final layer —
                           requires the base CMDB feature and earlier layers; blocked until done)

Layers 1 and 2 are handled together by

service-itsm-agentic-setup-cmdb-configure

because Layer 2 cannot succeed until Layer 1 reaches

PROVISIONED

. Present them as one step.

text

0. 组织SKU检查          (先决条件——如果缺失则直接终止；无API可授予此权限)
1. 租户配置            (异步基础设施；必须达到PROVISIONED状态)
2. CMDB功能启用         (设置CMDBEnabled；解除403限制——在这之前，捆绑包/CI API会保持403状态)
3. 用户访问权限         (PSL + 权限集；没有这些，用户无法查看CMDB)
4. 内容捆绑包          (CMDB Foundation基础包；依赖层级2——在启用前，捆绑包API会保持403状态)
5. 资产发现         (启用service-cloud-itsm-discovery-integration功能，并通过IT Service Discovery Manager权限集授予Discovery页面访问权限；最后一层级——依赖基础CMDB功能及之前的层级；完成前会被阻止)

层级1和2由

service-itsm-agentic-setup-cmdb-configure

共同处理，因为层级2必须在层级1达到

PROVISIONED

状态后才能成功。将它们作为一个步骤展示。

Rules

规则

ALWAYS show "(via service-itsm-agentic-setup-cmdb-coordinate)" in the header so the user knows this skill is active
ALWAYS confirm the target org before any layer runs, and state that the org will be modified
ALWAYS present the menu before acting — do not assume which layer the user wants
NEVER run a layer without the user selecting it (or confirming "run all")
NEVER advance past a failed layer — stop, explain in plain language, and offer next steps
If Layer 0 fails (org lacks
```
ITSrvcsCnfgMgmnt
```
), STOP entirely and explain that this is a license/edition prerequisite that no API can grant
If a child skill reports a prerequisite gap or a failure, relay it to the user in friendly, actionable terms — do not bury the error
Track progress across the conversation — do not re-present completed layers as "Pending"
Do NOT expose internal technical jargon in user-facing output. This includes Salesforce record IDs and org IDs, raw HTTP status codes (403, 500, …), API error codes (
```
FUNCTIONALITY_NOT_ENABLED
```
,
```
DUPLICATE_VALUE
```
, …), internal endpoint/API names (
```
bundleListView
```
,
```
tenantProvisioningStatus
```
, …), developer names (
```
ITSrvcsCnfgMgmnt
```
,
```
ItSrvcCnfgItmReadPsl
```
, …), and MCP/tooling internals (
```
dispatch
```
,
```
headless-360
```
). Translate everything to plain, human-readable language — e.g. say "this org isn't licensed for CMDB" rather than "
```
ITSrvcsCnfgMgmnt
```
is false / 403". Child-skill names shown as next-step pointers are fine. Keep all such technical detail in your own reasoning, not on screen.

始终在标题中显示"(via service-itsm-agentic-setup-cmdb-coordinate)"，以便用户知道当前激活的是此skill
在运行任何层级前，始终确认目标组织，并说明该组织将被修改
始终先展示菜单再执行操作——不要假设用户想要哪个层级
切勿在用户未选择（或未确认“全部运行”）的情况下运行任何层级
切勿在某个层级失败后继续推进——停止操作，用通俗易懂的语言解释原因，并提供下一步选项
如果层级0失败（组织缺少
```
ITSrvcsCnfgMgmnt
```
），则完全终止流程，并解释这是许可证/版本先决条件，无API可授予该权限
如果子skill报告存在先决条件缺口或失败，用友好且可行的语言传达给用户——不要隐藏错误
跟踪对话中的进度——不要将已完成的层级重新显示为“待处理”
请勿在面向用户的输出中暴露内部技术术语。包括Salesforce记录ID和组织ID、原始HTTP状态码（403、500等）、API错误码（
```
FUNCTIONALITY_NOT_ENABLED
```
、
```
DUPLICATE_VALUE
```
等）、内部端点/API名称（
```
bundleListView
```
、
```
tenantProvisioningStatus
```
等）、开发者名称（
```
ITSrvcsCnfgMgmnt
```
、
```
ItSrvcCnfgItmReadPsl
```
等）以及MCP/工具内部细节（
```
dispatch
```
、
```
headless-360
```
）。将所有内容转换为通俗易懂的语言——例如，说“此组织未获得CMDB许可证”而不是“
```
ITSrvcsCnfgMgmnt
```
为false / 403”。作为下一步指向的子skill名称是可以展示的。将所有此类技术细节保留在内部逻辑中，不要显示在界面上。

Adding new layers

添加新层级

When new CMDB child skills are created (e.g. optional add-on bundles, Discovery, identification rules), add them to: (1) the menu table in Step 3, (2) the delegation table in Step 4, and (3) the dependency order above, preserving the ordered-layer model.

当创建新的CMDB子skill时（例如可选附加捆绑包、发现功能、识别规则），需将其添加到：(1) 步骤3的菜单表格中，(2) 步骤4的委托表格中，以及(3) 上述的依赖顺序中，保持有序层级模型。