nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

jobid, taskid and wa info not passed from workflow to external cgi.

padmanabh

Hi,
TeamSite version 6.7.1
OS windows
TeamSite workflows:
I am having some issues while getting jobid, taskid and WORKAREA from a workflow.
In my workflow there is an external task that calls a cgi

In source workflow the external cgi is called in the following way,

command v = "__INSERT__("$iwhome");/iw-perl/bin/iwperl.exe __INSERT__("$iwhome");/httpd/iw-bin/gl/sr.cgi gl/sample_WFT_Files/SourceWF.wft __INSERT__($p1); __INSERT__($p2); __INSERT__($fileList);"

sr.cgi is called correctly. However in the sr.cgi I do not get jobid, taskid and WORKAREA values. They are blank. Other parameters are received ok.

What may cause this behavior?

Please let me know if any additional information is required.

Thanks

Find more posts tagged with

Comments

ISCBorisB

External Tasks and CGI Tasks have different parameter passing mechanisms. For the CGI Task information is posted
through certain Form. Within your CGI code you should get Task ID, instantiate CGI Task Object and obtain information
you need from it. Like this
[php]use TeamSite::CGI_lite;
use TeamSite::WFtask;

$cgi = new TeamSite::CGI_lite;
$cgi->parse_data();
$taskId = $cgi->{form}{task_id};
$task = TeamSite::WFtask->new($taskId);

if ($task->IsValid()) {
my $area = $task->GetArea();
my @files = $task->GetFiles();
. . .
}
else {
#log out failure information for debugging, etc...
}[/php]

padmanabh

Thank you very much ISCBorisB for looking into this!

Sorry for not being clear. Actually I am using an Externaltask in the workflow and not a cgitask. The externaltask calls a cgi script located in /httpd/iw-bin/gl

Also note that it works properly fetching job/task/wa parameters on one of our machines but does not work in a customer environment.

Can it be related to some configuration parameter or something in iw.cfg that could prevent job/task/wa getting added to @ARGV?

Adam Stoller

If you want more assistance, please show the exact

command

parameter used for the task in question (you say it is an externaltask but that it is calling a CGI script - those two concepts do not tend to go together)

Also - you may need to post some of the actual code in the script in question (e.g.: the beginning part where you attempt to parse information)

ISCBorisB

If you want more assistance, please show the exact
command
parameter used for the task in question (you say it is an externaltask but that it is calling a CGI script - those two concepts do not tend to go together)

Also - you may need to post some of the actual code in the script in question (e.g.: the beginning part where you attempt to parse information)

Please explain how exactly you invoke a CGI from the external Task. I agree with
Ghoti that the idea is somewhat unconventional, to put it mildly. Do you call CGI using
some system/qx flavor or do you instantiate an Agent and execute HTTP request?

Note that
1. parameter passing Syntax differs for two options above. The code to obtain information
that you've passed differs also.

2. CGI GUI will not appear for WF User. In either case you will have to parse the result
(CGI Output) within external Task code.

3. __INSERT__ Method that you've used to pass (External?) Task Parameters actually exists
only in "wft" (WF Specs generation) Phase. You can not use them within External/CGI
Task code

padmanabh

Thank you very much for your replies. I really appreciate your help!
I am attaching the files here so that there is no more confusion and you can see exactly what I am doing here.
Just wanted to mention again that it works on my system but does not work on a customer environment.

Adam Stoller

Thank you very much for your replies. I really appreciate your help!
I am attaching the files here so that there is no more confusion and you can see exactly what I am doing here.
Just wanted to mention again that it works on my system but does not work on a customer environment.

The code you posted for sendRequestToGL.cgi has the inclusion of TeamSite::WFtask commented out, yet you attempt to use it on line 87.
Try uncommenting it and see if it works.

Beyond that, I don't have the time to debug your code - sorry.

padmanabh

Thanks Fish for looking into the code! However, I found that this line does not affect the behavior of the code. It still works on my machine and does not work on the customer machine. Strange!
Anyway, since the issue is about not getting the job/task/wa parameters from the wft to cgi/perl script, I am still focussing on that part only.