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; } } }

GetVariables method

Jenni

Hi All,

Thanks in advance. I am trying to print a variable of a task from another external task and getting a null value. Any pointers would be appreciated.

use TeamSite::WFtask;
use TeamSite::WFworkflow;
my $job = new TeamSite::WFworkflow($ARGV[0]);

open(FILE, ">D:/iw-home/tmp/plcdatadepl445.txt");
if ($job->IsValid()){
print FILE "JOB: '$ARGV[0]' (", $job->GetName(), ")\n";
my $name = "iw_mailheader_pt";
my $a = $job->GetVariable($name);
print FILE "\t a=[", $a, "]\n";
}
close(FILE);

The value of $a is null. The variable iw_mailheader_pt has a defined value in the workflow.

Thanks!
Jenni

Find more posts tagged with

Comments

Jenni

TS 6.5
Windows 2003
WFT file

Thanks!
Jenni

nipper

Post how and where you are defining the variable in the WFT (or the whole wft)

Jenni

Post how and where you are defining the variable in the WFT (or the whole wft)

Hi Andy,

Here is my WFT (datasubmit1 and datasubmit2) as an attachment. datasubmit2.txt is the continuation of datasubmit1.txt, split coz the wf file was large to upload.

Thanks!
Jenni

iwovGraduate

In your wft you have defined the iw_mailheader_pt as a task variable but in your code snippet you are trying to read a job variable. I think that explains why you are getting a null value. You need to define it as job variable or if you want to read the task variable, you need to do something like :

...
$task = new TeamSite::WFtask($taskid); # The argument to new method should be a valid task id.
...
my $val = $task->GetVariable('iw_mailheader_pt');
...

kaalraa

Dont you think you had initiated the iw_mailheader_pt as task variable and fetching it as job variable. It is better if you set the value of your variable as job variable using wfvarstartop or wfvarfinishop.

Moreover using the value as task variable, the value would be lost after the task gets inactivated.

Jenni

Dont you think you had initiated the iw_mailheader_pt as task variable and fetching it as job variable. It is better if you set the value of your variable as job variable using wfvarstartop or wfvarfinishop.

Moreover using the value as task variable, the value would be lost after the task gets inactivated.

Thanks for the reply guys. Yes you are right. I was trying to fetch a task variable instead of a job variable. I am trying to get a job variable. I am encountering errors while I mention the job variables in the following format.
[html]

....code...

....definitions...

....code...

[/html]
Is this a correct way of declaring the *global* job variables outside the externaltask tag?

Thanks!
Jenni

nipper

It should be something like this

[html]

owner="__INSERT__($varApprover3);"
creator="__INSERT__($varApprover3);">

value="foo"/>

value="bar"/>

[/html]

kaalraa

Is this a correct way of declaring the *global* job variables outside the externaltask tag?
Thanks!
Jenni

As far as I understood your code, you need to set up the value of one particular value after each external task... then you can use wfvarstartop or wfvarfinishop.

Please confirm... if your requirement differs from my understanding.

Adam Stoller

Dont you think you had initiated the iw_mailheader_pt as task variable and fetching it as job variable. It is better if you set the value of your variable as job variable using wfvarstartop or wfvarfinishop.

Moreover using the value as task variable, the value would be lost after the task gets inactivated.

The first part only makes sense if you actually intend for the variable to be a job variable - which in the case of "iw_mailheader_pt" doesn't make much sense unless you've re-written the iw_solution_email.ipl script (which might be worthwhile, but that's fodder for another thread)

The statement about the value being lost after the task gets inactivated is, I believe, false. If you can create a task object for the specific task - you should be able to access all of its task variables even if the task has been inactivated. (I don't have time to verify this right now - but I'm pretty sure that's the case).

Adam Stoller

Thanks for the reply guys. Yes you are right. I was trying to fetch a task variable instead of a job variable. I am trying to get a job variable. I am encountering errors while I mention the job variables in the following format.
[html]

....code...

....definitions...

....code...

[/html]
Is this a correct way of declaring the *global* job variables outside the externaltask tag?

Thanks!
Jenni

I think you are confusing the order in which you are reading the workflow template and the manner in which the code is actually processed.

There is a DTD associated with the WFTs which dictates that the job variables comes before any of the task definitions - and after that, it doesn't matter what order the task definitions are declared as long as all of the successors and predecessors connect to one another - so even if you could do:

variable by iw_solution_email.ipl - so even if you manage to make it into a job variable correctly - how are you planning on using it?You might also want to take a look at the perldoc for TeamSite::WFconstructor as it provides the means of developing WFTs in an object-oriented Perl fashion - which tends to be easier than the old XML way.

Jenni

[QUOTE=ghoti]I think you are confusing the order in which you are reading the workflow template and the manner in which the code is actually processed.

There is a DTD associated with the WFTs which dictates that the job variables comes before any of the task definitions - and after that, it doesn't matter what order the task definitions are declared as long as all of the successors and predecessors connect to one another - so even if you could do:

First of all thank you very much for all your replies. Here is what I am trying to achieve. The workflow, has a couple of external tasks (datadeployment and opendeployment). If any one of them fails, I am trying to shoot out an email to the user on the status of the deployment (whether it was successful/failed) and incase of failure, I am aslo sending an email with the output (root cause of failure) to the administrator. I am trying to pass the output got from the deployment scripts to the next successor task in the workflow. This is the reason, why I am trying to get the global variable and set its value in a taskA and trying to access in taskB.Is there any easy way to achieve this or the way I am trying to achieve this functionality is apt?Thanks!Jenni

Jenni

As far as I understood your code, you need to set up the value of one particular value after each external task... then you can use wfvarstartop or wfvarfinishop.

Please confirm... if your requirement differs from my understanding.

Hi,

I am trying to set the output (from the calling ipl) as the value to a job variable. But here with wfvarstartop or wfvarfinishop, we can set some value to the variable on *activation*. Please correct me if I misunderstood.

Thanks!
Jenni

Jenni

It should be something like this

[html]

owner="__INSERT__($varApprover3);"
creator="__INSERT__($varApprover3);">

value="foo"/>

value="bar"/>

[/html]

Hi Nipper,

Your code worked for me. I am able to invoke my wf successfully. But the wf just hangs at the external task. Here is the code for the invoking external ipl. I had defined a global variable (Deploymentvariable) at the beginning of the workflow as suggested by you.

use TeamSite::WFtask;
use TeamSite::WFworkflow;
use TeamSite::XMLparser;
use TeamSite::WFworkflow;

my($wfid, $taskid, $workarea) = (shift, shift, shift);

open(FILE, ">D:/iw-home/tmp/plcdatadepl334.txt");
if ($wfid->IsValid()){

my $deploymentvar = $wfid->GetVariable('Deploymentvariable');
print FILE "\t a=[", $deploymentvar , "]\n";

}
close(FILE);
$task->CallBack(0,"Retries are Over");

Is there any errors in my code? Feel it is perfect.

Thanks!
Jenni

ISCBorisB

Hi Nipper,

Your code worked for me. I am able to invoke my wf successfully. But the wf just hangs at the external task. Here is the code for the invoking external ipl. I had defined a global variable (Deploymentvariable) at the beginning of the workflow as suggested by you.

Is there any errors in my code? Feel it is perfect.

Thanks!
Jenni

Nothing is perfect. Your mistake is that you use $wfid as an object. In reality it's just a number (an ID),
you have to instantiate TeamSite::WFworkflow object first. For the External Task sample code, take a look here.

use strict;
use TeamSite::WFworkflow;
use TeamSite::WFtask;

my $trans_msg = "Invalid Job";
my($wfid, $taskid, $workarea) = (shift, shift, shift);
my $job = TeamSite::WFworkflow->new($wfid);
my $task = TeamSite::WFtask->new($taskid);

if ($job->IsValid()){
   $trans_msg = "Retries are Over";

   if (open(FILE, ">D:/iw-home/tmp/plcdatadepl334.txt")) {
      my $deploymentvar = $job->GetVariable('Deploymentvariable');
      print FILE "\t a=\[$deploymentvar\]\n";
      close(FILE);
   }
   else {
      $trans_msg = "Error, Can not open File - $!";
   }
}

$task->CallBack(0, $trans_msg);
exit 0;

nipper

Hi Nipper,

Your code worked for me. I am able to invoke my wf successfully. But the wf just hangs at the external task. Here is the code for the invoking external ipl. I had defined a global variable (Deploymentvariable) at the beginning of the workflow as suggested by you.

use TeamSite::WFtask;
use TeamSite::WFworkflow;
use TeamSite::XMLparser;
use TeamSite::WFworkflow;

my($wfid, $taskid, $workarea) = (shift, shift, shift);

open(FILE, ">D:/iw-home/tmp/plcdatadepl334.txt");
if ($wfid->IsValid()){

my $deploymentvar = $wfid->GetVariable('Deploymentvariable');
print FILE "\t a=[", $deploymentvar , "]\n";

}
close(FILE);
$task->CallBack(0,"Retries are Over");

Is there any errors in my code? Feel it is perfect.

Thanks!
Jenni

ICSBoris showed you the issue.

You should have:

use strict;

in the beginning of this.

Then if you ran:

iwperl -c externaltask_perl.ipl

you would see that $job was undefined.

Anytime an external task hangs, the first thing to check is if there is a syntax error in the Perl.

One final point, you should have a timeout on this task (and on ALL external tasks {perl, mail, deployments, etc}). If they do not complete in a reasonable time (10-30 minutes depending) go to an AdminFix task (after sending the admin an email)

Invariably when I visit a new site, I see hundreds or thousands of jobs hung in an external task. This lets you prevent that and fix the errors.

HTH

Andy

Jenni

use strict;
use TeamSite::WFworkflow;
use TeamSite::WFtask;

my $trans_msg = "Invalid Job";
my($wfid, $taskid, $workarea) = (shift, shift, shift);
my $job = TeamSite::WFworkflow->new($wfid);
my $task = TeamSite::WFtask->new($taskid);

if ($job->IsValid()){
   $trans_msg = "Retries are Over";

   if (open(FILE, ">D:/iw-home/tmp/plcdatadepl334.txt")) {
      my $deploymentvar = $job->GetVariable('Deploymentvariable');
      print FILE "\t a=\[$deploymentvar\]\n";
      close(FILE);
   }
   else {
      $trans_msg = "Error, Can not open File - $!";
   }
}

$task->CallBack(0, $trans_msg);
exit 0;

Thanks a bunch. It works now. I appreciate your time and helpful nature.

Thanks!
Jenni

ISCBorisB

Thanks a bunch. It works now. I appreciate your time and helpful nature.

Thanks!
Jenni

You are welcome. As for helpful nature I was not aware I possess one ;-)