The differences in behavior seem to be triggered by Adobe assessing the nature of the changes to the document as fundamentally different. User must then manually reimport the document to the repository, overwriting the original document. Because the document is stored to a DIFFERENT location, the Laserfiche Client does NOT detect a change to the file, and therefore does NOT prompt with the expected "Laserfiche Electronic Document" pop up.ĥ. Adobe prompts user to save file at at a DIFFERENT location than the temp location on the user's PC where it was stored when opened from LF. This is where the behavior changes for UserA vs UserB.ģ. User opens PDF from Laserfiche using Adobe Acrobat Pro, applies a digital signature to the form. ScenarioB: Updates any field values on the form INCLUDING digital signatureġ. This behavior is exactly as expected, and functions identically for UserA and UserB. User chooses "overwrite", and the changed file is imported into the repository, overwriting the previous document. Laserfiche Client detects the change to the file at the temp location, and prompts with the expected "Laserfiche Electronic Document" pop up, noting the file has been modified, and presents options to save to the repository (i.e., new version, overwrite existing, etc)ĥ. File location similar to:Ĭ:\Users\someuser\AppData\Local\Temp\sometempnameĤ. Adobe prompts user to save file at the same temp location on the user's PC where it was stored when opened from LF. User closes Adobe, is prompted by Adobe to save changes, answers YES.ģ. User opens PDF from Laserfiche using Adobe Acrobat Pro, modifies any form fieldĢ. ScenarioA: Update any field values on the PDF form except digital signatureġ. We have a client interacting with a fillable PDF that is experiencing different behavior for different users.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |