We have a client interacting with a fillable PDF that is experiencing different behavior for different users. Here's the following situation:
ScenarioA: Update any field values on the PDF form except digital signature
1. User opens PDF from Laserfiche using Adobe Acrobat Pro, modifies any form field
2. User closes Adobe, is prompted by Adobe to save changes, answers YES.
3. Adobe prompts user to save file at the same temp location on the user's PC where it was stored when opened from LF. File location similar to:
C:\Users\someuser\AppData\Local\Temp\sometempname
4. 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)
5. User chooses "overwrite", and the changed file is imported into the repository, overwriting the previous document.
This behavior is exactly as expected, and functions identically for UserA and UserB.
ScenarioB: Updates any field values on the form INCLUDING digital signature
1. User opens PDF from Laserfiche using Adobe Acrobat Pro, applies a digital signature to the form.
2. User closes Adobe, is prompted by Adobe to save changes, answers YES.
This is where the behavior changes for UserA vs UserB...
UserA...
3. Adobe prompts user to save file at the same temp location on the user's PC where it was stored when opened from LF. File location similar to:
C:\Users\someuser\AppData\Local\Temp\sometempname
4. 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)
5. User chooses "overwrite", and the changed file is imported into the repository, overwriting the previous document.
This behavior is as expected.
UserB...
3. 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. File location:
c:\user\Documents
4. User saves to default location prompted. 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.
5. User must then manually reimport the document to the repository, overwriting the original document.
The differences in behavior seem to be triggered by Adobe assessing the nature of the changes to the document as fundamentally different. I.e., ScenarioA is just a "save changes back to the original file", whereas ScenarioB, the digital signing, creates a hashed version of the document, which it's interpreting as a NEW DOCUMENT and thus it prompts with a SAVE AS dialogue, which exercises a different default for the save location.
What's really odd is the behavior is different for UserA and UserB. The only variation I can find is the OS version.
I also realize there may be saved user preference for saving new documents at play, either in Adobe or the OS, but I'm unable to find it.
If we use the Check-in and Check-out feature, the behavior works fine in all scenarios for both users. So that is what we're currently doing. However, having seen the functionality of just opening the document (without checkin/out) work properly for UserA, the client is wanting UserB to have the same option, thus eliminating the extra steps caused by checking in and out the document.
Any insight on this?
-UserA environment-
OS Client Version: Windows 8.1
LF Client Version: 9.01
Adobe Version: Acrobat Pro 10
LF Options for Open PDF Files set to: "the associated application"
-UserB environment-
OS Client Version: Windows 7 SP1
LF Client Version: 9.01
Adobe Version: Acrobat Pro 10
LF Options for Open PDF Files set to: "the associated application"