Skip to content

Update Taqnyat API Definition #3827

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Apr 15, 2025
Merged

Update Taqnyat API Definition #3827

merged 6 commits into from
Apr 15, 2025

Conversation

TaqnyatNocTeam
Copy link
Contributor

@TaqnyatNocTeam TaqnyatNocTeam commented Apr 6, 2025


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.

@TaqnyatNocTeam TaqnyatNocTeam requested a review from a team as a code owner April 6, 2025 10:08
vmanoharas

This comment was marked as duplicate.

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.

Hi @TaqnyatNocTeam,

Please fix the one review comment.

@TaqnyatNocTeam
Copy link
Contributor Author

Hi @TaqnyatNocTeam,

Please fix the one review comment.

Thanks @vmanoharas , typo was fixed

vmanoharas
vmanoharas previously approved these changes Apr 11, 2025
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 !!

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 [email protected]

Many thanks,
Power Platform
Copilot connector & plugin certification team

@vmanoharas
Copy link
Contributor

Hi @TaqnyatNocTeam,

PR is approved, but cannot merge due to conflict, please resolve the conflict.

image

@TaqnyatNocTeam
Copy link
Contributor Author

Hi @TaqnyatNocTeam,

PR is approved, but cannot merge due to conflict, please resolve the conflict.

image

Hi, the conflict has been resolved

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 !!

As next steps:

Learn about the new certification experience- Get your Power Platform connector and plugin certified - Overview
Package your connector and plugin files- Prepare Power Platform connector and plugin files for certification
Validate the package for structure before submitting the package for certification to Partner Center - Run Package Validator tool
Initiate a certification request in Partner Center- Verified publisher certification process
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)
Test your connector post certification to provide go-live for deployment- Testing Guidelines
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 [email protected]

Many thanks,
Power Platform
Copilot connector & plugin certification team

@vmanoharas vmanoharas merged commit 66e7594 into microsoft:dev Apr 15, 2025
1 check passed
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.

3 participants