Information about a small UX change in Sign API v2
1.What the change is about
The change is about ensuring that the signer opens all documents to be signed, before actually signing.
2.How the UX change works
The UX for the signer will simply disable the sign button, until all documents have been opened/scrolled into view, ensuring that the signer has opened all documents before signing.
2.1 Disabled sign button as not all documents are read
3. Why we introduce it
We introduce this small UX change to make it even clearer to the signer that there are multiple documents to review, before signing. It is also related to the freedom customers have today with the possibility to provide their own signText, which is displayed in the consent dialogue window, upon pressing the sign button.
From API documentation on signText
It is common to provide a signText that ensures that the signer consents to having read and understood the documents and their content. The default signText (if none is provided): “I have read and understood the presented documents and am ready to start signing”.
With the new UX change it is ensured that all documents are opened in case the customized signText provided by customers would leave out a clear consent formulation about having read and understood all documents.