(WF4) Workflow 4.0 Hosting Extensions

re: (WF4) Workflow 4.0 Hosting Extensions

tilovell09 — Thu, 10 Mar 2011 19:47:33 GMT

Hi Sanjay,

All I can say is maybe - Execution Properties might work pretty well for that. But it depends. I'd suggest actually trying it out. It's not very hard, and there's no better way to understand the 'it depends' part.

Tim

re: (WF4) Workflow 4.0 Hosting Extensions

SanjayS — Fri, 04 Mar 2011 23:10:36 GMT

Hello Tim,

I have a native activity which schedule bunch of coded activities. There are few arguments common to those which I am finding it hard to wireup. Is there a better way to pass info across scheduled activities without using arguments? Would you recommend Execution properties or Persistence participant? Thanks in advance.

re: (WF4) Workflow 4.0 Hosting Extensions

tilovell09 — Wed, 01 Sep 2010 17:36:49 GMT

Hi Andrew,

You're right that you can use persistence particpant to get extra information back from the workflow to the outside world. But guess what, in the samples I have seen so far, persistence participants are extensions too, which is why I have the link to that sample.

Tim

re: (WF4) Workflow 4.0 Hosting Extensions

Andrew Zhu — Wed, 01 Sep 2010 08:35:43 GMT

Hi, tim

->"So, the question is basically “How can I get extra information back from the workflow to the outside world (the host)?”"

I think we can use persistence participant to achieve this. We can also promote data if we use SqlWorkflowInstanceStore.

->"A second problem you might also see is the same problem but in the opposite direction: “How can I get extra information from outside world (in particular, the workflow host) into my activity, mid-execution of the activity?"

If a workflow instance needs some extera data from outside world, we can use the built-in. InvokeMethod activity. if the out side world has any data send into workflow instance, we can use bookmark.