Hi, I have built a custom workflow activity and used it in many workflows and MPRs. This is already deployed in live environment. Now, I need to modify the custom activity to -add a new text box in the activity screen and -modify the activity logic I will modify the same activity and built it. My question is "if I modify the same activity, will the already created Workflows automatically refer to the updated activity? or will I be needed to remove the previous activity from them and again include in the workflow"? Also, what will happen to the saved configurations of the activity/ workflows e.g Email templates, approver's name etcMayank Vaish

The saved configurations will remain intact, but you may need to edit all workflows and set a value for the new textbox (unless you intend this to be an optional property and the new logic won't throw an exception if you don't supply a value in the workflow config). So long as you don't change anything else in the activity UI you will retain backwards compatibility (i.e. just "modifying the logic" should not break anything so long as you're careful).Bob Bradley (FIMBob @ http://thefimteam.com/) ... now using Event Broker 3.0 @ http://www.fimeventbroker.com/ for just-in-time delivery of FIM 2010 policy via the sync engine

You'll also want to make sure you don't change the version (unless you use an assembly binding redirect) or sign the assembly with a different key. And as Bob mentioned, hopefully your new Dependency Attribute is optional, else you'll need to go back and add it into your existing workflows. Otherwise you're good...Frank C. Drewes III - Architect - Oxford Computer Group

One more thing - make sure you don't assume the new field (textbox) will be populated, or the existing workflows using this activity will start failing when they throw exceptions.My Book - Active Directory, 4th Edition My Blog - www.briandesmond.com