Skip to content

Conversation

@harshitav-docusign
Copy link
Collaborator


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.

sriharip-docusign and others added 30 commits January 19, 2023 10:57
FLOW-292: witness "name" should not be displayed as a required field
FLOW-271: Power Automate: Unable to turn off and turn back on, a flow, that uses connect trigger
FLOW-312 - Value property needs to be part Get envelope custom field action
FLOW-338: template prefill : in create from template action , add support for email subject and body
* support SMS delivery
* support all recipient types
harshitav-docusign and others added 25 commits October 16, 2023 16:26
(cherry picked from commit 9b6111c)
…-docusign/BugBashFixes

SalesCopilot: Recipient names as array. Status to TitleCase. DocumentNLP formatting
…Id_issue

RecordId and OrgUrl filters fixed. Activities and Records render latest first
SalesCopilot: Recipient names as array. Status to TitleCase. DocumentNLP formatting
Added back transformPdfFields. Bug fixes from the bugbash
Sales Co-pilot release candidate Ms flow.ds1003.10.17.2023
…uest #38 from harshitav-docusign/swagger_updates

Fixed swagger errors. Remove envelope Id from the description
{
var content = await response.Content.ReadAsStringAsync().ConfigureAwait(false);
var body = ParseContentAsJObject(content, false);

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I am removing this block of code to test it on the Preview environment on the issue of creating duplicate configs in the Connect.

@harshitav-docusign harshitav-docusign merged commit e077e2c into dev Mar 13, 2024
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.

5 participants