Versions Compared

Old Version 12

changes.mady.by.user John Brinckwirth

Saved on

compared with

New Version 13

changes.mady.by.user John Brinckwirth

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

You can copy a Pipeline to add it to another Project or to modify without impacting the original Pipeline. For a Pipeline that you copy to another Project, follow these best practices for referenced Assets:

  • If the Pipeline has one or more child Pipelines, copy them to the same Project.
  • If the Pipeline contains references to other Pipelines, Files, Accounts, or Tasks (which can be called from a Snap), handle them as follows:
    • Leave references to Assets in the global shared folder.
    • For Assets in a Project other than the destination Project:
      • If the reference to a File is an absolute path, do not change it.
      • If the Asset is available in the destination Project, change the reference to point to the destination project after copying the Pipeline.
      • If the destination Project does not have an Asset with the same label, but one exists in its shared folder or the global shared folder, change the reference to the appropriate location after copying the Pipeline.
      • If the Asset has a different label in the destination Project, change the reference before moving the Pipeline.


Excerpt

To copy a Pipeline:

  • In Designer, open the Pipeline to copy, and click the toolbar Copy Pipeline button ().
  • In Manager, select the checkbox next to the name of the Pipeline to copy, and click the toolbar Copy () button.

A dialog prompts you to select the project Project in which to put the Pipeline. You can filter the destination list by entering the first letters of a Project name in the text box. If a Pipeline with the same name exists in that Project, you will be asked if you want to overwrite it.

...