Skip to main content

There is a DocuSign CLM which has an Integration with Adobe Esign through DocuSign CLM (Admin-> Integrations -> Electronic Signature). Whenever user sends a document for signature via signature step inside workflow, the user is not required to click on “Preview/Edit Signature Fields” (See below screenshot).
Many times, user skips to add the signature fields by not clicking on this and then Adobe adds the sign fields to the end of the document by default. We need to mandate this inside the Review and Send for Signature Step so that user cannot proceed further before adding the signature fields inside the agreement.
 

 

Hi ​@Pawan Gangwani,

Hope all is well,

To prevent users from proceeding without adding signature fields in DocuSign CLM when integrated with Adobe Sign, you can take the following steps:

 

Workflow Configuration

Check if you can configure the workflow to make the signature fields mandatory. This may involve setting up rules that prevent users from moving past the "Review and Send for Signature" step unless signature fields are added.

 

Implement Validation Rules

If your DocuSign CLM account allows for custom validation, create a rule that checks for the presence of signature fields. If the fields are not present, display an error message and prevent the user from proceeding.

 

Restrict Access

Adjust user permissions so that they cannot send documents for signature unless they have added the required signature fields. This may involve creating specific roles or permissions that enforce this requirement.

 

Pre-Send Checks

Implement automated checks that run before the document is sent for signature. If signature fields are missing, the system should block the action and prompt the user to add the necessary fields.

 

Review Integration Options

Look into the integration settings between DocuSign CLM and Adobe Sign. There may be options to enforce signature field requirements directly within the app connector.

 

API or Custom Scripts

DocuSign API or a custom script can also help to enforce this requirement by intercepting the send action and checking for signature fields.

 

Test the Configuration

After implementing changes in UAT, conduct thorough testing to ensure that users cannot bypass the requirement. Gather feedback from users/testers to identify any issues or areas for improvement.

 

I hope this helps!