Comments (5)

  1. Notre says:

    Hi Tim,

    I like the idea of a group of activities with a private implementation.  What I'd be most interested in is doing is something like this, but in a Flowchart model.  In particular, I would like to string together a custom activity with a FlowSwitch or FlowDecision.  The problem that I can't get over is how to do this from the designer perspective, given that the FlowSwitch and FlowDecision are the only node types that allow more than one ouput path (and the whole reason I use FlowSwitch and FlowDecision to begin with).

    Could the principles of this blog mini-series be applied to the scenario I just described, somehow?


  2. Quintonn says:

    From your code I was able to solve a similar problem, thank you SOOOOO much

  3. tilovell09 says:

    Hi Notre,

    I guess you are asking either for a way to take an activity, which generates a value, on the flowchart, and a flowswitch or flow decision, from the same flowchart, and merge them into one blob – from the point of view of someone viewing the flowchart.

    I don't think the approach in this blog will help you achieve that, it is really only applicable to activities and FlowSwitch and FlowDecision are not activities.

    One thing that could resemble what you are asking in terms of appearance/behavior would be to embedding the value-generating activity inside of the expression in the FlowChart/FlowDecision – you can do it from xaml, but unfortunately there is no way to do this using the built-in expression editor UI.


  4. says:


    I have custom activity that schedules a Receive / SendReply activities along with other work that happens prior to and after the Recieve is executed.  I can't seem to get it to respect the WF instance correlation created by a built-in Receive activity that created the correlation handle for the WF instance.  I'm getting the error:

    The execution of an InstancePersistenceCommand was interrupted because the instance key '12046dfc-8594-015f-430a-921927710e48' was not associated to an instance. This can occur because the instance or key has been cleaned up, or because the key is invalid. The key may be invalid if the message it was generated from was sent at the wrong time or contained incorrect correlation data.

    Looking at your example, I see you're creating a WF instance in your Receive activity whereas I'm trying to use an existing one that is saved as WF instance variable scoped to the WF service.  My Receive accepts parameters content that passes in the WF instance correlation id used in the instance correlation handle.  Can you help me with how to setup the Receive CorrelatesWith and CorrelatesOn properties?


  5. louisila says:

    I can't seem to find part 2..?..  Is the link broken?

Skip to main content