Our Community is in read-only mode until April 8th, learn more here. You can still search existing threads or get help via Dropbox Support, the Dropbox Help Center, or Learn.
Forum Discussion
Solved
Template 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?
Thank you for your patience as we've looked into these issues. We've confirmed the following behavior with our engineering team:
- Field Options Parameter: We have confirmed that the `date_format` set in the `field_options` parameter will be applied to all date fields within a signature request. Please note that only one format is allowed per request, and the format specified using this parameter will be consistently applied to all date fields within the request.
- Template Created Event Response Object: Regarding the `template_created` event response object, the current behavior is expected. At this time, we do not include `font-family`, `font-size`, or `date_format` information in the response object for the `date_signed` form field. We understand that having access to this information could be beneficial, and I’d be happy to share this suggestion with our product team as a potential feature enhancement. However, we cannot guarantee if or when this functionality will be added to the product roadmap. To check for new updates and features, please review our documentation Changelog.
If you’ve encountered any other issues or if there’s anything else we can assist you with, please let me know.
- Field Options Parameter: We have confirmed that the `date_format` set in the `field_options` parameter will be applied to all date fields within a signature request. Please note that only one format is allowed per request, and the format specified using this parameter will be consistently applied to all date fields within the request.
4 Replies
Replies have been turned off for this discussion
Spencer HDropbox Staff
Hi there,
Thanks for reaching out. We’re currently taking a closer look at the issues you’ve identified. Specifically, we’re checking on the expected status of the `template_created` event and what information should be available based on the type of field you’re including.Here’s what we’ve found so far:
- We’ve been able to replicate the absence of `font-size`, `font-family`, and `date_format` in the `template_created` event for the `date_signed` field.
- We do see that `font-size` and `font-family` are present when creating `merge_fields` on the template -- we're investigating further.
Regarding `date_format`, we do provide the `field_options` parameter, which does allow you to set a `date_format` for the signature request as a whole if on a Premium API plan. However, it doesn’t seem to apply to the individual `form_fields_per_document` `date_signed` fields when testing. We’re continuing to investigate this discrepancy as well.
We appreciate your patience as we work through these details. I’ll follow up with another update as soon as we have more information to share.
Thanks for the reply
The `field_options` is something we missed. This solves the second issue.
We will be waiting for your update response- Spencer H
Thank you for your patience as we've looked into these issues. We've confirmed the following behavior with our engineering team:
- Field Options Parameter: We have confirmed that the `date_format` set in the `field_options` parameter will be applied to all date fields within a signature request. Please note that only one format is allowed per request, and the format specified using this parameter will be consistently applied to all date fields within the request.
- Template Created Event Response Object: Regarding the `template_created` event response object, the current behavior is expected. At this time, we do not include `font-family`, `font-size`, or `date_format` information in the response object for the `date_signed` form field. We understand that having access to this information could be beneficial, and I’d be happy to share this suggestion with our product team as a potential feature enhancement. However, we cannot guarantee if or when this functionality will be added to the product roadmap. To check for new updates and features, please review our documentation Changelog.
If you’ve encountered any other issues or if there’s anything else we can assist you with, please let me know.
- Field Options Parameter: We have confirmed that the `date_format` set in the `field_options` parameter will be applied to all date fields within a signature request. Please note that only one format is allowed per request, and the format specified using this parameter will be consistently applied to all date fields within the request.
Thanks for the answer
It would be a feature we would like to see.
We will try other solutions in the mean time.
