M-Files Configuration Frequency Interval

Hi,

The editor seems to render differently depending on...  Something.  Possibly your local PC settings.  In a lot of systems it renders as a 24-hour clock (which then makes more sense as an interval), but when it renders as an AM/PM time it's awkward.

In your instance "every two hours" would be "2am".  Every 14 hours would be "2pm".  As I said: awkward.

This hasn't come up as a significant issue thus far, but I will raise it with the VAF/configuration-editor team at some point to see whether there's a way we can force it to always be in 24-hour mode.

Regards,

Craig.

That is what we figured but additionally you cannot enter a 0 for the first hour so you cannot set an interval less than 1 hour with this issue.

If you place the cursor in the hour section and type "00", does it not move you to the minute section?

If you place the cursor in the hour section and type "00", does it not move you to the minute section?

No, in fact the 0 key does affect the hours at all. Only 1-9 have any affect.

I can't replicate this here (I see "00:00:00"), but I know a man who may be able to.  I will hopefully be able to test this tomorrow.

Craig asked me to test this, as he does not see the AM/PM issue in his environment.

It looks like you indeed cannot set "00" in the hour part. I cannot figure out the exact logic, but it looks like it turns it back to the previous "valid" input there was before as the hour. 

You can change the hour to 00 behind the advanced tab in JSON, then e.g. "00:00:00" will show up as "12:00:00 AM" in the editor. Which, I guess, somehow weirdly makes sense, as "00:00:00" would be midnight :)

One more thing: trying to set the interval to something big like "24:00:00" in JSON produces an "unsupported value" error on the editor side.