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 Modeler Email Subject Lines

TeamSite_Smasher

I have finally figured out how to properly modify the file: \workflow\email\ApprovalAuthorNotification.xsl

to be a little more custom.

problem is now, i can not find a way to modify the subject line..

instead of the default "Teamsite Task Notification" i want this to say "Teamsite Task Approved!" for instance...

How do i modify the subject lines of the emails sent, whether it be an approval, or rejection?
thx

Server: TS-PROD
Version: Interwoven TeamSite 6.7.2.0
Build Number: 69626
Workflow Modeler

Find more posts tagged with

Comments

Adam Stoller

I have finally figured out how to properly modify the file: \workflow\email\ApprovalAuthorNotification.xsl

to be a little more custom.

problem is now, i can not find a way to modify the subject line..

instead of the default "Teamsite Task Notification" i want this to say "Teamsite Task Approved!" for instance...

How do i modify the subject lines of the emails sent, whether it be an approval, or rejection?
thx

Server: TS-PROD
Version: Interwoven TeamSite 6.7.2.0
Build Number: 69626
Workflow Modeler

As I've mentioned before - the OOTB mail notification classes are not as customizable as the OOTB iw_solution_email.ipl script.

In order to do what you want, you need to create your own custom mail notification class - if so, I suggest you have it read the subject line from a task variable (e.g.: mail_subject) so that the code is much more flexible in terms of its usage.

interDev

As I've mentioned before - the OOTB mail notification classes are not as customizable as the OOTB iw_solution_email.ipl script.

In order to do what you want, you need to create your own custom mail notification class - if so, I suggest you have it read the subject line from a task variable (e.g.: mail_subject) so that the code is much more flexible in terms of its usage.

Can he actually not call the iw_solution_email.ipl script from any of the task (no the email task)and use it which is easily customizable as well?

ISCBorisB

Can he actually not call the iw_solution_email.ipl script from any of the task (no the email task)and use it which is easily customizable as well?

Normally, no.

iw_solution_email is an external Task Script. It means that it expects certain call conditions provided by WF Engine.
It does what it does by parsing TS Job and Task Objects, etc. It also executes transition callback.

Of course, if you know what you are doing and can accept built-in callback / Task transition and can provide all proper ET
parameters and know how to organize other WF Tasks to make mail work correctly - than sure, why not....

Adam Stoller

Normally, no.

iw_solution_email is an external Task Script. It means that it expects certain call conditions provided by WF Engine.
It does what it does by parsing TS Job and Task Objects, etc. It also executes transition callback.

Of course, if you know what you are doing and can accept built-in callback / Task transition and can provide all proper ET
parameters and know how to organize other WF Tasks to make mail work correctly - than sure, why not....

If my memory is correct (which at this point today, I'm no longer sure of ;-) the iw_solution_email.ipl just does a callback of 0 - i.e. it only expects a single successorset transition - as such, if you use a WFM Email Task and replace the command attribute to use iw_solution_email.ipl and provide the various task variables that it's looking for (and/or that you want to add for your PTs to use) - then it shouldn't be too much of a problem from that front.
The rest of it then lies in the PT code for header and body -- and because it's Perl (the script and the PTs) this won't work for "Non-OS Users" because of the issue with impersonation.
Assuming you get past all of that - yeah, it should work just fine.

On the other hand, if you bite the bullet and create your own custom class for handling mail notification, you can build in those goodies and then use it from that point forward.