Merge branch 'main' of https://github.com/docusign/developers-meetup-blr

Author: amrit930203

Workshop-1/01-Overview/Prerequisites.md

@@ -59,4 +59,4 @@ Contact your workshop facilitator or refer to the [Resources](../resources/Resou
 
 ## Next Step
 
-Proceed to [Docusign Salesforce Agentforce](../02-Docusign-Salesforce/Docusign-Agentforce-Integration.md)
+Proceed to [Docusign Salesforce Agentforce](../02-Salesforce%20Docusign%20Agentforce/demo_steps.md)

Workshop-1/02-Salesforce Docusign Agentforce/use-case.md

@@ -0,0 +1,46 @@
+![docusign-developers-logo](https://raw.githubusercontent.com/docusign/developers-meetup-blr/a271c616b0c6e69da79e90eda7ebea44ca0eed8a/assets/images/01-docusign_developers_lockup_387x50.svg)
+
+# Overview
+
+## Use Case
+
+Imagine you are the **lead developer at Fontaraa**. It is the final day of the financial quarter.
+
+Your high-performing sales representative is using Salesforce to close a deal with an enterprise-level customer. 
+Every minute counts and the last thing your team needs is a slow, manual agreement process standing between you and the close.
+
+> Your mission is to build a seamless, end-to-end agreement experience using **Docusign**.
+
+
+***
+
+## The Bottleneck
+
+Without the right tooling, your sales representative faces the following challenges:
+
+* **Manual data entry** : Generating a custom, negotiated MSA (Master Services Agreement) directly from Salesforce requires manually copying fields from the CRM such as account name, customer name, contract value, and more into the agreement template.
+* **Collaboration chaos** : Sending the agreement to the Customer, Legal, and Finance teams for approval results in an unmanageable email chain with no central place to track changes or versions.
+* **No visibility:** Stakeholders have no real-time visibility into where the agreement stands in the process.
+
+***
+
+## The Solution
+
+Using the Docusign platform, you will build a solution that addresses each of these bottlenecks:
+
+| Challenge               | Solution                                                                                                             |
+| ----------------------- | -------------------------------------------------------------------------------------------------------------------- |
+| Manual field population | Pull account name, customer name, contract value, and other CRM data directly from Salesforce into the MSA template. |
+| Disconnected approvals  | Route the agreement to Customer, Legal, and Finance through a structured, trackable workflow                         |              |
+| Lack of visibility      | Notify all stakeholders automatically at each stage of the agreement lifecycle                                       |
+
+***
+
+## The Outcome
+
+By the end of this workshop, you will have built a complete agreement workflow that takes your sales representative from a Salesforce opportunity all the way to a **signed MSA** without leaving the tools they already use, without manual data entry, and without chasing approvals over email.
+
+> The goal is simple: close the deal before the quarter ends.
+
+
+---

Workshop-1/03-Developer-Console/developer-console.md

@@ -46,7 +46,7 @@ Follow the procedure to generate Integrtion Key (IK) through Developer Console:
 - [ ] Step 1: Go to <https://apps.docusign.com/dev-console/integrations>
 - [ ] Step 2: Enter Email as ```docusigndevelopersworkshop@zohomail.in```
 - [ ] Step 3: Select **Next**
-- [ ] Step 4: Enter password as ``````
+- [ ] Step 4: Enter password as (displayed during the session)
 
 ## Add an Integration Key (IK)
 

Workshop-1/05-Workflow-Builder/Workflow-Builder.md

@@ -2,7 +2,7 @@
 
 # Workflow Builder
 
-This module covers building automated agreement workflows using Docusign's no-code/low-code **Workflow Builder**.
+This module covers building automated agreement workflows using Docusign's no-code/low-code **Workflow Builder** (Formerly Maestro)
 
 ---
 
@@ -17,106 +17,18 @@ This module covers building automated agreement workflows using Docusign's no-co
 
 ---
 
-## Key Concepts
-
-| Concept | Description |
-|---------|-------------|
-| **Trigger** | The event that starts the workflow (e.g., form submission, API call, scheduled time) |
-| **Step** | An individual action in the workflow (send envelope, wait, branch, etc.) |
-| **Condition** | Logic that determines which path the workflow takes |
-| **Participant** | A person involved in the workflow, resolved dynamically at runtime |
-
----
-
 ## Lab Steps
 
 ### Step 1 — Access Workflow Builder
 
-1. Log in to your Docusign sandbox
-2. Navigate to **Agreements > Workflow Builder**
-3. Click **New Workflow**
-4. Name your workflow: `Vendor Onboarding NDA`
-
-> Screenshot placeholder: `../assets/images/03-workflow-builder-canvas.png`
-
----
-
-### Step 2 — Configure the Trigger
-
-1. Select **Web Form** as the trigger type
-2. Define the input fields:
-   - Vendor Name (text)
-   - Vendor Email (email)
-   - Contract Value (number)
-3. Save the trigger configuration
-
----
-
-### Step 3 — Add a Send Envelope Step
-
-1. Click **+** on the canvas to add a step
-2. Select **Send Envelope**
-3. Choose your NDA template from the template picker
-4. Map participants:
-   - Role `Vendor` → Workflow input field `Vendor Email`
-5. Enable **Reminders**: every 2 days, up to 3 reminders
-
----
-
-### Step 4 — Add a Conditional Branch
-
-1. Add a **Branch** step after the envelope step
-2. Configure:
-   - **Branch A (Signed):** Trigger a webhook notification to your backend
-   - **Branch B (Declined/Voided):** Send a notification email to the internal team
-3. Add a **Wait** step in Branch A with condition: `Envelope Status = Completed`
-
----
-
-### Step 5 — Publish and Test
-
-1. Click **Publish** to activate the workflow
-2. Copy the web form URL generated by the workflow
-3. Open the URL in a new tab and fill in test data
-4. Monitor workflow execution in **Workflow History**
-
----
-
-## Exported Workflow Files
-
-Pre-built workflow exports for this workshop are located in the [`exports/`](./exports/) folder.
-
-| File | Description |
-|------|-------------|
-| `vendor-onboarding-nda.json` | Vendor NDA with conditional routing |
-| `employee-onboarding-packet.json` | Multi-document employee onboarding workflow |
-| `procurement-approval.json` | Procurement approval with manager escalation |
-
-To import an exported workflow:
-1. In Workflow Builder, click **Import**
-2. Select the `.json` file from the `exports/` folder
-3. Review and adjust participant mappings before publishing
-
----
-
-## Tips
-
-- Use **Test Mode** before publishing to simulate workflow runs without sending real emails
-- Name your steps clearly — they appear in the audit trail
-- Use **workflow variables** to pass data between steps
-
----
-
-## Troubleshooting
-
-| Issue | Resolution |
-|-------|-----------|
-| Workflow not triggering | Ensure the workflow is **Published**, not just saved |
-| Participant not resolved | Check that the participant email field mapping is correct |
-| Webhook not received | Verify the webhook URL is HTTPS and publicly accessible |
-
----
+1. Download the workflow files available in  [`05-Workflow-Builder/exports/`](./exports/)
+2. Log in to your Docusign Developer Account
+3. Go to **Agreements > Workflows**
+4. Select **Create Workflow**
+5. Select **Import Workflow**.
+7. Import both the workflow builder files.
+  * ```workflow-1-name```
+  * ```workflow-1-name```
 
-## Next Step
+> Follow the demo for the next steps of configuring workflows in Docusign Workflow Builder.
 
-Proceed to [Agreement Desk](../04-Agreement-Desk/Agreement-Desk.md)

Workshop-1/05-Workflow-Builder/exports/README.md

@@ -6,28 +6,16 @@ This folder contains exported Docusign Workflow Builder files (`.json`) that can
 
 | File | Description | Trigger Type |
 |------|-------------|--------------|
-| `vendor-onboarding-nda.json` | Vendor NDA workflow with conditional signed/declined routing | Web Form |
-| `employee-onboarding-packet.json` | Multi-document employee onboarding with sequential signing | API / Scheduled |
-| `procurement-approval.json` | Procurement approval workflow with manager escalation step | Web Form |
+| `workflow-1-name.zip` | Workflow to receive inputs Claude LLM and send as a request to Agreement Desk | API |
+| `workflow-2-name.zip` | Workflow to pull all the submitted requests in Agreement Desk, add documents, send approvals, and send envelopes for eSign | Events |
 
 ## How to Import
 
-1. Log in to your Docusign sandbox
-2. Navigate to **Agreements > Workflow Builder**
-3. Click the **Import** button (top right)
-4. Select the `.json` file you want to import
+1. Log in to your Docusign Developer Account
+2. Go to **Agreements > Workflows**
+3. Select **Create Workflow**
+4. Select **Import Workflow**.
 5. Review the imported workflow — check participant mappings and template references
-6. Update any template IDs to match templates in your own sandbox
-7. Click **Publish** when ready to activate
+6. Update any template IDs to match templates in your own Developer account.
+7. Select  **Save and Publish** when ready to activate
 
-## How to Export Your Own Workflows
-
-1. Open any workflow in Workflow Builder
-2. Click the **...** menu (top right)
-3. Select **Export**
-4. Save the `.json` file and add it to this folder
-
-## Notes
-
-- Exported workflows reference template IDs from the original account. You must re-link templates after importing into a different account.
-- Webhook URLs in exported workflows must be updated to point to your own endpoints.

Workshop-1/Readme.md

@@ -6,7 +6,7 @@
 
 ## Overview
 
-This workshop introduces developers to Docusign's **Intelligent Agreement Management** platform through a structured, progressive set of hands-on modules. Participants configure real integrations from setting up a Developer Console and connecting Claude via MCP, to building automated workflows in approximately **70 minutes**.
+Workshop-1 provides developers with a introduction to Docusign's Intelligent Agreement Management platform. Progressive modules guide participants through configuring real-world integrations starting with the Developer Console, connecting Claude via the Model Context Protocol (MCP), and building the automated workflows through Workflow Builder.
 
 ---
 
@@ -27,15 +27,15 @@ Before the session, ensure you have the following accounts set up and verified:
 
 | Requirement | Details |
 |-------------|---------|
-| **Docusign Developer Sandbox** | Free account at [Docusign Developer Account](https://www.docusign.com/developers/sandbox?postActivateUrl=https%3A%2F%2Fdevelopers.docusign.com%2F) |
+| **Docusign Developer Account** | Free account at [Docusign Developer Account](https://www.docusign.com/developers/sandbox?postActivateUrl=https%3A%2F%2Fdevelopers.docusign.com%2F) |
 | **GitHub** | Access to this repository |
 | **Claude (Anthropic)** | Access to [claude.ai](https://claude.ai) |
 
 **Before the session starts:**
 1. Create all accounts and verify your email addresses
 2. Locate your **8-digit Docusign Account ID** from your Docusign profile settings
 3. Share your Account ID with a workshop volunteer before the session begins
-4. Confirm you can log into all three platforms
+4. Confirm you can log into all three platforms (Docusign developer account, Github, and Claude)
 
 > See [`01-Overview/Prerequisites.md`](./01-Overview/Prerequisites.md) for detailed setup instructions.