using the "newjob" url to start workflow

Vishakha

I want to pass a parameter when I am invoking a workflow using the url "newjob".
Has anybody tried passing arguments on th new job url while invoking the workflow? When u chk the iwwft_instantiator.cgi it explains the following

#iw_setwfarg_...
# A lexical prefix for POST/GET args that cause the remainder
# of the name to be used as a custom workflow user variable
# keyname, and its value to be taken as the corresponding value
# (this is set after iwjobc, but before iwinvoke).
#
#
# Example:
#
# If you have the POST/GET args:
#
# iw_setwfarg_****=foo&iw_setwfarg_yyy=bar
#
# Then you end up with a workflow containing user variables:
#
#
#
#
#

However when I tried using it this way,
http://$hostName/iw-cc/newjob?iw_template_file=bgWorkflows/contentEditor_reviewer_workflow.wft&vpath=".$area_path."/".$contentFile."&iw_setwfarg_****=foo&iw_setwfarg_yyy=bar"

The workflow did not have the job variables "****" and "yyy".
Can anybody explain how this is used?

Adam Stoller

I want to pass a parameter when I am invoking a workflow using the url "newjob". Has anybody tried passing arguments on th new job url while invoking the workflow? When u chk the iwwft_instantiator.cgi it explains the following [...] However when I tried using it this way, http://$hostName/iw-cc/newjob?iw_template_file=bgWorkflows/contentEditor_reviewer_workflow.wft&vpath=".$area_path."/".$contentFile."&iw_setwfarg_****=foo&iw_setwfarg_yyy=bar" The workflow did not have the job variables "****" and "yyy". Can anybody explain how this is used?

The iw_setwfarg_ prefix is used within the TAG_info() section of the WFT. If you haven't defined it within your WFT it's not going to help passing it in on the command line.

Once you have it defined in the wft, I'm not sure whether or not you would address it in the URL with, or without, the prefix - but you can probably run a couple of tests to figure it out.