PagePixels Screenshots (Certified Publisher) #3937
Conversation
* Partner Center connector - new fields and deal registration actions (microsoft#2130) * Update apiDefinition.swagger.json * Latest changes * fix format warning * X-Caller_Id should be optional * Update apiDefinition.swagger.json Review changes - ->Added reg status and sub status fields. ->Update the fields descriptions as per api's details available on Microsoft public site. ->Remove submission related fields. ->Mark registration status field as read only. ->Remove offerId from root. ->Use Enum values in Create deal registration model. ->Create a separate model for update deal registration. Create a separate action for update deal registration. * Update apiDefinition.swagger.json * Update apiDefinition.swagger.json Add deprecate text in Update a referral by Id action * Update apiDefinition.swagger.json Connector status keep as Preview and UpdateReferralById deprecated keep as false but deprecated word in description. * Update apiDefinition.swagger.json update deal registration success message. * Update apiDefinition.swagger.json added title for registration object * Bitskout Connector (microsoft#2140) * Bitskout Connector * Requested changes * EC-14395 Make it so fields aren't required anymore for updates (microsoft#2150) * Added orderby parameter * Added orderby parameter * feat: add x-ms-pageable extension * feat: add updatenextlink policy instance * refactor: whitespace refactoring * Update apiProperties.json * fix(EC-14395): Integrate the patch schema endpoint * fix(EC-14395): Add specs for the schema endpoint's responses * fix(EC-14395): Add required fields to the schema Co-authored-by: Johannes Heesterman <[email protected]> Co-authored-by: johannesheesterman <[email protected]> Co-authored-by: Stan van Rooy <[email protected]> * ManageEngine ServiceDesk Plus Cloud app submission * Categories and readme document updated * Categories updated --------- Co-authored-by: Farhan <[email protected]> Co-authored-by: saferoombiz <[email protected]> Co-authored-by: Tess Ellenoir Duursma <[email protected]> Co-authored-by: Johannes Heesterman <[email protected]> Co-authored-by: johannesheesterman <[email protected]> Co-authored-by: Stan van Rooy <[email protected]> Co-authored-by: Mahbub Murshed <[email protected]> Co-authored-by: SDPCloud <[email protected]>
* - Initial Commit
|
@microsoft-github-policy-service agree |
There was a problem hiding this comment.
Hi @Anthony-Dev,
Can you please refer below Certified connector link and submit only files required. Additionally the logo file is not needed and readme file should include all the required sections.
https://github.com/microsoft/PowerPlatformConnectors/tree/dev/templates/certified-connectors
…ry logo.png file.
Thank you @certificationteam - I have removed the logo.png file and updated the Readme to match the structure in the provided template. |
certified-connectors/PagePixels Screenshots/apiDefinition.swagger.json
Outdated
Show resolved
Hide resolved
…apiDefinition to fix typos.
….json to define the Website, Privacy Policy, and Categories.
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
There was a problem hiding this comment.
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.
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
|
Hi @Anthony-Dev, Please change the branch from master to dev, as we cannot merge this code. You have used master branch 
Please use dev branch. 
|
Hi @vmanoharas - Thanks, I’ve updated the PR to target the microsoft:dev branch instead of master. I can also recreate this PR from the fork's |
|
Hey @vmanoharas / @certificationteam - I went ahead and created another PR request from PagePixels:dev into microsoft:dev explicitly, in case it is helpful. |
Thank you @Anthony-Dev for creating new PR. Kindly close this PR. |
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.
apiDefinition.swagger.json, by runningpaconn validatecommand.apiProperties.jsonhas a valid brand color and doesn't use an invalid brand color,#007ee5or#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: