Apply non-repetition interval for Notifications sent at Event End
The Non-Repetition Interval in Notification Rules is currently only applied to Notifications sent at Event Start. I would like the Non-Repetition Interval to also be applied to Notifications sent at Event End.
I agree with the comment below. It seems like this is a bug and should be fixed as soon as possible. It doesn't make much sense to have a non-repetition interval only apply to the start and not on the close.
Dirk Pauwels commented
We use start and end on all events related to alarms. Alarms have a tendancy to chatter sometimes. the non repetitive & resend intervals are a nice feature but it has to work on both start and end or it's of no use. Seems like a bug and should be fixed
Ryan Sullivan commented
I see this as a bug rather than an enhancement. In order to get around it, I have had to create > 10,000 TimeStamp tags to add to the analysis for event start tracking; then do a timerange comparison in the event frame start trigger.
Output expressions for EventFrame("StartTime") isn't appropriate since it is linked to an attribute in the EF template and not the Element Template where the evaluation is done; however it would still necessitate all the extra tags for timestamp tracking.
Please also apply the Non-Repetition Interval when the Notify Option "Event Start and End" is used.