Byte's account

Hi Duo, I tried another test this afternoon using a textbox. If I enter "Apples' in the text box, sign, clear the value in the textbox so it is now blank, then submit, the value on the final doc will be "Apples". If instead I change it to "Zebras" after signing then "Zebras" will appear on the final doc. So I guess the AJAX call is not triggering if the new value of the field is blank? One of two things would work for us 1\ After the associated signature is executed, the fields should become read-only, or 2\ Before submitting, the fields should be validated, and their most recent values should be reflected on the final document. The second option seems better, because it may not be obvious to the signer why they are being prevented from altering the fields, but either way would work. As it stands, we cannot use the feature because it arguably doesn't honor the intent of the signer.

Thank you Duo, what is the timeline on the new experience?

OK, thanks for the update.