multiple instance/model submission

ok, from the deafening silence from my previous post I can only assume 
that my query was either
a: completely ridiculous - perhaps someone might be kind enough to 
highlight why for me?
b: nobody had a clue what I meant
c: nobody cared enough to respond
d: nobody read it at all.

for those that missed it my query was this:
Is there a way to submit multiple instances as a single submission? I 
dont just mean a trigger element with multiple submissions, but so that 
the data all arrives as part of the same post?
I have instance data that I dont want to modify, and I'm trying to 
manage a workflow via jbpm with messages etc being transmitted separate 
to the main instance. I'd like to be able to handle more than a single 
instance - or even a model for that matter (can you submit a model? if 
not why not?) - can it be done?

to clarify my particular case this is whats going on.
I have xforms that are submitting data. That data is to be 
routed/rerouted with appropriate ancillary messaging and info etc by a 
workflow management system - in my case jbpm. I want to keep the data 
I'm interested in as a single xforms Instance - but I'd like to 
associate arbitrary 2nd/3rd/... Instances so that I can keep response 
messages and workflow related detail separate from the actual Data 
detail that I will actually finally store/do something with. To do this 
I really need a way to submit multiple instances to a server and have 
them all be associated with the same submission. Is there a way to do 
this currently?

eg:
lets say I have instance data:
<somedata>my data
</somedata>

and it gets submitted via an xform and requires review by at least 1 
person. so I have a second form that knows how to read this data and 
poses the question "accept" or "Reject" and allows a simple text message 
to be associated with the response (not an unusual situation I think).
I want to put this message info into another instance. That way my 
xforms dont all need to know about some schema that contains arbitrary 
elements that are only useful during a workflow. but I can have 
"workflow aware" forms that expect and can load this extra data as required.
Is there a better approach?
Should I be thinking differently?
How can I currently send 2 or more instances as the same posted package 
so that the server knows they should be kept together? do I have to try 
to maintain with some kind of tracking numbers? sounds horrid.
just being able to send an entire model in 1 hit would be very helpful, 
but I can see that it would also be handy to be able to specify multiple 
models for submission too.

any thoughts?

Thanks
Jason.

Received on Friday, 22 September 2006 06:56:19 UTC