Sample Project Plan for DocuSign Connect - lingkio/docusign-connect GitHub Wiki
Milestones
Configure the DocuSign connector in the Lingk Environment
Determine if the DocuSign connect .NET app will be deployed via Docker or directly into a VM
Create VM, if installing directly
Clone the Docusign-Connect repository
Get a simple DocuSign Form working with pre-fill
Start with a DocuSign form that just maps values to tabs
Create "Data Label" value for each tab that will be pre-filled
Update the config YAML file with SSO information
Enter your SAML metadata
Update the config YAML file with Lingk information
Enter your Lingk API Key and Secret from your project
Enter the Lingk Environment key where you have connect into DocuSign (see step #1) - click the "Pencil" icon to find the key
Update the config YAML file with data provider information
The default configured data provider is Postgres
Add another provider in the source code to enable other types of providers - APIs, MS SQL, Oracle, etc.
Ensure that the tables you are selecting have a unique identifier that maps to SSO (IMPORTANT)
In order for the data to be read from the provider, a unique identifier from the SAML payload must be used
Specify your first template
Specify a URL path (example "/addressChange") to be used for the template (this URL will be inserted into your portal software or website)
Use the template GUID from the DocuSign developer site
Specify which provider should be used to prefill
Specify the redirect URL (after signature)
Specify the mapping between SAML and the provider for the template
Configure mappings for each tab (you will need the column names from the database or API AND the tab "Data Label" value
Start the application as a .NET application or a docker image and pass in the config YAML file
Hit the URL path ("/addressChange")
If working properly, you should see your SSO page launch
Enter your credentials and you should be redirected to the envelope on DocuSign automatically
Sign the document to be redirect to the redirect URL
Push the .NET app and YAML configuration to production server / docker image
Troubleshooting
By default, the envelope Ids are reused if possible to reduce the number of envelopes. Delete the envelope ID for the user in order to get a new envelope for additional testing.