Trending Topics: Latest from our forums (August 2024)
See how our most popular recent threads on the Docusign Community and Stack Overflow can help you solve your own development issues.
Table of contents
Here are some of the latest popular questions that developers asked on Docusign Community and Stack Overflow in the month of August 2024. To make sure we see your questions on Stack Overflow, use the tag docusignapi.
Thread: Docusign won’t let me edit my app. This integration key could not be updated. Please try again in a moment
Summary: The developer is building a Next.js Docusign integration using CORS. Previously they had no issues, but recently they made an edit to their integration key and the application stopped working.
Answer: This issue was actually due to a recent change from Docusign that no longer allows localhost as a CORS origin for an app. Changing that origin solves the problem. As a workaround, you can use https://127.0.0.1 instead of https://localhost.
Thread: Generate Self-Signing url
https://community.docusign.com/esignature-api-63/generate-self-signing-url-19680
Summary: The developer is building an application with embedded signing and they want the signer to be able to use FreeForm Signing rather than requiring them to fill out a set of tabs that are defined on the envelope by the sender.
Answer: If a sender defines any tabs when sending an envelope, the signer won’t have the option to add any additional tabs. If you want your signers to be able to use FreeForm Signing, you should not include any tabs in the envelope definition. When the signer is directed to the signing URL, they will have the option to add any tabs that they’d like to the document, and they will be required to add at least one tab on the envelope before it is completed.
Thread: Python Docusign Automation: Composite template not working
Summary: The developer wants to use composite templates to apply a template to an envelope with the Python eSignature REST SDK. When they send the envelope they aren’t seeing any of the tabs or fields that they expect to see on the document.
Answer: The issue here was that the “Role” in the template didn’t match the role_name of the recipient in the developer’s code. For example, if you create the following recipient using the Python SDK, you need to update the role_name property to the same value as the Role defined in your template.
signer1 = Signer(
email=args["signer_email"],
name=args["signer_name"],
role_name="signer",
recipient_id="1",
client_user_id=args["signer_client_id"]
)
See How to request a signature using a composite template for an end-to-end example.
Additional resources
Paige has been working for Docusign since 2020. As a Sr. Programmer Writer on the Developer Content team, she writes content and code to help developers learn how to use Docusign APIs.
Related posts
Discover what's new with Docusign IAM or start with eSignature for free
