Customize an Installed Workflow

Learn what you can change in a Workflow installed from the Harness IDP Workflow Library, and how the clone and own model affects your edits.

A Workflow installed from the library is a full copy in your own scope, not a live reference to the library item. Nothing in your installed Workflow points back after the install finishes, so you can change any part of it without waiting for a library update.

---

What you can change

Everything. An installed Workflow is an ordinary Harness IDP Workflow, and its backing pipeline is an ordinary Harness Pipeline. You can:

• Add, remove, or reorder parameters on the developer-facing form.

• Split the form across pages, or merge existing pages.

• Swap any connector for a different one.

• Add, remove, or reorder steps and stages in the backing pipeline.

• Change the infrastructure the backing pipeline runs on.

• Change the output links and text developers see when the Workflow finishes.

• Rename the Workflow, change its description, or move it to a different scope.

Go to Understanding Workflow YAML for the full YAML reference, and to Configuring Workflow Inputs for the available input field types.

Go to Managing Workflows in Harness IDP to learn how to edit and manage Workflows.

---

How your changes interact with library updates

Your installed copy is independent of the library item it came from.

• If Harness publishes a newer version of the library item, your installed Workflow keeps running the version you installed. It does not change and it does not break.

• There is no in-product path to merge a newer library version into an installed copy, and no view that compares the two. To pick up a newer version, install it as a separate Workflow and carry your customizations across manually.

• Your edits are never overwritten by the library.