-
go to https://developers.docusign.com and create an account
-
go to Quickstart https://developers.docusign.com/docs/esign-rest-api/quickstart/
-
create an application and let docusign create a demo project for you
-
Docusign will create all needed resources to access this application for you
-
the generated demo project contains an application.json file
-
copy the values of the properties
spring.security.oauth2.client.registration.jwt.client-id
and
spring.security.oauth2.client.registration.jwt.guid
to your application.properties
docuSign.clientId
docuSign.userId
and copy the private.key to src/main/resources/docusign_private.key
- create a SaaS cluster with 8.3.0-alpha4
- create a new client in SaaS and copy the config params to application.properties
- create a secret SENDGRID_DEMO and pass by the sendgrid api key for the Consulting team (see Keeper via Okta)
- copy the process model to a web-modeler project
- deploy the process model from within the web-modeler (to activate the webhook)
- click the webhook connector and go to tab webhood
- copy the webhook-url
- go to docusign https://admindemo.docusign.com/apps-and-keys
- select on the left menu "Connect"
- add a new configuration ("custom")
- give it a name and paste the webhook url
- under trigger events select Envelope and recipients and click "Envelope signed/completed"
- start the application (do a mvn clean package first)
- go to http://localhost:8080/start
- you can choose example images to upload from demo-images (The Simpsons)
- the email provided for the "request" is being used to send a signature request, whereas the managers email in the userTask will receive the confirmation and the signed document.