You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Welcome to the MyMaestro sample app! MyMaestro is written using Node.js (server) and React (client), and showcase the new Maestro API and how developers can use the API to create solutions for HR use cases, specifically use cases related to hiring
7
+
Welcome to the MyMaestro sample app! MyMaestro is written using Node.js (server) and React (client), and showcase the new Maestro API. Docusign Maestro is a core platform service powering the Docusign. Easily build and deploy customized workflows that automate and accelerate your agreement processes without writing any code. Maestro connects all the tools and activities in your workflow so agreement processes are more efficient, more uniform, and have better visibility.
8
+
9
+
With Docusign Maestro, you can combine workflow steps for Docusign apps like ID Verification, Web Forms, and eSignature, and third-party extensions to automate your agreement process end-to-end.
6
10
7
11
## Configuring your integration
8
12
9
13
Before you can run this sample app on your local machine, you must first create a new integration with a Docusign developer account.
10
14
11
15
### Create a new integration
12
16
13
-
1. If you don't already have one, create a [free developer account](https://go.docusign.com/sandbox/productshot/?elqCampaignId=16535).
14
-
2. Log into your developer account, and navigate to [My Apps & Keys](https://admindemo.docusign.com/authenticate?goTo=apiIntegratorKey).
17
+
1. If you don't already have one, create a [free developer account](https://go.docusign.com/sandbox/productshot/).
18
+
2. Log into your developer account, and navigate to [My Apps & Keys](https://admindemo.docusign.com/apps-and-keys).
15
19
3. Select **Add App and Integration Key**.
16
-
4. Create a new integration that is configured to use **JSON Web Token (JWT) Grant**.
20
+
4. Create a new integration that is configured to use **JSON Web Token (JWT) Grant** and **Authorization Code Grant (ACG)**.
17
21
You will need the **integration key** itself and its **RSA key pair**. To use this application, you must add your application's **Redirect URI** to your integration key. See our video, [**Creating an Integration Key for JWT Authentication**](https://www.youtube.com/watch?v=GgDqa7-L0yo) for a demonstration of how to create an integration key (client ID) for a user application like this example.
18
22
- Save the **integration key** and **private RSA key pair** somewhere safe as you will need these later.
19
-
5. Add the following as redirect URIs for your app:
20
-
-http://localhost:3000
21
-
-http://localhost:3000/index
23
+
5. Add redirect URIs for your app. There are several variables from the **.env** file that are used in the code and configured for redirect urls. Find variables below in the **.env** file and add the values of these variables in the Docusign account settings in the appropriate **Redirect URIs** section:
Please pay attention that if you run the project in docker using the **docker-compose.local.yml** file, the variable FRONTEND_DEV_HOST there changes to the value **http://localhost:80**. Keep in mind that in this case this value will also have to be added to **Redirect URIs** section.
24
29
25
30
### Prerequisites
26
31
@@ -30,16 +35,6 @@ Before you can run this sample app on your local machine, you must first create
30
35
-[VS Code](https://code.visualstudio.com/)
31
36
-[Docker](https://docs.docker.com/get-docker/)
32
37
33
-
### Docusign account settings
34
-
35
-
The following must be enabled on your developer account in order to run all of the examples:
36
-
37
-
-**SMS delivery**: Follow the instructions in the [Docusign eSignature Admin Guide](https://support.docusign.com/guides/ndse-admin-guide-sending-settings) under the **Fields and Properties** section. Make sure "Allow SMS delivery to recipients" is checked.
38
-
-**Conditional routing**: Follow the instructions in the [Introduction to Conditional Routing](https://support.docusign.com/en/guides/ndse-user-guide-intro-to-conditional-routing) under the **Getting started with conditional routing** section. Make sure "Enable conditional routing" is checked.
39
-
-**CertifiedDelivery recipients**: Follow the instructions on this [Docusign eSignature Admin Guide](https://support.docusign.com/guides/ndse-admin-guide-sending-settings) under the **Recipient Roles** section. Make sure "Enable needs to view role" is checked.
40
-
-**Document visibility**: Follow the instructions on this [Docusign eSignature Admin Guide](https://support.docusign.com/guides/ndse-admin-guide-sending-settings) under the **Fields and Properties** section. Set your settings to "Must sign to view, unless sender," and make sure "Allow sender to specify document visibility" is checked.
41
-
-**IDV**: Follow the instructions in the [Docusign Identify - ID Verification Q&A](https://support.docusign.com/en/articles/Tech-Readiness-DocuSign-Identify-ID-Verification#How_to_add_ID_Verification_on_an_account) to enable IDV on your account.
42
-
43
38
### Install dependencies locally
44
39
45
40
1. Download or clone this repository to your workstation in a new folder named **sample-app-mymaestro-node**.
@@ -50,18 +45,23 @@ The following must be enabled on your developer account in order to run all of t
50
45
6. Install dependencies: **`npm install`**
51
46
7. Rename the **.env.example** file in the root directory to **.env**, and update the file with the integration key and other settings.
52
47
> **Note:** Protect your integration key and client secret. You should make sure that the **.env** file will not be stored in your source code repository.
53
-
8. Rename the **example_private.key** file to **private.key**, and paste your complete private RSA key into this file (including the header and footer of the key).
48
+
8. Rename the **example_private.key** file to **private.key**, and paste your complete private RSA key into this file (including the header and footer of the key). Private RSA you should get when created Docusign account.
54
49
55
-
## Running MyMaestro
50
+
## Running MyMaestro in development mode
56
51
57
52
1. Navigate to the application folder: **`cd sample-app-mymaestro-node`**
58
-
2. Navigate to the server folder: **`cd server`**
59
-
3. To start the server and client at the same time: **`npm run dev`**
60
-
4.**Or,** to run the server and client separately:
61
-
- In one terminal, navigate to the server folder (**`cd server`**) and run **`npm run server`**
62
-
- In a separate terminal, navigate to the client folder (**`cd client`**) and run **`npm start`**
63
-
5. Open a browser to **http://localhost:3000**
53
+
2. To start the server and client at the same time: **`npm run concurrently:dev`**
54
+
3.**Or,** to run the server and client separately:
55
+
- In one terminal, run **`npm run client:dev`**
56
+
- In a separate terminal, run **`npm run server:dev`**
57
+
4. Open a browser to **http://localhost:3000**
58
+
59
+
## Running MyMaestro in docker
64
60
65
-
## License information
61
+
You can run application in docker locally like in production mode
66
62
67
-
This repository uses the MIT License. See the [LICENSE](./LICENSE) file for more information.
63
+
1. Navigate to the application folder: **`cd sample-app-mymaestro-node`**
64
+
2. Make sure that you configured **.env** file and saved **private.key** in the root of the folder. Make sure that you have docker installed.
65
+
3. Run **`docker-compose -f docker-compose.local.yaml up -d`**
66
+
4. In order to stop containers run **`docker compose -f docker-compose.local.yaml down`**
0 commit comments