feat(data_export): add workflow support for data export #784

[LordofAvernus]

User description

Summary

• Add AuditWorkflowAndAdvanceStep to WorkflowRepo for data export workflow audit operations
• Add bounds check for CurrentWorkflowStepId in list endpoints to prevent index out of range
• Show workflow creator as pending operator in wait_for_export status
• Fix ProxyTarget version column size to 512

Related: https://github.com/actiontech/dms-ee/issues/784

---

Description

• 新增 "AuditWorkflowAndAdvanceStep" 接口实现

• 修改数据导出工作流中待操作人显示逻辑

• 扩大 "ProxyTarget" 版本字段长度到 512

• 优化事务处理与错误反馈

---

Diagram Walkthrough

flowchart LR
  A["\"WorkflowRepo接口更新\""] --> B["\"待操作人状态判断修改\""]
  B --> C["\"ProxyTarget版本字段扩展\""]
  A --> D["\"新增审批流程原子更新实现\""]

Loading

File Walkthrough

	Relevant files
Enhancement	data_export_workflow.go 新增审批流程原子更新接口                                                                                          internal/dms/biz/data_export_workflow.go 添加 AuditWorkflowAndAdvanceStep 方法定义 +1/-0      workflow.go 添加事务处理的审批更新实现                                                                                        internal/dms/storage/workflow.go 添加 AuditWorkflowAndAdvanceStep 方法实现 封装事务内更新流程步骤状态与推进 +18/-0
Bug fix	data_export_workflow.go 优化待操作人状态显示逻辑                                                                                          internal/dms/service/data_export_workflow.go 修改待操作人显示条件 增加 wait_for_export 状态判断逻辑 +10/-2    model.go 更新ProxyTarget版本字段长度                                                                            internal/dms/storage/model/model.go 将 ProxyTarget 版本字段长度由64改为512 +1/-1

---

[github-actions]

PR Reviewer Guide 🔍

⏱️ Estimated effort to review: 3 🔵🔵🔵⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No major issues detected

[github-actions]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	添加 nil 检查 建议在使用 step 前先判断是否为 nil，以避免由于传入 nil 导致运行时 panic。这样可以确保在后续使用 step.State、step.StepId 等属性时有有效值。 internal/dms/storage/workflow.go [288-304] func (d *WorkflowRepo) AuditWorkflowAndAdvanceStep(ctx context.Context, workflowRecordUid string, step *biz.WorkflowStep, nextStepId uint64, operateId, reason string) error { + if step == nil { + return fmt.Errorf("invalid step: step is nil") + } return transaction(d.log, ctx, d.db, func(tx *gorm.DB) error { // update current step state operateTime := time.Now() fields := map[string]interface{}{"operation_user_uid": operateId, "operate_at": operateTime, "reason": reason, "state": step.State} if err := tx.WithContext(ctx).Model(&model.WorkflowStep{}).Where("step_id = ? and workflow_record_uid = ?", step.StepId, step.WorkflowRecordUid).Updates(fields).Error; err != nil { return fmt.Errorf("failed to update current workflow step, err: %v", err) } // advance CurrentWorkflowStepId to next step if err := tx.WithContext(ctx).Model(&model.WorkflowRecord{}).Where("uid = ?", workflowRecordUid).Update("current_workflow_step_id", nextStepId).Error; err != nil { return fmt.Errorf("failed to advance workflow step, err: %v", err) } return nil }) } Suggestion importance[1-10]: 7 __ Why: The suggestion correctly adds a nil check for step to prevent runtime panics and improve error handling, addressing a potential edge case. However, as this is a defensive programming addition and related to error checking, the impact is moderate.	Medium