When client saved a document to Laserfiche, it just closed and there is no trace of the original document. It disappeared from any folder or recycle bin even.
Has this issue been seen before?
When client saved a document to Laserfiche, it just closed and there is no trace of the original document. It disappeared from any folder or recycle bin even.
Has this issue been seen before?
Hi Chase,
Are you meeting this issue when opening a Word document from Laserfiche Client? Is the network working stable at that time period? During the editing the word document, have you met any error message pops out, like 'The connection to repository has been disconnected.'? In Office Integration 10.1, a similar issue has been fixed. It will prompt save file dialog to make users save the file to local path if Operation time out error is met.
Thanks,
For word document, you have to create a new entry and attach it to the word document activity. Are you doing steps mentioned here?
If you are then are you seeing any error generated or how does your workflow look like.
There is no workflow. They just simply use the add-in in Word to save a document in Laserfiche.
Also I believe that guide is for pushing into a word file with 10.1 version. They are running on 9.2
I am sorry i thought you were talking about workflow activity. Your issue occurs when they are either not connected to LF Repository or internet and changes to word document ends up in temp folder. I am not sure how LF handles that situation.
If it happens again you should open up a case.
They are opening the document in Word from Laserfiche Client. Network is very stable. I get no errors. When trying to test myself I saw no issues. It pushed back into Laserfiche as expected. I will recommend they update to 10.1 and see if that resolves the issue in the long run for them.
Thanks.
We are currently on 10.2 and have a staff member experiencing this issue. We hope to go upgrade to 10.3 by June of this year, but it sounds like this issue should not be happening in 10.2 as it is. Has your issue been resolved with recent upgrades, or is there another solution to this problem?