#Docusign2 discussing

Hi everyone,

I am facing an issue with the DocuSign Apps Launcher package in a Salesforce Lightning environment. I recently switched from a free trial account to a paid eSignature subscription.

The entire signing process and routing loop work perfectly—the email template goes out via our custom button, the internal user signs, the candidate signs, and the envelope status reaches "Completed" in DocuSign. However, no data is writing back to Salesforce.

What I Have Done / Configured:

1. Object: Custom object Job_Application__c
2. Document Writeback: Checked “Save completed documents back to the Salesforce Job_Application__c Record” with the filename format set to “Document Name + Envelope Status +.pdf”.
3. Field Updates: Under the Options step, I have mapped three specific background field updates based on envelope events:
   • Envelope Completed $\rightarrow$ Updates a custom checkbox field Candidate Accepted Offer to True (Checked)
   • Envelope Declined $\rightarrow$ Updates a custom checkbox field Candidate Rejected Offer to True (Checked)
   • Envelope Voided $\rightarrow$ Updates a custom checkbox field Candidate Rejected Offer to True (Checked)
4. Permissions: I am running this process using a System Administrator profile.
5. Validation Rules: There are no validation rules active on the Job_Application__c object that would block edits or file attachments.

The Issue:

Even though the envelope finishes successfully on the DocuSign side, the completed offer letter PDF does not attach to the record's Notes & Attachments / Files related list, and the custom checkbox fields remain unchecked (False).

Note: Interestingly, this entire automation loop worked flawlessly when I was testing it on a free trial DocuSign account. The issue only started after migrating to the official paid eSignature subscription plan.

Has anyone encountered this sync drop after changing subscriptions? Where should I look to ensure the background webhook/DocuSign Connect interface is properly authorized to push data back into Salesforce?

Any guidance or troubleshooting steps would be highly appreciated!

Thanks in advance! 

#Docusign

When a user sends a contract off for signature through docusign they are receiving an email from "dse_demo@docusign.com" How do I change that email?  #Docusign

@* Sales Cloud - Best Practices *

• I want to write Apex to do exactly what the docusign "custom button" does. Is this possible and does anyone have experience with this or know someone who does?

CURRENT PROCESS

• When you create an Envelope Template in the DSFS app, it auto-generates a "custom button" that you can add to the target object's page layout. This allows a user to click this button when viewing a record detail page, which will then trigger the envelope to be created and document(s) sent for signatures based on however you configured the Template. All the button does is execute the Template settings you configured.
  • This is standard, OOTB functionality.

DESIRED FUTURE STATE PROCESS

• I want to replicate the exact same OOTB functionality as the docusign "custom button", EXCEPT that I want it to be triggered AUTOMATICALLY when a record update action occurs. Meaning, instead of a user having to click the button to start the docusign process, I want the button to be "clicked" automatically whenever certain record update criteria are met.

MY "working draft" SOLUTION

• After-save record-triggered flow with an Apex Action element.
  • SOURCE 1 - How to send an envelope from a Salesforce flow
  • SOURCE 2  - Sending with merge fields using the Apex Toolkit
  • The record ID, merge field values, and other required information would pass through to the envelope from the record-triggered flow, and then everything else should happen just like it is configured in the Template.

WHY

• Because we have an application process where dozens of "agreement" pdf contracts are sent out for e-signatures every week when the are placed in status "application accepted". Right now, someone on our team has to check each day for any Applications in the "application accepted" status, then open each one, and click the "send for signatures" button on the record detail page. 

1. The Template is set to "send now" so there's absolutely no reason for a human user to need to be involved.
2. If the human user is OOO or just overly busy, the sending of the agreement contracts can be delayed.
3. The volume of agreement contracts having to be sent out every week is large enough that this takes a decent amount of the human user's time. 

#Apex #Docusign #DocuSign For Salesforce #Flow