Difference between revisions of "Email Notification 1.6 Release Notes"
| (One intermediate revision by the same user not shown) | |||
| Line 22: | Line 22: | ||
<br /> | <br /> | ||
| − | |||
| − | |||
| − | |||
| Line 33: | Line 30: | ||
* [[ClearQuest_Email_Notification_Package_FAQ | Frequently Asked Questions ]] | * [[ClearQuest_Email_Notification_Package_FAQ | Frequently Asked Questions ]] | ||
* [[Notification_Examples | Examples]] | * [[Notification_Examples | Examples]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
Latest revision as of 03:35, 24 April 2017
Email Notification Package 1.5 Release Notes
Contents
Enhancements
Support for Non-ASCII code pages
Safe support of non-ascii code pages was added, with few limitations.
Using non-ascii field names
Currently, the parser does not provide full support non-ascii characters in field names using variable-like notation. For instance, the following field name would not be recognized: ${моё_самое_любимое_имя}. One of the possible workarounds is to use GetFieldValue function to access such fields in email notification rules. For instance, in my example, I could use the following syntax: GetFieldValue('моё_самое_любимое_имя')
Using non-ascii characters in message envelope
Using non-ascii characters email envelope is permitted. Nevertheless, you might hit some limitations in your environment. Please check the following page for details: Non-ASCII Characters in Email.
Prerequisites
ClearQuest client version
The package can be used with ClearQuest 7.0.0 or later. Earlier versions are supported in version 1.5 only.
