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

WFtask problem - task ->IsValid() returns 0 always

Srinivasa Talla

Task becoming invalid when we invoke a task from workflow and using the taskid to refere the existing task(that is newly created task from workflow)
(windows 2003, TS 6.5)
1. Call for external task in workflow(from generated job specification)

<externaltask name="Local_Group_Add" owner="domain1\ts-admin" lock="f" start="t">
<command v='D:/iw-home/iw-perl/bin/iwperl

/iw-home/local/bin/PLC_group_assignment.ipl "3" "HA888_22" "domain1\user1" "domain1\user2" '/>

2. Code from PLC_group_assignment.ipl
This is the first task in workflow, it invoked, but task becoming invalid.

use TeamSite::WFtask;

my $varCount = $ARGV[0] +1;
$projectNumber = $ARGV[1];

my $areaInt = $varCount +2;
my $area = $ARGV[$areaInt];
my $taskInt = $varCount +1;
my $task = new TeamSite::WFtask($ARGV[$taskInt]);

3. The values are

$task->IsValid() - 0(zero)
$task->GetArea() - GetArea failed: invalid workflow xml

projectNumber=HA888_22
varCount=4
areaInt=6
taskInt=5
area=\default\main\shan\internet\md\Projects\HA888_22\WORKAREA\workarea
taskid=3633

3. The task exists, 3633, but the task->IsValid() becoming 0.

4. I didn't understand why it is becoming 0(invalid), just got the value and trying to use with WFtask.

5. This is working code in 5.5.2, is there any change in 6.x?

6. when it is executing the ipl file, why is it showing error : invalid workflow xml...

thanks

Edited by raot on 09/30/05 05:46 AM (server time).

Find more posts tagged with

Comments

Adam Stoller

That's pretty bad argument parsing code - and it's possible that you're looking at a jobid instead of a taskid which might account for the problem. Try changing your code to look like this:use TeamSite::WFtask;

my($projectNumber, $branchName, $user1, $user2, $jobid, $taskid) = @ARGV;
my $task = TeamSite::WFtask->new($taskid);
if (! $task->IsValid()){
# error out here
}
# else - continue with scriptI'm not sure why you're passing the name of the branch to your script - I assume this is a branch name that is different from the areavpath specified for the task (my $area = $task->GetArea();).
I also don't know what the two userid's being passed to the script are for - you can get the task owner via my $owner = $task->GetOwner(); if that's what one of those two arguments was supposed to be?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Srinivasa Talla

thanks for your reply, fish.

1. There are 3 parameters , project number/branchname, user1,user2.
(branchname, no need to send as parameter, I agree, but existing code)
2. Here the users may vary from 2 to 5. So we are passing the parameter count.
3. After our parameters(in this particular case) always we will get 3 more parameters jobid(4th param),
taskid(5th param), areavpath(6th param).
4. So, here taskInt=5, so I am getting only taskid(5th param), existing task
(just created through workflow).
5. So, If I am getting the taskid, why is it becoming invalid?
6. One more interesting thing, when I am compiling the above .ipl file from command
line..if I have the line
if ($task->IsValid())
I am getting this error -> Could not connect to IWSERVER.
But if comment this line, no errors found.
7. Any one get into same situation?

Adam Stoller

1. There are 3 parameters , project number/branchname, user1,user2.
(branchname, no need to send as parameter, I agree, but existing code)
2. Here the users may vary from 2 to 5. So we are passing the parameter count.
3. After our parameters(in this particular case) always we will get 3 more parameters jobid(4th param),
taskid(5th param), areavpath(6th param).
4. So, here taskInt=5, so I am getting only taskid(5th param), existing task
(just created through workflow).

Ah, okay - I misunderstood how your parameters were being used from the code you had posted.
Based on the new information - I would write the code something like this:...
my $param_count = shift; # number of optional args
my %ARGS; # storage for optional args
$ARGS{project_number} = shift; # pull off first arg
for(my $i = 1; $i < $param_count; $i++){# loop through remaining args
$ARGS{"user_$param_count"} = shift; # pulling each one off
}
#======================================================================
# End result based on:
# PLC_group_assignment.ipl "3" "HA888_22" "domain1\user1" "domain1\user2"
#
# ARGS(project_number => "HA888_22",
# user_1 => "domain1\user1",
# user_2 => "domain1\user2");
#======================================================================
my ($jobid, $taskid) = @ARGV; # Pull off standard args
...5. So, If I am getting the taskid, why is it becoming invalid?
6. One more interesting thing, when I am compiling the above .ipl file from command
line..if I have the line
if ($task->IsValid())
I am getting this error -> Could not connect to IWSERVER.
But if comment this line, no errors found.

This sounds very suspicious. You're sure you're running this command on the TeamSite server? And TeamSite is running? Failure to connect to the IWSERVER could easily account for the taskid being considered invalid.

I'm not really sure what to suggest here - my guess is that there is something "peculiar" about your TeamSite setup that is confusing things, and you might try downloading and running the diagnostic script from the Support site and opening a case with Support using that data.

Assuming you do get this resolved, I'd be interested in hearing what the problem actually turns out to be.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Srinivasa Talla

Fish, the problem got solved, I think you saw another thread.

The reason is setting wrong value to environment variable.
$ENV{SYSTEMROOT} = 'C:\WINDOWS';//win 2003