We are currently using DocuSign keys in Oracle Integration Cloud (OIC) for a KYC process that is live and functioning well. Now, we have a new requirement to implement DocuSign for a separate employee onboarding process. I have a few questions regarding this: Since we already have a DocuSign key in the production environment for the KYC process, can we reuse the same key for the employee onboarding process? The flow for both processes is similar: Define a template in DocuSign (the templates differ for each process). Use these templates in our integration. Once an envelope is signed (by a customer or employee), the information is processed via a "Connect" configuration. For these two separate processes, can we set up two independent "Connect" configurations in DocuSign? If having two "Connect" configurations is possible, how can we ensure they do not overlap and that each configuration only handles the relevant process?

Solved

Using Multiple Integration Keys in OIC

3 months ago
December 9, 2024
1 reply
34 views

+1

Fusion06
Newcomer

We are currently using DocuSign keys in Oracle Integration Cloud (OIC) for a KYC process that is live and functioning well. Now, we have a new requirement to implement DocuSign for a separate employee onboarding process. I have a few questions regarding this:

Since we already have a DocuSign key in the production environment for the KYC process, can we reuse the same key for the employee onboarding process?
The flow for both processes is similar:
- Define a template in DocuSign (the templates differ for each process).
- Use these templates in our integration.
- Once an envelope is signed (by a customer or employee), the information is processed via a "Connect" configuration.
For these two separate processes, can we set up two independent "Connect" configurations in DocuSign?
If having two "Connect" configurations is possible, how can we ensure they do not overlap and that each configuration only handles the relevant process?

Best answer by Byungjae.Chung

1) Docusign recommends using one integration key per application. If the employee onboarding process is built on a different code base, you would need to add one more integration key for this particular application and promote it to the production account.

2) There are two types of Docusign Connect: 1) Envelope-level, 2) Account-level. If you write the code for the Envelope-level Connect, the Connect event will be sent per envelope. The Account-level Connect Configuration works per account basis so all the envelopes sent by this account will affect each Connect configuration to work. To avoid this, you must associate the specific list of the users/groups for each Connect configuration.

More information about the types of Connect is here: https://developers.docusign.com/platform/webhooks/connect/

3) As described in #2, associating users or groups is the only way to avoid the overlap for the Account-level Conenct configurations. Please refer to the "Associated Users/Groups" row on this page for more information: https://support.docusign.com/s/document-item?language=en_US&rsc_301&bundleId=pik1583277475390&topicId=zjq1665170940873.html&_LANG=enus

You can also find the tips on handling multiple Connect listeners in this blog post: https://www.docusign.com/blog/developers/the-trenches-handling-multiple-connect-listeners

View Original

Is this content helpful?

B

+7

Byungjae.Chung
Docusign Employee
66 replies
Answer
3 months ago
December 10, 2024

1) Docusign recommends using one integration key per application. If the employee onboarding process is built on a different code base, you would need to add one more integration key for this particular application and promote it to the production account.

2) There are two types of Docusign Connect: 1) Envelope-level, 2) Account-level. If you write the code for the Envelope-level Connect, the Connect event will be sent per envelope. The Account-level Connect Configuration works per account basis so all the envelopes sent by this account will affect each Connect configuration to work. To avoid this, you must associate the specific list of the users/groups for each Connect configuration.

More information about the types of Connect is here: https://developers.docusign.com/platform/webhooks/connect/

3) As described in #2, associating users or groups is the only way to avoid the overlap for the Account-level Conenct configurations. Please refer to the "Associated Users/Groups" row on this page for more information: https://support.docusign.com/s/document-item?language=en_US&rsc_301&bundleId=pik1583277475390&topicId=zjq1665170940873.html&_LANG=enus

You can also find the tips on handling multiple Connect listeners in this blog post: https://www.docusign.com/blog/developers/the-trenches-handling-multiple-connect-listeners

F

Reply

Rich Text Editor, editor1

Reply

Related topics

will nutanix discard api v1,v2,v3?icon

Unauthorized for Nutanix REST API. check username and passwordicon

Logs to check for REST APIs and Apache/Http issues

GET /api/nutanix/understanding-rest-api

Most helpful members this week

Sign up

You can login or register as either a Docusign customer or developer. If you don’t already have a Docusign customer or developer account, you can create one for free when registering.

Docusign Community

You can login or register as either a Docusign customer or developer. If you don’t already have a Docusign customer or developer account, you can create one for free when registering.

Scanning file for viruses.

This file cannot be downloaded