Web Access DocuSign Integration

SELECTED ANSWER

replied on March 2, 2016 • Show version history

Hi Dan,

While you can use a developer account, there is additional configuration necessary.

Add your Integrator Key to DocuSignSettings

<DocuSignSettings APIAccountId="1234abcd-1234-abcd-1234-1234abcd5678" APIUserEmail="YourDocuSignAccount@SampleCompany.com" Password="password“ IntegratorsKey="XMPL-ce45asdh-h328-123fe-4-53e5-89e25ca8434e"  />

Change API URLs under C:\Program Files\Laserfiche\WebAccess\Web Files\web.config

<!-- Change endpoint address to https://demo.docusign.net/api/3.0/credential.asmx  -->
<endpoint address="https://demo.docusign.net/api/3.0/credential.asmx"
          binding="basicHttpBinding" bindingConfiguration="CredentialSoap"
          contract="CredentialAPI.CredentialSoap" name="CredentialSoap" />
<!-- Change endpoint address to https://demo.docusign.net/api/3.0/api.asmx  -->
<endpoint address="https://demo.docusign.net/api/3.0/api.asmx"
          binding="basicHttpBinding" bindingConfiguration="APIServiceSoap"
          contract="DocuSignAPI.APIServiceSoap" name="APIServiceSoap" />

You can find your integrator key under Preferences > API:

If you don't have one yet, you can generate one using "Get Demo Integrator Key"

4 0

View 5 previous replies

replied on March 3, 2016 • Show version history

Thanks Brianna! This is exactly what I was looking for, however I'm still getting the same error so I guess I must have something else set wrong... Would you mind taking a quick look at these settings?

C:\Program Files\Laserfiche\Web Access\Web Files\web.config:

C:\Program Files\Laserfiche\Web Access\Web Files\Config\WebAccessConfig.xml:

C:\Program Files\Laserfiche\Web Import Services\DocuSignConnectService\Config\Config.xml

Options for DocuSign connect:

And options in Web Access:

I've not set up an X509 Certificate as shown towards the end of the documentation, but I have disabled this on the DocuSign Connect settings - would this still cause any issues?

Thanks for all your help!

Dan

0 0

replied on March 3, 2016 • Show version history

Hi Dan,

The code snippet I posted for changing the demo information was just what it looked like in the file before the changes were made, with the comments that had the instructions. It didn't actually have the change made. I went ahead and edited the post so you can just copy+paste

1 0

replied on March 4, 2016

Great! Thanks Brianna, it works! Up until it is sent to DocuSign anyway, then it gives this error, but I think this is probably because I haven't set up my template properly in DocuSign - I'll have a fiddle with it later.

Thanks for all your help!

Dan

0 0

replied on March 11, 2016

Hi All,

Unfortunately I'm still getting the above issue - has anyone else seen this? I've created a new template in DocuSign and as far as I'm aware all the settings are correct, however even trying to upload the exact same document that is specified in the template it still says it's expecting something different...

Any ideas are greatly appreciated, as this is the first time I've ever tried setting it up!

Cheers, Dan.

0 0

replied on March 11, 2016 • Show version history

Hi Dan,

This kind of issue is difficult to troubleshoot without having access to the configuration, template, and document. WA 10 definitely works with a demo account, so there is likely some configuration issue.

If you have a sample document that doesn't have private/confidential information, you could upload that document and your template xml (the template can be downloaded from the "Actions" menu that appears when a template is selected).

1 0

replied on March 14, 2016

Hi Brianna,

Yes almost certain it's a configuration issue on my behalf - sorry!

At the moment I'm only using a test template with one of the Laserfiche sample PDFs anyway so no issues with regards to confidential info. I've attached the document and XML so if you wouldn't mind having a look I'd really appreciate it!

Thanks again, Dan

P.S. I've had to upload the XML as a .txt file because uploading XML isn't allowed apparently

Test_Template.txt (303.4 KB)

| Download

SAMPLE 5.pdf (226.05 KB)

| Download

0 0

replied on March 14, 2016

Actually I've just found the problem (as is always the way!)

You mentioned downloading the XML and you only seem to be able to do this from the "Classic" version of DocuSign whereas I was using the "New" version. I also created the template from the new version, but creating a template from the Classic DocuSign website works fine... must be some difference in the way the templates are created between the versions. All working now though thanks!

Cheers, Dan.

2 0

replied on March 14, 2016

Hi Dan,

Thanks for letting us know the resolution! The new version concerns me, as it seems to be very different functionality in the UI. Hopefully DocuSign will continue to develop the new UI so that it matches the Classic UI functionality. I'll let our team know that they may need to take a look at the changes.

1 0

replied on July 17, 2017

It looks like Docusign is phasing out classic. Is the issue with the templates in the creation of the templates? Or assigning the template from Docusign? We have a customer who only uses Docusign for 1 type of document and the template is already there. They are still on 9.2.1. Trying to figure out if they are going to need to upgrade to 10.1+ or not.

Thank you,

Frankie

0 0

replied on July 17, 2017

The issue occurs when attempting to send the document from Web Access to DocuSign when using templates created in the new UI.

I believe if you already have a template, it will work, but they can test this now by manually switching over to the new experience and trying to send a document out for signing. The error is something like "DocuSign expects a signature on document 47685633, but only 1 documents were provided. " and is shown in the Request Signature dialog.

0 0

Question

Question

Answer

Replies

Sign in to reply to this post.