data360-activate

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

data360-activate: Data Cloud Act Phase

data360-activate：Data Cloud 激活阶段

Use this skill when the user needs downstream delivery work: activations, activation targets, data actions, or pushing Data Cloud outputs into other systems.

当用户需要下游交付工作时使用此技能：激活、激活目标、数据操作，或将Data Cloud输出推送至其他系统。

When This Skill Owns the Task

此技能适用的任务场景

Use

data360-activate

when the work involves:

```
sf data360 activation *
```
```
sf data360 activation-target *
```
```
sf data360 data-action *
```
```
sf data360 data-action-target *
```
verifying downstream delivery setup

Delegate elsewhere when the user is:

still building the audience or insight → data360-segment
exploring query/search or search indexes → data360-query
setting up base connections or ingestion → data360-connect, data360-prepare

当工作涉及以下内容时，使用

data360-activate

：

```
sf data360 activation *
```
```
sf data360 activation-target *
```
```
sf data360 data-action *
```
```
sf data360 data-action-target *
```
验证下游交付配置

当用户进行以下操作时，转用其他技能：

仍在构建受众或洞察 → data360-segment
探索查询/搜索或搜索索引 → data360-query
设置基础连接或数据导入 → data360-connect, data360-prepare

Required Context to Gather First

需先收集的必要上下文

Ask for or infer:

target org alias
destination platform or downstream system
whether the segment already exists and is published
whether the user needs create, inspect, update, or delete
whether the task is activation-focused or data-action-focused

需询问或推断：

目标组织别名
目标平台或下游系统
细分受众是否已存在并发布
用户需要执行创建、检查、更新还是删除操作
任务以激活为核心还是以数据操作为核心

Core Operating Rules

核心操作规则

Verify the upstream segment or insight is healthy before creating downstream delivery assets.

Run the shared readiness classifier before mutating activation assets:

node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase act --json

Inspect available platforms and targets before mutating activation setup.
Keep destination definitions deterministic and reusable where possible.
Treat downstream credential and platform constraints as separate validation concerns.
Prefer read-only inspection first when the destination state is unclear.

在创建下游交付资产前，验证上游细分受众或洞察是否正常。

在修改激活资产前，运行共享就绪度分类器：

node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase act --json

。

在修改激活配置前，检查可用平台和目标。
尽可能保持目标定义的确定性和可复用性。
将下游凭证和平台约束视为独立的验证事项。
当目标状态不明确时，优先进行只读检查。

Recommended Workflow

推荐工作流

1. Classify readiness for act work

1. 分类激活工作的就绪度

bash

node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase act --json

bash

node ../data360-orchestrate/scripts/diagnose-org.mjs -o <org> --phase act --json

2. Inspect destinations first

2. 先检查目标系统

bash

sf data360 activation platforms -o <org> 2>/dev/null
sf data360 activation-target list -o <org> 2>/dev/null
sf data360 data-action-target list -o <org> 2>/dev/null

bash

sf data360 activation platforms -o <org> 2>/dev/null
sf data360 activation-target list -o <org> 2>/dev/null
sf data360 data-action-target list -o <org> 2>/dev/null

3. Create the destination before the activation

3. 先创建目标系统再执行激活

bash

sf data360 activation-target create -o <org> -f target.json 2>/dev/null
sf data360 data-action-target create -o <org> -f target.json 2>/dev/null

bash

sf data360 activation-target create -o <org> -f target.json 2>/dev/null
sf data360 data-action-target create -o <org> -f target.json 2>/dev/null

4. Create the activation or data action

4. 创建激活或数据操作

bash

sf data360 activation create -o <org> -f activation.json 2>/dev/null
sf data360 data-action create -o <org> -f action.json 2>/dev/null

bash

sf data360 activation create -o <org> -f activation.json 2>/dev/null
sf data360 data-action create -o <org> -f action.json 2>/dev/null

5. Verify downstream readiness

5. 验证下游就绪状态

bash

sf data360 activation list -o <org> 2>/dev/null
sf data360 activation data -o <org> --name <activation> 2>/dev/null

bash

sf data360 activation list -o <org> 2>/dev/null
sf data360 activation data -o <org> --name <activation> 2>/dev/null

High-Signal Gotchas

关键注意事项

Activation design depends on a healthy published upstream segment.
Destination configuration usually comes before activation creation.
Downstream credential and platform constraints may live outside the Data Cloud CLI alone.
Read-only inspection is the safest first move when the destination setup is unclear.
```
CdpActivationTarget
```
or
```
CdpActivationExternalPlatform
```
means the activation surface is gated for the current org/user; guide the user toward activation setup, permissions, and destination configuration instead of retrying blindly.

激活设计依赖于正常发布的上游细分受众。
目标系统配置通常先于激活创建。
下游凭证和平台约束可能独立于Data Cloud CLI存在。
当目标系统配置不明确时，只读检查是最安全的第一步操作。
若出现
```
CdpActivationTarget
```
或
```
CdpActivationExternalPlatform
```
，表示当前组织/用户无法访问激活界面；应引导用户进行激活配置、权限设置和目标系统配置，而非盲目重试。

Output Format

输出格式

text

Act task: <activation / activation-target / data-action / data-action-target>
Destination: <platform or target>
Target org: <alias>
Artifacts: <definition files / commands>
Verification: <listed / created / blocked>
Next step: <destination validation or downstream testing>

text

激活任务: <activation / activation-target / data-action / data-action-target>
目标系统: <platform or target>
目标组织: <alias>
工件: <definition files / commands>
验证状态: <listed / created / blocked>
下一步: <destination validation or downstream testing>

References

参考资料

README.md
../data360-orchestrate/assets/definitions/activation-target.template.json
../data360-orchestrate/assets/definitions/activation.template.json
../data360-orchestrate/assets/definitions/data-action-target.template.json
../data360-orchestrate/assets/definitions/data-action.template.json
../data360-orchestrate/UPSTREAM.md
../data360-orchestrate/references/plugin-setup.md
../data360-orchestrate/references/feature-readiness.md

README.md
../data360-orchestrate/assets/definitions/activation-target.template.json
../data360-orchestrate/assets/definitions/activation.template.json
../data360-orchestrate/assets/definitions/data-action-target.template.json
../data360-orchestrate/assets/definitions/data-action.template.json
../data360-orchestrate/UPSTREAM.md
../data360-orchestrate/references/plugin-setup.md
../data360-orchestrate/references/feature-readiness.md