You are viewing limited content. For full access, please sign in.

Question

Question

LF Mobile - If in a no coverage area, can we upload documents or photos to a queue?

asked on February 5, 2014

A prospect is currently evaluating means to capture images at a crash site for upload to a case folder. As there are a number of network blackspots, 3/4G coverage is not available and they have asked the question as to how we would handle this? 

 

Is there a way to take images and have them automatically upload when network becomes available? I know that we could store them on the phone/tablet library and upload from there but will this cause data protection issues.

 

Second part of the question is that they have 2-3 regulatory documents that need a signature capture at crash sites and if no coverage, what is best option to do this?

 

0 0

Answer

APPROVED ANSWER
replied on February 7, 2014

Hi Fearghal,

 

If you're in a no coverage area, you'll want to use the standard camera app on the phone, and store the photos locally until you can re-establish a connection to the Laserfiche server.  Blake has a very interesting idea that I'll be sure to pass along to the Mobile team.

 

As for signing documents at the crash site, you'll probably need to go with a physical signature on a sheet of paper, and scan it into the system later.  You'll need an internet connection to use Laserfiche or DocuSign signatures.  I believe that Arx CoSign doesn't require an internet connection, but it probably does require a laptop.  It might be worth looking into though!

0 0

Replies

replied on February 5, 2014 Show version history

I would not think this is currently possible since when you authenticate with LF Mobile, you are authenticating to the Web Access server. So without a connection to the Web Access server, you would not be able to even log in and tell LF Mobile what folder you would want the document stored in. In a future update it would be interesting if Laserfiche can some how cache the credentials on the mobile device and allow access to LF Mobile and have LF Mobile remember the folder structure. It would be similar to how a cloud storage system works that has a desktop installer. Once it re-establishes connection with the server it would look for documents to be added and upload them accordingly.

 

I know this doesn't help you now, but it would be a great feature to be added.

3 0
replied on February 7, 2014

Thanks for these valid use cases. We know about them and we'll consider implementing them once the design/research is done.

 

There are multiple (seemingly conflicting) requirements - certain customers do not want anything cached on the phone at all- not even a picture to be imported to Laserfiche or document pages/electronic documents (PDFs or Office docs). Others need them encrypted - depending on the security requirements.

 

The goal is to have administrators set a policy which the end-user cannot override.

 

 As for signatures –for some people typing the name in a textbox and an “agree” checkbox is enough, for others applying a private stamp suffices, others need a signature drawn in a signing-pad app (generating an “electronic signature”) and others need the digitally signed documents / submitted forms.

 

 In general, making the app more “offline friendly” is an important goal for future releases. Thanks again for the suggestions.

2 0
replied on July 1, 2014

I have another use case where my end users are accessing documents via the App during a meeting. These documents are their Agenda items.

 

Since their meetings are not always at the same venue, connectivity is not always guaranteed. It would be an awesome feature if the Mobile App allowed for "caching" of specific folders' contents based on a setting by a user/administrator. Further to that, to ensure that users are not caching large files to their devices using Mobile Data, an option to only do this while in WiFi coverage would help or even a limit on total size. Then the docs could be cached while still at home or at the office and then instantly available when they need it.

 

Perhaps tie this in with a time limit, especially since security can be compromised if docs are cached locally to the device and the administrator disables that user while they are out of coverage. The App will never know if the user's been disabled until it comes online again.

 

Caching Template information would be very helpful too, and then only update changes when needed. Slow connectivity unfortunately makes the user experience ugly. It seems as if the Templates and Fields are "Loading" every time you access them. I assume they are downloading each time you request the info.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.