On close of DCT send html pages link in email

abhishek_gupta

Hi,

I am attaching the default workflow with email, which gets triggered upon the close of a DCT. This is done via tt_data in available_templates.cfg.
What happens is that the saved DCR is attached as a link and is sent via email. But what I require is that the new generated html page is sent as a link in the email, instead of the link to the DCR.
This peice of code is used in my wft -
<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>

Its actually taken from the default author assignment with email workflow.
It would be great if someone could help me out on this, as to how to send the generated html pages link in the email.

Thanks,
Abhi

Adam Stoller

In order to get this to work - accurately, you need to have a standardized naming convention for relating generated files to DCRs - more often than not, this is taken care of completely within the workflow so that the actual file being generated is done within either a cgitask or externaltask script - which then can use TeamSite::WFtask::AddFile(); to add the generated file to the list of workflow-associated files.

The code within the wft itself isn't going to do this for you for a tt_data initiated workflow because the only file that tt_data knows about is the DCR and presently there is no simple way to track from a DCR to pages generated from it (the other way is easily done though).

As an example of how to use a standardized naming convention - here's a description of what was being done at a recent customer site:
1) DCRs were stored in sub-directories of the 'data' directory - e.g. workarea-name/templatedata/category/type/data/subdir-name/dcrname (in some cases there may be more than one level of subdirectory).
2) the generated file was stored in the same subdirectory name from the *top* of the workarea - and the filename was the same as the dcrname with an extension added - e.g. workarea-name/subdir-name/dcrname.html
3) Given this straight-forward standardization of naming - if I started a workflow with a DCR - I could easily determine the name of the generated page and explicitly add it to the workflow.

Does that make sense/

--fish
(Interwoven Senior Technical Consultant)