I have a use case where an external java application creates files inside of TeamSite, and those files need to be immediately published (submitted and open-deployed to the apache servers). I found the following tech article:
http://devnet.interwoven.com/site.fcgi/techlib/55800We have a basic workflow that publishes static files like I want, so I generated workflow job specification (using debug mode). I followed the example from the tech article, and I actually get a workflow to start up, however it hangs at a CGI task. I can go into that task, click the "complete" button, and the workflow finishes correctly. When triggering this same workflow manually, it processes correctly without any user interaction other than the initial "submit" screen that allows me to add comments.
So, here are my questions:
1) Is there a better way to do what I'm trying to do? My external application is java, so I assumed CSSDK made sense, but maybe not.
2) Is generating the workflow job spec from within teamsite, and programmatically replacing the "variable" values a good way to go?
3) Following from #2, does a workflow job spec have to match exactly an existing workflow template, or can I cut it down to just the elements I care about (submittask, deploy, unlock file)?
Any help, especially code samples, would be appreciated.
