life-sciences-prerequisites-validate

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Life Sciences Cloud Prerequisites Validation

Life Sciences Cloud前提条件验证

Validates that a Salesforce org meets all prerequisites for Life Sciences Cloud for Customer Engagement. Runs checks via the

sf

CLI against the currently authenticated org and produces a consolidated pass/fail report with remediation steps for any failures.

验证Salesforce组织是否满足Life Sciences Cloud for Customer Engagement的所有前提条件。通过

sf

CLI针对当前已认证的组织运行检查，并生成整合的通过/失败报告，针对失败项提供补救步骤。

Scope

范围

In scope: Validating org settings, user permissions, OWD sharing, and feature toggles required for Life Sciences Cloud CE
Out of scope: Automatically enabling or configuring settings that fail validation

包含范围：验证Life Sciences Cloud CE所需的组织设置、用户权限、OWD共享及功能开关
排除范围：自动启用或配置验证失败的设置

Off-topic requests

偏离主题的请求

If the user asks for something unrelated to this skill (either at the start or mid-execution), do not attempt it. Tell the user you did not understand the request, then show what you can help with: validating Life Sciences Cloud org prerequisites (this skill), and — if relevant — point them to

life-sciences-territory-configure

for territory setup or

life-sciences-fieldsalesrep-coordinate

for the full end-to-end setup. Then stop and wait.

如果用户请求与本技能无关的内容（无论是在开始还是执行过程中），请勿尝试处理。告知用户您无法理解该请求，然后展示您可以提供的帮助：验证Life Sciences Cloud组织的前提条件（本技能），并——如果相关——引导用户使用

life-sciences-territory-configure

进行区域设置，或使用

life-sciences-fieldsalesrep-coordinate

进行完整的端到端设置。之后停止操作并等待。

Required Inputs

必要输入

Gather before proceeding:

Target org: The org alias or username to validate (from
```
sf config get target-org
```
or user-specified)
Confirmation: The logged-in user must be the admin whose profile and permission sets are being validated

在继续之前需收集：

目标组织：要验证的组织别名或用户名（来自
```
sf config get target-org
```
或用户指定）
确认信息：登录用户必须是其配置文件和权限集正在被验证的管理员

Workflow

工作流程

All checks run sequentially. Collect all results before presenting the final report.

所有检查按顺序运行。收集所有结果后再呈现最终报告。

Phase 1 — Validate Environment

阶段1 — 验证环境

Confirm org connection — run
```
sf org display --target-org <org>
```
to verify the org is accessible. If it fails, stop and ask the user to authenticate.
Identify the logged-in user — extract the username from the org display output.

确认组织连接 — 运行
```
sf org display --target-org <org>
```
以验证组织可访问。如果失败，停止操作并要求用户进行认证。
识别登录用户 — 从组织显示输出中提取用户名。

Phase 2 — Run All Prerequisite Checks

阶段2 — 运行所有前提条件检查

Run each check below. For each, record PASS or FAIL with the remediation steps. The checks use the canonical Check 1 – Check 12 numbering from the reference files and the final report; the managed-package check is an un-numbered hard-stop gate, not one of the 12 scored categories. Checks 1–3 (and the managed-package gate) are in

references/checks-user-and-package.md

; Checks 4–12 are in

references/checks-org-settings.md

STOP-GATE (report completeness). Every check MUST produce a row in the final report — a check that errors (e.g. Multi-Currency returns HTTP 400
INVALID_TYPE
, or an object isn't deployed) is a FAIL row, never a skipped/omitted row or a reason to abort the run. The report's row count MUST equal the full scored-check count (12 categories, Check 1 – Check 12). The one intended early exit is the managed-package gate (the un-numbered
lsc4ce
package check, step 4 below) — that legitimately stops the run with the "BLOCKED" message. In every other case, a query error is the FAIL signal: record it and continue. Do NOT let a single 4xx or unexpected-shape response silently drop a row or halt the sweep — a short report reads as "fewer things to fix" when the truth is "we didn't check."

Check 1 — user profile and permission sets — read
```
references/checks-user-and-package.md
```
section "User Profile and Permission Sets" for the exact queries and validation logic.
Managed-package gate (un-numbered hard stop) — read
```
references/checks-user-and-package.md
```
section "Managed Package Check". If the
```
lsc4ce
```
package is not installed, display the failure message and stop — do not proceed with remaining checks.
Check 2 — Life Sciences CE settings — read
```
references/checks-user-and-package.md
```
section "Life Sciences Customer Engagement Setup" for the exact queries.
Check 3 — Surveys enabled — read
```
references/checks-user-and-package.md
```
section "Surveys".
Check 4 — OWD sharing settings — read
```
references/checks-org-settings.md
```
section "OWD Sharing" for the exact objects and expected values.
Check 5 — Inventory Count — read
```
references/checks-org-settings.md
```
section "Inventory Count".
Check 6 — Sales Account Plans — read
```
references/checks-org-settings.md
```
section "Sales Account Plans".
Check 7 — Care Plans — read
```
references/checks-org-settings.md
```
section "Care Plans".
Check 8 — Chatter Settings — read
```
references/checks-org-settings.md
```
section "Chatter Settings".
Check 9 — Data Protection and Privacy — read
```
references/checks-org-settings.md
```
section "Data Protection and Privacy".
Check 10 — Multiple Currencies — read
```
references/checks-org-settings.md
```
section "Multiple Currencies".
Check 11 — State and Country/Territory Picklists — read
```
references/checks-org-settings.md
```
section "State and Country/Territory Picklists".
Check 12 — Person Accounts — read
```
references/checks-org-settings.md
```
section "Person Accounts".

运行以下每项检查。针对每项检查，记录通过或失败状态及补救步骤。检查使用参考文件和最终报告中的标准编号检查1 – 检查12；托管包检查是一个无编号的强制停止关卡，不属于12个评分类别。检查1–3（及托管包关卡）位于

references/checks-user-and-package.md

；检查4–12位于

references/checks-org-settings.md

。

停止关卡（报告完整性）。每项检查必须在最终报告中生成一行——检查出错（例如多币种返回HTTP 400
INVALID_TYPE
，或对象未部署）属于失败行，绝不能跳过/省略该行或中止运行。报告的行数必须等于完整的评分检查数量（12个类别，检查1 – 检查12）。唯一允许提前退出的情况是托管包关卡（无编号的
lsc4ce
包检查，即下文步骤4）——此时会显示“BLOCKED”消息并合法停止运行。在其他所有情况下，查询错误即为失败信号：记录错误并继续。请勿让单个4xx或非预期格式的响应静默删除行或停止检查——简短的报告会让用户误以为“需要修复的内容更少”，但实际情况是“我们未进行检查”。

检查1 — 用户配置文件和权限集 — 阅读
```
references/checks-user-and-package.md
```
中的“User Profile and Permission Sets”部分，获取精确的查询语句和验证逻辑。
托管包关卡（无编号强制停止） — 阅读
```
references/checks-user-and-package.md
```
中的“Managed Package Check”部分。如果未安装
```
lsc4ce
```
包，显示失败消息并停止——不继续剩余检查。
检查2 — Life Sciences CE设置 — 阅读
```
references/checks-user-and-package.md
```
中的“Life Sciences Customer Engagement Setup”部分，获取精确的查询语句。
检查3 — 调查已启用 — 阅读
```
references/checks-user-and-package.md
```
中的“Surveys”部分。
检查4 — OWD共享设置 — 阅读
```
references/checks-org-settings.md
```
中的“OWD Sharing”部分，获取精确的对象和预期值。
检查5 — 库存计数 — 阅读
```
references/checks-org-settings.md
```
中的“Inventory Count”部分。
检查6 — 销售客户计划 — 阅读
```
references/checks-org-settings.md
```
中的“Sales Account Plans”部分。
检查7 — 护理计划 — 阅读
```
references/checks-org-settings.md
```
中的“Care Plans”部分。
检查8 — Chatter设置 — 阅读
```
references/checks-org-settings.md
```
中的“Chatter Settings”部分。
检查9 — 数据保护与隐私 — 阅读
```
references/checks-org-settings.md
```
中的“Data Protection and Privacy”部分。
检查10 — 多币种 — 阅读
```
references/checks-org-settings.md
```
中的“Multiple Currencies”部分。
检查11 — 州和国家/地区选择列表 — 阅读
```
references/checks-org-settings.md
```
中的“State and Country/Territory Picklists”部分。
检查12 — 个人客户 — 阅读
```
references/checks-org-settings.md
```
中的“Person Accounts”部分。

Phase 3 — Report

阶段3 — 报告

Generate consolidated report — present results in a table:

markdown

| # | Prerequisite                              | Status | Remediation (if failed/warning)  |
|---|-------------------------------------------|--------|----------------------------------|
| 1 | System Administrator + Permission Sets    | PASS/FAIL | <steps if failed>            |
| 2 | Life Sciences CE Enabled                  | PASS/FAIL | <steps if failed>            |
| ...                                                                                       |

Status values are PASS, FAIL, or WARNING. Most checks are PASS/FAIL. The OWD Sharing check (Check 4) is WARNING-level: when its values differ from the expected ones, report WARNING (with the recommended value in the remediation column), never FAIL — see

references/checks-org-settings.md

for the exact rule.

Include a summary line:

X of 12 prerequisites passed. Y require action (Z warnings).

If all pass, confirm the org is ready for Life Sciences Cloud deployment.

生成整合报告 — 以表格形式呈现结果：

markdown

| # | 前提条件                                  | 状态 | 补救步骤（若失败/警告）  |
|---|-------------------------------------------|--------|----------------------------------|
| 1 | 系统管理员 + 权限集                       | PASS/FAIL | <失败时的步骤>            |
| 2 | Life Sciences CE已启用                  | PASS/FAIL | <失败时的步骤>            |
| ...                                                                                       |

状态值为PASS、FAIL或WARNING。大多数检查为通过/失败。OWD共享检查（检查4）为警告级别：当其值与预期值不同时，报告WARNING（补救列中给出推荐值），绝不能报告FAIL——具体规则见

references/checks-org-settings.md

。

包含总结行：

12项前提条件中，X项通过。Y项需处理（Z项警告）。

如果全部通过，确认组织已准备好部署Life Sciences Cloud。

Rules / Constraints

规则/约束

Constraint	Rationale
Run all checks even if early ones fail	Admin needs the full picture to remediate in one pass
Use `sf` CLI with `--target-org` for every query	Ensures correct org context even with multiple orgs authenticated
Never modify org settings	This skill validates only — it does not enable or configure anything
Report exact Setup navigation paths	Admins need to know where to click in Setup UI

约束	理由
即使早期检查失败，仍需运行所有检查	管理员需要完整的信息，以便一次性完成补救
所有查询使用 `sf` CLI并指定 `--target-org`	确保即使已认证多个组织，仍使用正确的组织上下文
绝不修改组织设置	本技能仅用于验证——不启用或配置任何内容
报告精确的设置导航路径	管理员需要知道在设置UI中点击哪里

Gotchas

注意事项

Issue	Resolution
Some settings are not queryable via Metadata API	Use Tooling API or org settings queries where Metadata API lacks coverage
Person Accounts cannot be disabled once enabled	Only check if enabled; no rollback possible
Multiple Currencies cannot be disabled once activated	Only check if activated; warn that this is irreversible if recommending enablement
State/Country Picklists enabling is irreversible	Include this warning in remediation steps

问题	解决方法
某些设置无法通过Metadata API查询	在Metadata API覆盖不足的情况下，使用Tooling API或组织设置查询
个人客户启用后无法禁用	仅检查是否已启用；无法回滚
多币种激活后无法禁用	仅检查是否已激活；若建议启用，需警告此操作不可逆
州/国家选择列表启用后不可逆	在补救步骤中包含此警告

Output Expectations

输出预期

Deliverables:

A formatted table showing pass/fail status for all 12 prerequisite categories
Remediation steps (Setup navigation paths and actions) for each failed check
Summary count of passed vs. failed checks

交付物：

格式化表格，显示所有12个前提条件类别的通过/失败状态
针对每项失败检查的补救步骤（设置导航路径和操作）
通过与失败检查的汇总统计

Reference File Index

参考文件索引

File	When to read
`references/checks-user-and-package.md`	During Phase 2 (checks 3–6) — exact sf CLI commands, expected values, and remediation for the user profile/permission-set, managed-package, Life Sciences CE feature, and survey checks
`references/checks-org-settings.md`	During Phase 2 (checks 7–15) — exact sf CLI commands, expected values, and remediation for the OWD sharing, inventory, account plans, care plans, chatter, data protection, currencies, picklists, and person-accounts checks

文件	阅读时机
`references/checks-user-and-package.md`	阶段2（检查3–6）期间——用户配置文件/权限集、托管包、Life Sciences CE功能及调查检查的精确sf CLI命令、预期值和补救措施
`references/checks-org-settings.md`	阶段2（检查7–15）期间——OWD共享、库存、客户计划、护理计划、Chatter、数据保护、币种、选择列表及个人客户检查的精确sf CLI命令、预期值和补救措施