consumer-goods-tpe-dashboard-configure

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Consumer Goods TPE Dashboard Configure

消费品行业TPE仪表盘配置

Bring a TPM org from bare state to a running TPE dashboard in one guided session, driven entirely by
sf
CLI + REST/anonymous-Apex against an already-authenticated org — never a password or interactive login on the user's behalf.
Persona: a Salesforce TPM System Admin setting up TPE dashboards for their org.
Delegates three of its twelve steps to standalone sibling skills (own
SKILL.md
, own inputs, self-contained per this repo's skills architecture rules — no shared files):
  • Step 7 →
    consumer-goods-tpe-datakit-deploy
  • Step 9 →
    consumer-goods-rtr-datacloud-export-configure
  • Step 12 →
    consumer-goods-tpe-dashboard-custom-kpi-configure
    (optional, only if the customer wants custom KPIs on the base dashboards)
Every other step runs directly in this skill.
通过一次引导式操作,将处于初始状态的TPM组织配置为可运行的TPE仪表盘,全程基于已完成身份验证的组织,通过
sf
CLI + REST/anonymous-Apex驱动——无需用户提供密码或进行交互式登录。
角色:为所在组织配置TPE仪表盘的Salesforce TPM系统管理员
将12个步骤中的3个委托给独立的关联技能(每个技能拥有独立的
SKILL.md
、独立输入,遵循本仓库的技能架构规则实现自包含——无共享文件):
  • Step 7 →
    consumer-goods-tpe-datakit-deploy
  • Step 9 →
    consumer-goods-rtr-datacloud-export-configure
  • 步骤12 →
    consumer-goods-tpe-dashboard-custom-kpi-configure
    (可选,仅当客户需要在基础仪表盘上添加自定义KPI时执行)
其余所有步骤均直接在本技能中执行。

Inputs to collect first

需预先收集的输入项

Ask before starting. Do not guess.
  1. TPM System Admin username — must already be authenticated via
    sf
    CLI. Verify with
    node ./scripts/sf-rest.js org-status --target-org <username>
    (never
    sf org display --json
    directly — see
    references/phases-1-6.md
    ).
  2. Dry-run? — offer by default. In dry-run, every read/verify/check step still runs; every write/trigger/install step is skipped and recorded as
    pending — not run (dry-run)
    .
Also detect the installed package namespace and version-gate the org (Consumer Goods Cloud >= 262.2 required) before Phase 1 — see "Namespace detection" in
references/phases-1-6.md
.
开始前请询问用户,请勿自行猜测。
  1. TPM系统管理员用户名——必须已通过
    sf
    CLI完成身份验证。请使用
    node ./scripts/sf-rest.js org-status --target-org <username>
    进行验证(切勿直接使用
    sf org display --json
    ——详见
    references/phases-1-6.md
    )。
  2. 是否执行试运行?——默认提供该选项。试运行模式下,所有读取/验证/检查步骤仍会执行;所有写入/触发/安装步骤将被跳过,并记录为
    pending — not run (dry-run)
此外,在第1阶段开始前,需检测已安装包的命名空间并对组织进行版本校验(要求Consumer Goods Cloud >= 262.2)——详见
references/phases-1-6.md
中的「命名空间检测」部分。

Phase list

阶段列表

PhaseStepSummaryDetails
SetupCollect inputs, detect namespace, version-gate the org
references/phases-1-6.md
1Tenant pairingAsk user to confirm Hyperforce Processing Service pairing (not verifiable programmatically)
references/phases-1-6.md
2TPM Admin permission set(s)Ask user to confirm org-specific persona permission sets are assigned
references/phases-1-6.md
3GenieAdmin / TableauEinsteinAdminQuery, and on confirmation assign, these two permission sets
references/phases-1-6.md
4SSOT packageVerify the
ssot
managed package is installed
references/phases-1-6.md
5Enable Tableau NextAsk user to confirm manual UI enablement (not verifiable programmatically)
references/phases-1-6.md
6C360 SDMVerify or trigger + poll the C360 Unified Semantic Model app install
references/phases-1-6.md
7TPM Accruals Data KitDelegated to
consumer-goods-tpe-datakit-deploy
references/phases-7-12.md
8Business Period exportAnonymous-Apex export via a Hyperforce-substrate Sales Org, poll, then confirm the
tpmbusinessperiod
Data Stream sync
references/phases-7-12.md
9RTR Data Cloud exportDelegated to
consumer-goods-rtr-datacloud-export-configure
references/phases-7-12.md
10TPM_PROMOTION_MEASURE Data TransformAsk (credit consumption), then run and poll the Data Transform
references/phases-7-12.md
11TPE Analytics App installTrigger + poll the async app-framework install (~15-20 min)
references/phases-7-12.md
12Customize KPIs (optional)Delegated to
consumer-goods-tpe-dashboard-custom-kpi-configure
, only if requested
references/phases-7-12.md
references/phases-7-12.md
also documents the shared
scripts/poll-status.js
poller and the full set of hard Rules (never authenticate on the user's behalf, never hardcode a namespace or Sales Org, never claim success on anything but a terminal success status, a poll timeout is not a failure, etc.) that apply across every phase.
阶段步骤概述详情
准备阶段收集输入项、检测命名空间、组织版本校验
references/phases-1-6.md
1租户配对请用户确认Hyperforce Processing Service配对(无法通过编程方式验证)
references/phases-1-6.md
2TPM管理员权限集请用户确认已分配组织特定角色的权限集
references/phases-1-6.md
3GenieAdmin / TableauEinsteinAdmin查询并在确认后分配这两个权限集
references/phases-1-6.md
4SSOT包验证
ssot
托管包已安装
references/phases-1-6.md
5启用Tableau Next请用户确认已通过手动UI操作启用(无法通过编程方式验证)
references/phases-1-6.md
6C360 SDM验证或触发并轮询C360 Unified Semantic Model应用的安装
references/phases-1-6.md
7TPM应计数据套件委托
consumer-goods-tpe-datakit-deploy
references/phases-7-12.md
8业务周期导出通过基于Hyperforce底层架构的销售组织执行Anonymous-Apex导出,轮询并确认
tpmbusinessperiod
数据流同步完成
references/phases-7-12.md
9RTR数据云导出委托
consumer-goods-rtr-datacloud-export-configure
references/phases-7-12.md
10TPM_PROMOTION_MEASURE数据转换询问用户(涉及积分消耗),然后运行并轮询数据转换任务
references/phases-7-12.md
11TPE分析应用安装触发并轮询异步应用框架安装(约15-20分钟)
references/phases-7-12.md
12自定义KPI(可选)委托
consumer-goods-tpe-dashboard-custom-kpi-configure
,仅在用户要求时执行
references/phases-7-12.md
references/phases-7-12.md
还记录了共享的
scripts/poll-status.js
轮询工具,以及适用于所有阶段的全套硬性规则(例如:切勿代表用户进行身份验证、切勿硬编码命名空间或销售组织、仅在获得最终成功状态时才可声明成功、轮询超时不算失败等)。

Scripts

脚本

  • scripts/sf-rest.js
    — authenticated REST calls; also exposes
    org-status
    (strips
    accessToken
    before printing).
  • scripts/poll-status.js
    — generic async-status poller, reused by Phases 6 and 11.
  • scripts/find-failure-reason.js
    — extracts the actual per-requirement failure reason for a
    FailedStatus
    app-framework install (Phase 11), including "DMO not available" detection.
  • scripts/render-apex.js
    — renders an anonymous-Apex template with
    --var
    substitutions; loads
    scripts/soql-escape.js
    to escape substituted literals.
  • scripts/soql-escape.js
    — escapes a value for safe interpolation into a single-quoted SOQL/Apex string literal.
  • scripts/run-data-transform.js
    — triggers and polls a named Data Transform (Phase 10).
  • scripts/schedule-business-period-export.apex
    — anonymous-Apex template for Phase 8.
  • scripts/sf-rest.js
    — 已认证的REST调用;同时提供
    org-status
    功能(打印前会移除
    accessToken
    )。
  • scripts/poll-status.js
    — 通用异步状态轮询工具,供第6和第11阶段复用。
  • scripts/find-failure-reason.js
    — 提取
    FailedStatus
    状态下应用框架安装(第11阶段)的具体需求失败原因,包括检测「DMO不可用」情况。
  • scripts/render-apex.js
    — 通过
    --var
    替换渲染anonymous-Apex模板;加载
    scripts/soql-escape.js
    对替换的字面量进行转义。
  • scripts/soql-escape.js
    — 对值进行转义,使其可以安全插入到单引号包裹的SOQL/Apex字符串字面量中。
  • scripts/run-data-transform.js
    — 触发并轮询指定名称的数据转换任务(第10阶段)。
  • scripts/schedule-business-period-export.apex
    — 第8阶段使用的anonymous-Apex模板。

Report

报告

At the end of a run, give the user a structured status per phase (1-12): pass / blocked / pending, with the specific blocking reason and remediation click-path where applicable. Call out anything skipped due to dry-run, a declined confirmation, or (Phase 12) the customer opting out of KPI customization.
运行结束后,向用户提供各阶段(1-12)的结构化状态:通过/阻塞/待处理,并在适用情况下提供具体阻塞原因和补救操作路径。需特别说明因试运行、用户拒绝确认或(第12阶段)客户选择不进行KPI自定义而跳过的内容。