NodeJs0Common API Tasks🐈: Require your signers to provide a reason when they decline to sign

[ad_1]

Welcome to an splendid new edition of the CAT (Common API Tasks) blog series. The CAT blogs provide all you need to complete small, specific, SDK-supported tasks using one of our APIs. You can find all articles in this series on the DocuSign Developer Blog.

In today’s edition I’m going to discuss what happens when your signers decline to sign an envelope that was sent to them. By default, a signer can choose Decline to Sign from the top-right menu, and if they do so, the envelope gets voided without the signer giving any reason.

It may be beneficial to require that your signers (or your customers’ signers) have to provide a reason before they can get the envelope voided when they decline to sign it (similarly to how the sender is required to do so if they wish to void an envelope).

This can be done account-wide for all envelopes that were sent from the account by going to the Signing Settings section of the web admin tool and checking “Require a reason when a recipient declines to sign” and updating the settings for the account.

Once this is done, the signer will only be able to to decline (and thus void the envelope) after providing a reason in the following dialog:

Of course, like everything else in this blog series, we show you how to do things programmatically, using the DocuSign APIs and the DocuSign SDKs.

The following code snippets update the account’s settings (For the account that was used to authenticate to DocuSign for the purpose of making API calls) and change it to require signers to provide a reason when they decline. Note that this code can only be run if you authenticate as a user with admin privileges.

C#

Java

Node.js

PHP

Python

Ruby

That’s all, folks! I hope you found it useful. If you have any questions, comments, or suggestions for topics for future Common API Tasks posts, feel free to email me. Until next time…

Additional resources

Disclaimer

DocuSign Inc. published this content on 23 January 2023 and is solely responsible for the information contained therein. Distributed by Public, unedited and unaltered, on 24 January 2023 17:01:54 UTC.

[ad_2]

Source link

Leave a Reply

Your email address will not be published. Required fields are marked *