Our system started out with FPMI/FSQL, and then we migrated to 7.3.3. We use external providers for our SQLTags so that we can manipulate certain aspects of tags on our own programmatically.
One of the actions we performed was to disable an alarm, but to still keep all of the threshold information (“maintenance mode” as we call it). This would involve us grabbing the alertmode from the sqlt_meta table (intval of 1 for digital, 2 for analog), and storing this information in a separate table. We then set the intval to 0, reload the tag, and acknowledge/clear any active alerts.
Since our upgrade to version 7.6, this is no longer working for us. If we place an active alert into maintenance mode, the alert clears as expected, is acknowledged, and disappears from our alert table, but shortly returns again.
It seems as if this functionality is somewhat mimicked through the shelving functions, but we would like to indefinitely disable an alarm without losing the threshold info until any work being performed is completed, during which we would re-enable the alarm. Is there a scripting function I can use to do this work for me?
Is the sqlt_as table no longer used? Can I replicate this functionality through the new sqlt_alarm and sqlt_alarm_meta tables which were created in the upgrade?