passing parameters to cgitask

I am trying to call /iw-cc/newform as the first task (cgitask) in my workflow (for use on submit within CCstd).. it does get called, but it seems to not pass in the 2 required parameters that I am trying to pass in.. (so its launching the pick your DCT page instead).. is there another way to pass in the parameters into the cgitask? (using 6.7.1 on Solaris 10)

also, anyone know what should the done_page variable be set to in order to continue back into the workflow?

any guidance would be appreciated.

here is a snippet of my code:

Find more posts tagged with

Comments

Adam Stoller

I am trying to call /iw-cc/newform as the first task (cgitask) in my workflow (for use on submit within CCstd).. it does get called, but it seems to not pass in the 2 required parameters that I am trying to pass in.. (so its launching the pick your DCT page instead).. is there another way to pass in the parameters into the cgitask? (using 6.7.1 on Solaris 10)

also, anyone know what should the done_page variable be set to in order to continue back into the workflow?

any guidance would be appreciated.

here is a snippet of my code:

I don't believe the CCI URLs understand task-level variables - instead I think you need to concatenate those parameters onto the URI (e.g.: /iw-cc/newform?****=yyy&zzz=aaa) except you may have to play around with the '&' part since XML tends not to like that character being used all over the place.

kaalraa

I am trying to call /iw-cc/newform as the first task (cgitask) in my workflow (for use on submit within CCstd).. it does get called, but it seems to not pass in the 2 required parameters that I am trying to pass in.. (so its launching the pick your DCT page instead).. is there another way to pass in the parameters into the cgitask? (using 6.7.1 on Solaris 10)
also, anyone know what should the done_page variable be set to in order to continue back into the workflow?
any guidance would be appreciated.
here is a snippet of my code:

As far as i have experienced, there is not much space been given by Interwoven to talk between the workflow and the DCTs. You can play with the items through scriptframe object, but can not pass querystring variables after the URL being provided by IWOV as they all are being passed from a compiled jsp code.

Instead you can call your customised CGI file directly with parameters as querystring. For done_page you can provide the URL being used for workflow details window passing the job id along with. This way the details about active and inactive tasks would be listed as refreshed.

ISCBorisB

...is there another way to pass in the parameters into the cgitask? (using 6.7.1 on Solaris 10)...

How do you pass (or try to pass) required parameters? Code fragment you provided does not have any.
Whatever is the mechanism you've tried you may want to run WF in Debug mode and check if the syntax you
want/expect has been generated

Migrateduser

I don't believe the CCI URLs understand task-level variables - instead I think you need to concatenate those parameters onto the URI (e.g.: /iw-cc/newform?****=yyy&zzz=aaa) except you may have to play around with the '&' part since XML tends not to like that character being used all over the place.

that was my original thought..

when I put that in the cmd.. i get:

"The given path //webcmsdt1/default/main/TEST/WORKAREA/jpr_test?iw_jobid=14338 is not a valid path for form entry."

seems to add another "?" after mine and break the URL..

here is the full URL:


using the as my cgi_command: 

my $cgi_command = "/iw-cc/newform?iw_tdt=library/content&amp;vpath=//webcmsdt1/default/main/TEST/WORKAREA/jpr_test";

this is what the browser tries to load:

http://localhost/iw-cc/newform?iw_tdt=library/content&amp;vpath=//webcmsdt1/default/main/TEST/WORKAREA/jpr_test?iw_jobid=14338&amp;done_page=/iw-cc/base/util/refresh_done_target_and_close_window.jsp?done%5ftarget=fs%5fget%5flist%5fframe%28%29&amp;user_role=&amp;taskid=14339&amp;taskID=14339&amp;iw_desc=&amp;task_id=14339&amp;iw_overwrite=&amp;iw_user=watadmin&amp;iw_workarea=/default/main/TEST/WORKAREA/jpr_test&amp;iw_template_name=Submit to DB-2&amp;iw_taskid=14339&amp;session=52616e646f6d4956e844b685343705832a4073971697bcd447a5b12f091797b29eeeb53a94bfdc4fd99e374759e405eb727a5b50167609b7&amp;iw_session=52616e646f6d4956e844b685343705832a4073971697bcd447a5b12f091797b29eeeb53a94bfdc4fd99e374759e405eb727a5b50167609b7&amp;area_path=/default/main/TEST/WORKAREA/jpr_test&amp;iw_role=&amp;iw_home=/opt/iw-home&amp;user_name=watadmin&amp;iw_branch=/default/main/TEST&amp;iw_use_default=&amp;iw_areaowner=watadmin&amp;iw_template_file=waters/sampledd2.wft

Migrateduser

How do you pass (or try to pass) required parameters? Code fragment you provided does not have any.
Whatever is the mechanism you've tried you may want to run WF in Debug mode and check if the syntax you
want/expect has been generated

well I was trying to do it this way:

< variables >
< variable key="iw_tdt" value="library/content"/ >
< variable key="vpath" value="__VALUE__('$area_vpath');"/ >
< /variables >

but that didnt work.. and the in the command itself (as in my above post) and that did not work either.. I can deal with making it dynamic once I get it working as a static. for now I am just hard coding it trying to get it working..

Adam Stoller


using the as my cgi_command: 

my $cgi_command = "/iw-cc/newform?iw_tdt=library/content&amp;vpath=//webcmsdt1/default/main/TEST/WORKAREA/jpr_test";

this is what the browser tries to load:

http://localhost/iw-cc/newform?iw_tdt=library/content&amp;vpath=//webcmsdt1/default/main/TEST/WORKAREA/jpr_test?iw_jobid=14338&amp;done_page=/iw-cc/base/util/refresh_done_target_and_close_window.jsp?done%5ftarget=fs%5fget%5flist%5fframe%28%29&amp;user_role=&amp;taskid=14339&amp;taskID=14339&amp;iw_desc=&amp;task_id=14339&amp;iw_overwrite=&amp;iw_user=watadmin&amp;iw_workarea=/default/main/TEST/WORKAREA/jpr_test&amp;iw_template_name=Submit to DB-2&amp;iw_taskid=14339&amp;session=52616e646f6d4956e844b685343705832a4073971697bcd447a5b12f091797b29eeeb53a94bfdc4fd99e374759e405eb727a5b50167609b7&amp;iw_session=52616e646f6d4956e844b685343705832a4073971697bcd447a5b12f091797b29eeeb53a94bfdc4fd99e374759e405eb727a5b50167609b7&amp;area_path=/default/main/TEST/WORKAREA/jpr_test&amp;iw_role=&amp;iw_home=/opt/iw-home&amp;user_name=watadmin&amp;iw_branch=/default/main/TEST&amp;iw_use_default=&amp;iw_areaowner=watadmin&amp;iw_template_file=waters/sampledd2.wft

Hmm - Perhaps you need to create a wrapper script in httpd/iw-bin/ and have it construct the URI for iw-cc/newform and do a redirect - rather than trying to do it directly from the wft itself.

In that way, you could specify the parameters as task-level variables and perhaps it will work -- also you'll need to do something in order to get the task to transition when you're done - though perhaps passing the job_id and task_id will make that happen automatically (don't know - don't have time to test it out right now either - sorry)

ISCBorisB

well I was trying to do it this way:

< variables >
< variable key="iw_tdt" value="library/content"/ >
< variable key="vpath" value="__VALUE__('$area_vpath');"/ >
< /variables >

but that didnt work.. and the in the command itself (as in my above post) and that did not work either.. I can deal with making it dynamic once I get it working as a static. for now I am just hard coding it trying to get it working..

Please note that "newform" is not a CGI Task, it's just one of the Content Center URLs. As such it has no idea that you are trying to use it in the
Workflow, much less that you set some variables to process.

That said, you should be able to use standard CGI syntax: ...newform?vpath=foo&iw_tdt=moo. As noted before by Ghoti that may (will?) create malformed
WF XML, so the real syntax will be something like ...newform?vpath=foo&ampamp;iw_tdt=moo

Unrelated note: if you do something like WFT Fragmewnt above you should probably use "__TAG__('$area_vpath');" not __VALUE__

Migrateduser

Please note that "newform" is not a CGI Task, it's just one of the Content Center URLs. As such it has no idea that you are trying to use it in the
Workflow, much less that you set some variables to process.

That said, you should be able to use standard CGI syntax: ...newform?vpath=foo&iw_tdt=moo. As noted before by Ghoti that may (will?) create malformed
WF XML, so the real syntax will be something like ...newform?vpath=foo&ampamp;iw_tdt=moo

Unrelated note: if you do something like WFT Fragmewnt above you should probably use "__TAG__('$area_vpath');" not __VALUE__

I tried that as posted above, and its adds an additional set of params (and the question mark) after mine, so it does not seem to work.

ISCBorisB

I tried that as posted above, and its adds an additional set of params (and the question mark) after mine, so it does not seem to work.

You may want to switch debug to ON in your wft and attach generated XML, (not raw wft code). Still, it may not work even if the syntax is letter perfect.

The reason is that WF Engine posts certain Form to CGI code(that I know), your own attributes may be ignored(and that is just an educated guess).

Frankly, I was surprised that anything at all was rendered when you supplied a URL (rather than CGI code) as your command.
As proposed before, make a wrapper and build/call URL/process callback from there