Skip to content

Conversation

@youngl-docusign
Copy link
Contributor


When submitting a connector, please make sure that you follow the requirements below, otherwise your PR might be rejected. We want to make you have a well-built connector, a smooth certification experience, and your users are happy :)

If this is your first time submitting to GitHub and you need some help, please sign up for this session.

  • I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
  • I attest that the connector works and I verified by deploying and testing all the operations.
  • I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
  • I attest that I have added response schemas to my actions, unless the response schema is dynamic.
  • I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
  • If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

If you are an Independent Publisher, you must also attest to the following to ensure a smooth publishing process:

  • I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
  • Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
  • Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
  • If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

harshitav-docusign and others added 30 commits March 14, 2024 18:16
Flow-532: Add MS keywords to the Get Envelopes by recipients
Flow 507: Custom action to return envelopes based on their status
Flow-544: Output Requirements: pagination and sorting functionality
Flow-536: Ability to configure Envelope expiry in Power Automate
Flow 547: Add custom fields search ability to the AI plugin ListEnvelopes custom action
Port changes from  Msds1006.4.3.2024.demo  to Harshita dev
youngl-docusign and others added 22 commits January 24, 2025 15:39
Add logic for no signer when grabbing signer name in list envelopes
* Update Sender Name

* Bulk change items
* Update Sender Name

* Bulk change items
…#88)

* Fix object null checks for list envelopes and co-pilot list envelopes
@youngl-docusign
Copy link
Contributor Author

youngl-docusign commented Jan 31, 2025

@microsoft-github-policy-service agree company="Docusign"

Copy link
Contributor

@vmanoharas vmanoharas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dear Partner,

Congratulations your PR is approved !! We are proud to announce the Brand-New Certification experience for you to certify Power Platform Copilot Connectors & Plugins. Read the blog here- Announcing Partner Center to certify and publish Power Platform Copilot Connectors and Plugins - Microsoft Power Platform Blog

As next steps:

  1. Learn about the new certification experience- Get your Power Platform connector and plugin certified - Overview
  2. Package your connector and plugin files- Prepare Power Platform connector and plugin files for certification
  3. Validate the package for structure before submitting the package for certification to Partner Center - Run Package Validator tool
  4. Initiate a certification request in Partner Center- Verified publisher certification process
  5. Ensure your connector & plugin files comply to the Marketplace policies here- 5000 Power Platform Connector Policies for Marketplace and also 1000 Marketplace policies(as applicable)
  6. Test your connector post certification to provide go-live for deployment- Testing Guidelines
  7. If you wish to Update your connector or plugin in future- Updating Guidelines

For any queries or concerns please get in touch with us on certificationteam@microsoft.com

@vmanoharas
Copy link
Contributor

Hello @youngl-docusign,

Please accept the CLA, even though we have already approved this PR. Once the CLA is accepted, we will proceed further.

@youngl-docusign
Copy link
Contributor Author

youngl-docusign commented Jan 31, 2025

@youngl-docusign please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

  • (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
  • (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree company="DocuSign"

@youngl-docusign
Copy link
Contributor Author

Hello @youngl-docusign,

Please accept the CLA, even though we have already approved this PR. Once the CLA is accepted, we will proceed further.

@vmanoharas Thank you for approving. I have accepted the agreement.

@vmanoharas vmanoharas merged commit 72e93a2 into microsoft:dev Feb 3, 2025
2 checks passed
jeremiahsm-docusign added a commit to release-docusign/PowerPlatformConnectors that referenced this pull request Feb 20, 2025
* Flow-532

* Filters working for most of the cases

* Working for status, emailid

* remove debuggin lines

* Implemented sorting order, Skip and top, folder-Ids

* updated the description

* Added expiry after in the Add reminder for envelope

* Added custom field support

* Fixed indendation

* Add custom name search field

* correct the customFieldName

* correct the spell error

* Bunmping the release number

* Prod branch for DS1006 release created

* correct the host name

* Update the description

* Branding update added

* Resend envelope AI enabled

* ListEnvelope for sales copilot added

* Migrated code from demo to Prod

* Undo prod related texts

* spell corrections

* Update spelling error

* fixed the if case at filteredEnvelopes

* Remove extra brackets

* to and from Date propertiews updates. Resend automatically picks up the Account id

* Key sales custom action added

* Email summary added

* update the connector description to be within character limit.

* Prod code updated

* Update description of the demo connector.

* Descriptions updated to related activities and records

* Email summary and Key sales info are tested to be working

* Update the description

* Update background color to white

* swagger updates are made and protocol is filtered for crmOrgURL

* Update the description

* Check for forward slash and update the parameter

* Add recipientGuid. Add TabInfo in the tabs

* add decline tab to add tabs action

* support all tab types

* Read hostURL from the context

* Rename the host url methods and optimise the GetEnvelopeURL code

* Renaming variables

* UpdateDSDemoDescription

* Upgrade the version number

* FLOW-198 suuport all tab types

* remove unused array

* FLOW-20 Apply a template

* Fix sales copilot Email Summary issue

* Updated the description of List envelopes

* Hostname changes ported from Prod connector

* Update the end date description

* FLOW-623 numerical tab field update

* FLOW-623 update numerical value field label

* FLOW-629 document ID field added to Checkbox groups

* get tab info action does not support tab groups

* Update the spelling of the associated word

* FLOW-608 support sms delivery option

* Porting demo code to Prod connector

* Changes for adding single document download to Get envelope documents action.

* Revert "Changes for adding single document download to Get envelope documents action."

* hotfix revert enums in tabs

* rebase with young's repo

* remove unnecessary change

* add missing bracket that was removed when rebasing

* prefill tabs logic added

* MS.DS1007.11.15.2024.Prod.Hotfix

* rebased with dev

* prod folder updated

* swagger title reverted

* Extended GetRecipientFields method to accept Recipient Guid as well

* support tab values

* FLOW-247-composite-templates

* enum added for numerical tabs

* syntax error

* FLOW-74-bulk-send

* remove some changes

* revert enum changes

* recipient types added

* Add recipientId to the Get recipient info from envelope

* Audit list event added

* additional enhancement

* removed manual bulk send

* broken down into smaller functions

* removed status field

* name of the action changed

* changes after product review

* Composite Templates minor language update

* Add radio tab type to Get info tab

* composite templates revert operation ID

* Added UpdateDocGen method

* DocGen feature from harshita-dev

* fix the typo in the description

* Add error message in the swagger file for the 200 response

* Fixing backward compatibility issue

* bulk send updates after demo

* comments addressed

* STRATEGIC-81 add signing group to composite templates

* Search List Envelopes action
Creates a brand new action based on the exist copilot list envelopes
action

* STRATEGIC-87 deprecate create envelope with recipients

* FLOW-670 add checkbox value to get document tabs

* name also added

* Content updates for DocGen

* Flow-650 add dictionaries for api variable names (#64)

* Flow-650 add dictionaries for api variable names

* Changes to add new action - start Maestro workflow.

* Feature/flow 650 results boolean (#66)

* Update wording

* Add scopes need for Maestro actions.

* STRATEGIC-166 SMS delivery only

* email retireved from body instead of query

* Changing the nuld_number call method to PUT call

* STRATEGIC-90 id verification with EU

* description updated

* STRATEGIC-162 signing url for in person signer fixed

* language update

* remove signer email

* Feature/STRAT 185 (#73)

Content changes for list envelopes and bulk send actions

* Code changes to update error message for invalid JWT token.

* Update content on signer emial and SMS phone number for "update recipient" action and "add recipient to envelope" action (#76)

* Updated the description of Table row and Table name

* STRATEGIC-186-hide-recipient-ID-in-embedded-signing-flow

* deprecated old action

* STRATEGIC-193 update create envelope with recipients and tabs

* email body lowercased

* language update

* ID capitalized

* STRATEGIC-192-add-sms-method

* Add logic for no signer when grabbing signer name in list envelopes and co-pilot list envelopes

* paconn validate fixes

* Bugfix/content change (#82)

* Update Sender Name

* Bulk change items

* remove descriptions

* add empty string

* adding gray text back

* paconn validate fixes

* Bugfix/content change (#82)

* Update Sender Name

* Bulk change items

* remove descriptions

* add empty string

* adding gray text back

* version bump

* Build 8 Prod folder rebase

* remove missingInput variable

* Fix object null checks for list envelopes and co-pilot list envelopes (#88)

* Fix object null checks for list envelopes and co-pilot list envelopes

---------

Co-authored-by: Harshita Vinnakota <harshita.vinnakota@docusign.com>
Co-authored-by: harshitav-docusign <118772192+harshitav-docusign@users.noreply.github.com>
Co-authored-by: release-docusign <126611882+release-docusign@users.noreply.github.com>
Co-authored-by: DOCUSIGNHQ\Prashanth.Bachu <prashanth.bachu@docusign.com>
Co-authored-by: prashanthb-docusign <prashanth.bachu@dsxtr.com>
Co-authored-by: jeremiahs-docusign <jeremiah.smith@docusign.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants