5a304e21c4
* FLOW-78: Support for adding recipient type in the add recipient action * add core required param for add recipient - param name : custom fields * Add custom fields to recipient * Support setting core params for all signer types * Support for inperson signer recipient type * Update response to fit schema for in person signer * New schema changs for connec 2.0 json sim * Update model to recognize Connect SIM 2.0 format * add custom fields to the webhook response model * Update webhook response transformation logic for connect 2.0 json sim format * FLOW-133: Support recipient types Agent, CC, Certified Delivery, Editor & Intermediary * Add recipient step has following 2 changes. * Remove custom fields * Update dropdown labels to match with NDSE * FLOW-136: Support witness recipient type * FLOW-84: Create envelope from template expects input for body when no recipients are specified Instead, present the user with option to add recipient name, email * Add dropdown menu for recipient verification * add static response UI verification - phone call * Add static response to phone call option * Add phone call info to body request * Reword the description of AdditionalRecipientData * Add routingOrder to Swagger.json * Remove commented code, and fix description. * Add phone call verification * Add static response for SMS UI * Add SMS verification action * Tag the recipient id field returned by add recipient step "important" , so that it shows in the UI output * Fix Code and Add Phone Call Verification * Change visibility of routingOrder * Add accesscode to function AddParams * Add access code verification * Add knowledge base verification * Add enum for drop down menu * adjust script file to add enum * Fix typo * Fix Typo * Fix typo * In case recipient roles are not specified in the template, request "Email subject" and "Email body" from the user * Fix whitespaces * Add get request * Add dropdown menu for workflow IDs * Add identity verification * Make the connect trigger changes backward compatible using versioning * Keep the previous version of operation id the same for create envelope using template action * Combine the SMS and Phone call verification * Fix typo * Update name for send envelope using template * Add Knowledge base to the branch * Replace async to void * Add client user id to recipient * fix typo * Fix Typo * Add embedded signing UI * Add the URL in the output * Change the clientID to advanced options * Change 'D' to 'd' * Change 'A' to 'a' * Add custom fields to "create envelope using template" FLOW action * Change name to "GenerateEmbeddedSigningURL" * Rename the method * Extract parsing custom fields to a separate method * Use a prefix to differentiate between text custom field and list custom field * FLOW-159: enable user to set label for tabs, in the add recipient tabs step * Change default URL * Add embedded sender action * Add embedded sender response * Add embedded sender url method * Add method to transformRequestBody * Add open in drop down * Add open in tagging or prepare function * Add drop down menu for return URL * Add the return URL * FLOW-180: Version "add recipient to an envelope" action * Remove space in the return url * Change name of return URL * Change return URL name in script file * Change letter to lowercase * Remove duplicated method * FLOW-184: Support adding list custom fields for "create envelope using template" and "create envelope" actions List custom fields shows up as an enum * FLOW-168: list custom fields missing in the connect response * Rename custom fields variable name * Fix merge conflicts * Move the login information code block to where it was * Add verification type action * Add ClientUserId to Recipient Co-authored-by: Srihari Padmanabhan <srihari.padmanabhan@docusign.com> Co-authored-by: Srihari Padmanabhan <90345666+sriharip-docusign@users.noreply.github.com> Co-authored-by: Angel Garcia Reyes <angel.garcia.reyes@docusign.com> |
||
|---|---|---|
| .. | ||
| apiDefinition.swagger.json | ||
| apiProperties.json | ||
| readme.md | ||
| script.csx | ||
readme.md
Title
DocuSign helps organizations connect and automate how they prepare, sign, act on, and manage agreements. The DocuSign Demo connector connects only to DocuSign Demo environments but offers the same functionality as the regular DocuSign connector. Any documents in a DocuSign Demo environment are not legally binding. For all non-demo uses, use the regular DocuSign connector.
Prerequisites
To use the Connect trigger in this integration, DocuSign Connect must be enabled in your DocuSign account. It is not enabled by default. Once enabled, the Connect Settings page can be accessed from the DocuSign Admin web application. Using the Connect trigger in this integration will automatically register the webhook for you.
Obtaining Credentials
To try the connector, please use a DEMO account:
- Go to https://developers.docusign.com/
- Create Sandbox account.
These are different than free trials in that they never expire, have 90% of our paid account features, and none of the documents sent through DEMO are legally binding ((https://support.docusign.com/en/articles/Free-account-vs-Developer-account).
Connector Documentation
For detailed documentation around the connector please refer to https://support.docusign.com/en/guides/DocuSign-eSignature-for-Microsoft-Power-Automate
Known Issues and Limitations
For issues with DocuSign please try this link first: https://support.docusign.com/en/articles/How-Do-I-Open-a-Case-in-the-DocuSign-Support-Center.
Deployment Instructions
Please use these instructions to deploy this connector as custom connector in Microsoft Power Automate and Power Apps.