# Salesforce / CM / BI Front-Door Escalation Ladder

Date: `2026-07-07`

## 用法

这份文档是
`升级梯子版`
。

只回答 5 个问题：

- `Salesforce 现网会做什么`
- `CM 目前已经接住什么`
- `CM 当前未支持 / 疑似未支持什么`
- `最先影响哪张报表`
- `什么时候才能把这张报表升级成 runtime 题`

如果只想快速判断
`这张报表现在该开 parity 票，还是已经够资格开 runtime 票`
，
优先看这份。

如果要看 4 张最高优先报表的超短排查版，
再看：

- [salesforce-cm-bi-frontdoor-execution-sheet-2026-07-07.md](/Users/amber/ai/nexuscrm-pingcap-pack/docs/salesforce-cm-bi-frontdoor-execution-sheet-2026-07-07.md)

如果要看
`true runtime`
和
`candidate`
的一页总图，
再看：

- [salesforce-cm-bi-runtime-overview-map-2026-07-07.md](/Users/amber/ai/nexuscrm-pingcap-pack/docs/salesforce-cm-bi-runtime-overview-map-2026-07-07.md)

## 读法

| 如果当前问题是 | 默认读法 |
|---|---|
| `报表里有 gap，是不是就等于 CM 做不到` | `不是，先看这张梯子里的 当前结论` |
| `现在该不该开 runtime issue` | 先看 `升级前必须先清什么` |
| `这条最后会归到哪类 runtime` | 看 `升级后归哪组` |

## Escalation Ladder

| front-door 报表 | Salesforce 现网会做什么 | CM 目前已支持什么 | CM 当前未支持 / 疑似未支持什么 | 当前结论 | 升级前必须先清什么 | 升级后归哪组 | 次级受影响面 |
|---|---|---|---|---|---|---|---|
| `1733a75e-a1b2-4415-8732-2c053657e245` `pipeline data quality / cleanup monitor` | 维护 `Opportunity` stage / forecast / close-date / launch-date / owner-team；维护 `Quote` service-window / nonstandard-term / cleanup | `Std_OpportunityStageDerivedFields`、`Opportunity_Cloud_Order_Type_Set`、`Opportunity_Close_Date_Auto_Set`、Quote validation substrate 已在 | `Quote_update_nonstandard_conditions_checkbox`、`_2`、`OpportunityShareToPersalesOwner` / `OpportunityUpdateShareToPerSalOwner` 缺失；部分 validation 仍 inactive；清完后才可能剩 `OpportunityTrigger` / `QuoteTrigger` residuals | `L2 exact-flow parity + activation-state mismatch`，现在不应直接叫 `CM 真 gap` | Quote exact-name parity、owner-share parity、同面 inactive validation | `Opportunity / Quote runtime` | `837...`、`0f2...`、`aadb...`、`d916...` |
| `8c6f30a4-c6fe-4536-ac62-d937d0176ebd` `campaign attribution / contact-opportunity touch` | 维护 `CampaignMember.first_responded_date`、response / involvement、lead-contact convert 后 relink、contact/opportunity attribution | `Lead_Set_First_And_Last_CampaignMember*`、`Contact_Set_First_And_Last_CampaignMember*`、`Std_ConvertLeadCampaignPreview` 已在 | `Campaign_Member_Key_Message_Update` 仍缺；补完后若仍漂才是 `Trigger_CampaignMember` / Contact residuals | `L2 CampaignMember parity`，当前还是 `runtime candidate`，不是 true runtime | `Campaign_Member_Key_Message_Update`，以及 contact stitching 邻近 parity | `CampaignMember runtime candidate` 或 `Contact runtime candidate` | `fd12...` |
| `fd12e3fc-d36f-4cc5-b2d9-9ed2808489dc` `lead funnel / ICP path` | 维护 lead lifecycle、`lead_mql_timestamp`、`lead_iqm_timestamp`、lead-account stitching、convert 前后 campaign path | `IQM_Completion_Flow`、`Lead_Status_Duration`、`Std_ConvertLeadCampaignPreview`、lead 主链字段承接已在 | `Lead_StatusChangeTimestamp` 仍只是近似承接；Lead assignment / reminder / notification 长尾 parity 未清；清完后才是 `LeadTrigger` / `LeadAITrigger` residuals | `semantic mismatch + L2 Lead lifecycle parity`，还不是直接 runtime | `Lead_StatusChangeTimestamp` 语义收窄、Lead lifecycle 邻近 parity、同面 campaign 邻近干扰 | `Lead runtime` | `salesforce_leads`、`dws_lead_timeline`、`dws_icp_summary`、次级 `8c6f...` |
| `58339683-7a7a-4bb6-91bd-14b149572ac9` `account + current/monthly order MRRARR composite` | 维护 account shared-key、tenant bridge、`account_current_order_type`、`order_product_family`、current-month ARR/MRR | `Org_Set_Account`、`Order_Default_RevRec_Entity`、`Cloud_Registration_Source_from_Org_to_Order` 已在 | `Account_Current_Order_Type`、`Order_Org_Auto_Set_Account_*`、`Order_Set_PLG_BD_Pool` 缺失；`Account_Partner_Sales_Owner_Set` 当前更适合作为 `#3707` 的次级回归项；清完后才可能剩 `AccountTrigger` / `OrderTrigger` / line-item runtime | `L2 Account/Order parity`，当前不要直接升级成 runtime | account exact-name parity、order carry-over parity、shared-key 邻近漂移 | `Account runtime candidate` 或 `Finance runtime` | `690...`、`673... / 212...`、次级 `837...` / `f9c4...` |
| `837f6250-3c3d-44b9-af6f-4db9aeb30a94` `ARR summary + regional/company forecast` | 维护 Opportunity ARR/forecast、Order current-month finance、Revenue revrec，以及 line-item `product_family / net_fees / service window` | `Order_Default_RevRec_Entity`、Order 对 `Revenue__c` 的 rollup、`Order_Product__c` 公式/rollup/validation 已在 | `Order_Org_Auto_Set_Account_*`、`Order_Set_PLG_BD_Pool`、`RevRec_Set_PLG_BD_Pool` 缺失；`Revenue__c.Name` / line-item `Name` auto-number 仍未补；清完后才是 finance trigger residue | `L2 finance carry-over + revrec parity`，当前不要先开 `RevenueTrigger` runtime 票 | order carry-over parity、revrec parity、auto-number parity 与 line-item 邻近差异 | `Finance runtime` | `1733...`、`583...`、`salesforce_revrec`、`monthly_revrec_orders` |
| `f9c4bd70-8ce4-487c-abb1-5518ffffd6bd` `activated-order / monthly revrec by account+tenant` | 维护 activated-order、monthly revrec、tenant/account bridge、collections helper、marketplace / org-to-collection bridge | `Invoice_Collection__c` helper 字段已在；Order 侧 collections rollup 已在；order finance snapshot substrate 已在 | `Collection_Set_PLG_BD_Pool`、`Collection_Amount_and_Payable_Amount_exc_tax*`、`Cloud_Registration_Source_from_Org_to_Collections` 缺失；同组 `Order_*` / `RevRec_*` 也会打这里 | `L2 Order/IC/Revenue carry-over parity`，当前不要直接说 `CM 做不到 collections` | collections helper parity、marketplace bridge parity、order/revrec 邻近 carry-over parity | `Finance runtime` | `salesforce_order_daily_view`、`salesforce_org_monthly_revrec`、`monthly_revrec_collections`、次级 `690...` |
| `690c8087-0697-4272-b05e-2ee37d728c15` `PLG signup / billing-capable cloud funnel` | 通过 tenant/account bridge 把 cloud signup、billing-capable user、tenant identity 串起来；当前 strongest front-door 还是 `tenant_*` + funnel metric | `Account_ID__c` auto-number、`Org_Set_Account`、`dws_cloud_tenants_basicinfo` 这条 substrate 已在 | account-side missing names 与 order-side carry-over 仍会回流污染这里，但当前更稳地读成 `583...` 与 `673... / 212...` 清理后的 dependent consumer | `dependent consumer + tenant-bridge drift`，当前更像 candidate，不是 true runtime | `583...` current-order-type parity、`673... / 212...` owner/governance parity、order-side contamination cleanup | `Account runtime candidate` | `583...`、`673... / 212...`、`model_tidbcloud.dws_cloud_tenants_basicinfo` |
| `673c89ef-fb02-4303-a9a2-5519a652051c` / `2128769b-9f86-4c7a-a9f4-8cc7491868e3` `account + forecast surfaces` | 维护 `account_number`、`fy26_icp`、`fy26_segmentation`、account/tenant/forecast snapshot、owner / sales-team 邻近治理语义 | `Account_ID__c` auto-number、`Org_Set_Account`、`salesforce_accounts` / `dim_org` / `dim_tenant` 链路已在 | `Account_Contract_Valid_Message`、`Account_Partner_Sales_Owner_Set` 缺失；`Account_Current_Order_Type` 当前不再作为这组 front-door 的主实现范围；清完后才可能剩 `AccountTrigger` residuals | `L2 Account owner / governance parity`，当前仍是 `runtime candidate` | owner/shared-dimension parity、account governance parity、tenant bridge 邻近漂移 | `Account runtime candidate` | `583...`、`690...`、`salesforce_accounts`、`dim_org`、`dim_tenant` |

## 升级规则

1. 先把同面
   `exact-name Flow parity`
   、
   `activation-state mismatch`
   、
   `semantic mismatch`
   清掉。
2. 如果验收字段在对应 front-door 仍持续漂移，
   再升级成 runtime 讨论。
3. 只有升级后仍能明确落到
   `Lead runtime`
   、
   `Opportunity / Quote runtime`
   、
   `Finance runtime`
   、
   或 candidate 组，
   才值得单开 runtime issue。

## 一句话收口

`这张梯子不是“CM 无能力清单”，而是“每张报表目前处在哪一层：L2 parity、candidate，还是已经够资格升级成 runtime”。`