Alert Services with the Persistent Parameter
Several alert services contain the persistent parameter. The following behavior is consistent for alert services with this parameter:
• If the persistent parameter is false, then the action (for example, enabling/disabling alerts, adding/removing alerts, etc.) from the service remains active until Tomcat is restarted. These changes are not visible in Composer. For example, if you remove an alert using the RemoveAlert service without persisting it, the alert is still visible on the thing’s property in Composer.
• If the persistent parameter is true, then the action from the service is permanent and reflected in Composer.
The following alert services contain the persistent parameter.
• AddOrUpdateAlert
• DisableAlertsForProperty
• DisableAllAlerts
• EnableAlertsForProperty
• EnableAllAlerts
• RemoveAlert
• SetBooleanAlertParameter
• SetDateTimeAlertParameter
• SetIntegerAlertParameter
• SetLocationAlertParameter
• SetNumberAlertParameter
• SetStringAlertParameter
As an example, if the AddOrUpdateAlert service is called to create a new alert on a property with the Persistent parameter set to false, then the alert is created and exists until Tomcat is restarted.
After Tomcat is restarted, the alert no longer exists. However, if the service was called with the Persistent parameter set to true, then the alert always exists.
Related Links