https://github.com/abbi-gaurav/prototype-docusign-kyma

A prototype integration between DocuSign and Kyma
https://github.com/abbi-gaurav/prototype-docusign-kyma

Last synced: about 1 month ago
JSON representation

A prototype integration between DocuSign and Kyma

• Host: GitHub
• URL: https://github.com/abbi-gaurav/prototype-docusign-kyma
• Owner: abbi-gaurav
• Created: 2019-11-22T13:30:12.000Z (almost 5 years ago)
• Default Branch: master
• Last Pushed: 2020-10-27T09:46:39.000Z (about 4 years ago)
• Last Synced: 2024-06-20T11:05:49.430Z (5 months ago)
• Language: Go
• Size: 5.38 MB
• Stars: 0
• Watchers: 2
• Forks: 1
• Open Issues: 1
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Overview

A sample integration of [DocuSign](https://www.docusign.com/) with [Kyma](https://kyma-project.io) to demonstrate how Kyma can be leveraged to enable side-by-side extensibility flows for DocuSign when used with SAP applications such as SAP Service Cloud.

It uses a [DocuSign addons connector](./addons) to connect DocuSign with Kyma.

## Demo workshop

### What will be covered?

* Set up connectivity between DocuSign and Kyma

* Deploy an example lambda that

  * Is executed on DocuSign Envelope events

  * Makes API calls to DocSign

### Prerequisites

* DocuSign tenant.

* APIs and Keys already configured in DocuSign. We will be using `X-DocuSign-Authentication` based authentication to make API calls. Refer to this [documentation](https://developers.docusign.com/esign-soap-api/reference/Introduction-Changes/Authentication) for further details.

* DocuSign tenant URL to make API calls,  Username, password and Integrator Key are handy to be used later.

* A running Kyma instance

### Steps

* Create a new namespace in Kyma. We will be doing the whole workshop by deploying resources and workloads in this namespace.

![](./assets/steps/add-new-ns.png)

![](./assets/steps/create-ns.png)

* Navigate back to Kyma console main. Create a new Kyma application for connecting DocuSign. 

Think of `Kyma application` as a proxy for the actual DocuSign Tenant to which APIs and events connectivity will be achieved.

Next step is to bind the application to the namespace. By binding, we are essentially saying that workloads running in this namespace has access to data coming from this application (namely Events and APIs).

![](./assets/steps/to-main.png)

![](./assets/steps/create-application.png)

![](./assets/steps/bind-application-to-ns.png)

* Lets go back to our namespace.

Provision the addon. This addon will then provide us a connector that will be used to establish connectivity between Kyma and DocuSign.

For the URL, provide `git::https://github.com/abbi-gaurav/prototype-docusign-kyma//addons/index.yaml?ref=master`.

Once addon is deployed, the connector will be avaialble in `Catalog->addons`. 

![](./assets/steps/back-to-ns.png)

![](./assets/steps/addons-config.png)

![](./assets/steps/catalog-docusign-connector.png)

* Provision the connector. Provide the details as required to make API calls to DocuSign.

Additionally provide the basic authentication details for the event gateway that will receive DocuSign events.

![](./assets/steps/provision-connector.png)

* Post provisioning, DocuSign APIs and events will be available in `Catalog->Services` section.

Add once both APIs and events.

![](./assets/steps/apis-and-events.png)

![](./assets/steps/events-add-once.png)

![](./assets/steps/create-api-instance.png)

* Lets configure the DocuSign to be able to send events to Kyma.

Kyma API has already been deployed as a part of the connector. It exposes an URL over internet that will receive DocuSign events and will forward it to Kyma.

Lets go ahead and configure this URL in DocuSign admin console.

![](./assets/steps/kyma-api-event-gateway.png)

![](./assets/steps/docusign-add-connect-config.png)

![](./assets/steps/docusign-create-connect.png)

![](./assets/steps/docusign-connect-events.png)

* Lets take a minute to understand what we have acheived so far. We have now enable APIs and events connectivity with DocuSign. 

That implies, 

  * Workloads in Kyma (lambdas, microservices) can now be triggered with DocuSign events.

  * Lambdas and microservices from Kyma can make API calls to DocuSign.

![](./assets/docusign-config-done.png) 

* Lets take it to next part and write a lambda that 

  * will be triggered by a DocuSign event.

  * Make an API call back to DocuSign.

* Create a lambda, select event trigger. Use the [application code](./assets/lambda/demo-docusign-connector.js) and [npm dependencies](./assets/lambda/package.json).

Configure the Service binding that will enable making API calls back to DocuSign.

![](./assets/steps/lambda-event-trigger.png)

![](./assets/steps/lambda-code-dependencies.png)

![](./assets/steps/do-service-binding.png)

* In DocuSign, create a test envelope and sign it. The activity on DocuSign side will trigger the lambda and its logic will be executed.

You can check the lambda logs to see what is going.

* Next action items for you, 

  * Write your own lambda. Add logic as per your business scenario.

  * Integrate with other SAP systems and also third party systems.