I'm using nested conversations for a wizard-like creation of objects and sub-objects, similar to the "issues" example. This works great so far.
However, I can't figure how to raise events from a Conversation and let it find it's way up the conversation stack.
Why do I need this? I want to update the @DataModel in the master-view while changing childs in the details view. Thanks to the nested conversations, users may have different workspaces like this:
edit master (Conversation ID A) -------- edit child 1 (Conversation ID B) \-------- edit child 2 (...) \-------- ....
we are suffering from the same troubles.
gavin mentioned in another thread, that raiseAsyncEvent can be used to notify observers outside of the current conversation. However we were not able to find out how this should be done.