From b2087bd160b19fa13cfe1baa6b48a0209d098953 Mon Sep 17 00:00:00 2001 From: lorne <1991wangliang@gmail.com> Date: Thu, 5 Nov 2026 11:06:28 +0800 Subject: [PATCH 1/2] =?UTF-8?q?chore:=20.gitignore=20=E5=BF=BD=E7=95=A5=20?= =?UTF-8?q?.codebuddy/=20=E7=9B=AE=E5=BD=95?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .gitignore | 3 +++ 1 file changed, 3 insertions(+) diff --git a/.gitignore b/.gitignore index 844f2b8b..d2dabb29 100644 --- a/.gitignore +++ b/.gitignore @@ -40,6 +40,9 @@ build/ ### workbuddy ### .workbuddy/ +### codebuddy ### +.codebuddy/ + ### Worktrees ### .worktrees/ From 74060d5aaf2fa0e5419fd6dcbc33443969c70605 Mon Sep 17 00:00:00 2001 From: lorne <1991wangliang@gmail.com> Date: Thu, 5 Nov 2026 15:10:26 +0800 Subject: [PATCH 2/2] =?UTF-8?q?docs:=20=E4=BE=9D=E6=8D=AE=E4=BB=A3?= =?UTF-8?q?=E7=A0=81=E4=BA=8B=E5=AE=9E=E5=AF=B9=E9=BD=90=E9=A1=B9=E7=9B=AE?= =?UTF-8?q?=E6=96=87=E6=A1=A3?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - AGENTS/CLAUDE: FlowService 8 个入口、事件 8 种、Controller 端点与 node-view 补充 - README: REST API 层端点描述同步 - Integration: Controller 数量、框架版本 17.3.1、node-view 路径、/exists 端点、reset 请求 operatorId、异常子类 6 个、编程式 API 补 resetSubProcess/import/export - capabilities: 异常体系补 WorkflowTransferException、FlowService 补 resetSubProcess、NodeType.START 修正、FlowScriptContext 委托表述、重置请求 operatorId、版本号 --- AGENTS.md | 6 +++--- CLAUDE.md | 4 ++-- README.md | 2 +- docs/Integration/README.md | 4 ++-- docs/Integration/extension-points.md | 3 ++- docs/Integration/programmatic-api.md | 3 +++ docs/Integration/rest-api.md | 13 ++++++++++--- docs/Integration/script-integration.md | 2 +- docs/Integration/user-integration.md | 2 +- .../flow-engine-framework/exception.md | 17 ++++++++++------- .../flow-engine-framework/flow-service.md | 7 ++++++- docs/capabilities/flow-engine-framework/node.md | 2 +- .../flow-engine-framework/script.md | 4 ++-- .../flow-engine-framework/sub-process.md | 2 +- docs/capabilities/index.md | 4 ++-- docs/capabilities/springboot/data-jpa.md | 2 +- 16 files changed, 48 insertions(+), 29 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 22b28522..132c8f2d 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -36,7 +36,7 @@ Flow Engine 是一个企业级工作流引擎,基于 Java 17 和 Spring Boot 3 ### 服务编排模式(FlowService) -`FlowService`(`flow-engine-framework/.../service/FlowService.java`)是 `@Transactional` 业务入口。**每个流程操作对应一个独立的 `FlowXxxService`**(`FlowCreateService` / `FlowActionService` / `FlowRevokeService` / `FlowDeleteService` / `FlowUrgeService` / `FlowDetailService`),通过 `IRepositoryHolder` 注入依赖,且每次操作前调用 `FlowOperatorLocalThreadCache.getInstance().clear()` 清理线程缓存。新增流程操作应沿用此模式:新建 `FlowXxxService(request, repositoryHolder)`,并在 `FlowService` 暴露一个入口方法。 +`FlowService`(`flow-engine-framework/.../service/FlowService.java`)是 `@Transactional` 业务入口,共 8 个入口方法(detail / processNodes / create / action / revoke / delete / urge / resetSubProcess)。**每个流程操作对应一个独立的 `FlowXxxService`**(`FlowCreateService` / `FlowActionService` / `FlowRevokeService` / `FlowDeleteService` / `FlowUrgeService` / `FlowDetailService` / `FlowProcessNodeService` / `FlowSubProcessResetService` / `FlowSubProcessResultService` / `FlowDelayTriggerService` / `OperatorAssignmentService` 等),通过 `IRepositoryHolder` 注入依赖,且每次操作前调用 `FlowOperatorLocalThreadCache.getInstance().clear()` 与 `FlowRuntimeScriptLocalCache` 清理线程缓存。新增流程操作应沿用此模式:新建 `FlowXxxService(request, repositoryHolder)`,并在 `FlowService` 暴露一个入口方法。 ### 仓储持有者(IRepositoryHolder) @@ -64,11 +64,11 @@ REST 层通过请求参数 `mockKey` 分流到 Mock 实例(见 `FlowRecordCont ### 事件(IFlowEvent + EventPusher) -7 种事件:开始 / 待办 / 已办 / 完成 / 催办 / 撤销(`FlowRecordRevokeEvent`)/ 删除(`FlowRecordDeleteEvent`)。操作完成后用 `EventPusher.push(event)` 推送;事件通常携带 `FlowRecord` + `mock` 标记。外部可用 Spring `@EventListener` 订阅。 +8 种事件:开始 / 待办 / 已办 / 完成 / 催办 / 撤销(`FlowRecordRevokeEvent`)/ 删除(`FlowRecordDeleteEvent`)/ 子流程重置(`FlowSubProcessResetEvent`)。操作完成后用 `EventPusher.push(event)` 推送;记录类事件携带 `FlowRecord` + `mock` 标记,重置事件携带新旧聚合组快照。外部可用 Spring `@EventListener` 订阅。 ### API 模块划分 -- **命令操作**:`flow-engine-starter-api` — `FlowRecordController`(`/api/cmd/record`:create / action / revoke / delete / urge / detail)与 `WorkflowController`(`/api/cmd/workflow`:流程设计 CRUD) +- **命令操作**:`flow-engine-starter-api` — `FlowRecordController`(`/api/cmd/record`:create / action / revoke / delete / urge / detail / processNodes / subProcess/reset)、`WorkflowController`(`/api/cmd/workflow`:流程设计 CRUD 及导入导出)与 `NodeViewJavaScriptController`(`/api/cmd/node-view`:节点视图脚本 getScript / save) - **查询**:`flow-engine-starter-query` — `FlowRecordQueryController`(`/api/query/record`:list / todo / done / notify)与 `WorkflowQueryController`(`/api/query/workflow`:list / options / versions) - **持久化**:`flow-engine-starter-infra` — JPA 实体与仓储实现(含达梦方言) diff --git a/CLAUDE.md b/CLAUDE.md index 36ac241d..8f27c79f 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -36,7 +36,7 @@ Flow Engine 是一个企业级工作流引擎,基于 Java 17 和 Spring Boot 3 ### 服务编排模式(FlowService) -`FlowService`(`flow-engine-framework/.../service/FlowService.java`)是 `@Transactional` 业务入口。**每个流程操作对应一个独立的 `FlowXxxService`**(`FlowCreateService` / `FlowActionService` / `FlowRevokeService` / `FlowDeleteService` / `FlowUrgeService` / `FlowDetailService`),通过 `IRepositoryHolder` 注入依赖,且每次操作前调用 `FlowOperatorLocalThreadCache.getInstance().clear()` 清理线程缓存。新增流程操作应沿用此模式:新建 `FlowXxxService(request, repositoryHolder)`,并在 `FlowService` 暴露一个入口方法。 +`FlowService`(`flow-engine-framework/.../service/FlowService.java`)是 `@Transactional` 业务入口,共 8 个入口方法(detail / processNodes / create / action / revoke / delete / urge / resetSubProcess)。**每个流程操作对应一个独立的 `FlowXxxService`**(`FlowCreateService` / `FlowActionService` / `FlowRevokeService` / `FlowDeleteService` / `FlowUrgeService` / `FlowDetailService` / `FlowProcessNodeService` / `FlowSubProcessResetService` / `FlowSubProcessResultService` / `FlowDelayTriggerService` / `OperatorAssignmentService` 等),通过 `IRepositoryHolder` 注入依赖,且每次操作前调用 `FlowOperatorLocalThreadCache.getInstance().clear()` 与 `FlowRuntimeScriptLocalCache` 清理线程缓存。新增流程操作应沿用此模式:新建 `FlowXxxService(request, repositoryHolder)`,并在 `FlowService` 暴露一个入口方法。 ### 仓储持有者(IRepositoryHolder) @@ -68,7 +68,7 @@ REST 层通过请求参数 `mockKey` 分流到 Mock 实例(见 `FlowRecordCont ### API 模块划分 -- **命令操作**:`flow-engine-starter-api` — `FlowRecordController`(`/api/cmd/record`:create / action / revoke / delete / urge / detail)与 `WorkflowController`(`/api/cmd/workflow`:流程设计 CRUD) +- **命令操作**:`flow-engine-starter-api` — `FlowRecordController`(`/api/cmd/record`:create / action / revoke / delete / urge / detail / processNodes / subProcess/reset)、`WorkflowController`(`/api/cmd/workflow`:流程设计 CRUD 及导入导出)与 `NodeViewJavaScriptController`(`/api/cmd/node-view`:节点视图脚本 getScript / save) - **查询**:`flow-engine-starter-query` — `FlowRecordQueryController`(`/api/query/record`:list / todo / done / notify)与 `WorkflowQueryController`(`/api/query/workflow`:list / options / versions) - **持久化**:`flow-engine-starter-infra` — JPA 实体与仓储实现(含达梦方言) diff --git a/README.md b/README.md index fac60bbc..91f0d0cc 100644 --- a/README.md +++ b/README.md @@ -29,7 +29,7 @@ Flow Engine 是一个基于 Java 17 和 Spring Boot 3.5.9 构建的企业级工 flow-engine ├── flow-engine-framework # 核心流程引擎框架 ├── flow-engine-starter # Spring Boot 自动配置入口 -├── flow-engine-starter-api # REST API 层(命令操作:create / action / revoke / delete / urge / detail) +├── flow-engine-starter-api # REST API 层(命令操作:create / action / revoke / delete / urge / detail / processNodes / subProcess/reset,含节点视图脚本接口) ├── flow-engine-starter-infra # 持久化层(JPA 实体、11 个仓储实现、含达梦方言) ├── flow-engine-starter-query # 查询层(流程记录与流程定义只读 API) ├── flow-engine-example # 示例应用(H2/达梦数据库、JWT 认证、端口 8090) diff --git a/docs/Integration/README.md b/docs/Integration/README.md index 618bd511..cb169277 100644 --- a/docs/Integration/README.md +++ b/docs/Integration/README.md @@ -35,7 +35,7 @@ | [流程事件机制](./event-integration.md) | 8 种事件、`EventPusher`、`IHandler` 订阅、异步分发管道、事务变体、推送时机 | | [仓储抽象与持久化](./repository-integration.md) | `IRepositoryHolder`、12 个仓储接口(含 11 个 JPA 实现 + 需自行实现的 `NodeViewJavaScriptRepository`)、脚本仓储、锁机制 | | [Spring Boot 自动配置](./auto-configuration.md) | `AutoConfiguration` 8 个 Bean、4 个 Register、必选/可选 Bean 清单 | -| [REST API](./rest-api.md) | 4 个 Controller、`mockKey`/`operatorId` 分流机制、请求/响应结构 | +| [REST API](./rest-api.md) | 5 个 Controller、`mockKey`/`operatorId` 分流机制、请求/响应结构 | | [Mock 模式](./mock-mode.md) | 全内存沙箱 `MockInstance`、15 分钟过期、接入方式 | | [节点/动作/策略扩展](./extension-points.md) | 19 种节点 × 8 种动作 × 15 种节点策略 × 2 种流程策略,扩展方式 | | [编程式 API](./programmatic-api.md) | `WorkflowBuilder`/`FlowFormBuilder` 构建流程、`FlowService` 服务编排、查询服务 | @@ -72,7 +72,7 @@ REST 请求 → FlowRecordController ## 版本约定 - 引擎版本:`0.1.0-SNAPSHOT`(根 pom `revision`) -- 外部框架依赖(根 pom `codingapi.framework.version = 17.3.0`): +- 外部框架依赖(根 pom `codingapi.framework.version = 17.3.1`): - `com.codingapi.springboot:springboot-starter` —— 事件体系(`EventPusher`/`IHandler`)、`UserContext`、`LocaleMessageException` - `com.codingapi.springboot:springboot-starter-script` —— Groovy 脚本引擎(`GroovyScript`/注解/仓储 SPI) - `com.codingapi.springboot:springboot-starter-data-fast` —— `FastRepository`(JPA 仓储基类) diff --git a/docs/Integration/extension-points.md b/docs/Integration/extension-points.md index d3753564..2e26f61c 100644 --- a/docs/Integration/extension-points.md +++ b/docs/Integration/extension-points.md @@ -150,7 +150,7 @@ IFlowAction#run ## 5. 异常体系 -基类 `FlowException extends LocaleMessageException`,5 个子类(`exception/` 包),均以静态工厂方法构造: +基类 `FlowException extends LocaleMessageException`,6 个子类(`exception/` 包),均以静态工厂方法构造: | 子类 | 典型工厂方法与错误场景 | |---|---| @@ -159,5 +159,6 @@ IFlowAction#run | `FlowStateException` | `repositoryNotRegistered`、`recordAlreadyDone`、`operatorNotMatch`、`workflowAlreadyDisable`、`recordNotSupportRevoke` 等 | | `FlowNotFoundException` | `workflow(workCode)`、`record(recordId)`、`node(nodeId)`、`operator(operatorId)`、`action(actionId)` | | `FlowPermissionException` | `accessDenied(operation)` | +| `WorkflowTransferException` | `invalidSchema()`、`unsupportedSchema()`、`scriptNotFound()`、`scriptTypeUnsupported()`、`replaceTargetNotFound()`(流程导入导出) | REST 层经 `LocaleMessageException` 统一转换为 `{ errCode, errMessage }` 响应。 \ No newline at end of file diff --git a/docs/Integration/programmatic-api.md b/docs/Integration/programmatic-api.md index da20be26..c3f23358 100644 --- a/docs/Integration/programmatic-api.md +++ b/docs/Integration/programmatic-api.md @@ -15,6 +15,7 @@ public class FlowService { void revoke(FlowRevokeRequest request); // 撤销 void delete(FlowDeleteRequest request); // 删除(仅未流转实例) void urge(FlowUrgeRequest request); // 催办 + void resetSubProcess(FlowSubProcessResetRequest request); // 子流程数据重置(独立接口) } ``` @@ -66,6 +67,8 @@ void saveWorkflowRuntime(WorkflowRuntime workflowRuntime); WorkflowRuntime getOrCreateWorkflowRuntime(Workflow workflow); // @Transactional(REQUIRES_NEW) + lockById WorkflowRuntime getWorkflowRuntime(String workId, long workVersion); String importWorkflow(String body, IFlowOperator createOperator); // 导入流程 JSON,返回 workId +String importWorkflow(String body, IFlowOperator createOperator, WorkflowImportMode mode); // 指定导入模式(增量/覆盖) +String exportWorkflow(String workId); // 导出流程及其全部版本和脚本 ``` - `saveWorkflowVersion(version, creatable, enable)`:保存版本(`creatable=true` 时创建新版本并切为当前;`enable` 控制是否启用),内部会固化脚本(`WorkflowGroovyScriptUtils.saveScripts`)。 diff --git a/docs/Integration/rest-api.md b/docs/Integration/rest-api.md index 638b1893..85c6b34f 100644 --- a/docs/Integration/rest-api.md +++ b/docs/Integration/rest-api.md @@ -53,6 +53,7 @@ operatorId 请求参数 → 存在 → 使用该 id 作为当前操作人 | POST | `/api/cmd/workflow/create-custom-action` | — | `SingleResponse` | 创建自定义动作默认配置 | | POST | `/api/cmd/workflow/mock` | — | `SingleResponse` | 创建 Mock 沙箱,返回 mockKey(需流程管理员) | | POST | `/api/cmd/workflow/cleanMock` | `IdRequest` | `Response` | 清理 Mock 沙箱 | +| GET | `/api/cmd/workflow/exists` | query `code` | `SingleResponse` | 判断流程编码是否存在 | ## 4. 查询(`/api/query/record`) @@ -86,11 +87,14 @@ public interface FlowRecordQueryService { | GET | `/api/query/workflow/options` | — | `MultiResponse` | 流程下拉选项 | | GET | `/api/query/workflow/versions` | query `id`(workId) | `MultiResponse` | 流程版本列表 | -## 6. 节点视图脚本(`/api/view/javascript`) +## 6. 节点视图脚本(`/api/cmd/node-view`) `flow-engine-starter-api/src/main/java/com/codingapi/flow/api/controller/NodeViewJavaScriptController.java` -提供节点视图 JS 的读写接口(`NodeViewJavaScript` 持久化经 `NodeViewJavaScriptRepository`)。 +| 方法 | 路径 | 参数/请求体 | 说明 | +|---|---|---|---| +| GET | `/api/cmd/node-view/getScript` | query `key` | 按缓存 key 获取节点视图 JS 内容 | +| POST | `/api/cmd/node-view/save` | JSON 请求体 | 保存节点视图 JS(`NodeViewJavaScript`,持久化经 `NodeViewJavaScriptRepository`) | ## 7. Groovy 脚本接口(`/api/groovy-script`) @@ -145,11 +149,14 @@ public interface FlowRecordQueryService { ```json { "recordId": 456, + "operatorId": 1001, "resetInstanceProcessIds": ["选中重建的子流程实例流程id"], "advice": "重置说明" } ``` +- `operatorId` 必填(`verify()` 强制大于 0,缺失抛 `FlowValidationException.required("operatorId")`)。 + - 重置不属于审批动作,不经过 `/action` 接口;仅当子流程节点开启 `resettable` 能力且当前待办位于其下游时可调用。 - 无需指定子流程节点:由选中实例流程id定位其所属聚合组,选中实例须同属一个已放行且未取代的聚合组。 - 流程详情 `FlowContent.resetSubProcess` 标识字段表明当前记录是否具备该能力,前端据此提供交互。 @@ -201,4 +208,4 @@ recordId / timeoutTime / recordState / flowState / notify | `SingleResponse` | `{ data: T, success, ... }` | | `MultiResponse` | `{ data: T[], total, success, ... }` | -异常统一为 `LocaleMessageException` 体系(`FlowException` 的 5 个子类,见 [扩展点](./extension-points.md#异常体系)),错误码见各异常工厂方法。 \ No newline at end of file +异常统一为 `LocaleMessageException` 体系(`FlowException` 的 6 个子类,见 [扩展点](./extension-points.md#异常体系)),错误码见各异常工厂方法。 \ No newline at end of file diff --git a/docs/Integration/script-integration.md b/docs/Integration/script-integration.md index 8fe5aa7f..03277403 100644 --- a/docs/Integration/script-integration.md +++ b/docs/Integration/script-integration.md @@ -153,7 +153,7 @@ request.getWorkflow() // Workflow 对象(可访问 form/nodes 等) ### 4.1 脚本对象(`GroovyScript`) -来自外部依赖 `com.codingapi.springboot:springboot-starter-script:17.3.0`。构造方式: +来自外部依赖 `com.codingapi.springboot:springboot-starter-script:17.3.1`。构造方式: ```java GroovyScript groovyScript = GroovyScript.builder(key) diff --git a/docs/Integration/user-integration.md b/docs/Integration/user-integration.md index 0c598e07..8e5a0cb6 100644 --- a/docs/Integration/user-integration.md +++ b/docs/Integration/user-integration.md @@ -72,7 +72,7 @@ public class GatewayContext { ### 3.1 用户实体实现 `IFlowOperator` -`flow-engine-example/src/main/java/com/codingapi/example/entity/User.java`: +`flow-engine-example/src/main/java/com/codingapi/example/entity/User.java`(节选,实际类还包含 `ADMIN_ROLE`/`ADMIN_ACCOUNT` 等常量、静态工厂 `admin(PasswordEncoder)`、`getRoles()`、`encodePassword()` 等成员): ```java package com.codingapi.example.entity; diff --git a/docs/capabilities/flow-engine-framework/exception.md b/docs/capabilities/flow-engine-framework/exception.md index 29bed720..87f9c8fb 100644 --- a/docs/capabilities/flow-engine-framework/exception.md +++ b/docs/capabilities/flow-engine-framework/exception.md @@ -1,7 +1,7 @@ --- name: flow-engine-framework/exception module: flow-engine-framework -description: 流程异常体系,包含异常基类和 5 种业务异常子类 +description: 流程异常体系,包含异常基类和 6 种业务异常子类 status: 已实现 scope: 后端 source: 项目自有 @@ -13,6 +13,7 @@ symbols: - FlowStateException - FlowNotFoundException - FlowPermissionException + - WorkflowTransferException content_hash: 1a3438bf88b6b98d84a03fabe6f08ed66948a8da8f44fea35b8a9d49d1f84458 --- @@ -20,7 +21,7 @@ content_hash: 1a3438bf88b6b98d84a03fabe6f08ed66948a8da8f44fea35b8a9d49d1f84458 提供流程引擎的标准化异常体系,解决以下问题: -- **异常分类**:按业务语义将异常分为执行异常、验证异常、状态异常、未找到异常和权限异常五类 +- **异常分类**:按业务语义将异常分为执行异常、验证异常、状态异常、未找到异常、权限异常和导入导出异常六类 - **错误码标准化**:每种异常使用 `errorCode + message` 格式,支持国际化消息 - **工厂方法创建**:每种异常提供静态工厂方法,统一异常创建方式并确保错误码一致 @@ -30,11 +31,12 @@ content_hash: 1a3438bf88b6b98d84a03fabe6f08ed66948a8da8f44fea35b8a9d49d1f84458 ``` FlowException(抽象基类,继承 LocaleMessageException) -├── FlowExecutionException — 流程执行过程中的错误 -├── FlowValidationException — 流程配置或参数验证错误 -├── FlowStateException — 流程状态不允许当前操作 -├── FlowNotFoundException — 请求的资源不存在 -└── FlowPermissionException — 操作者无权限执行操作 +├── FlowExecutionException — 流程执行过程中的错误 +├── FlowValidationException — 流程配置或参数验证错误 +├── FlowStateException — 流程状态不允许当前操作 +├── FlowNotFoundException — 请求的资源不存在 +├── FlowPermissionException — 操作者无权限执行操作 +└── WorkflowTransferException — 流程定义导入导出错误 ``` ### 各类异常的工厂方法 @@ -46,6 +48,7 @@ FlowException(抽象基类,继承 LocaleMessageException) | `FlowStateException` | `repositoryNotRegistered()`, `recordAlreadyDone()`, `operatorNotMatch()`, `edgeConfigError()`, `recordLimitUrgeError()` | | `FlowNotFoundException` | `workflow()`, `record()`, `node()`, `operator()`, `action()` | | `FlowPermissionException` | `accessDenied()` | +| `WorkflowTransferException` | `invalidSchema()`, `unsupportedSchema()`, `scriptNotFound()`, `scriptTypeUnsupported()`, `replaceTargetNotFound()` | ### 扩展新异常 diff --git a/docs/capabilities/flow-engine-framework/flow-service.md b/docs/capabilities/flow-engine-framework/flow-service.md index dcb96891..8e0aa72a 100644 --- a/docs/capabilities/flow-engine-framework/flow-service.md +++ b/docs/capabilities/flow-engine-framework/flow-service.md @@ -18,6 +18,10 @@ symbols: - FlowProcessNodeService - FlowRevokeService - FlowUrgeService + - FlowDeleteService + - FlowSubProcessResetService + - FlowSubProcessResultService + - SubProcessSessionFactory - OperatorAssignmentService - WorkflowGroovyScriptUtils content_hash: 48847288af1a4551b8327e398d01a8ec4de643dce1c049b90dcdc8ad0134df3b @@ -27,7 +31,7 @@ content_hash: 48847288af1a4551b8327e398d01a8ec4de643dce1c049b90dcdc8ad0134df3b 提供流程引擎的业务服务层,将复杂的流程操作封装为高内聚的服务接口,解决以下问题: -- **流程操作入口**:`FlowService` 作为流程审批操作的统一入口,支持创建、审批、撤销、删除、催办 +- **流程操作入口**:`FlowService` 作为流程审批操作的统一入口,支持创建、审批、撤销、删除、催办、子流程重置 - **流程设计管理**:`WorkflowService` 管理流程定义的 CRUD 和版本操作 - **职责分离**:每种操作由独立的 Service 实现(如 `FlowActionService`、`FlowCreateService`),保持单一职责 - **线程安全**:每次操作前通过 `FlowOperatorLocalThreadCache.clear()` 与 `FlowRuntimeScriptLocalCache.clear()` 清理线程缓存 @@ -45,6 +49,7 @@ content_hash: 48847288af1a4551b8327e398d01a8ec4de643dce1c049b90dcdc8ad0134df3b | `urge(FlowUrgeRequest)` | 催办 | | `detail(FlowDetailRequest)` | 查询流程详情 | | `processNodes(FlowProcessNodeRequest)` | 查询流程节点记录 | +| `resetSubProcess(FlowSubProcessResetRequest)` | 子流程数据重置(独立接口,REST 端点 `POST /api/cmd/record/subProcess/reset`) | ### WorkflowService — 流程设计管理 diff --git a/docs/capabilities/flow-engine-framework/node.md b/docs/capabilities/flow-engine-framework/node.md index 5fb8e24d..84af97ac 100644 --- a/docs/capabilities/flow-engine-framework/node.md +++ b/docs/capabilities/flow-engine-framework/node.md @@ -91,7 +91,7 @@ IFlowNode(核心节点接口) ```java // 通过工厂创建默认节点 -IFlowNode startNode = NodeFactory.getInstance().createNode(NodeType.StartNode); +IFlowNode startNode = NodeFactory.getInstance().createNode(NodeType.START); // 从 Map 反序列化节点 Map nodeData = ...; diff --git a/docs/capabilities/flow-engine-framework/script.md b/docs/capabilities/flow-engine-framework/script.md index b04c8b0a..0c896465 100644 --- a/docs/capabilities/flow-engine-framework/script.md +++ b/docs/capabilities/flow-engine-framework/script.md @@ -36,7 +36,7 @@ content_hash: 42b4c00cdcb8aac4c1695f7d503b1ec953ab4ea3b3f92067e2312c31ea9d4a69 - **脚本注册表**:通过 `ScriptRegistryContext` 单例管理各类默认脚本,支持替换默认实现 - **脚本类型封装**:将各种脚本场景封装为强类型类(如 `RouterNodeScript`、`ConditionScript` 等) -- **脚本执行上下文**:`FlowScriptContext` 提供脚本 `$bind` 上下文(Spring Bean、流程记录、操作者查询);脚本的实际执行由 `FlowScriptRuntimeContext` 结合 spring-boot 的 `GroovyScript` 完成 +- **脚本执行上下文**:`FlowScriptContext` 提供脚本 `$bind` 上下文(Spring Bean、流程记录、操作者查询),内部持有 `IBeanFactory` 并委托其实现;脚本的实际执行由 `FlowScriptRuntimeContext` 结合 spring-boot 的 `GroovyScript` 完成 - **脚本请求封装**:`GroovyScriptRequest` / `GroovyWorkflowRequest` 封装脚本执行所需的参数 ## 如何使用 @@ -75,7 +75,7 @@ ScriptRegistryContext.getInstance().setRegistry(new IScriptRegistry() { ### 脚本执行上下文 -`FlowScriptContext` 承载脚本的 `$bind` 上下文,实现 `IBeanFactory`,供 Groovy 脚本以 `$bind.getBean(...)`、`$bind.getRecordById(...)`、`$bind.getOperatorById(...)` 等方式访问 Spring 容器中的 Bean、流程记录与操作者信息;脚本的实际执行由 `FlowScriptRuntimeContext` 结合 spring-boot 的 `GroovyScript` 完成。 +`FlowScriptContext` 承载脚本的 `$bind` 上下文,内部持有 `IBeanFactory` 字段并委托其实现(具体实现由 starter 的 `FlowScriptContextRegister` 装配),供 Groovy 脚本以 `$bind.getBean(...)`、`$bind.getRecordById(...)`、`$bind.getOperatorById(...)` 等方式访问 Spring 容器中的 Bean、流程记录与操作者信息;脚本的实际执行由 `FlowScriptRuntimeContext` 结合 spring-boot 的 `GroovyScript` 完成。 ## 使用实例 diff --git a/docs/capabilities/flow-engine-framework/sub-process.md b/docs/capabilities/flow-engine-framework/sub-process.md index c70023f8..82b64def 100644 --- a/docs/capabilities/flow-engine-framework/sub-process.md +++ b/docs/capabilities/flow-engine-framework/sub-process.md @@ -89,7 +89,7 @@ def run(request){ ### 接口与定位方式 -- 请求 `FlowSubProcessResetRequest`:`recordId`(当前操作的待办记录)+ `resetInstanceProcessIds`(选中重建的实例流程id)+ `advice`(重置说明)。 +- 请求 `FlowSubProcessResetRequest`:`recordId`(当前操作的待办记录)+ `operatorId`(必填,当前操作人)+ `resetInstanceProcessIds`(选中重建的实例流程id)+ `advice`(重置说明)。 - **不需要指定子流程节点**:由选中实例的流程id定位其所属聚合组(全部选中实例须同属一个未取代聚合组),重置始终是整个子流程**从头重走一次**——重建时重新执行子流程节点配置的创建脚本,按旧实例在聚合组中的创建顺序取对应的 `FlowCreateRequest`,再按创建脚本的自动提交策略提交;不跳转、不迁移、不自动跳过任何历史数据。 - **参数与人员设定由脚本决定**:重置接口不接受表单、发起人、流程标题或人员设定参数,这些均以创建脚本重新执行的输出为准(`FlowCreateRequest.formData` / `operatorId` / `operatorSelectMap` / `workTitle` / `actionId`),与首次发起完全一致;「发起人设定 / 审批人设定」(`INITIATOR_SELECT` / `APPROVER_SELECT`)类节点在重置后仍由脚本指定的人员接收待办。 - **数量一致性校验**:创建脚本返回的创建请求数量必须与旧聚合组实例数一致,否则抛出 `state.subProcess.resetScriptMismatch` 并拒绝重置,避免按错位请求重建、打乱多实例的创建顺序与数据组装。 diff --git a/docs/capabilities/index.md b/docs/capabilities/index.md index 3454ff05..44841d7a 100644 --- a/docs/capabilities/index.md +++ b/docs/capabilities/index.md @@ -9,7 +9,7 @@ | [commons/lang3](./commons/lang3.md) | commons | Apache Commons 工具库,提供字符串、集合、IO 等通用工具方法 | 后端 | 框架:Apache Commons | | [flow-engine-framework/action](./flow-engine-framework/action.md) | flow-engine-framework | 流程动作体系,包含 8 种动作类型、动作接口和动作工厂 | 后端 | 项目自有 | | [flow-engine-framework/delay](./flow-engine-framework/delay.md) | flow-engine-framework | 延迟任务调度能力,支持延迟节点的定时触发、任务持久化与共享调度线程 | 后端 | 项目自有 | -| [flow-engine-framework/exception](./flow-engine-framework/exception.md) | flow-engine-framework | 流程异常体系,包含异常基类和 5 种业务异常子类 | 后端 | 项目自有 | +| [flow-engine-framework/exception](./flow-engine-framework/exception.md) | flow-engine-framework | 流程异常体系,包含异常基类和 6 种业务异常子类 | 后端 | 项目自有 | | [flow-engine-framework/flow-service](./flow-engine-framework/flow-service.md) | flow-engine-framework | 流程服务层,封装流程的创建、审批、撤销、催办等核心业务操作 | 后端 | 项目自有 | | [flow-engine-framework/gateway-context](./flow-engine-framework/gateway-context.md) | flow-engine-framework | 网关上下文,提供操作者网关的注入和线程级缓存 | 后端 | 项目自有 | | [flow-engine-framework/node-manager](./flow-engine-framework/node-manager.md) | flow-engine-framework | 流程节点管理器,负责节点查找、下一节点计算和节点状态管理 | 后端 | 项目自有 | @@ -24,7 +24,7 @@ | [flow-engine-framework/workflow](./flow-engine-framework/workflow.md) | flow-engine-framework | 工作流引擎核心模型,包含流程定义、构建器、版本管理和运行时快照 | 后端 | 项目自有 | | [flow-engine-starter/auto-configuration](./flow-engine-starter/auto-configuration.md) | flow-engine-starter | Spring Boot 自动配置入口,注册流程引擎的核心组件和仓储上下文 | 后端 | 项目自有 | | [lombok/lombok](./lombok/lombok.md) | lombok | Lombok 代码简化工具,通过注解自动生成 getter/setter/builder 等样板代码 | 后端 | 框架:Lombok | -| [springboot/cache](./springboot/cache.md) | springboot | Spring Cache 声明式缓存能力,通过注解简化缓存操作 | 后端 | 框架:Spring Boot | +| [springboot/cache](./springboot/cache.md) | springboot | 手写 LRU 本地缓存能力(LinkedHashCache/WorkflowRuntimeCache),通过 LinkedHashMap accessOrder 实现 | 后端 | 框架:Spring Boot | | [springboot/data-jpa](./springboot/data-jpa.md) | springboot | Spring Data JPA 能力,提供 ORM、Repository 抽象和分页查询 | 后端 | 框架:Spring Boot | | [springboot/ioc](./springboot/ioc.md) | springboot | Spring Framework IoC 容器、依赖注入、AOP 和事件发布 | 后端 | 框架:Spring Boot | | [springboot/web](./springboot/web.md) | springboot | Spring Boot Web 能力,提供 REST API、Controller 和请求处理 | 后端 | 框架:Spring Boot | diff --git a/docs/capabilities/springboot/data-jpa.md b/docs/capabilities/springboot/data-jpa.md index 87c5db5f..19b28cb1 100644 --- a/docs/capabilities/springboot/data-jpa.md +++ b/docs/capabilities/springboot/data-jpa.md @@ -6,7 +6,7 @@ status: 已实现 scope: 后端 source: 框架:Spring Boot import: "com.codingapi.springboot:springboot-starter-data-fast" -framework_version: "由 codingapi.framework.version 17.3.0 管理" +framework_version: "由 codingapi.framework.version 17.3.1 管理" --- ## 解决什么问题