cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Add a hookup to allow customers to insert custom email footer

Add a hookup to allow customers to insert custom email footer

This request is to add a way to allow customers of Windchill to plugin or specify custom email footer/message that is added to the end of every email sent from Windchill.

Due to compliance requirements we need to include Export Control warning message to be included to each and every emails sent out from Windchill. Through investigation, we've found all emails seem to be from wt.mail.EmailMessage, which would be a convenient point to make some changes to plug in our custom message. However, currently there is no hookup/plugin point available to allow us to append our custom message to the end of email. Some way of allowing customers to specify/hookup custom legal/compliance messages will help PTC customers to easily solve this problem, without having to make changes to PTC out of box code.

2 Comments
Garnet

Lei Yu,

Does your footer include variable information?  Or just standard text?

If you're talking about just standard text, does CS43584 meet your requirement?  This document describes how to customize the templates for the various emails that are sent from Windchill.

Newbie

Hi Ben,

Thank you for your comment, great question.

To answer your question - this is meant to be a static/standard text - in our particular case it's a mandated export control warning text (required for compliance reasons) with no variable information.

Yes, we are aware that templates can be customized and in fact we do make changes to some of them. However, there are so many email templates and there are so many different technologies used in Windchill to send out emails or email notifications... that make this a significantly larger effort for an otherwise simple task, and it may be difficult to be thorough. From a maintenance perspective, having to change so many files (quite a few of these we otherwise we do not need to change), and having to manage these files in our customization on an ongoing bases would significantly add to our maintenance overhead. When PTC makes changes to these templates, we would need to update, when PTC introduces new templates, we would need to know and would need to make changes to these new templates as well to avoid being in a situation of out of compliance. From a software design and reuse perspective, it is hardly an elegant design to repeat the exact same changes to many files if a single change can address the needs.

As you see, these are some of the challenges if we use the approach of making many changes... major concerns are effort of making initial changes, effort of ongoing maintenance, and lack of confidence that 100% of emails from Windchill are covered.