It will read this value upon initialization and then proceed to listen for changes to the property. Setting a binding to persistent is the recommend way to ensure that the value is saved with the component config and loaded upon component initialization.
You could try using the new filterAlarm extension function that is available for both alarm tables, but I’m not sure how useful that would be since there seems to be a delay between when the filter is updated via params.
I’d might suggest adjusting the refreshRate of the alarm table to decrease the delay and improve the experience. Changing the refreshRate changes the interval in which the backend of the component queries alarms. When a difference is detected between the previous data set, the backend will send the data to the front end to process and display.
