For workspaces in basic mode under the same Alibaba Cloud account, you can use the cross-workspace cloning feature to isolate the development environment from the production environment. You can also use this feature to clone and migrate nodes, such as computing or sync nodes, between workspaces. This topic describes how to process the dependencies between nodes during cross-workspace cloning.

If you clone nodes across workspaces by using the cross-workspace cloning feature, DataWorks automatically modifies output names in the destination workspace to distinguish nodes in different workspaces under the same Alibaba Cloud account. This allows you to successfully clone node dependencies.
Note
  • Cross-workspace cloning cannot be used to clone nodes across workspaces in different regions.
  • Currently, you cannot directly clone nodes in a workflow of earlier versions to a workspace in the latest version. To clone nodes in a workflow of earlier versions to the destination workspace, migrate the nodes to a folder under Business Flow and then clone the entire workflow to the destination workspace.
You can set the owner of cloned nodes in the destination workspace to Default or Clone Task Creator.
  • If the owner of the nodes to be cloned are the workspace administrator, you can set the owner of the cloned nodes in the destination workspace to Default or Clone Task Creator when creating the clone task.

    After the nodes are cloned to the destination workspace, their owner is set to the original owner preferentially. If the original owner is not added to the destination workspace, the clone task creator will become the owner.

  • If you, the clone task creator, are the owner of the nodes to be cloned, you can set the owner of the cloned nodes in the destination workspace to Default or Clone Task Creator when creating the clone task.

    After the nodes are cloned to the destination workspace, their owner is set to you preferentially. If you are not added to the destination workspace, you are asked whether to change the owner. If you agree to change the owner, you will become the owner of the cloned nodes. If you do not agree to change the owner, the clone task is canceled.

Clone a workflow

Assume that the output of the task_A node in the Project_1 workspace is project_1.task_1_out. If you clone a workflow that contains the task_A node to the destination workspace Project_2, the node output name changes to project_2.task_A_out in the destination workspace.Process

Clone node dependencies

Assume that the task_ B node in the Project_1 workspace depends on the task_A node in the Project_3 workspace. If you clone the task_B node in the Project_1 workspace to the destination workspace Project_2, the dependency between the task_A and task_B nodes is also cloned. The task_B node in the Project_2 workspace also depends on the task_A node in the Project_3 workspace.Cross-workspace dependency