Situation: Attribute of an AF element is one of the triggers for Event Frame analysis for sending critial Notifications.
Currently: After creating a new version of an AF Element and setting a new value for the attribute the changed value will possibly not trigger the (Event Frame) analysis (if start trigger is true). This results in missing critical Notifications.
Reason is that the analysis is restarted after a new version is created and the value may be changed before the analysis is operational again. The analysis doesn't see the changed value as an event than.
Periodic triggering may not be a work-around since this will give extra load when frequency and number of analysis is high.
Solution could be: evaluate start trigger on start of analysis.
