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

Question

Question

When sending in form as new version why does format change?

asked on August 5, 2016

In response to my prior questioning about 'losing' a signature when the form is not set for " make read only to users " in post https://answers.laserfiche.com/questions/101898/Why-isnt-the-native-Signature-appearing-on-form-in-repository#repliesToMain I chose to save the document to the repository BEFORE any user tasks were executed.

Since I would be saving two copies of the form, the one with the signature and the completed form (with changes and without the signature) I set the folder to track versions on existing documents and subfolders.

When the process completed, I noticed that the completed form ended up as three pages instead of two pages.  The difference between the signature version (1) and the completed version (2) is that the hidden form content was saved as part of the completed version.

Why does this happen? How do I get it to save the correct fields?

I checked Client vs. Web Access and found that this holds true there as well.  In addition, in the client, some of the template fields show up in different fonts on the signature version vs. the completed version.

V1 - Signature.PNG
V2 -Completed.PNG
V2 -Completed.PNG (133.97 KB)
0 0

Replies

replied on August 8, 2016

How did you hide those fields on the completed form? By field rules or custom JavaScript?

Can you share your field rules/custom script here?

0 0
replied on August 8, 2016

Morning Rui,  I used field rules to hide the fields.  I attached images of the sections that should be hidden in this example as well as the field rules that I have for this form.

8-8-16 hidden sections.PNG
8-8-16 field rules 1.PNG
8-8-16 field rules 2.PNG
0 0
replied on August 8, 2016 Show version history

Ran some more passes on this business process where I kept the folder versioned, but named my signature version differently from my completed version.  I did this to see if I had the same issue with sections appearing when they shouldn't.  All four tests where I sent the signature version into the repository under a different name resulted in the correct sections showing up in both the signature and completed versions of the form.

I changed the document name on the signature version back to the same name as the completed version and tested another time.  This time using a Change option on the form.  What happened was the reverse of the test from Friday.

On the signature version (first save to repository-V1) I got the Remove section appearing and no signature on the form. On the completed version (V2) I got the Change sections with no Remove sections.

Same field rules, but the first and second saves to the repository acted differently than the sample I sent on Friday.

8-8-16 ver test 5 v1.0.png
8-8-16 ver test 5 v2.PNG
0 0
replied on August 8, 2016 Show version history

Thanks for the testing Michelle.

I tried with the same field rules and enabled tracking versions in repository, but didn't get the issue in my environment.

Could you please contact your VAR and open a support case on this issue?

0 0
replied on August 9, 2016

Understood.  I will contact my VAR.  Thank you.

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

Sign in to reply to this post.