openxiangda 1.0.29 → 1.0.31

package/openxiangda-skills/references/automation-v3.md

@@ -9,52 +9,147 @@ Automations have two files:
 
 Automation can run from form events, workflow events, fixed cron schedules, or a form date field reaching a configured time. Pair these triggers with JS_CODE when the action must execute on the backend and cannot be handled reliably by a frontend page.
 
+AI-authored automations must use `trigger_v2`. The CLI passes this JSON through unchanged and only fills the root `appType` and `formUuid` when they are missing and can be resolved from the active workspace/profile.
+
 Form submit trigger:
 
 ```json
 {
-  "type": "form_data_submitted",
+  "version": "trigger_v2",
+  "mode": "event",
+  "appType": "APP_XXX",
+  "formUuid": "FORM_XXX",
+  "enabled": true,
+  "event": {
+    "source": "form_data",
+    "action": "submitted"
+  },
+  "filters": {
+    "conditions": []
+  }
+}
+```
+
+Form update/delete triggers use the same shape with `event.action` set to `updated` or `deleted`. Update events expose `ctx.formData.current`, `ctx.formData.previous`, `ctx.formData.changes`, and `ctx.triggerEvent.data.metadata.changeRecords`.
+
+Form field change trigger:
+
+```json
+{
+  "version": "trigger_v2",
+  "mode": "event",
+  "appType": "APP_XXX",
+  "formUuid": "FORM_XXX",
+  "enabled": true,
+  "event": {
+    "source": "form_field",
+    "action": "changed"
+  },
+  "filters": {
+    "fieldChange": {
+      "fieldId": "status",
+      "changeType": "to_value",
+      "toValue": "approved"
+    }
+  }
+}
+```
+
+`fieldChange.changeType` can be `any`, `from_to`, `to_value`, or `from_value`.
+
+Workflow task trigger:
+
+```json
+{
+  "version": "trigger_v2",
+  "mode": "event",
   "appType": "APP_XXX",
   "formUuid": "FORM_XXX",
-  "enabled": true
+  "enabled": true,
+  "event": {
+    "source": "workflow_task",
+    "action": "approved"
+  },
+  "filters": {
+    "workflow": {
+      "processDefinitionId": "workflow-id",
+      "nodeId": "approval-node-id",
+      "operatorId": "",
+      "assigneeId": "",
+      "previousAssigneeId": ""
+    }
+  }
 }
 ```
 
-Form update trigger:
+Workflow task actions are `approved`, `rejected`, `returned`, `transferred`, and `cancelled`. Returned task events include `ctx.workflowData.targetNodeId` and `ctx.workflowData.targetNodeName` when the platform can resolve the target node.
+
+Workflow process trigger:
 
 ```json
 {
-  "type": "form_data_updated",
+  "version": "trigger_v2",
+  "mode": "event",
   "appType": "APP_XXX",
   "formUuid": "FORM_XXX",
-  "enabled": true
+  "enabled": true,
+  "event": {
+    "source": "workflow_process",
+    "action": "rejected"
+  },
+  "filters": {
+    "workflow": {
+      "processDefinitionId": "workflow-id",
+      "finalResult": "rejected"
+    }
+  }
 }
 ```
 
-Scheduled trigger:
+Workflow process actions are `started`, `approved`, `rejected`, `terminated`, and `withdrawn`. Final approval is backed by `workflow_process_completed`; final rejection is backed by `workflow_process_terminated` with `finalResult: "rejected"`; manual termination uses `finalResult: "terminated"`.
+
+Fixed-time scheduled trigger:
 
 ```json
 {
-  "type": "scheduled",
+  "version": "trigger_v2",
+  "mode": "scheduled",
   "appType": "APP_XXX",
   "enabled": true,
-  "scheduleType": "fixed_time",
-  "fixedTime": {
-    "startTime": "2026-05-21T09:00:00+08:00",
-    "cronExpression": "0 0 9 * * *"
+  "schedule": {
+    "type": "fixed_time",
+    "fixedTime": {
+      "startTime": "2026-05-21T09:00:00+08:00",
+      "cronExpression": "0 0 9 * * *",
+      "maxExecutions": 1
+    }
   }
 }
 ```
 
-Workflow trigger:
+Form date-field scheduled trigger:
 
 ```json
 {
-  "type": "workflow_process_completed",
+  "version": "trigger_v2",
+  "mode": "scheduled",
   "appType": "APP_XXX",
   "formUuid": "FORM_XXX",
-  "processDefinitionId": "workflow-id",
-  "enabled": true
+  "enabled": true,
+  "schedule": {
+    "type": "form_date_field",
+    "formDateField": {
+      "fieldId": "dueAt",
+      "startOffset": {
+        "type": "before",
+        "days": 1,
+        "time": "09:00:00"
+      },
+      "endFieldId": "",
+      "cronExpression": "0 0 9 * * *",
+      "maxExecutions": 1
+    }
+  }
 }
 ```
 
@@ -102,7 +197,18 @@ Resource manifest shape:
 {
   "code": "daily_ticket_digest",
   "name": "每日工单摘要",
-  "triggerConfig": { "type": "scheduled", "enabled": true },
+  "triggerConfig": {
+    "version": "trigger_v2",
+    "mode": "scheduled",
+    "enabled": true,
+    "schedule": {
+      "type": "fixed_time",
+      "fixedTime": {
+        "startTime": "2026-05-21T09:00:00+08:00",
+        "cronExpression": "0 0 9 * * *"
+      }
+    }
+  },
   "definitionFile": "definition.code.json",
   "previewFile": "preview.json",
   "publish": true,

package/openxiangda-skills/skills/openxiangda-workflow-automation/SKILL.md

@@ -92,6 +92,18 @@ Inside the TypeScript script, prefer `export default async function (ctx) {}` or
 
 ## Automation Flow
 
+New automation triggers must use `trigger_v2`.
+
+Use these v2 event sources and actions:
+
+- Form data: `event.source: "form_data"` with `submitted`, `updated`, or `deleted`.
+- Form field: `event.source: "form_field"`, `event.action: "changed"`, and `filters.fieldChange` with `fieldId` plus `changeType: "any" | "from_to" | "to_value" | "from_value"`.
+- Workflow task: `event.source: "workflow_task"` with `approved`, `rejected`, `returned`, `transferred`, or `cancelled`; use `filters.workflow.nodeId`, `operatorId`, `assigneeId`, and `previousAssigneeId` when needed.
+- Workflow process: `event.source: "workflow_process"` with `started`, `approved`, `rejected`, `terminated`, or `withdrawn`; set `filters.workflow.finalResult` for final outcomes.
+- Scheduled: `mode: "scheduled"` with `schedule.type: "fixed_time"` or `"form_date_field"`.
+
+The CLI passes `trigger_v2` through unchanged and fills root `appType`/`formUuid` from the active profile when omitted and resolvable, for example with `--form-code customer`. Do not put profile-specific IDs into reusable examples unless they are resolved from local workspace state.
+
 1. Create a trigger JSON and automation v3 definition JSON locally.
 2. Validate:
    ```bash

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "openxiangda",
-  "version": "1.0.29",
+  "version": "1.0.31",
   "description": "OpenXiangda CLI, workspace build tools, runtime SDK, and form components.",
   "private": false,
   "bin": {
@@ -109,8 +109,8 @@
     "vite": "^6.0.0"
   },
   "peerDependencies": {
-    "react": ">=18",
-    "react-dom": ">=18"
+    "react": ">=18 <19",
+    "react-dom": ">=18 <19"
   },
   "devDependencies": {
     "@testing-library/jest-dom": "^6.9.1",