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

Submit DCR and Generated File

System

I have an issue with the default submit files. It appears that the workflow only submits a DCR to staging. This causes either the author to also submit the generated page, this creating another workflow OR the reviewer to approve the task and then go to the workarea and submit direct the generated file. This behavior seems odd to me as what we really care about in the submit/workflow process should be the generated file.

What would be the best way to have the workflow also submit the generated file?

Find more posts tagged with

Comments

ela

Hi,
I've got more or less the same problem/wish; I would like to submit both the DCR and the generated html file to the staging area. We've got two kinds of workflows, a fast deployment for existing files (for web publishers) and a standard workflow (for authors). With the fast deployment we can add any file to the workflow, also the html files, and then they get submitted as well, but that requires that the html file has been generated before. What I really would like, is to have both the DCR and the html file submitted with the standard workflow. I hope there's somebody out there who can help us!?

tvaughan

Hi

Put this at the end of each TPL that you use to generate HTML (note that I'm putting a space between my less-than-signs and my CDATA or iw_perl strings to make this show up. Get rid of that space when you copy & paste this):


  < iw_perl>
        < ![CDATA[

            my $outputName = iwpt_get_ofile_name();
            my $dcrName = iwpt_get_dcr_name();
            my $param = iwpt_get_flag_param('-oprefix');

             if($param eq ''){
                updateDCR($outputName,$dcrName);
                 }


            sub updateDCR {

                my $htmlname = shift;
                my $dcrname  = shift;

              my $cmd;

              $cmd = "iwextattr -s HtmlLocation=$htmlname $dcrname";
                `$cmd`;

                }
          ]]>
  < /iw_perl>

Just stick it at the bottom of the TPL file.

Then, in your workflow, have a section like this:


 < externaltask name = "AttachHTML"
                                lock = "f"
                                owner="__TAG__('iw_user');"
                                start = "t"
                                description = "Attach Daily News Page">
        < areavpath v = "__INSERT__($iw_area_vpath);"/>
        < successors>
            < successorset description = "Go to Submittask">
                < succ v = "Submittask"/>



          ");
            for (my $i=0; $i < @submit_file; ++$i) {
                __INSERT__("
                ");
            }
            __INSERT__("\n\t");
        }
        ]]>< /template_script>
    < /externaltask>

That section above makes reference to a script "attach_html.ipl." ($hf_scripts is our private variable where we keep our scripts like this one here). We had to custom write it, and it looks like this:


#!/teamsite/iw-home/iw-perl/bin/iwperl
use TeamSite::WFtask;
use TeamSite::WFworkflow;
use Mail::Mailer;
use Getopt:td;
use TeamSite::Config;

my $VERSION = "4.5.1 Build 2065 SYM Interwoven 20001027";
my $iwhome = TeamSite::Config::iwgethome();
my $iwmount = TeamSite::Config::iwgetmount();
my $hostname = TeamSite::Config::hostname();
my $debug_output = `$iwhome/bin/iwconfig iwsend_mail debug_output`;

$debug_output =~ s/\n$//;

################################################################################
######
# Read in site specific configuration information
################################################################################
######

getopts("hv");
die("$0 v. $VERSION\n") if ($opt_v);
die("Usage: $0 [(-h|-v)][-H] userid wfid taskid arevpath\n") if ($opt_h);

my $wfid      = $ARGV[0];
my $taskid    = $ARGV[1];
my $area      = $ARGV[2];

my $task     = new TeamSite::WFtask($taskid);
my $job      = new TeamSite::WFworkflow($wfid);
debug("hostname = $hostname\n");

$fullarea = "$iwmount" . "$area/";

my(@iw_files, $iw_files);
map { push(@iw_files, "$fullarea$_"); } $task->GetFiles();
$iw_files = join("\n", @iw_files);
print "$iw_files is the list of files \n";

debug("iwhome = $iwhome\n");
debug("iwmount = $iwmount\n");
debug("taskid = $taskid\n");
debug("wfid = $wfid\n");
debug("area = $area\n");
debug("files = $iw_files\n");

$location = `/$iwhome/bin/iwextattr -g HtmlLocation $iw_files 2>&1`;
$location =~ s/\n$//;
debug("HtmlLocation = $location\n");

my $htmfile = "";
my $comment = "HTML_file_from_DCR";
#$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

$location =~ /^(\/.iwmnt)($area)\/(.*)$/;
my $htmfile = $3;
$task->AddFile($htmfile,$comment);

#$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

debug("htmlfile = $htmfile\n");

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

sub debug
{
    if ($debug_output)
    {
        print STDERR @_;

        # Just return if it fails to open debug file
        open (OUT, ">>$debug_output") || return;
        print OUT @_;
        close OUT;
    }
}

Good luck.

Bowker

We accomplished this same issue the other way around.

We built an option under file menu that will create a new HTML document and the associated DCR in one shot. That way the HTML is automatically tied to the DCR and the user never needs to really know about the DCR. When the user is ready to submit the file for approval they select the .html document and start a work flow. The DCR is automatically appended to the job by an external task that looks at the extended attributes and attaches the DCRs.

If you (or anyone else) wants any of this, drop me an e-mail with "interwoven" somewhere in the subject line.

Dan Bowker
Northern Trust Company
ddb@ntrs.com

rwinterpacht

The idea of adding a file menu option sounds great...however, our need is more from an author's perspective. The author only sees the Templating piece via the CCI interface (URL's, essentially.) The user is therefore never accessing files via the GUI. What I would like to do is have the auther enter/edit content, save and close, and have the submit workflow generate a file automatically from the DCR's submitted. Then the Generated files should be deployed via OpenDeploy, and the dcr records (which contain metadata as fields, not extended attributes) be deployed to a DB via DataDeploy.

Migrateduser

It looks like your workflow script is missing some code... the successorset is not closed and there is a close CDATA tag with no open tag...can you repost the complete code? Thanks!

tvaughan

Sorry about the incomplete workflow snippet. I thought the **** "pre" tags would take care of the problem where if you put gt and lt signs in a post the tags wouldn't get rendered. Here's our workflow section, with spaces added between every gt sign and the tag:


 < !-- ========================== Attach HTML ========================== -->

    < externaltask name = "AttachHTML"
                                lock = "f"
                                owner="__TAG__('iw_user');"
                                start = "t"
                                description = "Attach Daily News Page">
        < areavpath v = "__INSERT__($iw_area_vpath);"/>
        < successors>
            < successorset description = "Go to Submittask">
                < succ v = "Submittask"/>
            < /successorset>
        < /successors>
        < command v = "__INSERT__($hf_scripts);/attach_html.ipl"/>
          < template_script>
        # insert file list if we have it
        if (__ELEM__('iw_file')) {
            __INSERT__("< files>");
            for (my $i=0; $i < @submit_file; ++$i) {
                __INSERT__("
                < file path='$submit_file[$i]' comment='task file'/>");
            }
            __INSERT__("\n\t< /files>");
        }
        < /template_script>
    < /externaltask>
   < !-- ================================================================= -->

Tom

Migrateduser

Thanks for the code update! I have one more problem. It looks like the code that is placed at the bottom of the TPL file is not setting the extra attributes...is there a way to debug this? I have run the iwextrattr -l command to list the attributes for the page I created using the template, but it does not seem to be creating the attribs. Any clue? Thanks!

tvaughan

Hmm . . .

You mean after you generate an HTML page off the TPL, the attributes aren't getting set and aren't available to the workflow?

You could do some pretty lame debugging by piping messages out of the "iw_perl" section at the bottom of the TPL. Like, you could put lines like:
`echo "Just started updateDCR" >> /tmp/tpl_error.log`
throughout the TPL's iw_perl code. Reminds me of my good old CS 101 days. . .

Anyway, then generate the HTML and cat the /tmp/tplerror.log file and see what happened.

Tom

Migrateduser

Tom,

Ok...my mistake. I was looking at the attributes of the generated page, not the DCR. It appears that the extended attribs of the DCR are being set properly. On to my next issue, this time I'm not looking in wrong place ;-)

It appears, that in the ipl file (i'm calling it jsp_attach.ipl) the following command on/near line 39 is not executing:

$location = `$iwhome/bin/iwextattr -g HtmlLocation $iw_files 2>&1`;

If I run this command from the command line on the server, it returns the exteneded attrib that we set for HtmlLocation ok. Here is the output from the iwsend_mail.log:

hostname = 127.0.0.1
fullarea = Y:\Intranet\main\Inside\WORKAREA\Inside3\
iwhome = c:\iw-home
iwmount = Y:
taskid = 5508
wfid = 5507
area = \Intranet\main\Inside\WORKAREA\Inside3
files = Y:\Intranet\main\Inside\WORKAREA\Inside3\templatedata\internal\Test\data\alliances\test.dcr
location2 =
location3 =
HtmlLocation =
htmlfile =
Success sending Email

location2 and location3 are debug lines that I added to see what the value of location was after each iteration, ie what $location was set to after the iwextattr command, then the value of $location after the substitution:

$location =~ s/\n$//;

I even changed the iwextattr command to print out to the iwsend_mail.log and it appears to be printing exactly as the command should be executed.

I'm stumped here!

I appreciate your help on this and sharing your code, this will be a lifesaver for me if I can get it running.

<steve>

mogoo

Tom-
Thank you SO much! This code works like a charm. I really appreciate your help and your posting the code. You always have very informative posts.
Thanks again,
maureen

Bowker

Ela -

Did you get what you needed? I can send you the external task we use in our workflows that attaches the DCRs of documents that are already attached to the workflow.

Dan Bowker
ddb@ntrs.com

PCL6.zip