Hi,
After updating the DataMiner Web Apps to 10.6.0 (CU0) with server version 10.5.0.0-17345, I noticed that a Time range component linked to a Trigger component resets its time to the default range every time that the trigger fires. When a user picks a range, for example, Last 7 days, it correctly sets the range to last 7 days and also updates the graphs linked to it, but then as soon as the trigger fires, it resets back to the default range again.
Previously, selecting a range manually used to override the default range in the Time range component. Users could then either have the default range and see as time progressed naturally but also select a specific range they want to investigate further. In short, the trigger did not override and reset to the default range.
Is this the intended behavior or am I thinking of this incorrectly? Is there another method to achieve what I just described?
Thanks!
Hi Arvid,
The behavior that you are expecting is correct. A trigger will make the time range recalculate its current relative time span based on the current time. It should not reset it back to the default configured time span.
I wasn't able to reproduce your issue on my local setup. I suggest you get into contact with tech support (support@dataminer.services) so that we can look into what might be going wrong here. It might have something to do with what else is linked to the time range component.
Hi Wout,
Thank you, I will get in touch with DataMiner support and see if they can gather anything from the logs.