Describe the bug
Timer interval for refreshing usage data is wrong initialized. This is because APP_TIMER_REFRESH_USAGEDATA is missed in APP configuration settings template. Subsequently, after setup from scratch the configuration value remains "changeIt" and can not be customized (!)
How to Reproduce
Steps to reproduce the behavior:
Setup OSCM from scratch
Run following query in a second DB container
SELECT * FROM bssappuser.configurationsetting WHERE settingkey='APP_TIMER_REFRESH_USAGEDATA';
Observed behavior
Setting value is "changeIt"
Expected behavior
Setting value is one day milliseconds (86400000)
Version Info v19.1 latest, 2021-04-07
Describe the bug Timer interval for refreshing usage data is wrong initialized. This is because
APP_TIMER_REFRESH_USAGEDATA
is missed in APP configuration settings template. Subsequently, after setup from scratch the configuration value remains "changeIt" and can not be customized (!)How to Reproduce Steps to reproduce the behavior:
SELECT * FROM bssappuser.configurationsetting WHERE settingkey='APP_TIMER_REFRESH_USAGEDATA';
Observed behavior Setting value is "changeIt"
Expected behavior Setting value is one day milliseconds (86400000)
Additional context Ask me