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

Attaching file in WF

Jenni

Hi All,

Thanks in advance. My question is that whenever, we select a file and trigger a workflow, does the workflow automatically attaches the selected file to itself or should we have a madatory task to attach the file?

In my current workflow that I am developing, I don't see the selected file attaching to the WF.

TS 6.7.1 Windows

Thanks,
Jenni

Find more posts tagged with

Comments

Adam Stoller

Hi All,

Thanks in advance. My question is that whenever, we select a file and trigger a workflow, does the workflow automatically attaches the selected file to itself or should we have a madatory task to attach the file?

In my current workflow that I am developing, I don't see the selected file attaching to the WF.

TS 6.7.1 Windows

Thanks,
Jenni

Are you writing a WFT or a WFM?

In either case - you, as the workflow developer, have the choice of whether to automatically attach pre-selected files, have a task sepecifically for that purpose, or both.

You should spend some time reading the Workflow Developer's Guide (WFT: look around page 77) or Workflow Modeller User's Guide (WFM - not sure what page)

ISCBorisB

Hi All,

Thanks in advance. My question is that whenever, we select a file and trigger a workflow, does the workflow automatically attaches the selected file to itself or should we have a madatory task to attach the file?

In my current workflow that I am developing, I don't see the selected file attaching to the WF.

TS 6.7.1 Windows

Thanks,
Jenni

You have to provide this WF functionality yourself. Unless your process requires additional user input or some special
treatment there is no need to do it through dedicated Task though.

WF Engine supplies checked File List using 'iw_file' HTTP request key, each Path is relative to WF Area.
The following sample shows what I normally do to obtain the list in the classical WFT Model.
Perhaps somebody with more WFM Experience will chime in to illustrate the technique there. You may want
to look into iwhome/local/config/wft/solutions Directory for more samples.

# Declare required references
my ($attached_files, $file_comments) = ([], []);

# Retrieve Pre-Selected files if any. Sort Files in unencoded form, 
# then html-encode via CGI_lite
if (__ELEM__('iw_file')) {
@$attached_files = map {
      push(@$file_comments, 'Pre-Selected File');
      TeamSite::CGI_lite::escape_html_data($_);
   } sort __VALUE__('iw_file');
}
...
# If you DO NOT use WF Constructor you woud have to process '$attached_files' to
# generate files/file XML Tags within your starting Task XML.

# If you use WF Constructor (I would recommend it), it's simpler:
declare_workflow(
   name          => 'Your WF Name ',
   owner         => $iw_user,
   creator       => $iw_user,
   description   => __VALUE__('iw_desc'),
   files         => $attached_files,
   file_comments => $file_comments,
);

Jenni

Thanks a lot for the replies.

Here is the external script that gets invoked by the WF in order to attach the file to WF. Looks like the perl script is getting executed, but the file is not getting attached to the workflow. Any pointers please?

Thanks.
[html]
use strict;
use TeamSite::Config;
use TeamSite::WFtask;
use TeamSite::WFworkflow;
use CGI;
use XML: Smiley Very Happy

OM;

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

my ($wfid, $taskid, $workarea, @files) = @ARGV;
my $job = new TeamSite::WFworkflow($wfid);
my $task = new TeamSite::WFtask($taskid);
#my @files = $task->GetFiles();

my $dcrfile_to_submit = 'Y:/default/main/Safari/WORKAREA/default/templatedata/safari/weather/data/test1';
$task->AddFile($dcrfile_to_submit, "Approved for submission");

$task->CallBack(0, "Done");
exit(0);

[/html]

moonkhanna

Thanks a lot for the replies.

Here is the external script that gets invoked by the WF in order to attach the file to WF. Looks like the perl script is getting executed, but the file is not getting attached to the workflow. Any pointers please?

Thanks.
[html]
use strict;
use TeamSite::Config;
use TeamSite::WFtask;
use TeamSite::WFworkflow;
use CGI;
use XML:OM;

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

my ($wfid, $taskid, $workarea, @files) = @ARGV;
my $job = new TeamSite::WFworkflow($wfid);
my $task = new TeamSite::WFtask($taskid);
#my @files = $task->GetFiles();

my $dcrfile_to_submit = 'Y:/default/main/Safari/WORKAREA/default/templatedata/safari/weather/data/test1';
$task->AddFile($dcrfile_to_submit, "Approved for submission");

$task->CallBack(0, "Done");
exit(0);

[/html]

you need to use the vpath of the file in the AddFile function and not the actual path.. ;-)

nipper

One problem with the code you posted is that AddFile expects a path relative to the workarea. So you cannot add a file from a different workarea and it will fail with the path you provided. Perldoc is your friend. :-)

It should be something like this


my $dcrfile_to_submit = 'templatedata/safari/weather/data/test1';
$task->AddFile($dcrfile_to_submit, "Approved for submission");

Jenni

Thanks for the replies. Yes I got that fixed.

Now, I want to pass on the value of the selected file to the external script.

[html]
my $attachFiles_cmd = "$iwhome/iw-perl/bin/iwperl $iwhome/custom/Safari/bin/attachFile.ipl $selectFile";
[/html]

If i have this line in my WF, it is hangging at the task. Is there something wrong? Could we pass on the values to the perl script along whenn it is called?

Thanks!
Jenni

nipper

OK, step back for a second. Is this an external task or something you are trying to run in the header code ? If it is an external task, then you can use $task->getFiles() instead of passing it as a parameter.

Jenni

Yes, I am trying to send the selected file information to the external task(which would attach the file to the Workflow).

nipper

So this is the file I select before I hit submit ?

Jenni

So this is the file I select before I hit submit ?

You are right.

ISCBorisB

you need to use the vpath of the file in the AddFile function and not the actual path.. ;-)

That's incorrect. "Path" parameter should be relative to 'iw_workarea'. As pointed by Andy, it's all clearly documented

Jenni

That's incorrect. "Path" parameter should be relative to 'iw_workarea'. As pointed by Andy, it's all clearly documented

Hi Boris,

Yes I got that. But my question here is how am i going to pass on the selected file information to the external script?

[html]
$attachFiles_cmd = "$iwhome/iw-perl/bin/iwperl $iwhome/custom/Safari/bin/attachFile.ipl $selectFile";
[/html]

ISCBorisB

You are right.

Adam already asked that. I'll try one more time: Are you writing a WFT or a WFM?

moonkhanna

That's incorrect. "Path" parameter should be relative to 'iw_workarea'. As pointed by Andy, it's all clearly documented

Hi Bo, That was a typo error. Yes, it should be relative.

Error log.txt

Jenni

I am using WFT

nipper

I always have code like this in the header of my WFT:

[html]

#=====================================================================
# file list for start task
#=====================================================================
my($iw_selected_files) = iw_get_filelist();

#=====================================================================
# Name: iw_get_filelist
# Args: None.
# Usage: $xml = iw_get_filelist();
# Purpose: Generate an XML formatted list of all the files that
# were pre-selected when the workflow was initiated.
# Returns: Returns the XML formatted list if files were selected.
# Returns an empty string if no files were selected.
# Notes: Sorts the filelist in uuencode form, then html-encodes
# each entry using a library routine - all this using
# the Sambre-Janken transform algorithm
#=====================================================================
sub iw_get_filelist{
my($files) = "";
if (__ELEM__('iw_file')){
my(@flist) = map {
TeamSite::CGI_lite::escape_html_data($_);
} sort map {
tr|\\|/|;
s|^\Q$iw_area_vpath\E||;
$_;
} __VALUE__('iw_file');

$files = "\n";
for (my $i = 0; $i < @flist; ++$i) {
$files .= "\t\n";
}
$files .= "\n";
}
return($files);
}
[/html]

And then use insert the selected files in the start task of the WFT like this:

[html]

__INSERT__($iw_selected_files);

[/html]

ISCBorisB

I am using WFT

You should probably build a WFT that instantiates a Job with pre-selected Files already attached.

Andy's sample shows how to do that when you yourself code Job XML Specs. Note that in this case you must insert
<files>(and nested <file>) Tags within 'start' Task specifications.

My sample (post #3) illustrates how you can achieve the same using WFConstructor - my personal preference. Either way,
your Job will have all pre-selected Files already attached, no extra external Attachment Task needed. Use TeamSite::WFtask::GetFiles
method to obtain a File List in External/CGI Tasks for processing.

Jenni

Hi Guys,

Thanks soo much for the replies. Yes i was able to get the information into my external script.

Thanks!
Jenni