Why are the forms time fields rounding everything to the nearest hour if they include minutes and seconds?
It doesn't seem like anything other than a number field between 0 and 23
Hi Chad,
I don't see the behavior with a simple time field. Could you provide more details about how the time field is set up and when does the value got rounded? And what type of form is being used, new form or classic form?
Thanks,
Ziyan
Here is a video of what it looks like. It might only be with the 24 hour format, by why have mm and ss if it is never used, it really just becomes a 0-23 number field.
I see. The 12:00:00 is being auto selected when 'Enter' is entered. If user change focus by mouse or Tab key instead, the value will be kept.
The user experience seems not good enough, I will file a bug to follow up.
I've reproduced this issue with cloud but not on-prem Forms. Are you using Business Process on cloud?
This is on-prem, actually the video was shown using a keyboard and Chrome, but where we ran into the problem is with the LF App and there is no enter key on a mobile device.
Do you know why we would be running into it within the app?
Missed a step when reproduce with on-prem, can reproduce now.
Experience of fill form in LF App should be similar with using browser. If user fill form with QWE keyboard, there is enter/confirm key right? Or could you specify how you run into the problem without an enter key on mobile device?
I just tested on my mobile using the app. I have an iPhone. If I press the big blue button on the keyboard labeled "Go" then it rounds up my time. If I don't press this it does not round up my time.
This is confusing though, why does Go round up?
Yes, 'Go' on mobile is similar to 'Enter' in keyboard, so the root cause is same. I've filed bug(321708) for this issue, and we will look into it.
As mentioned above, this issue is related to auto suggestion in time field. One workaround is to disable the auto suggestion in time field
https://answers.laserfiche.com/questions/144203/Turn-off-time-picker#144214
This issue has been fixed with Forms 11 Update 2.