Difference between revisions of "Email Notification 1.4 Release Notes"
Line 180: | Line 180: | ||
− | [[Category:ClearQuest]] [[Category:Email_Notification_Package]] | + | |
+ | [[Category:Rational]] [[Category:ClearQuest]] [[Category:Email_Notification_Package]] |
Latest revision as of 14:46, 1 February 2013
Email Notification Package 1.4 Release Notes
Bug Fixed
SMTP Header Line Length Limit
A workaround was implemented preventing address lines with multiple recipients exceeding 1000 characters. It could break SMTP header in previous version.
Creating Perl interpreter failed
A fix for an intermittent issue was implemented. Thanks to Adam Skwersky.
A dot after variable name
In a parameterized text field, a dot placed immediately after variable name is no longer causing any issues.
Multiline SQL queries and DB2
An issue was resolved that was causing issues with some releases of DB2 database.
Enhancements
ClearQuest 7.1.x installation
ClearQuest 7.1.x installation was improved
Expressions in function list of parameters
In list of parameters, there no need to use brackets around expressions. For example,
IF( $a > $b, "a", "b" )
$EmailNotificationRuleName built-in variable
New built-in variable, $EmailNotificationRuleName, was introduced to carry evaluated rule name.
Rules Evaluation Order
You can change Notification Rules evaluation order. Sort key is a text field. All rules are sorted in ascending order by the Order field.
FROM Email address
A parameterized text field was added to Notification rule to customize From address.
- when Notification Rule From field is not empty, it is expanded and used as from address on generated email
- when From field is empty, and email_from database property exists, email_from content is evaluated to be used as from address
- otherwise, email address of the user executing action triggering email is used as from email address
Applying package to a stateless record
Package can be applied to a stateless record type using package wizard (using command line was required in previous release). In order to apply to a record type that belongs to a package, package editing needs to be enabled.
Email self-subscription
Optional self-subscription functionality is available with optional EmailSubscription package.
Access controls
Unified access control was implemented.
Record Type | Action | Permissions |
---|---|---|
udb_visibility | Submit |
|
Update |
| |
Remove |
| |
udb_property | Submit |
|
Update |
| |
Remove |
| |
Email_Notification_Rule | Submit |
|
Update |
| |
Remove |
| |
en_email_message | Submit |
|
Update |
| |
Remove |
| |
Email_Subscription | Submit |
|
Update |
| |
Remove |
| |
Subscribe_Me |
| |
Unsubscribe_Me |
|
Submit action can be enabled for all users by setting Notification_Bypass_Access_Control database property.
Prerequisites
ClearQuest client version
The package can be installed using ClearQuest 7.0.0 or later. Nevertheless, it can be used with pre-7.0 clients as well.
Read More
- ClearQuest Email Notification Package
- Package configuration guide
- Frequently Asked Questions
- Examples