[Bug] [Master] When using the complement function, turn on the dependent mode to generate multiple unrelated workflow instances

[zhuangchong]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

When using the complement function, turn on the dependent mode to generate multiple unrelated workflow instances.

I found that the definitionCodeOptions data is included in the parameters of the dependent task node in the database, causing problems for tasks that depend on this workflow definition downstream of the query

What you expected to happen

Use the complement function to open the dependency model and generate downstream workflow instances that depend on this workflow definition.

How to reproduce

In a workflow definition with dependent tasks, click the dependent task node, select different workflows for different projects in the original dependency relationship, and click Cancel. Then click Save to view and update the workflow definition interface input parameter contains definitionCodeOptions data

Anything else

No response

Version

3.1.x

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[github-actions]

Thank you for your feedback, we have received your issue, Please wait patiently for a reply.

• In order for us to understand your request as soon as possible, please provide detailed information、version or pictures.
• If you haven't received a reply for a long time, you can join our slack and send your question to channel #troubleshooting