Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
On behalf of Celanese InField super users:
When executing a checklist in offline mode on a mobile device; it has been discovered that there is a risk of losing data due to accidentally refreshing the screen. Due to the design of the UI of InField 2.0, it is common to frequently scroll through a checklist when completing. Most users do this rather quickly without giving it much thought. However, when scrolling back to the top of a checklist, a user could be at risk of accidentally refreshing the screen whenever they reach the boundary limit (very top item) of a checklist. This is due to how the touch interface works on the mobile devices. To refresh the browser, the user needs to only press and drag their finger down on the screen window to initiate a refresh. This is a common movement when scrolling through checklists and could be inadvertently initiated.
Would it be possible to include visual indicators or engineers controls that could limit the possibility of this issue occurring? Perhaps something that lets the user know they have made it to the top of the checklist and prevent them from further scrolling and initiating a reset? We will also explore if this is something that could be controlled within the device settings themselves.
Hi@crgomez13 , thanks a lot for this feedback!
For offline mode, this is how the intended functionality should currently work:
With 2) it actually means that a use refreshing the screen shouldn’t result in data being lost. However, when testing this now I see that we have a bug here, so we’ll fix that asap.
Although the functionality is built to prevent data from being lost if the screen is refreshed, I do agree that we can add some logics on 1) to prevent the refresh from happening in the first place. What we can do as a first step is probably to add some validation in offline mode, e.g. “are you sure you want to refresh?”. Could that work?
Br,
Kristoffer
Apologies on the delayed response to this! Thanks for the explanation on this. We were under the impression that if the screen was refreshed during offline mode data capture, the data would then be lost. However, it sounds like the data is still stored and uploaded once connectivity is re-established. Is that correct? Is this still intended to be normal functionality?
In terms of the potential fix for screen refresh, I agree that a validation prompt could work.
We have discussed internally with Ram and agree this is a BLOCKER for Celanese.