Using Workflow Changes in Workflows
Workflow changes let you make changes at run time to a running instance of a workflow. These changes might be motivated by omissions at design time, changes to properties and bindings of activities, or a need for business logic that enhances and more completely models business processes. Workflow changes are not intended for situations in which you want to make wholesale changes, resulting in a workflow that differs significantly from original design principles. In a case such as this, you should design a new workflow instead of making changes to a running instance.
Workflow changes apply to a single instance of a workflow. They do not support type-based changes that replicate to all running and future instances of a given workflow type.
You can use workflow changes to do the following:
Change a running workflow instance.
Change run-time behavior.
Change workflow structure, for example, add or remove an activity.
Change flow control.
Add a new custom activity or an InvokeWorkflowActivity activity if you have to add a new business process to your workflow after you deploy and start running it.
Author changes declaratively using workflow markup from outside the workflow, taking updated markup as a parameter to make the change.
Add a new EventDrivenActivity activity to respond to a new event, such as an additional approval step.
Applying a workflow change to a running workflow can occur in two different entry points: in the workflow code file, and outside the workflow, such as the workflow host. For more information about applying workflow changes, see How to: Apply Workflow Changes to Workflows.
Send comments about this topic to Microsoft.