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

Externaltask/CGItask?

GodBlessMe

I am working on a Workflow which deploys DCRs attached to the workflow to Staging based on the value of LaunchDate item in that DCR itself. I want to call a Perl script that will go thru each DCR, parse it and push the value of LaunchDate item into an array and return the array to the workflow.

#!/iw-home/iw-perl/bin/iwperl

use TeamSite::WFtask;
use TeamSite::Config;

my $iwhome = TeamSite::Config::iwgethome();
my $area = $ARGV[2];
my $task = new TeamSite::WFtask($ARGV[1]);
my @files;
my %LaunchDateTable;

if ($task->IsValid())
{
@files = $task->Getfiles();
for (my $i = 0; $i < @files; $i++)
{
#system("$iwhome/bin/iwunlock", $area . "/" . $files[$i]);
print $files[$i];
$LaunchDateTable{'$files[$i]'} = &get_dcr_attr($files[$i]);
}

}

sub get_dcr_attr {
my ($dcr,$element_name) = @_;
open(DCR, $dcr) or die("$! - Can't open DCR.Contact teamsite admin");
local $/=undef;
my $xml = <DCR>;
close DCR;
select STDOUT;
my $parser = TeamSite::XMLparser->new();

if (defined ($parser))
{
my $rootnode = $parser->parse($xml);
if (defined ($rootnode))
{
my $retvalue = $rootnode->value($element_name);
if (defined ($retvalue))
{
return $retvalue;
}
}

}

return 0;
}

How do I return %LaunchDateTable to the calling workflow?
Or is there any alternative way to do this?
Thanks

Find more posts tagged with

Comments

Migrateduser

This is wrong:

for (my $i = 0; $i < @files; $i++)

A foreach statement would be a better choice anyway.

Dave Smith
Sr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com

Adam Stoller

Smitty -

for (my $i = 0; $i < @files; $i++) { ... }

is perfectly legal / correct Perl syntax. A foreach my $i (@files) { ... } statement would simply be a different way of writing it (and accessing the members of the list).

--fish
(Interwoven Senior Technical Consultant)

Edited by ghoti on 04/17/03 05:50 AM (server time).

Adam Stoller

How do I return %LaunchDateTable to the calling workflow?
Or is there any alternative way to do this?

You would have to translate the key/value pairs of %LaunchDateTable into a simple string and then put that string into a workflow or task level variable within the workflow, to then be extracted and used by a subsequent externaltask or cgitask script.

my $str = "";
foreach(sort(keys(%LaunchDateTable))){
    $str .= "$_;$LaunchDateTable{$_};";
}
chop($str); # yes! chop() not chomp() - to remove the trailing semicolon.

The code that retrieves it could easily turn it back into a hash using something like this:

my $str = $****->GetVariable("launchdatetable");
my %LaunchDateTable = split(/;/, $str);

--fish
(Interwoven Senior Technical Consultant)

Migrateduser

MY opinion is that foreach is a better construct than for (I miss it all the time in Java). Otherwise you use variables like $i (or enumerations in Java) too much.

foreach my ${file} ( @files )
{
# handle $file
}

Seems more logical than

for( my ${i} = 0 ; ${i} < $#files ; ${i}++ )
{
my ${file} = $files[$i];
# handle $file
}

An obvious exception would be where you want to increment a counter on each iteration of the loop.

Anyway I think it is more clear to the reader to do $#files than @files in the condition. I remember something about a performance difference between for and foreach but I imagine it doesn't really matter.

Adam Stoller

While I'd agree that foreach() tends to be simpler - my point was that the code that was written was syntactically correct.

I actually prefer using the @list construct to the $#list construct because (a) the latter requires more typing ;-) and (b) the latter requires that you use <= rather than just < - which tends to trip up a lot of folks. I.e.:

while ($i < @foo) { ... } is equivalent to
while ($i <= $#foo) { ... }

However - this is a side issue - hopefully the purpose of the original post has been answered somewhere along the way ;-)

(whew - nearly caught up with this forum - 3 or for more forums to go....)

--fish
(Interwoven Senior Technical Consultant)