ThingWorx Model Definition and Composer > Alerts > Alert Services with the Persistent Parameter
  
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 (e.g. enabling/disabling alerts, adding/removing alerts, etc.) from the service will remain 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 will still be visible on the thing’s property in Composer.
If the persistent parameter is true, then the action from the service will be 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 will be created and will exist until Tomcat is restarted.
After Tomcat is restarted, the alert will no longer exist. However, if the service was called with the Persistent parameter set to true, then the alert will always exist.
Related Links
Alerts
AddOrUpdateAlert Service Attributes
Alerts with Persistent Properties
Alert Types
Retrieving Threshold Information from Alerts
Automated Monitoring Thresholds