WF Instance Reuse

Hello all,

I'm developing a workflow that will take data from a list item and
send it to two different external sources (Active Directory and
Exchange). I'm developing two custom activities, one for each data
source. Right now, they simply get the list item from
workflowProperties and process it. However, I've seen in multiple
places that if an instance of the workflow is already running when a
new instance is started, SharePoint will reuse the old workflow
instance's objects.

This is very confusing to me. If SharePoint reuses the Workflow
object and all of its activities, doesn't that mean I can't use any
instance variables? Do correlation tokens come into this at all?

Any information helps.

Thanks,
--Kyle Sluder

Mike
Thu Jul 24 02:32:49 CDT 2008

It sounds as if this is a VS workflow.

If so post it to the Programming newsgroup .development_and_programming.

(Although probably best would be the SharePoint - Workflow *forum* here

http://forums.technet.microsoft.com/en-US/sharepointworkflow/threads/ )

Mike Walsh
WSS FAQ http://www.wssfaq.com / http://wss.collutions.com
no questions by e-mail please



Kyle wrote:
> Hello all,
>
> I'm developing a workflow that will take data from a list item and
> send it to two different external sources (Active Directory and
> Exchange). I'm developing two custom activities, one for each data
> source. Right now, they simply get the list item from
> workflowProperties and process it. However, I've seen in multiple
> places that if an instance of the workflow is already running when a
> new instance is started, SharePoint will reuse the old workflow
> instance's objects.
>
> This is very confusing to me. If SharePoint reuses the Workflow
> object and all of its activities, doesn't that mean I can't use any
> instance variables? Do correlation tokens come into this at all?
>
> Any information helps.
>
> Thanks,
> --Kyle Sluder

Kyle
Thu Jul 24 10:11:19 CDT 2008

On Jul 24, 3:32=A0am, Mike Walsh <englantilai...@hotmail.com> wrote:
> It sounds as if this is a VS workflow.

Yep, it is. Thanks for the 302.

--Kyle Sluder