How do you suppose, assuming you can even make this work, that your externaltask will callback to the workflow?
I don't know shell scripting - maybe it will work. It's maybe a 3 line script in perl. I would do it in perl, but if this works then you'll be all set.
Ah Smitty!, love your sarcasm in other posts Your suggestion looks more then legit, i forgot about the callback.The new idea is to call this bash script (working on it, will post the results later):#!/bin/bashecho init >> external_task_logecho job id: $1 >> external_task_logecho external id: $2 >> external_task_logecho external id: $3 >> external_task_logecho creo edizione >> external_task_log/bin/date +%D:%H,%M | xargs -iTOKEN /Interwoven/iw-home/bin/iwpublish -g -f //asd.asd.italy/default/main/asd STAGING 'TOKEN: Deploy EASY file di contenuto pagine sitepublisher o file statici'echo richiamo il callback >> external_task_log/Interwoven/iw-home/bin/iwcallback -s asd.asd.italy $1 0Does this seem more reasonable? the idea is to save the external id that should be passed to the external task and later callback with the iwcallback clt.Thanks!Emanuel.
Ok the above script works, i can see the edition, but the manuals i've read (clt / workflow / etc) are not very clear on several aspects of the callback:1) How to apply logic upon the return code.2) The impact of a potentially wrong taskID that you specify in the callback.As of now i give to the iwcallback the (hopefully) rigth task id (that is, the second parameter that gets passed to my external).Cheers from italy!Emanuel.