On Sep 8, 2006, at 5:14 PM, Chris Miner wrote:


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.
Perhaps I can deliver you some hints (not sure if there are obstacles we have to remove first)


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
No this would then not be a part of the workitem! This additional attributes are used by magnolia but not by the OpenWFE Engine. The information would never reach the engine. This is exactly why it would be nice if we store the workitem using jcr instead of persisting the workitem serialized to an xml in a single property.

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.


Ok, I see your intention, but I think this is just a workaround. It will be difficult (not unpossible) to use this information in the workflow definition. Therefore I suggest to use the woritem as it is foreseen.

Perhaps we should really wait until John was able to make the solution A) working.

How does that sound?

----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------


----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------

Reply via email to