DocuSign Return Payload Missing Custom Fields

Question

I'm working on building a SpringCM workflow that uses DocuSign for sending and recieving electronic signatures. Durring our testing and build we were pointed to a Test/Trial DocuSign Account.

We had created a process that after the Document was signed it looked for the 'Custom Fields' inside of the returned payload to grab the 'Effective Date'. Nothing special was set up in our trial/demo account to accomidate this.

Now that we are pointed to the customers production account inside of DocuSign we are no longer recieving the 'Custom Fields' in the payload recieved from DocuSign.

Old Payload in Trial account WITH custom fields:

<HistoryEvent>
  <Email>[email protected]</Email>
  <Status>Signed</Status>
  <DelegatedTo />
  <UpdatedDate>2018-09-25T21:20:48.847Z</UpdatedDate>
  <Comments />
  <CustomFields>
    <CustomField>
      <Name>Signature 1_SignHere_0146017e-d0c8-4a85-b890-51c79e66a8a3</Name>
    </CustomField>
  </CustomFields>
</HistoryEvent>

New payload in production account WITHOUT custom fields:

   <HistoryEvent>
      <Email>[email protected]</Email>
      <Status>Signed</Status>
      <DelegatedTo />
      <UpdatedDate>2018-10-10T14:46:15.507Z</UpdatedDate>
      <Comments />
      <CustomFields />
    </HistoryEvent>

Question: Is there a setting or something inside of DocuSign that is causing me to NOT get the 'Custom Fields' in this new DocuSign environment?

Any suggestions on why I am not getting the data I'm expecting?

Thanks

Rickey S Rickey S · Accepted Answer · 2018-10-11T03:58:33

I assume you are using Connect to receive this payload?

There is a setting in the connect configuration to under "Include:" for Document Fields. That should push the custom fields through in the payload.

DocuSign Return Payload Missing Custom Fields

1 Answers