Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DSIP-48][Process] Sub process support other project child node #16162

Open
2 tasks done
yeahhhz opened this issue Jun 17, 2024 · 0 comments · May be fixed by #16138
Open
2 tasks done

[DSIP-48][Process] Sub process support other project child node #16162

yeahhhz opened this issue Jun 17, 2024 · 0 comments · May be fixed by #16138
Assignees
Labels
DSIP feature new feature

Comments

@yeahhhz
Copy link
Contributor

yeahhhz commented Jun 17, 2024

Search before asking

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

Motivation

Currently, the sub-process task node can only select the current project workflow as a child node. We want to enable it to use workflows from different projects, allowing for flexible reuse instead of repeatedly creating definitions. We discovered that this feature can be achieved by simply modifying the frontend code.

Design Detail

add a new form item call child node project in sub process node and save a new field data childNodeProjectCode in task params

Compatibility, Deprecation, and Migration Plan

No response

Test Plan

No response

Code of Conduct

@yeahhhz yeahhhz added DSIP Waiting for reply Waiting for reply labels Jun 17, 2024
@ruanwenjun ruanwenjun removed the Waiting for reply Waiting for reply label Jun 17, 2024
@ruanwenjun ruanwenjun assigned qingwli and yeahhhz and unassigned qingwli Jun 17, 2024
@ruanwenjun ruanwenjun added the feature new feature label Jun 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DSIP feature new feature
3 participants