You are viewing limited content. For full access, please sign in.

Question

Question

DocuSign Envelope Status field not coming across in DocuSignConnectService

asked on July 22, 2016 Show version history

We've configured the DocuSignConnectService to handle all of the events and map the DocuSign meta data to Laserfiche fields:

<OnSignedEvent>
      <FieldValues>
        <FieldValue name="DocuSign Envelope Status">%(Status)</FieldValue>    
        <FieldValue name="DocuSign EnvelopeID">%(EnvelopeID)</FieldValue>
        <FieldValue name="TransactionID">%(CustomFields.TransactionId)   </FieldValue>     
        <FieldValue name="STP Sponsor">%(CustomFields.SponsorId)</FieldValue>
        <FieldValue name="STP Environment">%(CustomFields.Environment)</FieldValue>           
      </FieldValues>
      <DocumentNotFound>
        <DefaultFolder>\DocuSign\Completed</DefaultFolder>
      </DocumentNotFound>
    </OnSignedEvent>

EnvelopeID gets populated, as well as the CustomFields, but Status does not. Is there some change in the way DocuSign is sending that value?  I know from the XML DocuSign is sending (here's the log):

<Status>Completed</Status>

...that a value is populated, it just isn't getting set in the meta data in LF via the service.

0 0

Replies

replied on September 11, 2017 Show version history

Hi there,

I know this reply may be a little late, however, perhaps this may help someone in the future learning about the Laserfiche and DocuSign integration.

I came across this post whilst recently researching about and testing the DocuSign integration and with some help from others have been advised that with regard to the DocuSign %status token, it is a value of type DocuSignAPI.EnvelopeStatusCode and therefore it isn't a standard string type which would explain why a value is not populated as you're expecting.

As an alternative, you can use plain text to track DocuSign status - since the status is related the event. Below is an example:

 

Hope it helps.

Tim

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.