Thanks for reporting this issue, you are right that LF Connector creates the document and then launches scanning to populate it. We will look into having LF Connector clean up the document if nothing is scanned.

Thanks for the feedback! I was wondering if anyone had a use case where it might make sense to let the user choose to keep the document even if they didn't scan into it. I'm not so sure there is one (I haven't encountered one myself), but I wanted to get people's take before we update the behavior to always clear out the in-progress document in this case. 

Justin, I agree.  I don't see a use case for keeping an empty shell document.  We use them in other places, but if I click scan, and then cancel that scan (maybe I was in the wrong account).  I wouldn't want that shell document sitting empty in the repository.  

We use the idea of a blank shell document in our workflows and document / loan tracking module.   When a new document set is created, we create empty shell documents for all the required documents for that document set (Loan types, new account opening etc.).  Then as the documents come in for that document set, we either move the pages from the document that comes in to the shell it goes to, or our tracking tool offers the ability to scan or capture electronic documents directly into the shell document. 

Then the progress of that document set can be viewed by what required documents have been captured, signed, marked as complete by the MSR or Loan officer, etc.

Also, we send out weekly reports to the stakeholders for all missing required documents to keep everyone on task.

All - we have another customer that is having the same issue that Jason described and they do not want the documents to stay within the folder. Any updates on a fix or patch to resolve this issue? Is the best option to write the workflow to remove the 0 page documents within the folder that they scan documents into?