Change workflow notification email template

Hi there, I would like to know whether the workflow notification email body can be change?

I would like to remove the approve/reject button from the email. Instead, I want to put a link there for the user to link back to TeamSite.

Please advise, Thanks.

Find more posts tagged with

Comments

Ambuj

Hi there, I would like to know whether the workflow notification email body can be change?

I would like to remove the approve/reject button from the email. Instead, I want to put a link there for the user to link back to TeamSite.

Please advise, Thanks.

You can change the look & feel of workflow. You can also remove these buttons. Please post your wft file.

Adam Stoller

Hi there, I would like to know whether the workflow notification email body can be change?

I would like to remove the approve/reject button from the email. Instead, I want to put a link there for the user to link back to TeamSite.

Please advise, Thanks.

That email is being generated via iw_solution_email.ipl using some PTs that are referenced within the workflow.

If you copy the PTs to some other name (and/or location) and change the reference to them in the WFT - you can modify the look-and-feel of the email notification as you see fit.

waikong

You can change the look & feel of workflow. You can also remove these buttons. Please post your wft file.

Please advise. Thanks alot!

Tbag

Do you see the definition of the $reviewer_email_body_template variable around line #230? It's set to "va_reviewer_email_body_template" which is probably located in your $iwhome/local/config/wft/solutions/ directory (search around for it if it isn't there).

Anyway, when you find that template file, crack it open and search for either the button HTML or -- more likely -- an include component that pulls in the buttons from a smaller included template.

Comment out or remove the button section and add a section like:


       <[iw_include pt="ccmail_button.tpl" mode="ptlocal">
        <![CDATA[
            $iw_param{label} = "Get Started";
            $iw_param{href} = "/iw-cc/viewtaskdetails?taskid=" . iwpt_dcr_value('user_task@id');
        ]]>
        </iw_include>

This will include a small template to include a button that says "Get Started" that will take the user directly to the task in TeamSite.

Note that the "ccmail_button.tpl" is a template that IWOV ships out of the box in the $iwhome/local/wft/solutions directory. You'll need to replace the "iwpt_dcr_value('user_task@id')" section with some code that will return you the ID of the task you're emailing the user about....it may already be defined in your va_reviewer_email_body_template, but double-check.

Good luck!

Adam Stoller

&uot

Do you see the definition of the $reviewer_email_body_template variable around line #230? It's set to "va_reviewer_email_body_template" which is probably located in your $iwhome/local/config/wft/solutions/ directory (search around for it if it isn't there).

Anyway, when you find that template file, crack it open and search for either the button HTML or -- more likely -- an include component that pulls in the buttons from a smaller included template.

Comment out or remove the button section and add a section like:
       <[iw_include pt="ccmail_button.tpl; mode="ptlocal">
        <![CDATA[
            $iw_param{label} = "Get Started";
            $iw_param{href} = "/iw-cc/viewtaskdetails?taskid=" . iwpt_dcr_value('user_task@id');
        ]]>
        </iw_include>
This will include a small template to include a button that says "Get Started" that will take the user directly to the task in TeamSite.

Note that the "ccmail_button.tpl" is a template that IWOV ships out of the box in the $iwhome/local/wft/solutions directory. You'll need to replace the "iwpt_dcr_value('user_task@id')" section with some code that will return you the ID of the task you're emailing the user about....it may already be defined in your va_reviewer_email_body_template, but double-check.

Good luck!

In general, rather than making changes to a product-supplied PT or script - it's better to make a copy of the file in question and modify the copy - and then change references to point to the copy. This might mean making a copy of both the PT and the WFT so that both can be changed.

Otherwise you stand a good chance of "losing" the changes when you upgrade or apply a patch or service pack.

waikong

&uot
In general, rather than making changes to a product-supplied PT or script - it's better to make a copy of the file in question and modify the copy - and then change references to point to the copy. This might mean making a copy of both the PT and the WFT so that both can be changed.

Otherwise you stand a good chance of "losing" the changes when you upgrade or apply a patch or service pack.

Thanks for the reminder, I am infact, modifying the copy of the wft, I place it under a custom folder and reference it at available_templating.cfg.

but I do change some part of the code directly, because I have no idea how to copy them out, such as the function in the "author assignment" workflow installation screen, the select author windows actually too small to list about 90++ user, thus, I actually expand the size of it. I hope that won't broke the functionality.

Adam Stoller

Thanks for the reminder, I am infact, modifying the copy of the wft, I place it under a custom folder and reference it at available_templating.cfg.

but I do change some part of the code directly, because I have no idea how to copy them out, such as the function in the "author assignment" workflow installation screen, the select author windows actually too small to list about 90++ user, thus, I actually expand the size of it. I hope that won't broke the functionality.

Part of what code? Where? If you have to change something in the Author Assignment workflow - you should make a copy of it and modify that copy (and reference that copy in available_templates.cfg) -- if you're doing that, then there shouldn't be much to worry about.

waikong

Part of what code? Where? If you have to change something in the Author Assignment workflow - you should make a copy of it and modify that copy (and reference that copy in available_templates.cfg) -- if you're doing that, then there shouldn't be much to worry about.

I'd changed this file:
$iw-home\iw-perl\vendor\lib\TeamSite\Usertask.pm


sub make_l10n_input_with_roles_callout {
    my ($field,$default,$button_label,$locale,@roles) = @_;

    if ($button_label eq '') { $button_label = 'Select...'; }
    my $roles_arg = join('|',@roles);
    my $html =<<EOS;
<table cellspacing="0" cellpadding="0" border="0">
<tr>
<td>
  <input name="$field" type="text" size="20" class="iw-base-text-field-data">
</td>
<td>
  <img src="/iw-cc/base/images/clear.gif"/>
</td>
<td>
    <script language="JavaScript">
function show_${field}_win() {
newwin = window.open("/iw-bin/iwuserselect.cgi?role=$roles_arg&field=$field&default=$default&iw_locale=$locale","userselect", "height=400,width=300,resizable");
}
    </script>
  <table cellspacing="0" cellpadding="0" border="0">
  <tr>
  <td nowrap>
    <table cellspacing="0" cellpadding="0" border="0">
    <tr>
    <td width="1"><img src="/iw-cc/base/images/dialog_btn_left.gif"/></td>
    <td nowrap valign="middle" align="middle" background="/iw-cc/base/images/dialog_btn_mid.gif">
      <a href="javascript&colon;show_${field}_win()" class="iw-base-actionlist-link">

$button_label

      </a>
    </td>
    <td width="1"><img src="/iw-cc/base/images/dialog_btn_right.gif"/></td>
    </tr>
    </table>
  </td>
  </tr>
  </table>
</td>
</tr>
</table>
EOS
    return $html;
}

Adam Stoller

I'd changed this file:
$iw-home\iw-perl\vendor\lib\TeamSite\Usertask.pm
...

To be frank (or harry?) Usertask.pm is of questionable value and you'd probably be better off copying /modifying the code you actually use from there into your own module (under iw-perl/site/lib/) and modifying (and referencing) that copy.

The original author of that module still lurks on the forums from time to time and even he would probably tell you the same (it was developed for some old OOTB workflows that I don't believe are shipped anymore, nor used by many organizations).

nipper

To be frank (or harry?) Usertask.pm is of questionable value and you'd probably be better off copying /modifying the code you actually use from there into your own module (under iw-perl/site/lib/) and modifying (and referencing) that copy.

The original author of that module still lurks on the forums from time to time and even he would probably tell you the same (it was developed for some old OOTB workflows that I don't believe are shipped anymore, nor used by many organizations).

You are being kind. I would never trust the guy who wrote that PM.

ISCBorisB

You are being kind. I would never trust the guy who wrote that PM.

My, my... What happened to his "School of making friends and influencing Customers"?

nipper

My, my... What happened to his "School of making friends and influencing Customers"?

You can see I was an honors student. :-)

Migrateduser

You are being kind. I would never trust the guy who wrote that PM.

The guy who wrote that PM is a genius. Nipper and Ghoti are just jealous. That was the best code ever written.

nipper

The guy who wrote that PM is a genius. Nipper and Ghoti are just jealous. That was the best code ever written.

That sounds like a challenge. I guess we should review the PM and show how little he knew (or knows) about Perl.

Migrateduser

I knew enough to get that gig with Interwoven. And look what a solid company they have become!

Adam Stoller

I knew enough to get that gig with Interwoven. And look what a solid company they have become!

heh - I figured you'd chime in.

Honestly though - if you had to write code for a wft would you actually use that module as it exists today?