@stalfh233/omc-cli 0.4.28 → 0.4.29

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -548,7 +548,7 @@ export function registerRuntimeDataLane(tools) {
548
548
  sheetCode: z.string().optional(),
549
549
  formData: runtimeFormDataArg,
550
550
  workflowCode: z.string().optional().describe("portal draft-save shape: create the row AND a DRAFT workflow instance + start workItem (finishStart=FALSE); submit later via data.submit with the returned workItemId. formData must NOT carry an id — in-place workflow start has no REST surface in 8.6.26"),
551
- submit: z.boolean().optional().describe("r18 retro:true=一调完成态——保存后立即直提(无流程模型 DRAFT→COMPLETED,触发 Create 业务规则);与 workflowCode 互斥(流程草稿须走 data.submit 两段式)。默认 false 仅存草稿"),
551
+ submit: z.boolean().optional().describe("true=保存后立即直提(无流程模型 DRAFT→COMPLETED,触发 Create 规则);与 workflowCode 互斥。**按业务约定正式数据优先直接 data.submit(无 id=新建并提交一调完成)——本参数是便捷别名,save 的定位是草稿/暂存**"),
552
552
  ...readbackProjectionArgs,
553
553
  }, async (session, args) => {
554
554
  // F-A (self-audit): the combo used to be silently ignored (the workflow
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@stalfh233/omc-cli",
3
- "version": "0.4.28",
3
+ "version": "0.4.29",
4
4
  "description": "CloudPivot 8.6 configuration capability CLI — governed, fail-closed, coverage-manifest bounded.",
5
5
  "type": "module",
6
6
  "bin": {
@@ -51,7 +51,7 @@
51
51
  },
52
52
  "dependencies": {
53
53
  "commander": "14.0.3",
54
- "omc-core": "0.4.28",
54
+ "omc-core": "0.4.29",
55
55
  "proper-lockfile": "4.1.2",
56
56
  "write-file-atomic": "6.0.0",
57
57
  "zod": "^3.23.8",
@@ -171,10 +171,11 @@ only the section for the capability you need —
171
171
  - **recipe**:
172
172
  - `omc describe data.save --example workflow-backed-data-save`
173
173
  - `omc describe data.submit --example workflow-backed-data-submit`(有流程)
174
- - 无流程模型的规则验证路径(两选):
175
- - 一调:`data.save {schemaCode, formData, submit:true}` ——保存+直提 COMPLETED,触发 Create 规则(模型有已发布流程时会拒绝并指路两段式)
176
- - 两步:`data.save`(DRAFT)→ `data.submit {schemaCode, bizObjectId, formData}` ——示例 `omc describe data.submit --example plain-data-submit`
177
- - 流程模型:`data.save {workflowCode}`(返回 workItemId)→ `data.submit {bizObjectId, workflowInstanceId, workItemId}`(workflow-backed-data-submit)
174
+ - **正式数据一律 data.submit**(业务约定;save 的新建永远是 DRAFT 草稿):
175
+ - 无流程模型一调:`data.submit {schemaCode, formData}`(无 id=新建并提交,COMPLETED,触发 Create 规则)——示例 `omc describe data.submit --example plain-data-submit`
176
+ - 已存草稿直提:`data.submit {schemaCode, bizObjectId, formData}`
177
+ - 流程模型两段式:`data.save {workflowCode}`(返回 workItemId)→ `data.submit {bizObjectId, workflowInstanceId, workItemId}`(workflow-backed-data-submit)
178
+ - `data.save` 定位=草稿/暂存;其 `submit:true` 便捷参数仍在(无流程模型等同直提),但按约定优先直接 data.submit
178
179
  - **边界 / 陷阱**:读实际业务记录是 OMC 独有能力。**计算字段(FORMULA/子表计算)不由 API 回填**——写测试数据带预算值,公式正确性人工前台确认;带子表计算字段的模型 API 写可能 50000(服务端重算 NPE),前台正常。
179
180
 
180
181
  ---