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

Question

Question

Docusign Demo Environment Integration with Cloud

asked on July 25, 2019

We are experiencing the issue brought up in this answers post.

https://answers.laserfiche.com/questions/135419/DocuSign-integration#138023

 

The problem is that we have no access to those web config files since the process is being built on Laserfiche Cloud. We used the Prod Docusign environment and everything is dandy, but we want to use tests in order to preserve the integrity of our live environment.

 

Has anyone been able to get this working?

2 0

Replies

replied on July 25, 2019

Hi Brett, 

 

Currently, Laserfiche Cloud doesn't support the use of Demo DocuSign environments. 

0 0
replied on September 18, 2019

Hi Ryan,

 

Has this since changed or will there be an update to address this?

 

Thank you!

0 0
replied on September 18, 2019

Hi Aaron, 

 

This hasn't changed yet. There's no immediate timeline for when we might support this. 

0 0
replied on April 18, 2023

Hi there - please consider adding this!! We are having to use our real DocuSign account for development and demonstrations. Not ideal.

0 0
replied on April 20, 2023

That's an interesting use case. Even self-hosted, the DocuSign endpoint (dev vs prod) is a global setting in the web.config file. But it sounds like you would want it to be a per-user setting? Or is there a different way you envision it working?

0 0
replied on April 20, 2023 Show version history

Hi Brian, when configuring DocuSign settings in LF Cloud (Repository Management) you need a DocuSign API Account ID, email Address (user account) and an Application Password (generated for the 'connected' user account).

We can get all of these things within a DocuSign demo environment (appdemo.docusign.com) - but we just can't specify which DocuSign 'endpoint' (prod or demo) to use.

If there was a field or radio button within Laserfiche repository Management so that we could specify that appdemo.docusign should be used, then that would be ideal.

This means that our own sandbox/demo LF Cloud instance could be connected to our sandbox DocuSign environment. So we wouldn't be consuming real envelopes, or having 'fake' DocuSign Templates in our real environment, any deep integrations we would do would be zero risk of upsetting our prod DocuSign account etc etc.

Also, because we have to use our real DocuSign site - the 'signed contracts' that result from a demo or development/testing are also not watermarked with 'demonstration only', and we have to ensure this is done on the underlying document.

2 0
replied on November 3, 2023

Has their been any update on this capability of pointing LF Cloud to a Sandbox\Developer\Demo Docusign Demo account?

3 0
replied on December 5, 2023

This a Huge issue and stopping many LF Solution providers from being able to show and test real world signing solutions. No one is going to make a large investment in Docusign Integration before they can be sure it will work. Also for many Customers before deploying a solution they could test functionality. Anyway I feel just like Ryan that it would be simple for DEVELOPMENT to provide a Check Box in User Options and Administration Integration sections that deal with Docusign.   the Sandbox Dev Docusign demo simply authenticates and operates from   https://demo.docusign.net   everything else is the same.

I tried to set this up and after much frustration came to this conclusion.

Please add this functionality, Trust me we will make lots more sales of Laserfiche Cloud.

3 0
replied on September 10, 2024

Totally agree with Milton, this is a problem for us at the county since we do not want to test the integration of laserfiche to docusign production burning envelopes in production. 

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

Sign in to reply to this post.