08.08.2025, 09:16
Hello everyone,
We notice that when we create an event on an object with a datatype 1, it is created in the scheduler_events table with a value of true or false.
If custom values are added to objects with a datatype 1, they are created with the keys 0 = customValues1, 1 = customValues2.
The problem is that in /scada-vis/schedulers, when opening an event associated with a Boolean object with custom values, the value of the event displayed and selected is therefore "". The problem appears to lie in eventShowControl, where the true/false values are not converted to 1/0 and are therefore not translated by customValues2/customValues1. This leads to more than just a display issue: if a user modifies any other property of the event without noticing the empty value, the event may be saved with "", which effectively sends 0/false to the object at the scheduled time — potentially causing unintended and critical behavior.
To confirm the bug, we also changed the value of the events from true/false to 1/0 in scheduler_events and noticed that the problem no longer occurred. On the contrary, if we put true/false instead of 1/0, the problem appeared systematically.
Could you advise on how best to handle or resolve this?
Thank you for further help.
Tested on firmware 20240426.
We notice that when we create an event on an object with a datatype 1, it is created in the scheduler_events table with a value of true or false.
If custom values are added to objects with a datatype 1, they are created with the keys 0 = customValues1, 1 = customValues2.
The problem is that in /scada-vis/schedulers, when opening an event associated with a Boolean object with custom values, the value of the event displayed and selected is therefore "". The problem appears to lie in eventShowControl, where the true/false values are not converted to 1/0 and are therefore not translated by customValues2/customValues1. This leads to more than just a display issue: if a user modifies any other property of the event without noticing the empty value, the event may be saved with "", which effectively sends 0/false to the object at the scheduled time — potentially causing unintended and critical behavior.
To confirm the bug, we also changed the value of the events from true/false to 1/0 in scheduler_events and noticed that the problem no longer occurred. On the contrary, if we put true/false instead of 1/0, the problem appeared systematically.
Could you advise on how best to handle or resolve this?
Thank you for further help.
Tested on firmware 20240426.