I had some troubles implementing a dialog save handler combo that worked to extract values from a work item during dialog presentation and back them back in the workflowitem afterward during the save process.
Since the workflow item is actually stored as a node under something like: /flow/1.x/63/1157640296863/participant/0.0.1 I wonder if it wouldn't make sense to simply add another attribute like participant, value, and ID to this node and use that to store data associated with the workflow item as it courses its way through the system? Say content attribute which would hold a mgnl:content node. Then I could use the existing dialog machinery as is. But would have to copy this important collection of data as the flowitem was saved. Otherwise this seems like a logical and simple extension to the existing solution. Just adds the concept of a workflow item having a content node. How does that sound? ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
