For the template defined in UI , can the values be injected using Field names rather than ids
Thursday, March 5, 2020 at 09:12amHi,
Is it possible to inject the values using field names rather than ID , since its becoming very difficult to send values using id because if we have four environments each time its very difficult to inject values using ID.
In that case prod environment will have new set of id values , which meaning we will not able to test .
Reply to: For the template defined in UI , can the values be injected using Field names rather than ids
Thursday, March 5, 2020 at 11:57amHi there,
From the API's perspective, you can't update a field without the field ID, because you'll have to build the API with the format "PUT /api/packages/{packageId}/approvals/{approvalId}/fields/{fieldId}", and as you observed, you can't specify approval/signature and the field ID through UI.
However, if you are copying the templates from environment to another (for example, from sandbox to production) using the copy tool I've built, all signature and field IDs will keep the same, so as long as you are able to test in sandbox, the same sets of IDs will work for production environment.
Duo
Reply to: For the template defined in UI , can the values be injected using Field names rather than ids
Friday, March 6, 2020 at 09:24amHi Duo ,
I can't install exe files , Is there anything like api or export import feature like in docusign to this functionality ?
Reply to: For the template defined in UI , can the values be injected using Field names rather than ids
Friday, March 6, 2020 at 09:30amHi,
My tool is written in Java and runs as an Executive jar, so no need to install extra software to your system. All calls invoked internally are APIs exposed to all integrators.
(Unfortunately, there's no out-of-the-box export & import function yet)
Duo