1. 环境准备与版本兼容性检查在开始整合之前我们需要先确认几个关键点。若依分离版是基于SpringBoot的前后端分离架构而Activiti7作为新一代工作流引擎两者整合最需要注意的就是版本兼容性。我去年在金融项目里就遇到过因为版本不匹配导致的启动报错排查了整整两天才发现是SpringBoot版本过高的问题。目前经过实测最稳定的组合是若依分离版基于SpringBoot 2.5.x版本Activiti7使用7.1.0.M6版本JDK建议1.8虽然支持11但会有更多依赖冲突这里有个小技巧在pom.xml里先不要急着加依赖先用mvn dependency:tree命令查看现有项目的依赖树。我遇到过若依自带的security版本和Activiti7冲突的情况这时候就需要在dependencyManagement里做版本锁定。比如dependencyManagement dependencies dependency groupIdorg.springframework.security/groupId artifactIdspring-security-bom/artifactId version5.6.3/version typepom/type scopeimport/scope /dependency /dependencies /dependencyManagement2. 数据库配置与表结构初始化Activiti7默认会创建28张表比老版本多了3张这些表主要分为5大类ACT_RE_*存储流程定义和静态资源ACT_RU_*运行时流程实例数据ACT_HI_*历史流程数据ACT_GE_*通用数据如二进制资源ACT_ID_*身份认证相关配置时最容易踩的坑是历史记录开关。很多同学发现流程跑完了查不到历史就是因为没开这个配置。在application.yml里要特别注意这几个参数spring: activiti: database-schema-update: true db-history-used: true history-level: full check-process-definitions: false特别提醒如果用的是MySQL 8.0记得在连接串里加上nullCatalogMeansCurrenttrue参数否则初始化时会报表不存在错误。我在某次项目上线前夜就被这个坑过血泪教训啊3. 安全框架无缝集成方案若依分离版已经集成了SpringSecurity而Activiti7也自带Security集成这就可能造成冲突。经过多次实践我发现最优雅的解决方案是排除Activiti自带的Security依赖dependency groupIdorg.activiti/groupId artifactIdactiviti-spring-boot-starter/artifactId version7.1.0.M6/version exclusions exclusion groupIdorg.springframework.security/groupId artifactIdspring-security-core/artifactId /exclusion /exclusions /dependency实现Activiti的IdentityService接口Service public class CustomIdentityService implements IdentityService { Autowired private SysUserService userService; Override public User newUser(String userId) { SysUser sysUser userService.selectUserById(userId); User user new UserEntity(); user.setId(sysUser.getUserId().toString()); user.setFirstName(sysUser.getUserName()); return user; } // 其他接口实现... }配置自定义用户组查询Configuration public class ActivitiConfig { Bean public SpringProcessEngineConfiguration processEngineConfiguration( DataSource dataSource, PlatformTransactionManager transactionManager, CustomIdentityService identityService) { SpringProcessEngineConfiguration config new SpringProcessEngineConfiguration(); config.setDataSource(dataSource); config.setTransactionManager(transactionManager); config.setDatabaseSchemaUpdate(true); config.setIdentityService(identityService); return config; } }4. 请假审批实战案例现在我们来做个完整的请假审批流程。首先准备BPMN文件建议使用Eclipse的Activiti插件绘制!-- leave-request.bpmn -- process idleaveProcess name请假流程 startEvent idstart/ userTask idapply name提交申请 activiti:assignee${applicant}/ userTask idmanagerApprove name经理审批 activiti:candidateGroupsdeptManager/ exclusiveGateway iddecision/ sequenceFlow sourceRefstart targetRefapply/ sequenceFlow sourceRefapply targetRefmanagerApprove/ !-- 其他节点和连线 -- /process部署流程的Service层实现Service public class ProcessServiceImpl implements ProcessService { Autowired private RepositoryService repositoryService; public String deployProcess(String processName) { Deployment deployment repositoryService.createDeployment() .name(processName -部署) .addClasspathResource(processes/ processName .bpmn) .addClasspathResource(processes/ processName .png) .deploy(); return deployment.getId(); } public ProcessInstance startProcess(String processKey, String businessKey, MapString, Object variables) { return runtimeService.startProcessInstanceByKey( processKey, businessKey, variables); } }前端调用示例Vue3TypeScriptconst startLeaveProcess async () { const { data } await axios.post(/activiti/process/start, { processKey: leaveProcess, businessKey: LEAVE_ Date.now(), variables: { applicant: store.state.user.id, days: formData.days, reason: formData.reason } }); if (data.code 200) { ElMessage.success(流程启动成功); } };5. 流程监控与任务处理整合后最重要的就是任务列表展示和处理。我推荐两种方案方案一扩展若依原有任务表ALTER TABLE sys_task ADD COLUMN process_instance_id VARCHAR(64), ADD COLUMN task_id VARCHAR(64), ADD COLUMN process_definition_id VARCHAR(64);方案二单独开发任务中心GetMapping(/task/list) public TableDataInfo taskList(ActivitiTaskVO taskVO) { startPage(); ListTask tasks taskService.createTaskQuery() .taskCandidateOrAssigned(taskVO.getUserId()) .processDefinitionKey(taskVO.getProcessKey()) .listPage(taskVO.getPageNum(), taskVO.getPageSize()); return getDataTable(tasks.stream() .map(t - new ActivitiTaskDTO(t)) .collect(Collectors.toList())); }任务处理的核心代码Transactional public void completeTask(String taskId, MapString, Object variables) { // 业务校验 Task task taskService.createTaskQuery() .taskId(taskId).singleResult(); if (task null) { throw new RuntimeException(任务不存在或已完成); } // 业务处理如更新请假状态 String businessKey runtimeService.createProcessInstanceQuery() .processInstanceId(task.getProcessInstanceId()) .singleResult().getBusinessKey(); updateBusinessStatus(businessKey); // 完成任务 taskService.complete(taskId, variables); }6. 高级功能扩展对于企业级应用还需要考虑以下增强功能1. 会签实现userTask idjointSign name部门会签 multiInstanceLoopCharacteristics activiti:collection${signUsers} activiti:elementVariablesignUser completionCondition${nrOfCompletedInstances/nrOfInstances 0.6}/completionCondition /multiInstanceLoopCharacteristics /userTask2. 动态审批人配置Service public class DynamicAssigneeService implements TaskListener { Override public void notify(DelegateTask task) { String processKey task.getProcessDefinitionId() .split(:)[0]; String taskKey task.getTaskDefinitionKey(); // 从数据库读取配置 ListString assignees assigneeConfigService .getAssignees(processKey, taskKey); if (assignees.size() 1) { task.setAssignee(assignees.get(0)); } else { task.addCandidateUsers(assignees); } } }3. 流程版本控制public void rollbackProcess(String processDefinitionId) { // 1. 终止当前所有实例 ListProcessInstance instances runtimeService .createProcessInstanceQuery() .processDefinitionId(processDefinitionId) .list(); instances.forEach(instance - runtimeService.deleteProcessInstance( instance.getId(), 版本回滚)); // 2. 激活上一版本 ProcessDefinition currentDef repositoryService .createProcessDefinitionQuery() .processDefinitionId(processDefinitionId) .singleResult(); ProcessDefinition previousDef repositoryService .createProcessDefinitionQuery() .processDefinitionKey(currentDef.getKey()) .processDefinitionVersion(currentDef.getVersion() - 1) .singleResult(); repositoryService.activateProcessDefinitionById( previousDef.getId(), true, null); }7. 性能优化建议在大规模使用时我总结了几条优化经验历史数据归档定期将ACT_HI_*表数据归档到历史表CREATE TABLE ACT_HI_TASK_ARCHIVE LIKE ACT_HI_TASK; -- 每月执行一次 INSERT INTO ACT_HI_TASK_ARCHIVE SELECT * FROM ACT_HI_TASK WHERE END_TIME_ DATE_SUB(NOW(), INTERVAL 3 MONTH); DELETE FROM ACT_HI_TASK WHERE END_TIME_ DATE_SUB(NOW(), INTERVAL 3 MONTH);启用异步执行器spring: activiti: async-executor-activate: true async-executor-thread-pool-size: 10缓存配置Bean public ProcessEngineConfigurationImpl processEngineConfiguration( DataSource dataSource, TransactionManager transactionManager) { SpringProcessEngineConfiguration config ...; config.setProcessDefinitionCacheLimit(100); config.setProcessDefinitionInfoCacheLimit(50); config.setEnableProcessDefinitionInfoCache(true); return config; }批量操作优化// 不好的写法 tasks.forEach(task - taskService.complete(task.getId())); // 优化后的写法 ListString taskIds tasks.stream() .map(Task::getId) .collect(Collectors.toList()); taskService.completeTasks(taskIds);