Skip to main content
Solved

Prepopulate doclauncher config form: post request

  • January 8, 2026
  • 1 reply
  • 23 views

Forum|alt.badge.img+6

Hi all,

I’m able to successfully initiate a DocLauncher task via the API using the following request:

POST {{baseUrl}}/v2/{{accountId}}/doclaunchertasks

Body: { "DocLauncherConfiguration": { "Href": "https://apiuatna11.springcm.com/v2/.../doclauncherconfigurations/c19edc..." }, "Datatype": "xml", "Data": "<dd><num>1234</num></dd>" }

I use the ResultUrl from the response to launch the configuration in ui mode and fill some additional details apart from the dd field. I’ve created a form with a textbox with mergetag dd along with some additional fields to be filled by the user.

The form launches and but the initial data that I passed is not visible on the form ui. However, after the workflow launches after the document generation. Here are the observed params:

<TemplateFieldData ...> <transactions>456</transactions> <transactions_unformatted>456</transactions_unformatted> <dd><![CDATA[]]></dd> </TemplateFieldData>

the dd field is some obscure value and doesn’t have expected data. I’ve tried to modify the Data in the request body in various ways, still the issue persists.

Why isn’t the custom field (dd) being populated from the XML payload? Is there a specific XML structure or root element required for DocLauncher to map custom fields correctly?

Any guidance or examples would be greatly appreciated!

Best answer by Servesh

To resolve the issue, we found that the DocuSign DocGen Form required editing the fields in Edit as JSON. After switching to Advanced Mode, we added the following properties to ensure the fields are correctly pre‑populated:

 

"TargetIdentifier": "Text_field_for_the_user",     //Merge tag on form

"ExtractionSourceId": "XMLExtractor",              //DO NOT CHANGE

"SourceIdentifier": "//Text_field_for_the_user"  //Node to be mapped

 

These configurations allow the DocGen engine to map and populate the field values from the XML source as expected.

1 reply

Forum|alt.badge.img+6
  • Author
  • Digital Collaborator
  • Answer
  • January 15, 2026

To resolve the issue, we found that the DocuSign DocGen Form required editing the fields in Edit as JSON. After switching to Advanced Mode, we added the following properties to ensure the fields are correctly pre‑populated:

 

"TargetIdentifier": "Text_field_for_the_user",     //Merge tag on form

"ExtractionSourceId": "XMLExtractor",              //DO NOT CHANGE

"SourceIdentifier": "//Text_field_for_the_user"  //Node to be mapped

 

These configurations allow the DocGen engine to map and populate the field values from the XML source as expected.