Difference between revisions of "JSP Attachment Deprecation"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| Line 1: | Line 1: | ||
{{Deprecated|A JSP page can no longer be | {{Deprecated|A document template based on a JSP page can no longer be included as attachment in an [[Email Template]], due to limitations on the number of contexts in which they can be successfully used. | ||
''' | '''Explanation:''' | ||
:JSP | :An attachment that is generated from JSP a template works when a message is sent interactively. However, it is not possible to send such an attachment from a Rule, a Process, or one of the Java sendEmail APIs. | ||
'''Suggested Alternative:''' Use an [[HTML Document Template]]. | '''Suggested Alternative:''' Use an [[HTML Document Template]]. | ||
:* | :* Use Velocity code for loops and conditionals, in place of Java code. | ||
:* | :* If necessary, use Java code to create a [[Document Template Class]], and use that class to provide the data that the template processes. | ||
{{Best|Identify existing document templates that are based on JSP pages, so designers know to avoid them in the contexts listed above. For example, add the word "JSP" to the template name. (That practice also helps to identify document templates that need to be converted.)}} | {{Best|Identify existing document templates that are based on JSP pages, so designers know to avoid them in the contexts listed above. For example, add the word "JSP" to the template name. (That practice also helps to identify document templates that need to be converted.)}} | ||
}} | }} | ||
Revision as of 00:44, 21 March 2014
DEPRECATED: A document template based on a JSP page can no longer be included as attachment in an Email Template, due to limitations on the number of contexts in which they can be successfully used.
Explanation:
- An attachment that is generated from JSP a template works when a message is sent interactively. However, it is not possible to send such an attachment from a Rule, a Process, or one of the Java sendEmail APIs.
Suggested Alternative: Use an HTML Document Template.
- Use Velocity code for loops and conditionals, in place of Java code.
- If necessary, use Java code to create a Document Template Class, and use that class to provide the data that the template processes.
Best Practice:
Identify existing document templates that are based on JSP pages, so designers know to avoid them in the contexts listed above. For example, add the word "JSP" to the template name. (That practice also helps to identify document templates that need to be converted.)
