Loading
Salesforce now sends email only from verified domains. Read 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
          Enable OAuth 2.0 With Custom Settings In Omnistudio for Managed Packages (Managed Package)

          Enable OAuth 2.0 With Custom Settings In Omnistudio for Managed Packages (Managed Package)

          For the managed package runtime, salesforce recommends the more secure OAuth 2.0 for DocuSign. We've introduced a custom implementation for you to switch from OAuth 1.0 to OAuth 2.0 authentication for Omniscripts using custom objects (OmniScript__c). If you’re setting up DocuSign for the first time, you don't need to change the custom settings. If OAuth 2.0 authentication isn’t loading or you’re still using OAuth 1.0, enable OAuth 2.0 with the custom settings.

          Managed Package app icon This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.

          In OAuth 2.0, the DocuSign Send On Behalf Of (SOBO) functionality is supported only through Named Credential. To send or sign DocuSign on behalf of another user, create a Send On Behalf field in the User object and assign the Send on Behalf named credential from that field in the user’s page. See Setup Send on Behalf of Another User.

          1. To change to OAuth 2.0, open Setup.
          2. Go to Custom Code | Custom Settings.
          3. For General Settings, click Manage.
          4. Click New.
          5. Enter the name as DocuSignAuth. The name and value fields are case-sensitive.
          6. Enter the value as OAuth 2.0.
          7. Save your changes.
           
          Loading
          Salesforce Help | Article