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

Question

Question

Can't save signature throughout multiple process stages.

Laserfiche Version 11 Forms
Updated May 9
asked on May 9

I've been having an issue with saving signatures through multiple process stages. I'm currently using modern designer on Laserfiche 11. I have a form that on submission we need to carry along the signature throughout the review stages. After some research the main thread that got me moving in the right direction was this:

https://answers.laserfiche.com/questions/216947/show-signature-image-inside-html

I figured since the signature variable is save and preserved when moving between stages that I could just grab it and put it into a custom html field. 

using this code snippet from the above answer and tweaking it a bit better fit my scenario; I ended up with this:

I had it set to onFieldChange for testing purposes, but this takes the image generated from the signature and appends it to a preexisting block of custom html. The custom html block looks like this:


This whole setup works as intended as once the user signs, that signature data is grabbed and placed within the div. My initial assumption was that would save the html and would continue onto the next process stage. Also note following the suggestion from this thread: 

https://answers.laserfiche.com/questions/209594/LFForm-object-ChangeFieldSettings-in-Custom-HTML-field-does-not-save-changes-to-repository#209812

I set the form to read-only, or at least I think I do. I'm not quite sure how or when the form needs to be set to read-only, but from my research I know that any change can only be saved when the form is in read only. Of course, this was the first thing I tried before going down this path, along with following the suggestion of this thread:
https://answers.laserfiche.com/questions/64696/Forms-92-Signature-Not-Carrying-Through-Steps

Keeping the field as read-only or moving over to a read-only field does not maintain it through steps. I tried to disable it using field rules but that didn't work and setting it to read-only after the fact also does not work. I know through the process monitor that the variable is populated with the signed signature, but I have not had any luck in even touching it after the default stage. If anyone has struggled with this or has any suggestions that would be appreciated. I believe it's right there and the main hurdle is finding a way to save the custom html after its populated. 
 

Alternatively I noticed that the signature is signed, and populated when monitoring the variables of the submission.


Is there a way to make use of this variable in the review stage or at least in the repository saving step.


 

0 0

Answer

SELECTED ANSWER
replied on May 9

With self-hosted, that functionality wasn't added until Laserfiche 12 (I believe it was with the first release in November 2024).

Since this post is tagged as Laserfiche 11, it unfortunately means this isn't an available option, without upgrading to 12.

My recommendation would still not be to try to do this with code however.  My recommendation would be to make a second copy of the form, with the only difference being that the signature field is marked read-only on the second copy.  Any tasks that need to refer to the form with the signature field already populated would use the second form where it is read only.

This does mean you don't have a single-form solution, so if that is important to you, you'll want to look into upgrading to 12 to get the functionality that @████████mentioned.

3 0

Replies

replied on May 9

If you select "Mark field as read-only when signed in a previous step", it will carry the signature through the rest of the process, including the save to repository task. No javascript or html required.

1 0
SELECTED ANSWER
replied on May 9

With self-hosted, that functionality wasn't added until Laserfiche 12 (I believe it was with the first release in November 2024).

Since this post is tagged as Laserfiche 11, it unfortunately means this isn't an available option, without upgrading to 12.

My recommendation would still not be to try to do this with code however.  My recommendation would be to make a second copy of the form, with the only difference being that the signature field is marked read-only on the second copy.  Any tasks that need to refer to the form with the signature field already populated would use the second form where it is read only.

This does mean you don't have a single-form solution, so if that is important to you, you'll want to look into upgrading to 12 to get the functionality that @████████mentioned.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...