-
Feature Request
-
Resolution: Fixed
-
L3 - Default
-
7.7.0
-
None
One of the things I always liked about engine configuration is that when it comes to timers/intervals config, I did not have to think if the long value that is expected represents millis, seconds, days, ... I would just use a clear, unambiguous ISO statement.
I am confused now that with the introduction of the TTL for history clean up you changed this and I now can only use a number of days ...
I would love to have support for ISO statements here. As a fall back, since the release is out now, maybe the rule could be: if it is numeric, stick to days, if its a String, interpret it ...
This is the controller panel for Smart Panels app
TTL for history cleanup should support ISO-8601 format
-
-
Resolution: Fixed
-
L3 - Default
-
7.7.0
-
None
One of the things I always liked about engine configuration is that when it comes to timers/intervals config, I did not have to think if the long value that is expected represents millis, seconds, days, ... I would just use a clear, unambiguous ISO statement.
I am confused now that with the introduction of the TTL for history clean up you changed this and I now can only use a number of days ...
I would love to have support for ISO statements here. As a fall back, since the release is out now, maybe the rule could be: if it is numeric, stick to days, if its a String, interpret it ...
This is the controller panel for Smart Panels app
-
Roman Smirnov
-
- Votes:
-
0 Vote for this issue
- Watchers:
-
5 Start watching this issue
- Created:
- Updated:
- Resolved: