Loading
Salesforce now sends email only from verified domains. Read More
Help Agent Performance DegradationRead More
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Use the DocuSign Signature Action to Sign Documents From Within an Omniscript (Managed Package)

          Use the DocuSign Signature Action to Sign Documents From Within an Omniscript (Managed Package)

          For the managed package runtime, after you prepare the DocuSign template and map the fields from the Omniscript to the template using an Omnistudio Data Mapper Transform, you can create a DocuSign Signature Action in the Omniscript. When the action runs, a DocuSign window opens containing the prefilled document. The user must sign or decline to sign the document before continuing the Omniscript.

          To create a DocuSign Signature Action:

          1. From the Omniscript Designer Build tab, drag a DocuSign Signature Action element from the Actions section into a Step or block element, where it renders as a button.
            Note
            Note

            Edit Block doesn't support the DocuSign Signature action.

          2. In the DocuSign Signature Action properties, click Add Template. The Edit Template window opens.
          3. Select your DocuSign Template.
          4. Select a template Role. Roles are defined in the DocuSign template.
          5. In the DR Interface field, enter the name of the Data Mapper Transform.
          6. Click Save. The Edit Template window closes.
          7. Enter a Signer Name and Signer Email.

            The Signer Name and Signer Email fields support merge fields. For example %FirstName% %LastName% merges the contents of the FirstName and LastName fields into the Signer Name field during runtime.

          8. Add an Email Subject and Email Body that recipients receive after signing.
          9. If needed, enter a DocuSign Return Url that replaces the DocuSign window after signing is complete.
          Note
          Note

          To use an Omniscript with a DocuSign Signature Action in an Experience Cloud site, add the OmniScriptLwcDocuSignViewPdf Visualforce page permission to any profiles using the Omniscript.

          When the DocuSign window opens, a node is written to the Omniscript data JSON in this format:

          "DocuSignElementName": [
            {
              "status": "Declined",
              "envelopeId": "xyz123"
            },
            {
              "status": "Completed",
              "envelopeId": "xyz123"
            }
          ]

          A new status and envelopeId are generated every time the DocuSign window launches. Statuses include Completed, Declined, and In Process.

          If you’re a developer overriding the OmniScriptDocuSignReturnPage in your Omniscript, post the DocuSign Return Page status back to the Omniscript using window.parent.postMessage. For example:

          window.addEventListener('DOMContentLoaded', function(event){
          var domClass = '';
          var searchStr = event.currentTarget.location.search;
          
          searchStr = searchStr.substring(searchStr.indexOf('&event='), searchStr.length);
          searchStr = searchStr.substring(searchStr.indexOf('=') + 1,searchStr.length);
          
          if(searchStr === 'signing_complete') {
          domClass = document.getElementById('signing_complete');
          domClass.style.display = 'block';
          } else {
          domClass = document.getElementById('signing_failed');
          domClass.style.display = 'block';
          }
          _window.parent.postMessage(searchStr, '');_*
          });
           
          Loading
          Salesforce Help | Article