Skip to main content
Blog
Home/

Trending Topics: Latest from our forums (March 2022)

Author Inbar Gazit
Inbar GazitSr. Manager, Developer Content
Summary3 min read

See how our most popular recent threads on Stack Overflow can help you solve your own development issues.

    • Additional resources

    Table of contents

    Here are some of the latest popular questions that the Docusign developers community asked on Stack Overflow in the month of March 2022. You too can ask questions by using the tag docusignapi in Stack Overflow.

    Thread: Docusign C# SDK setting prefilled fields

    https://stackoverflow.com/questions/71388823/

    Summary: The developer is trying to use the C# SDK and the pre-fill fields feature and send an envelope based on a template that includes pre-fill tabs. They are getting an error that says A Required field is incomplete. TabId:

    Answer: The term pre-fill tabs relates to a specific feature of Docusign that enables the sender to provide data in the envelope that is not tied to any recipient. This feature does not support using templates to send envelopes. You can only use this feature when sending envelopes directly, not based on a template. However, there are other ways to update information in an envelope without using pre-fill tabs. You can create regular text tabs that are read-only and cannot be modified by the recipient. You then assign them to the first recipient based on routing order. You can use the eSignature REST API to update the values of these tabs. You can find a step-by-step guide for this scenario with code examples in eight languages on the Docusign Developer Center.

    Thread: How to pass phone verification in Docusign?

    https://stackoverflow.com/questions/71491231/

    Summary: This developer is using Visual Basic.NET (VB.NET) with the Docusign C# SDK and is attempting to use the Phone verification option for Docusign and is running into some issues.

    Answer: Phone verification can be set from the API, but it does require that your developer account has the feature enabled. Once enabled, you can use the following VB.NET code with the Docusign C# SDK version 5.9 or above to get a recipient using phone verification (that can be either SMS or phone call):

    Dim workflow As RecipientIdentityVerification = New RecipientIdentityVerification() With { 
      .WorkflowId = workflowId, 
      .InputOptions = New List(Of RecipientIdentityInputOption) From { 
      New RecipientIdentityInputOption With { 
        .Name = "phone_number_list", 
        .ValueType = "PhoneNumberList", 
        .PhoneNumberList = New List(Of RecipientIdentityPhoneNumber) From { 
          New RecipientIdentityPhoneNumber With { 
            .Number = phoneNumber, .CountryCode = countryAreaCode 
          } 
        } 
      } 
    }
    
    

    Tip: you can use Telerik Code Converter to convert any C# code to VB.NET code

    Thread: How to obtain Access Token using production environment in Docusign?

    https://stackoverflow.com/questions/71618566/

    Summary: The developer finished the go-live process with an integration using JWT Grant for authentication and is having trouble getting the integration to work in the Docusign production environment.

    Answer: When using JWT Grant authentication and changing from the developer environment to the production environment, you have to do the following:

    1. Pass go-live and get approval to have your integration key (app) in production.

    2. Promote your IK to your production account.

    3. Create a new RSA key for the new IK in the production account. You cannot use the RSA key from your developer account.

    4. Change the URL for authentication from https://account-s.docusign.com to https://account.docusign.com.

    5. The user ID for the user will be a different GUID; you’ll need to update.

    6. The account ID for the account will be a different GUID; you’ll need to update.

    Additional resources

    Author Inbar Gazit
    Inbar GazitSr. Manager, Developer Content

    Inbar Gazit has been with Docusign since 2013 in various engineering roles. Since 2019 he has focused on developer content. Inbar works on code examples including the launchers, available on GitHub in eight languages, and helps build sample apps showcasing the various Docusign APIs. He is also active on StackOverflow, answering your questions. Inbar can be reached at inbar.gazit@docusign.com.

    More posts from this author

    Related posts

    • Docusign 2024 Release 3: Capture the Critical Business Value Hidden in Your Agreements
      Intelligent Agreement Management

      Docusign 2024 Release 3: Capture the Critical Business Value Hidden in Your Agreements

    • How to improve your app’s UX while users wait for API calls to complete

      How to improve your app’s UX while users wait for API calls to complete

      Author Larry Kluger
      Larry Kluger
    • Trending Topics: Latest from our forums (November 2024)
      Author Paige Rossi
      Paige Rossi
    How to improve your app’s UX while users wait for API calls to complete

    How to improve your app’s UX while users wait for API calls to complete

    Author Larry Kluger
    Larry Kluger
    Trending Topics: Latest from our forums (November 2024)
    Author Paige Rossi
    Paige Rossi

    Discover what's new with Docusign IAM or start with eSignature for free

    Explore Docusign IAMTry eSignature for Free
    Person smiling while presenting