@stalfh233/omc-cli 0.4.56 → 0.4.57

package/dist/lanes/runtime-data.js

@@ -499,8 +499,16 @@ export function registerRuntimeDataLane(tools) {
                     const selected = fields ?? Object.keys(data).filter((field) => !["id", "bizObjectId", "schemaCode", "sequenceStatus", "createdTime", "updatedTime", "creator", "updater"].includes(field));
                     return { id: row.bizObjectId ?? row.id ?? data.id, fields: Object.fromEntries(selected.map((field) => [field, data[field] ?? null])) };
                 });
+                // Live 2026-10-19: when a model has NO configured list view, the
+                // platform projects only system columns — every business field comes
+                // back null while `data.load` shows the real values. That reads as
+                // "the write failed". Detect an all-null business projection (items
+                // present, zero non-null business values) and say so.
+                const businessKeys = fields ?? Object.keys(items[0]?.fields ?? {}).filter((field) => !["id", "bizObjectId", "schemaCode", "sequenceStatus", "createdTime", "updatedTime", "creator", "updater", "name"].includes(field));
+                const projectionEmpty = items.length > 0 && businessKeys.length > 0 && items.every((item) => businessKeys.every((key) => item.fields[key] === null || item.fields[key] === undefined));
                 const readback = {
                     schemaCode: args.schemaCode,
+                    ...(projectionEmpty ? { projectionWarning: { reason: "business-columns-null", hint: "模型可能未配置列表视图：data.list 只投影列表列，业务列会全为 null；核对写入结果请用 data.load（或先建列表视图）" } } : {}),
                     ...(args.queryCode !== undefined ? { queryCode: args.queryCode } : {}),
                     total: args.showTotal === false ? null : page.total,
                     // This branch is the non-`all` read: the platform's default filter

package/dist/lanes/workflow.js

@@ -914,7 +914,21 @@ async function childTableFieldsOf(session, schemaCode) {
     };
     const rows = (await read("false")).length > 0 ? await read("false") : await read("true");
     return rows
-        .map((row) => ({ code: String(row.code ?? row.propertyCode ?? ""), name: String(row.name ?? row.code ?? ""), isChild: Number(row.type ?? row.propertyType ?? 0) === 8 || String(row.type ?? row.propertyType ?? "").toUpperCase() === "CHILD_TABLE" || row.subSchema !== undefined }))
+        .map((row) => {
+        const type = row.propertyType ?? row.type ?? 0;
+        // Live 2026-10-19: the list face carries `subSchema: null` on EVERY row,
+        // so `subSchema !== undefined` classified every scalar/relation field as
+        // a child table and refused `required` with a false reason. Only a
+        // NON-EMPTY subSchema marks a child table (plus the real type code:
+        // propertyType 8 = CHILD_TABLE / SHEET).
+        const subSchema = row.subSchema;
+        const hasSubSchema = subSchema !== undefined && subSchema !== null && String(subSchema).trim() !== "";
+        const isChild = Number(type) === 8 ||
+            String(type).toUpperCase() === "CHILD_TABLE" ||
+            String(type).toUpperCase() === "SHEET" ||
+            hasSubSchema;
+        return { code: String(row.code ?? row.propertyCode ?? ""), name: String(row.name ?? row.code ?? ""), isChild };
+    })
         .filter((row) => row.isChild && row.code !== "");
 }
 const CHILD_TABLE_LIST_BUTTONS = [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@stalfh233/omc-cli",
-  "version": "0.4.56",
+  "version": "0.4.57",
   "description": "CloudPivot 8.6 configuration capability CLI — governed, fail-closed, coverage-manifest bounded.",
   "type": "module",
   "bin": {
@@ -50,9 +50,9 @@
     "access": "public"
   },
   "dependencies": {
-    "@stalfh233/omc-fake-platform": "0.4.56",
+    "@stalfh233/omc-fake-platform": "0.4.57",
     "commander": "14.0.3",
-    "omc-core": "0.4.56",
+    "omc-core": "0.4.57",
     "proper-lockfile": "4.1.2",
     "write-file-atomic": "6.0.0",
     "zod": "^3.23.8",

package/skills/omc-write-hazards.md

@@ -38,6 +38,14 @@ omc help omc-write-hazards
 - **运行时写值的最小形状**（组合出错只会得到一个不透明的 `50000`/NPE，逐一最小化再合）：单选关联(9) → id 字符串 `"<id>"`；**人员/组织(50/51/60/61) → `[{"id":"<id>","type":3,"name":"<名>"}]`，`type` 必填且为整数**（缺/非整数 → `BizField.parseFromClient` 拆箱 NPE→50000；用户=3、部门=1）；日期(3) → 字符串 `"2026-09-30 10:00:00"`；子表(8) → 行对象数组 `[{"<子列code>":<值>, ...}]`。先各写一条最小行通过，再组合。
 - **DATE(3) 字段的 `options.format` 必须是平台大写枚举**（`YYYY-MM-DD`、`YYYY-MM-DD HH:mm:ss`、`YYYY年MM月DD日`…），**不是 Java 的 `yyyy-MM-dd`**：平台 `DateBizField` 按字面比较，Java 写法能创建字段但**首次运行时 save 稳定 `50000`（`不支持的format`）**（2026-09-30 R5 实测）。`field.create`/`intent` 会就地拒绝非枚举值。
 
+## 业务规则与流程事件（源码实证，1.1.25）
+
+- **`Create` 的触发判定是「旧状态→新状态」**：旧 `DRAFT` 且新 `PROCESSING` 或 `COMPLETED`（`DomainServiceImpl#getDefaultRuleCode`）。所以无流程模型一调 `data.submit`（→COMPLETED）**和流程表单提交（DRAFT→PROCESSING）都触发 Create**；`data.save` 存草稿不触发。不要因为"目标表没变化"就断言规则没触发。
+- **副作用缺失归因三步**：先查执行记录（`h_log_biz_service` 按服务/方法/时间，或容器日志）→ ①无调用=规则/触发问题 ②有调用但失败=参数/权限/业务异常 ③调用成功但不可见=视图投影/事务未提交/查询条件。禁止只看目标表。
+- **BIZ_ACTION 判成功只看传输**：REST 适配器解析响应后直接返回，**不校验 `errcode`**。扩展接口回 `{"errcode":50000}` + HTTP 200 会被当成节点成功（日志 `biz action node execute successful`）。要阻断必须走表单 `onValidate` 或数据规则，不能靠业务返回码。
+- **流程事件处理器吞异常**：`start`/`end`/`cancel`/`activate` 中的 BIZ_ACTION 抛异常时，`InstanceContext#processingBusiness` 只记 `processingBusiness error.` 并返回失败结果，**流程继续**。事件处理器不能做"提交前拦截"。
+- **禁写当前单据**：BIZ_ACTION 是 HTTP 自调用，外层事务已持行锁；同事务更新当前单据会等到 15s 超时并整条回滚。副作用写独立表；需要留痕用独立事务/异步重建 `RequestContext`。
+
 ## 运行数据读取的默认过滤
 
 - `data.list` **默认不含 DRAFT**（`total` 也只算 COMPLETED）：清测试数据时 `total:0` 不代表没有残留。核对/清理一律显式 `{"all":true,"showTotal":true}`，或读回体里的过滤标注。`data.load` 用于单行核对。