Some suggestions...

I noticed that when an event (normal) clears out an alarm (critical) and you request an email to be sent with a message built up using macros, well the email is nearly empty as the macros are returning empty strings (%M, %A... only severity and time/date are given).
Email subject is: [%S] %A - only severity returned
Body content is: Alarm: [%S] %A\nNode: %n [%a]\nTime: %t - %A is not returned!

Using %m is not always convenient!

All this because the cleaning event is not creating any alarm. The only flexibility is about the message key for cleaning related events.

It would be nice to still be able to define a message text available for action such as sendmail.
You will most probably suggest to use %M or %[name] but for some scenarios no script is used. So it is quite cumbersome to have to define a script just for the sake of having a text message available.

Suggestion: get events configured as for alarms and give the option to display event in alarm list or not. Then message text still exists and is available for actions. Further extension: active event list, history event list, archives. Created events are displayed in alarm list. When ack'ed or terminated, then instead of trashing them from the alarm list, park them in a history event list (new window) for a while (configurable) then trash it... or preferably archive it in a text file.

Best regards,

Jdamien