Allow users to configure the "next" button on the template level for signers via API
We often have issues where clients send a document to someone to sign and a number of non-required fields are missed. When the signers use the "next" button, it jumps from one required field to the next, meaning intermediate non-required, but important fields are missed.
1
vote
Josh Sapira
shared this idea