How to pass BindVariables to External Process (Workflow)

Question

I build a shell script (unix) which accepts a command line parameter .... a "filename"
The "filename" is a dynamic name!
The workflow is build with a custom input parameter "filename" ... which I want to pass to an external process, which calls this shell script:
How can I do that ?
ExtProcess:
Command : Val=/bin/ksh
Parameter_List : Val=":/home/bin/myscript.sh:${Task.Input}:"
(Binding ":Filename" replaces the whole value, sorry)
Succes_Threshold: Val=0
Script : Val="" , Binding=":Filename"
... does not pass the value of ":Filename"
Script : Val="/tmp/fixed.name"
... works only with fixed names
what I really need is something simple like:
Parameter_list : Val=":/home/bin/myscript.sh:${Parameter.Filename}:FIXPARAM:"
or Script : Val=":${Parameter.Filename}:${Parameter.Param2}:${Parameter.Pram3}"
... similar problem I had with FTP, I found no way to pass dynamic filenames or other parameters (except LOCATION Parameters)
... similar problem I had with EMAIL I found no way to include PARAMETERS to the mail body (except to replace the whole body by 1 parameter)
Is there a solution or is in current version OWB 9.2 only "static" parameters supported.
I also was missing to pass OUTPUT-parameters for example of a TRANSFORMation,
I also was missing some urgent SYSTEM-parameters for self identification of the process(like "SYSTEM.TASK_NAME" "SYSTEM.EXECUTION_AUDIT_ID" "SYSTEM.ITEM_KEY" )
Thanks for all hints and best regards
Martin

Answer 1

Actually... After further investigation this may not be needed. I'd be interested in the answer, to understand what is possible.
The concept of passing parameters in the OWB workflow designer is rather limited, in my humble opinion. Sure, you can designate a "start" sequence that takes a parameter and you can pass that to mappings/transformations but there is no chance for feedback. Ie, if I manually (or through some rigged script) execute the flow with the "PARAMETER" then it will be able to bind. What about mid-flow. IE, select the record to be "processed", then call a "flow" with that as a parameter.
Am I mistaken? Is there a way to expose the "out" parameters of a mapping, or the return of a "transformation function" as "OUTS" in the process flow.
Of course, in a world where everything is OWB and in the DB one can leave data in tables, and pick it up on the other mappings. HOWEVER, most BI systems involve external retrievals, etc. that need a bit more "intelligence" then "run and return 1,2,3" . :)
Hope this is helpful for product feedback. If I'm mistaken on the WF capabilities please clue me in. :)
btw, I'm an OWB fan, certainly. The progress over the past two years has been excellent.