Help understanding auto-populate fields
Sunday, July 23, 2017 at 04:22pmI need some help figuring out how to auto-populate fields in our documents (i.e. fields that auto-fill upon signature).
So, I've been able to add an auto-populating date field to one of our documents using this JSON:
{
"binding": "{approval.signed}",
"validation": null,
"id": "mKOpnLGSlY0Q",
"page": 0,
"height": 50,
"subtype": "LABEL",
"width": 200,
"top": 250,
"left": 175,
"extract": false,
"extractAnchor": null,
"data": null,
"value": "yyyy-MM-dd HH:mm:ss 'GMT'",
"name": "",
"type": "INPUT"
}
This all works just fine - as expected, I get an auto-populating date field. Presumably, this is because of what I've specified in the "value" field - eSignLive sees that this is a date format and knows I want a date field. But this is where my confusion comes in - we have a requirement to also auto-populate the signer's title (if available). When I reference this documentation - http://docs.esignlive.com/content/c_integrator_s_guide/sdk/e_preparing_documents/fields.htm - I see that "Signer's Title" is one of the available options, but I'm struggling to find any documentation that shows what I would need to alter in my above example JSON to switch this from a date field to a title field.
Could someone please help point me in the right direction?
Thanks,
Nick
Reply to: Help understanding auto-populate fields
Sunday, July 23, 2017 at 07:41pmReply to: Help understanding auto-populate fields
Monday, July 24, 2017 at 05:42amReply to: Help understanding auto-populate fields
Monday, July 24, 2017 at 08:47amReply to: Help understanding auto-populate fields
Wednesday, August 30, 2017 at 09:18amReply to: Help understanding auto-populate fields
Wednesday, August 30, 2017 at 09:29amOh, just found this thread: https://community.onespan.com/forum/timezone-customization Sounds like Q3 of next year perhaps for tz support.