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

trouble seeing selected files

bagman

I'm working on a WF that creates a new workarea and copies the user selected files to the new WA. All the relevant code is attached. (It would only let me attach one file, but it's the script in question.)

The verification task calls a dummy script which does nothing. Right now it just writes out the filelist to a debug file. The create WA scripts work properly. However, the copy files to WA script is not getting the filelist. The script right now tries to read the filelist and right it out to a debug file.

I've tried $task->GetFiles() and setting external_task_add_filelist to true and reading it through @ARGV.

I'm desperately behind schedule and would appreciate any help.

Mark

Edited by bagman on 05/28/03 12:55 PM (server time).

Find more posts tagged with

Comments

Migrateduser

Can you also attach your debug output from executing this script and which part is not working for you?

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

bagman

Here's the output I'm getting...

@files ->
$k ->
==== Starting Job =======
$wfid -> 108632
$taskid -> 108637
$area -> /default/main/REDESIGN/about/WORKAREA/WA_108632
$task -> TeamSite::WFtask=HASH(0x4cf190)
$job -> TeamSite::WFworkflow=HASH(0x4d1864)
$jobname -> FedEx_Author_Submit_with_IT_Workflow
$jobdesc -> test
@iw_files ->

-- Starting loop --
-- End loop --

-- Starting Second Loop --
--End Second Loop --

==== Ending Job =======

I'm thinking I should get the filelist as part of the first loop. The second loop would only be populated if the file had an associated DCR.

eInvoice_test.rar

Migrateduser

Are you certain you have files attached to the job prior to executing this script? How are you attaching the files to the job?

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

bagman

attached is the workflow file. The first task is where (I think) the files are getting attched...

Migrateduser

So in other words, you are pre-selecting files in a workarea and then kicking off this job? If you are not pre-selecting files before running the job, no files will be attached to the job yet.

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

bagman

Correct... the user selects the files and hits the submit button. The submit button calls this workflow. The enter the description and continue.

The first task calls a script that uses $task->GetFiles() and writes out the list to a dummy file. I assume that since this works properly, the files are correctly attached to the WF...

Migrateduser

How about this...at your usertask (which looks like it preceeds the externaltask that calls the script you posted) view your Job Details and see if the files are attached to the job at this point. When the pop-up comes up after you click View Details, just click on the link for the current usertask and the list of files attached to the job should appear in a new pop-up.

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

bagman

well... there is no usertask before the script gets called... there's one defined, but it's only used if the create workarea script fails, which is rare...

I guess I could define one just to see what happens...

thanks

Migrateduser

Just as a nit, although the first filename should have been assigned to your first element in your @files array, this statement is not going to get you your whole filelist. I suspect you already know this as you commented out the correct statement just above this - I'm just calling it out as something that is not good practice, unless of course you don't plan on using the files that are passed in automatically to your script.

my($wfid, $taskid, $area, @files) = (@ARGV[0..3]);

You should use:

my($wfid, $taskid, $area, @files) = @ARGV;

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

bagman

ok... I've added a usertask before the copy script and, viola, there are no files attached... now I'm really confused...

doesn't this code attach the files to the wf?

<command v='__INSERT__($verification_cmd);'/>
<template_script><![CDATA[
if (@submit_file != 0)
{
__INSERT__("<files>\n");
for (my $i=0; $i < @submit_file; ++$i)
{
__INSERT__("
<file path='$submit_file[$i]' " .
"comment='__TAG__(File_comment_$i);'/>");
}
__INSERT__("</files>\n");
}

]]></template_script>

Migrateduser

Yes it does, and since you said your initial externaltask script (the verification one) does print out the attached files to your log, then we know the files are at least there when the jobs starts. What I would do is add a usertask as your initial task, and another usertask between each externaltask. I know this is tedious but it will at least tell you where in your workflow your files are getting lost. At each usertask check and see if your files are still attached to the job. When you don't see the files anymore, you know which script is the culprit. That's a start. I suspect it might be your create workarea script. But it could also be your verification script. Narrow it down and maybe that will give you the info you need to debug in the right place.

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

Adam Stoller

The externaltask script appears to have been written by (or copied from) several different sources - you have multiple variables defined with essentially the same names and I believe for the same purpose - and some of them are used and some of them are unused.

As a first step - I suggest you make the first line of the script read:
#!/opt/teamsite/iw-home/iw-perl/bin/iwperl -w
and add
use strict;
where you are bringing in all the modules. Then run:
iwperl -w -c scriptname
and clean up all the warnings.

Next - I would suggest changing the way you receive the command line arguments. I recommend the following:

my($wfid, $taskid) = @ARGV;
my $task = new TeamSite::WFtask($taskid);
die "Invalid taskid? '$taskid'" if (!$task->IsValid());
my $job = new TeamSite::WFworkflow($wfid);
die "Invalid wfid? '$wfid'" if (!$job->IsValid());
my $area = $task->GetArea();
my @files = $task->GetFiles();

Among other things, this will make it a lot easier to debug - because you can comment out the CallBack and then run the script in the debugger from the command line as:
iwperl -d scriptname jobid taskid

If you're running from the console of the TeamSite server - you can even use the visual debugger:
iwperl -dtkdb scriptname jobid taskid

--fish
(Interwoven Senior Technical Consultant)