-
Notifications
You must be signed in to change notification settings - Fork 61
Add Editable Merge Fields support #30
Comments
I am also facing this issue at the moment.
To this, I got the following error - I read the docs and the code to find no examples for this. Kindly respond back soon about this issue. If there is a workaround to this, please post here. Thank you. |
Hi, Thanks for your request. We are getting this into our queue and will provide you with an update. -Ronald |
Heya @ketan37dm - this should be ready to go now, as of v3.2.8 of the SDK, which I've just pushed here and to Rubygems. You can now specify custom_fields as you have above, as an array of (Hash) objects. Note that you must have custom_fields of the same name (API label) in the template you're using to send the request as well. For an example reference, this is what I used to verify the fix: res = client.send_signature_request_with_template(
:test_mode => 1,
:template_id => "bd925f9abf7edec3b8fb957aacfc605cfe9511ab",
:subject => 'Purchase Order',
:message => 'Glad we could come to an agreement.',
:signers => [
{
:email_address => 'test@example.com',
:name => 'George',
:role => 'Client'
}
],
:custom_fields => [ { name: 'first_name', value: "someValue", editor: 'Client', required: true}, { name: 'email', value: "hodor@example.com", editor: 'Client', required: true } ]
)
puts res.data |
thank you @renderf0x @rmelencio I appreciate your quick response guys 👍 |
When updating the SDKs to include editable merge fields, please also update the SDK git repos README examples (if necessary) and the following in the API docs:
The text was updated successfully, but these errors were encountered: