Forgive me if this has already been answered, but I couldn’t find anything in the forums or manual on this.
We’re running into a little bit of a headache with the UDT’s that we have configured. Whenever we make edits to the UDT it causes any alarms configured in the UDT to re-evaluate and re-send any alarm notifications that were already active. It makes sense why it happens, but I was wondering (and hoping) if there is a way that we can prevent alarms - that were active prior to the update - from creating a new alarm event in the journal and also prevent them from resending the alarm notification? We have quite a few instances of this particular UDT so it can create quite the barrage of notifications and new alarm events in the journal.
Thanks in advance!