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

workflow to attach generated files

Markandeyulu

Hi my users create a dcrn and then generate html pages out of it...and then do a save and close...
at this step i want the pop up box that asks the users to submit the workflow... and then the generated file with any associated files(images etc) need to attach to the work flow and send it to the approver.

I want to find out how it is possible for me to get the list of the generated files and then attach that to the workflow..is there a mechanism with which i can do that...
let me know if any one has done this in the past if so ..pls attach some . script... that gives me an idea what needs to be done..

Alternatively can i have a workflow ask the user whether he needs to generate the page while doing a save and close and open the teamsite window for the user to browse to the actual path(the team site browse window that pops up while generating the page) and after he clicks on generate .. ask the user if he needs to submit it for approval and then attach the files...

I am not sure if this is a complicated workflow... coz i haven't done a workflow that asks for 2 pop ups and i am not sure how i can trigger it...

pls let me know..

Find more posts tagged with

Comments

Adam Stoller

One of the things my current customer is doing is having the PT's modify the DCR by attaching EA's to the DCR of the form:
path_some_unique_tag=area_relative_path_to_gen_file
Then if you look at the EAs on the DCR, you can easily find all the path_* attributes and from there find all the files that were generated.

There's more to the whole process, and currently having to run iwextattr multiple times during the course of generating files and figuring out which files to add to your workflow incurs a fair amount of process overhead - but it does provide a nice way of being able to find your way from the DCR to the files that were generated from it.

Before just blindly trying to go forward with this solution though, I strongly advise thinking it through and *designing* the solution before trying to implement it - you may find situations that you have to carefully work-around (in my customer's case - all the filenames generated from the DCR use the DCR name as the basis of the generated filename (with a few exceptions which are specifically handled)

--fish
(Interwoven Senior Technical Consultant)

Gregg Faus

I just attach these additional files within the primary TPL file. I wrote a custom library function called "set_task_file". Here is a non-module version of it:

#####################################################################
# The following adds a file to the task only if it doesn't exist
# Parameters:
# $task_file - file to add
# $task_id - id of task
#####################################################################
sub set_task_file {

 my $task_file = shift;
 my $task_id = shift;
 my $file_exists = 0;

 my $task = new TeamSite::WFtask($task_id);

 my @files = $task->GetFiles();

 # Iterate through task file list
 for (my $i = 0; $i < @files; $i++) {  
  if($files[$i] eq $task_file) {
   $file_exists = 1;
  } 
 }

 # Add if it doesn't exist
 if($file_exists == 0) {  
  $task->AddFile($task_file, "Generated from workflow.");
 }
}

In my TPL I would generally use it when the output is being generated via workflow. Here is a sample of calling it:

# Add xml summary to workflow if a task ID is available
$task_id = $iw_arg{task};

if(defined $task_id) {
 $task  = new TeamSite::WFtask($task_id);

 $full_path_xml_destination =~ /.*\\(templatedata.*)/; 
 $task_file = $1;
 set_task_file($task_file);
}

This sample was used to attach a XML file that was to be updated any time a DCR was submitted.

Hope that helps.