I am trying to validate that a signature field holds a value and run a form record rule, only if it holds a value i.e has been signed. The form record rule runs even if the signature field has not been touched.
I have been on this for over a week trying alternative methods to achieve what i need but it comes back to needing to ensure the signature field holds a value.
The form record rule should run when the signature field ‘is not blank’. It still runs.
Can anyone help with this, it’s driving me crazy and preventing months of work from going live.
Thats an interesting question, and I feel your pain if this is what is holding you up now.
From what I can see the signature pad function is an Angual/javascript applet and it creates a png image of a signature - if signed. And a blank png image if not. The test for the signature being there will always show that it is, because there is always an image - even a blank image.
Of course the blank images (unsigned) are smaller in size, and all blank images are same small size, but as there is no pipe that accesses file sizes of stored files that difference can’t be used.
My only suggestion is to see if you can create a Javascript that will detect the use of the Angular signature pad function. But I guess you already tried that.
A couple of alternative ways to approach your workflow:
Create a signature field and make it required.
Create a radio option field with only one option (like “Yes”)
Place the radio option field below the signature field in the page builder and add a title that says something like “Do you want to confirm all information and signatures are accurate”, make the radio button a required field so they have to click “yes” to proceed.
Set a record rule based off of the “Yes” radio button to trigger whatever you have set up already.
Option 2:
Same concept for the required signature field and a radio option field however, don’t place the option field on the front-end page.
Create one record rule that will trigger the option field to be set as “Yes” when the form is submitted.
Create a second record rule that will run whatever you already have in place.
Important for Option 2, the record rule to set the option field must be first in the list of record rules in the form submission. Forms will run record rules top to bottom/first to last.
Not sure if either of these will be a good fit but sometimes it best to get yourself out of a focused mindset to make something work when other workarounds exist.
I had started to venture down this route and your response has confirmed its the best solution.
I have this working now which i’m really pleased about. We can remove Adobe sign from our work flow now and all e-signing is automated in the app (well once i have finished tetsing it).