We are in the beginning stages of this same process to plug in XML to create jobs and the products task. Our development people are creating the XML process so I can't speak to that. I have asked for as many fields as I can get upfront for future expansion of different tasks. We do however have XML triggering auto-archiving our in-process PackEdge files at the end of the process after proof approval. One thing I have found using XML this way is it is a trigger for the process but the workflows and tasks are what is carries the info contained in the XML on after the trigger.