Please help. Inline command in DCT

Hello,

I am using an inline command (Perl Script) inside of the Tagging UI datacapture.cfg. The Tagging is part of the workflow, where a user either creates or updates DCRs . This Perl Script basically checks for the value of an EA, if the value exists, do nothing. Because it basically tells me it is an existing DCR. If no value exists in the EA, then the script will set a value to it.

I have an “if and else” statement in the script and I am planning to use the iwextattr –g option, but need to know the path to the DCR if it is an exiting DCR. I checked user manual, it says there are four variables available to inline scripts, IW_ROLE, IW_DCT, IW_WORKAREA, IW_USER, but none of them is giving me the path to the DCR. I have also print out the environment variables but again, none of them seems to be useful.

I can actually hardcode the path, but need to know how to get the file name. Can anyone help?? Is there a better way? I don’t know FormAPI yet. Thanks.

Find more posts tagged with

Comments

Migrateduser

I don't believe you have access to this information at the time an inline runs. You will probably have to do this as a FormAPI call instead.

jbonifaci

If you want to do this in your DCT logic, you're probably going to want to do this with an "onSaveDone" eventHandler and a callServer.

But if your DCR creation is done as part of a workflow, your first external task after the DCR has been attached to the workflow can set the desired EA.

And for future reference, this post probably should have been made in the TeamSite FormsPublisher (Templating) Forum.

~Jeff

Adam Stoller

If you want to do this in your DCT logic, you're probably going to want to do this with an "onSaveDone" eventHandler and a callServer.

But if your DCR creation is done as part of a workflow, your first external task after the DCR has been attached to the workflow can set the desired EA.

And for future reference, this post probably should have been made in the TeamSite FormsPublisher (Templating) Forum.

~Jeff

Just to get this thread back on-track (despite being potentially in the wrong forum)

The contents of the original post indicate that the subject of the customization is the METADATA CAPTURE [MDC] DCT - not FormsPublisher.

And MDC DCTs do not [currently - as of 6.5SP2] support the use of FormAPI code.

asianknight_7

Thanks everyone for the great suggetions! I took the advice and made an external task right after the tagging cgi task and was able to get the file name that way. Below is my script:

#!d:/Interwoven/iw-home/iw-perl/bin/iwperl

# --------
# Author: John Chu
# This script checks for an EA value called TeamSite/Metadata/EntryID. If a value exists, do nothing and return.
# If no value exists, open waveid.dat, grap the number, set the EA and increase the number by one and return.
# --------
use strict;
use warnings;

use TeamSite::WFtask;
use TeamSite::WFworkflow;
use TeamSite::XMLnode;
use TeamSite::Config;

#my $dbgfile = "d:/inline_dbg.txt";
#if (open(OUT, '>', $dbgfile)){
# print OUT "DEBUGGING DATA&colon; " . localtime() . "\n";
# print OUT "[ARGV]: $_\n" foreach(@ARGV);
# print OUT "[ENV]: $_ => '$ENV{$_}'\n" foreach(sort(keys(%ENV)));
#
#}

(my $iwhome = TeamSite::Config::iwgethome()) =~ tr|\\|/|;
(my $iwmount = TeamSite::Config::iwgetmount()) =~ tr|\\|/|;

my ($wfid, $taskid, $workarea, @files) = @ARGV;
my $task = new TeamSite::WFtask($taskid);
my @files = $task->GetFiles();
(my $area_vpath = $workarea)=~ tr/\\/\//;

my $data_file = "d:/Interwoven/iw-home/custom/Wave/waveid.dat";

my $LOCK_EXCLUSIVE = 2;
my $UNLOCK = 8;
my $test;

foreach my $file (@files) {
$file =~ s/\\/\//g;

$test=`iwextattr -g TeamSite/Metadata/EntryID $area_vpath\/$file`;

if($test eq "")
{

open (FILE, "+<", "$data_file") || die ("problem opening $data_file\n");
flock FILE, $LOCK_EXCLUSIVE;
my $number=;
my $return = `iwextattr -s TeamSite/Metadata/EntryID="$number" $area_vpath\/$file`;

$number=++$number;
seek(FILE,0,0);
print FILE ("$number");
close(FILE);

}
}
#close (OUT);

$task->CallBack(0, "Completed Setting EAs");

It works just the way I wanted....again, thanks everyone's help.

Adam Stoller

Below is my script:

#!d:/Interwoven/iw-home/iw-perl/bin/iwperl
...
use strict;
use warnings;
...
my ($wfid, $taskid, $workarea, @files) = @ARGV;
my $task = new TeamSite::WFtask($taskid);
my @files = $task->GetFiles();
(my $area_vpath = $workarea)=~ tr/\\/\//;
...
$task->CallBack(0, "Completed Setting EAs");

I find it hard to believe this compiles with 'strict' enabled the code should really be:

...
my ($wfid, $taskid) = @ARGV;
my $task = TeamSite::WFtask->new($taskid);
if (!$task->IsValid()){
   # error
}
(my $area_vpath = $task->GetArea()) =~ tr|\\|/|;
my @files = $task->GetFiles();
...

You've got

@files

declared twice, you don't validate the task object before dereferencing it, and there's no reason to assume more than wfid and taskid in ARGV - everything else you should retrieve from the validated task object.

asianknight_7

Fish,

You are correct, I went back and looked my code and discovered I copied from one of the versions I saved. The last known working version that I have has the following code:

my ($wfid, $taskid, $workarea) = @ARGV;
my $task = new TeamSite::WFtask($taskid);
@files = $task->GetFiles();
(my $area_vpath = $workarea)=~ tr/\\/\//;

Based on my research, I find that every external task gets three variables pass in automatically by the system which are wfid, taskid and workarea.

Adam Stoller

Fish,

You are correct, I went back and looked my code and discovered I copied from one of the versions I saved. The last known working version that I have has the following code:

my ($wfid, $taskid, $workarea) = @ARGV;
my $task = new TeamSite::WFtask($taskid);
@files = $task->GetFiles();
(my $area_vpath = $workarea)=~ tr/\\/\//;

Based on my research, I find that every external task gets three variables pass in automatically by the system which are wfid, taskid and workarea.

They get passed 3+ arguments - but for debugging purposes it's best if you define them as taking 2 (plus any preliminary arguments you might have declared yourself) - and derive the rest from the task object - after it's been verified as valid.