Environment : LF Forms 10.3.1.635, Mobile Server 10.4.0.67179, Application (Android) 10.4.1.100858

'Read-only' field state not honored in Forms when used on device app, if 'Required' is also checked.

We have a form that uses single line fields as containers for other selection / drop-down results. We do this to maintain a non read-only state in the fields we grab data from, while preventing modification in the displayed fields (being informative only). The read-only fields are populated using '=VariableName' Calculation in the 'Advanced' tab, referencing the selection field.

The issue is that the Android Laserfiche app is permitting input in our single line fields when both 'Required' and 'Read-only' states are ticked. It will indeed populate the intended 'VariableName' correctly but offers a blinking cursor for text input when tapping on the field, and can receive characters from the (phone) on-screen keyboard. Submission permitted, but saved form may display unintended characters if said read-only fields are modified.

Seems to happen with multi-line fields also. Other fields we use in the same manner without the 'Required' state, just 'Read-only', rightly restrict any input (no blinking cursor at all). And logging into the same form on a PC through the web does present the blinking cursor in the field but no entry occurs / permitted from a desktop or on-screen keyboard.

I believe this was happening in the next version of the Android app as well, but reverted back before thorough testing as there was a broken placeholder for the barcode icon and haven't been available to see if that was the extent of issues in that version.

An FYI, don't expect it's intended behaviour, not sure of other platforms.

Thanks,

Grant