Skip to content

Conversation

@MohsinAQ
Copy link
Contributor

@MohsinAQ MohsinAQ commented Feb 11, 2022


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

@MohsinAQ MohsinAQ requested a review from a team as a code owner February 11, 2022 12:25
@ghost
Copy link

ghost commented Feb 11, 2022

CLA assistant check
All CLA requirements met.

@Amjed-Ayoub
Copy link
Contributor

Dear partner,

We apologize for the delay you might be experiencing while we are working on a high volume of connector requests. Rest assured that we are doing everything we can to address this volume. We are taking measures like improving our processes and hiring additional team members to guarantee resolving your connector requests in a timely manner.

Please let us know if you have any questions in the meantime.

@MohsinAQ
Copy link
Contributor Author

MohsinAQ commented Mar 3, 2022 via email

@sriyen-msft
Copy link
Contributor

@MohsinAQ I'm just checking in to see how things are going with updating your connector artifacts as per the given feedback. Please feel free to reach out with any questions you may have, Thanks.

@MohsinAQ
Copy link
Contributor Author

@MohsinAQ I'm just checking in to see how things are going with updating your connector artifacts as per the given feedback. Please feel free to reach out with any questions you may have, Thanks.

@sriyen-msft Hi. I have a few questions regarding one of the changes requested. Can we schedule a quick call?

@MohsinAQ
Copy link
Contributor Author

MohsinAQ commented Mar 15, 2022 via email

@sriyen-msft
Copy link
Contributor

Hi, I have a few questions regarding the changes requested. Can we please schedule a quick call to discuss? Best Regards, Mohsin Ahmed Qureshi Development Manager Microsoft Business Applications Imperium Dynamics | https://imperiumdynamics.comhttps://imperiumdynamics.com/

________________________________ From: Srikanth Yenagandhula @.> Sent: Tuesday, March 15, 2022 7:01 AM To: microsoft/PowerPlatformConnectors @.> Cc: Mohsin Ahmed @.>; Mention @.> Subject: Re: [microsoft/PowerPlatformConnectors] Power Textor (PR #1425) @MohsinAQhttps://github.com/MohsinAQ I'm just checking in to see how things are going with updating your connector artifacts as per the given feedback. Please feel free to reach out with any questions you may have, Thanks. — Reply to this email directly, view it on GitHub<#1425 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AVSFK7NJBTS7PKZD7ZPLIFDU77VPZANCNFSM5OED6REA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you were mentioned.Message ID: @.***>

@MohsinAQ Can you please let us know your questions here, or you can start an email thread with us (ConnectorPartnerMgmtTeam@service.microsoft.com) by listing down all the questions you have on the feedback?

@MohsinAQ
Copy link
Contributor Author

Hi. I have replied to one of the changes you guys have requested with a query I have against it. Please get back to me whenever possible, Thanks!

@Amjed-Ayoub
Copy link
Contributor

Hello @MohsinAQ,
I am following up with you to see how things are going with updating your connector.
Please let us know if you need any help as we are always happy to assist you.
Thank you very much.

MohsinAQ added 3 commits April 5, 2022 15:40
Updated API definition swagger file and readme file
@MohsinAQ MohsinAQ requested a review from sriyen-msft April 5, 2022 10:48
@MohsinAQ
Copy link
Contributor Author

MohsinAQ commented Apr 5, 2022

Hi @Amjed-Ayoub,
I have updated this pull request with the requested changes.
Please review the changes and let me know if any further change is required.
Thank you.

@Amjed-Ayoub
Copy link
Contributor

Hi @MohsinAQ, Thank you for the update. Our Certification Engineers will review soon.
Thank you very much

@v-eisljami v-eisljami merged commit efbf464 into microsoft:dev Apr 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants