Saving workflows as templates allows you to conveniently open a saved workflow and make changes to it. If you have Workflow Conductor 2.0 or higher configured to use the Simple Publishing method, simply publish the workflow with the same name. You will be prompted to overwrite the existing version. Workflow instances already running will continue to run under the old version, and new workflow instances will automatically run with the new version.
If you have Workflow Conductor 1.6.1 or earlier or Workflow Conductor 2.0 or higher configured to use the Solution Deployment method, you cannot deploy another workflow with the same name to the same Web application. To deploy a new version of a workflow, you can either deploy it with a different name and remove the previous version from the list, or you can retract and remove the previous version from the Web application before deploying the updated version with the same name.
After you deploy a Workflow Conductor workflow solution, you may want to make a minor change to it and deploy a new version. However, once a workflow solution is deployed to a web application, you cannot deploy another workflow with the same name to the same web application. The Solution Deployment method deploys workflows as farm solutions. To deploy a new version of a workflow, you have two options:
- Give the workflow a new name when deploying it in Conductor Studio.
- Retract and remove the workflow from the web application
See Detailed Instructions for Retracting and Removing the Existing Workflow from the Web Application.
NOTE: Solution Deployment workflows can overwrite Simple Publishing workflows of the same name directly from Conductor Studio. You do not need to remove the existing published workflow before deploying the new workflow solution.