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

dcr's extended attribs in email

Bhargav Coca

I am on TS6.5 on win2k. I was wondering if anyone have tried to include extended attributes taken out of a dcr and inserting them in a email notification to the approver?
thank you

Find more posts tagged with

Comments

jbonifaci

Sure, this is pretty straight forward. Just modify your email script to read the extended attributes of a DCR and include it in the email body.

~Jeff

Bhargav Coca

Correct, I know how to read my extended attributes from the file. All i am confused is changing the email script. Are you talking about the tpl file for the reviewer? reviewer_emailbody.tpl? Please advice.
Thank you

jbonifaci

You would do this within the tpl. Get the DCR or DCRs that are attached to the task. Read their extended attributes and output them as you wish.

~Jeff

reddyl

If you are using the solutions email templates the can modify the reviewer_emailbody.tpl to add dcr extended attributes.

changeCSV.zip

Bhargav Coca

Thank you Guys

Bhargav Coca

I am getting an error in writing my extended attributes into email, it says

"Try debugging like this: iwpt_compile ... -ocode ****.ipl; ****.ipl "

And here is my snippet,

###########################For Status Report########################
use TeamSite::XMLnode;
use TeamSite::WFtask;
use TeamSite::WFworkflow;

my $iwhome = TeamSite::Config::iwgethome();
my $iwmount = TeamSite::Config::iwgetmount();

my $ext_attr_cmd = "$iwhome/bin/iwextattr";
my $workflow;
my $task;
my $workarea;
if ($task_id){
$task = new TeamSite::WFtask($task_id);
$workflow = new TeamSite::WFworkflow($task->GetWorkflowId());
$workarea = $task->GetArea();
}
####################################################################
my @file_list = $task->GetFiles();
my $dcrs_attached = "";

foreach my $file (@file_list){
#print LOG "File list : $file\n";
if($file =~ /templatedata/){
my $entirepath = "$workarea\\$file";
my $cmd_ea_dcr = qq|$ext_attr_cmd -g TeamSite/Templating/DCR/Type "$entirepath"|;
print LOG "Extended Attrib for john is here: $cmd_ea_dcr\n";
my $ea_dcr = `$cmd_ea_dcr`;

###########################################################################

Calling this in email tpl , i am using this:

<iw_perl><![CDATA[
iwpt_output("$ea_dcr");
]]></iw_perl>

jbonifaci

Well, I didn't look too closely, but here is the first problem:

$task = new TeamSite::WFtask($task_id);$task_id is never defined, so you can't get the task and therefore can't interact with the task object. Look at some of the OOTB email TPL's to see how they get the task information.

~Jeff

Bhargav Coca

Sorry i missed it but it was there,
my $job_id = $ARGV[0];
my $task_id = $ARGV[1];
my $areavpath = $ARGV[2];

But still gives me the same error.
Thanks

data.txt

dazzlad

You said you are on Win2K yet you are constructing your iwextattr command like this:

 my $ext_attr_cmd = "$iwhome/bin/iwextattr";

Then capturing the result with backticks.

You need to use backslashes on windows if you are running a system command - you can construct file paths using forward slashes, which is good practice for cross platform code, however, only if you are using builtin perl routines to access these paths. I normally use a routine like the following to make sure any system calls have the slashes pointing in the right direction.

 sub prepareCommand {
 my $command = shift;

 if(lc($^O) eq 'mswin32') {
  $command = forwardSlashesToBackSlashes($command); 
 } else {
  $command = backSlashesToForwardSlashes($command);
 }

 return $command;
}

Also, you should really check if your task is valid by doing if( $task-> IsValid()) rather than assuming that all is ok.

I'm not sure if this is the solution to your whole problem, as I still don't quite understand what you are trying to do here, but these are a couple of points worth noting. Could you post your WFT file?

Thanks.

Darren.

Adam Stoller

You need to use backslashes on windows if you are running a system command

Uhm - no - that's incorrect. You can use forward slashes on Windows too - even at the command prompt you can do so - as long as you double-quote the command string (i.e. DOS has recognized forward slashes within quotes for a long time)

However - what I would not do - is mix both '/' and '\' in the same command line - which is being done with the code as posted:foreach my $file (@file_list){
#print LOG "File list : $file\n";
if($file =~ /templatedata/){
my $entirepath = "$workarea\\$file";
my $cmd_ea_dcr = qq|$ext_attr_cmd -g TeamSite/Templating/DCR/Type "$entirepath"|;
print LOG "Extended Attrib for john is here: $cmd_ea_dcr\n";
my $ea_dcr = `$cmd_ea_dcr`;
Aside from not seeing the end of this if or foreach loop - the variable $entirepath is clearly being constructed with back-slashes - I'd adjust the code to look something like this:foreach my $file (@file_list){
#print LOG "File list : $file\n";
if($file =~ /templatedata/){
(my $entirepath = "$workarea/$file") =~ tr|\\|/|;
my $cmd_ea_dcr = qq|$ext_attr_cmd -g TeamSite/Templating/DCR/Type "$entirepath"|;
print LOG "Extended Attrib for john is here: $cmd_ea_dcr\n";
chomp(my $ea_dcr = qx($cmd_ea_dcr));
# do something with $ea_dcr here ...
}
# do something if $file is not in templatedata?
}

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

dazzlad

Uhm - no - that's incorrect. You can use forward slashes on Windows too - even at the command prompt you can do so - as long as you double-quote the command string (i.e. DOS has recognized forward slashes within quotes for a long time)

Don't I feel like a muppet!

Darren.

Bhargav Coca

I got this working using forward slashes. I had to include the the extended attributes name in double quotes, cuz it was breaking at that point.
Thanks