Commit 23844b930cdafa34edf5f45fd5b911cfb7b65eed
1 parent
42eb89b2
fix: 解决审批节点表单无可编辑字段时,variables流程变量值为空,流程节点流转异常问题
Showing
2 changed files
with
13 additions
and
11 deletions
yudao-module-bpm/yudao-module-bpm-biz/src/main/java/cn/iocoder/yudao/module/bpm/framework/flowable/core/util/BpmnModelUtils.java
| @@ -907,16 +907,9 @@ public class BpmnModelUtils { | @@ -907,16 +907,9 @@ public class BpmnModelUtils { | ||
| 907 | * @return 符合条件的路径 | 907 | * @return 符合条件的路径 |
| 908 | */ | 908 | */ |
| 909 | private static SequenceFlow findMatchSequenceFlowByExclusiveGateway(Gateway gateway, Map<String, Object> variables) { | 909 | private static SequenceFlow findMatchSequenceFlowByExclusiveGateway(Gateway gateway, Map<String, Object> variables) { |
| 910 | - // TODO 表单无可编辑字段时variables为空,流程走向会出现问题,比如流程审批过程中无需要修改的字段值, | ||
| 911 | - SequenceFlow matchSequenceFlow; | ||
| 912 | - if (CollUtil.isNotEmpty(variables)){ | ||
| 913 | - matchSequenceFlow = CollUtil.findOne(gateway.getOutgoingFlows(), | 910 | + SequenceFlow matchSequenceFlow = CollUtil.findOne(gateway.getOutgoingFlows(), |
| 914 | flow -> ObjUtil.notEqual(gateway.getDefaultFlow(), flow.getId()) | 911 | flow -> ObjUtil.notEqual(gateway.getDefaultFlow(), flow.getId()) |
| 915 | && (evalConditionExpress(variables, flow.getConditionExpression()))); | 912 | && (evalConditionExpress(variables, flow.getConditionExpression()))); |
| 916 | - }else { | ||
| 917 | - matchSequenceFlow = CollUtil.findOne(gateway.getOutgoingFlows(), | ||
| 918 | - flow -> ObjUtil.notEqual(gateway.getDefaultFlow(), flow.getId())); | ||
| 919 | - } | ||
| 920 | if (matchSequenceFlow == null) { | 913 | if (matchSequenceFlow == null) { |
| 921 | matchSequenceFlow = CollUtil.findOne(gateway.getOutgoingFlows(), | 914 | matchSequenceFlow = CollUtil.findOne(gateway.getOutgoingFlows(), |
| 922 | flow -> ObjUtil.equal(gateway.getDefaultFlow(), flow.getId())); | 915 | flow -> ObjUtil.equal(gateway.getDefaultFlow(), flow.getId())); |
yudao-module-bpm/yudao-module-bpm-biz/src/main/java/cn/iocoder/yudao/module/bpm/service/task/BpmTaskServiceImpl.java
| @@ -558,12 +558,21 @@ public class BpmTaskServiceImpl implements BpmTaskService { | @@ -558,12 +558,21 @@ public class BpmTaskServiceImpl implements BpmTaskService { | ||
| 558 | taskService.addComment(task.getId(), task.getProcessInstanceId(), BpmCommentTypeEnum.APPROVE.getType(), | 558 | taskService.addComment(task.getId(), task.getProcessInstanceId(), BpmCommentTypeEnum.APPROVE.getType(), |
| 559 | BpmCommentTypeEnum.APPROVE.formatComment(reqVO.getReason())); | 559 | BpmCommentTypeEnum.APPROVE.formatComment(reqVO.getReason())); |
| 560 | // 2.3 调用 BPM complete 去完成任务 | 560 | // 2.3 调用 BPM complete 去完成任务 |
| 561 | + // 如果流程变量前端传空,需要从历史实例中获取,原因:前端表单如果在当前节点无可编辑的字段时variables一定会为空 | ||
| 562 | + // 场景一:A节点发起,B节点表单无可编辑字段,审批通过时,C节点需要流程变量获取下一个执行节点,但因为B节点无可编辑的字段,variables为空,流程可能出现问题 | ||
| 563 | + // 场景二:A节点发起,B节点只有某一个字段可编辑(比如day),但C节点需要多个节点(比如workday,在发起时填写,因为B节点只有day的编辑权限,在审批后。variables会缺少work的值) | ||
| 564 | + // 历史中的变量值 | ||
| 565 | + Map<String, Object> variables = new HashMap<>(instance.getProcessVariables()); | ||
| 566 | + // 如果变量值不为空,则覆盖历史变量 | ||
| 567 | + if (CollUtil.isNotEmpty(reqVO.getVariables())) { | ||
| 568 | + variables.putAll(reqVO.getVariables()); | ||
| 569 | + } | ||
| 561 | // 校验并处理 APPROVE_USER_SELECT 当前审批人,选择下一节点审批人的逻辑 | 570 | // 校验并处理 APPROVE_USER_SELECT 当前审批人,选择下一节点审批人的逻辑 |
| 562 | - Map<String, Object> variables = validateAndSetNextAssignees(task.getTaskDefinitionKey(), reqVO.getVariables(), | 571 | + Map<String, Object> resVariables = validateAndSetNextAssignees(task.getTaskDefinitionKey(), variables, |
| 563 | bpmnModel, reqVO.getNextAssignees(), instance); | 572 | bpmnModel, reqVO.getNextAssignees(), instance); |
| 564 | // 完成任务 | 573 | // 完成任务 |
| 565 | - runtimeService.setVariables(task.getProcessInstanceId(), variables); | ||
| 566 | - taskService.complete(task.getId(), variables, true); | 574 | + runtimeService.setVariables(task.getProcessInstanceId(), resVariables); |
| 575 | + taskService.complete(task.getId(), resVariables, true); | ||
| 567 | 576 | ||
| 568 | // 【加签专属】处理加签任务 | 577 | // 【加签专属】处理加签任务 |
| 569 | handleParentTaskIfSign(task.getParentTaskId()); | 578 | handleParentTaskIfSign(task.getParentTaskId()); |