Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Dropbox Sign
5 TopicsTemplate Created callback does not contain metadata for Date signed field type
We use embedded templates in our web app to create templates. However, when we receive the callback in our Java application, the TemplateResponseDocumentFormFieldDateSigned object does not include metadata values such as font family, font size, and date format. Secondly, when we create a signature request using the SubFormFieldsPerDocumentDateSigned object, we notice that only the font_family and font_size properties are implemented, while the date format is missing. When creating a "Date Signed" field in the embedded template editor, we can set the font family, font size, and date format. Why aren't these values included in the template creation callback? Additionally, why is the date format missing when manually creating the fields for a signature request?Solved224Views0likes4CommentsWhat to include in a Support Ticket Request
Hey Sign API Community! We're glad to see your engagement and activity after opening up this space! If you do find that you need to write into our support team, we wanted to highlight some helpful pieces of information that our team needs to investigate your issue. Please submit a request from the primary email address associated with your account and include the following if applicable: Error / description of issue Signature request ID (aka Document ID) and/or Template ID for affected request API Endpoints & SDK version you are using in your workflow (i.e. /v3/signature_request/create_embedded etc.) Any screenshots, recordings, and applicable code snippets are also extremely helpful in our investigations. We look forward to assisting you with your Sign API integration!925Views1like0CommentsWelcome to the Sign API Developer Community
We're excited to introduce the Sign API Developer community, a space for you to engage with everything related to the Sign API. This forum is where you can ask questions, share knowledge, and collaborate to get the most out of Sign API. Whether you're an experienced developer or just starting with the Sign API, this forum is your go-to resource for technical exchange. Who should join? The forum is open to all, especially developers and technical users of the Sign API. If you have insights to share, questions to ask, or are looking to enhance your understanding of the Sign API, this community is for you. How to leverage this Community forum We encourage you to: Discuss: Engage in technical discussions, ask questions, and provide answers. Share: Contribute your knowledge, share your use cases, and explore new ways to use the Sign API. Feedback: Offer suggestions for improvements or new features, or bugs that need to be addressed. Tell us what you think We’d love to hear your thoughts on the Sign API community, so please leave any feedback in the comments below.3.4KViews4likes0CommentsCan't resolve './aes' error when using @dropbox/sign
Node: 18.17.1 @dropbox/sign: 1.1.3 Hi, when I try to use the sdk I get the following error: - error ./node_modules/@dropbox/sign/dist/api.js Module not found: Can't resolve './aes' The error comes from this simple piece of code: import * as DropboxSign from '@dropbox/sign'; const signatureRequestApi = new DropboxSign.SignatureRequestApi(); Would be very greatful for any help on this. Best, S2.8KViews2likes10Comments