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

Discussion

Discussion

Forms - Read Only Required for Signature Fields - How and Where is it set?

Forms
Updated July 12, 2017
posted on September 19, 2016 • Show version history

If Read Only is required for signature fields to maintain the image, how and where do we set this. I have tried setting read only at the next user task, tried setting the whole form to read only, and removing the read-only attribute on the specific signature field. It just seems to ignore all javascript relating to calling signature fields.

0 0
replied on September 19, 2016

So your issue is when the whole form is set to read-only, the custom JavaScript related to the signature doesn't work? But it works when the signature field itself is set to read-only? Can you give sample for your customize JavaScript?

0 0
View 3 previous replies
replied on September 19, 2016

Well for example when the form goes to the next user for a signature, I want to set the signature to read only so that the image is not lost. I do this on the form when it is sent to the next user right?

 

So I would do this

 

$('.sig1 input').attr('readyonly',true);

or 

$('.sig1 input').prop('readyonly',true);

Neither seems to work. Also do I need to set the field to read only before the task moves to the next user? Looking for the standard method of making sure we don't lose the signature.

0 0
replied on September 20, 2016

Use JavaScript to set the signature field to read-only won't have any effect. Whether to display the signature data submitted from previous step or show signature control is decided in the backend when generating the form, not through JavaScript.

To retain the signature, you need to use separate forms for separate steps(you can just copy the original forms), in the form used for the user task, set the signature field to read-only. 

0 0
replied on May 10, 2017

Is there going to be a option to allow this in future releases?

0 0
replied on July 12, 2017

Under the signature field options, there is an option that I checked that made this work. When the form is sent through the process to others, the signature is maintained, but new signatures can be added where necessary. I did have the signature field in a collection, though, which makes a difference.

 

0 0
replied on July 12, 2017

This must be in forms 10?  I do not see this option in 9.2

 

0 0
replied on July 12, 2017

Yes, we're on Forms 10, sorry for not specifying. I never tried it on Forms 9, so I don't know.

Also, I don't have this option unless the signature is inside of a collection. So in one scenario, I added it as the only field in a collection (and removed the ability to "Add" to the collection) while hiding the header also. So when the form loads, it looks like a regularly placed field, even though it's technically in a collection on my end.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...