CheckBox Validation

Hi Byte, I observed the outbound traffic during Signing Ceremony, it seems after signing and before submitting, if you change field values, the page will send out an AJAX in real time to change the package metadata, which is the desired behavior for you I think. But for checkbox, only when you check the button, an AJAX was sent out, but the uncheck action won't trigger any request, that's why the checkbox always kept checked. I believe the bottom line here is to display an error message and tells signer the checkbox is required to be checked instead of directly showcasing the checked box. Kindly share your opinion and we will escalate this issue to our R&D team! Duo

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.

Hi Byte, Yes, I agree with you that the behavior is not designed properly. I will create a support ticket on your behalf and CC you to have this issue reported. Duo

Hi Byte, I just got a reply from our R&D and PM team that they totally agreed that this situation is handled poorly, and this issue will be corrected in the upcoming new signing ceremony experience. Since this behavior has been there for a long time and this is the first time is has been reported as an issue, the old signing ceremony will not be fixed for this. Duo

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

Hi Byte, Sorry for the late reply, I apologize for that. I tested the use case in new Signing Ceremony and it's already resolved, all fields binding to a signature will be locked after the signature was signed regardless of whether the whole document was confirmed or not. As far as I am informed, the new Signing Ceremony will be brought to Sandbox and ready for public test from 11.30 SaaS version. (Refer to Trust Center for detailed release date) However, I didn't find it documented anywhere officially yet. I will update this thread as long as I got a confirmation on this. Duo

OK, thanks for the update.

Hi Byte, The documentation describing the new signer experience is up in this page. And I also got some upcoming dates: - September 19, 2019 : The New Signer Experience will be available to all OneSpan Sign customers in sandbox starting September 19, 2019. Contact your customer success representative or our support team to enable the New Signer Experience in your Sandbox account. Your transactions and data will remain intact. - September 19 - October 2, 2019 : To ensure a seamless transition to the new environment in production, we recommend that you test the New Signer Experience in Sandbox before enabling it in Production. If you wish to test in Sandbox for a longer period of time, we can create a new Sandbox account. Contact our support team to create a new Sandbox account. Once you have completed testing, you can migrate your Production account at your convenience at a later release. We recommend that you consult the Quick Start Guide to help you perform the necessary steps to migrate both your sandbox or production account to the New Signer Experience. - October 2 - October 16, 2019 : We are currently targeting availability of the New Signer Experience in production between October 2 – October 16. Please visit the OneSpan Sign Trust Center to view the deployment dates. Please note that not all features and functionalities of the signing experience will be included in the first release of the New Signer Experience. Please consult the feature deployment timeline in the Quick Start Guide to help you plan your transition to the New Signer Experience with the features required to support your use cases. Duo