DataSphereStudio is a one stop data application development& management portal, covering scenarios including data exchange, desensitization/cleansing, analysis/mining, quality measurement, visualization, and task scheduling.
[X] I had searched in the issues and found no similar feature requirement.
Problem Description
There are many nodes in some workflows, and when there is a need to split a workflow or migrate a workflow (with the aim of splitting the project), it is necessary to copy the original workflow.
Description
The first phase only supports workflow replication within the same project. Supporting cross project workflow replication requires third-party appconn to implement a new node copy specification, which will be implemented in the second phase.
When a user has edit or publish permissions for the project to which the workflow belongs, add the "Copy Workflow" option in the workflow settings
When the user copies the workflow, there is a pop-up window as shown in the following figure
Add replication history (copying in progress, copying successful, copying failed)
Select the copied workflow (automatic filling, user cannot modify): The front-end automatically fills in the name of the selected workflow (user modification is not allowed, and the workflow name is displayed for confirmation only);
Copy to Project (required): The user selects which project they want to copy the workflow into, and provides them with a dropdown box for selection. The items displayed in the dropdown list are those that the user has publish or edit permissions for;
Copy workflow name (required): defaults to "original workflow name" and allows users to customize and modify the name;
Copy workflow node name suffix (optional): All nodes of the copied workflow will automatically add this suffix name, such as the workflow node name sql0233. If the user fills in copy in this item, the copied workflow node name will be sql0233_ copy;
The newly added workflow pop-up window is as follows:
To prompt users about the issue of duplicate workflow node names, the following prompt has been added. When the mouse is moved to the prompt icon on the right, the corresponding prompt floating window will be displayed
Click OK to start copying the project
Pay attention to the following points when copying:
When copying workflows, it is necessary to copy resource files
2.When copying workflow A to workflow B, if the copying is not completed, it is not allowed to copy workflow A to workflow C. If the user wants to drag a node or perform any operation, the following prompt will be given
3.When workflow A is copied to workflow B, workflow A cannot be edited (can only be opened, cannot be edited or saved), and workflow B cannot be opened. Users clicking on workflow B will receive the following prompt
a) On successful replication
The user refreshes the page and clicks on Copy History. If the status is Successful and there are no errors, it means the copy was successful.
b) When replication fails
Error messages with a status of Failed and workflow replication failure in the replication history:
Copy History View
Add the 'Copy History' tab on the toolbar
The copy history includes the following columns: see the return value in the attachment Interface Software design description for details
zqburde
commented
1 year ago
Search before asking
Problem Description
There are many nodes in some workflows, and when there is a need to split a workflow or migrate a workflow (with the aim of splitting the project), it is necessary to copy the original workflow.
Description
The first phase only supports workflow replication within the same project. Supporting cross project workflow replication requires third-party appconn to implement a new node copy specification, which will be implemented in the second phase.
When a user has edit or publish permissions for the project to which the workflow belongs, add the "Copy Workflow" option in the workflow settings
When the user copies the workflow, there is a pop-up window as shown in the following figure Add replication history (copying in progress, copying successful, copying failed)
Select the copied workflow (automatic filling, user cannot modify): The front-end automatically fills in the name of the selected workflow (user modification is not allowed, and the workflow name is displayed for confirmation only); Copy to Project (required): The user selects which project they want to copy the workflow into, and provides them with a dropdown box for selection. The items displayed in the dropdown list are those that the user has publish or edit permissions for; Copy workflow name (required): defaults to "original workflow name" and allows users to customize and modify the name; Copy workflow node name suffix (optional): All nodes of the copied workflow will automatically add this suffix name, such as the workflow node name sql0233. If the user fills in copy in this item, the copied workflow node name will be sql0233_ copy; The newly added workflow pop-up window is as follows:
To prompt users about the issue of duplicate workflow node names, the following prompt has been added. When the mouse is moved to the prompt icon on the right, the corresponding prompt floating window will be displayed
Pay attention to the following points when copying:
3.When workflow A is copied to workflow B, workflow A cannot be edited (can only be opened, cannot be edited or saved), and workflow B cannot be opened. Users clicking on workflow B will receive the following prompt
a) On successful replication The user refreshes the page and clicks on Copy History. If the status is Successful and there are no errors, it means the copy was successful.
b) When replication fails Error messages with a status of Failed and workflow replication failure in the replication history:
Copy History View Add the 'Copy History' tab on the toolbar The copy history includes the following columns: see the return value in the attachment Interface Software design description for details
Use case
No response
solutions
New Interface:
Anything else
No response
Are you willing to submit a PR?