bulk transaction creation from Adhoc
Wednesday, April 8, 2020 at 06:12pmdear team, can i use the Adhoc tool to create a bulk transaction creation with a CSV file where i can add a field l like Salary that is in the file and is filled in during in the document template field. i was looking at the csv file format and saw
<PlaceholderRoleName>,FIRST_NAME,LAST_NAME,EMAIL,AUTH_TYPE,AUTH_PROMPT,AUTH_CHALLENGE,SIGNER_VERIFICATION,<FieldId1>,<FieldId2>
but i am not sure if the last 2 fields are according to the template as for example salary and that it gets filled in the document in a test filed or label from the csv file information for a specific signer.
Reply to: bulk transaction creation from Adhoc
Thursday, April 9, 2020 at 11:55amYes, data such as <FieldId1> will be injected in the template's document before sending the transaction for signature. To make this happen, put a label (if you want a read-only field) or a text field (if you want to allow the signer to edit the field) on your document and give a name, e.g. "MyField". Then in your CSV file, put a column with the same name.
Please reply if that does not work or if you have any clarifying questions.
Reply to: bulk transaction creation from Adhoc
Thursday, April 9, 2020 at 02:03pm
Thanks Francois for the answer!
From my test,
(1) The field ID(s) here actually refers to the field Name, so as the first parameter refers to the placeholder's name instead of ID. This is because both placeholder name and field name are configurable at sender UI:
(2) In the CSV file, it takes a variable number of field columns, depending on the actual situation.
(3) If you have multiple placeholders, you'd reproduce the headers in the same row, but replaced with different role name and field name(s). For example, if I have a template with two signers, each signer has a signature and a label field.(template metadata as attached) I'd create a CSV like below:
Duo