pphelan

Extraction and the populated field names in the signed PDF

Tuesday, August 13, 2019 at 08:13am
0 votes
Hi, Is there a way to use the field extraction feature and also set the name of the (form) fields in the pdf to store the data. In my PDF for signing I set the following: Field [Title], Value [Project Manager] Field [[Client.Capture1.label1.Name]], Value [] Field [[Client.Capture1.label1.Date]], Value [] Field [[Client.Capture1.]], Value [] and I enable extraction when I build the package: ....withDocument(DocumentBuilder.newDocumentWithName("Test Sign doc").fromFile(myPdfFileName).enableExtraction()).build(); however when I get the PDF back / look at the field summaries: Format: SignerId | DocumentId | FieldId : FieldValue // Function Calls: fieldsummary.getSignerId(), .getDocumentId() .getFieldId() , .getFieldValue() I see the following displayed: Client, | ce934053459349593405934 | 5345345345342: Mr. Manager Client, | ce934053459349593405934 | 7899789789787: 2019-08-09T13:07:242 I saw the feature guide (https://developer.esignlive.com/guides/feature-guides/retrieve-field-values/) where it had nice names but nothing about the PDF used. Can I set the FieldId with extraction to be a more "nicer name" like client_name and client_signerdate __OR__ put the values into the [[Client.Capture1.label.Name]] form fields ? Thanks ~Patrick
Approved Answer
Duo_Liang

Reply to: Extraction and the populated field names in the signed PDF

Tuesday, August 13, 2019 at 08:57am
0 votes
Hi Patrick, The production behavior before 11.28 SaaS version was, when using document extraction, the field name will be automatically generated in a certain naming convention, which means you could use the field name (not field ID, because ID should be unique and will be generated by OSS when using extraction) to locate the field with its value. But very unfortunately, this capability was removed since 11.28 because of a conflict with another feature. In this case, I am afraid there's no longer a method to map the PDF form to its field name or ID. If your document was not complex, you can still understand which field stores the data you desired. But if it's not acceptable for you, I would suggest to use Text Tags feature (guide here) or Position Extraction feature (guide here) for all fields instead. For text tags feature, its syntax allowing you to set the field name: {{Xesl[_fieldName]:roleName:fieldType[:parameter1,parameter2,...]}} And for position extraction feature, you can assign the field name and even ID during adding the field through SDK. Hope this could help! Duo

Duo Liang OneSpan Evangelism and Partner Integrations Developer

pphelan

Reply to: Extraction and the populated field names in the signed PDF

Wednesday, August 14, 2019 at 01:46am
0 votes
Thanks, I will try that out :) ~Patrick

Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off

LoginSign Up