Preventing Timecard Manipulation with Hardware Battery Time since Power Cycle

[Wesley]

In the way AppSheet can see a unique device identifier can it receive the device hardware battery time since power cycle? I don’t understand the specifics but the key is the battery time since power cycle being un-changeable in a way system time isn’t, and comparing battery run time before/after successful syncs and when the record is saved.

I don’t need this but it seems it may help - key would be the employee in field with no service couldn’t let their phone die between syncs.

Prevent timestamp manipulation? Questions

Is there a way to ensure that the timestamp is the actual time and not the device’s time? We just discovered someone manipulating their timecard by manually setting the device time and then punching in to show they were on time. Sneaky… I can go into the audit logs which timestamps the actual time of the operation to verify but this would get pretty cumbersome when trying to manage 35+ timecards. The device’s belong to the employees and we install the app on their phone. Thank you.