PowerPlatformConnectors icon indicating copy to clipboard operation
PowerPlatformConnectors copied to clipboard

Proposal - ConnectWise Manage (Independent Publisher)

Open TBecktold opened this issue 2 years ago • 4 comments


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 :)

Developer note: This is not a full submission of a connector, simply a proposal (following these instructions) to create a ConnectWise Manage connector. Please let me know if this is not the most current way to do this and I will make the necessary changes. Thanks!

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

  • [ X] 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:

  • [ X] 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.

TBecktold avatar Jan 18 '23 20:01 TBecktold

Hello @TBecktold, Thank you so much for your new proposal submission. We are looking forward to seeing your connector artifacts soon. Please let us know if you have any questions. Thank you so much again for working with us.

Amjed-Ayoub avatar Jan 19 '23 17:01 Amjed-Ayoub

Hello @TBecktold ,

I hope you are doing well.

We would like to know the status of your connector. It has been in our repo since January 2023. Please let us know how you would like to proceed.

Please do not hesitate to reach out if you have any questions as we are always happy to help.

Thank you very much.

Amjed-Ayoub avatar Jun 05 '23 23:06 Amjed-Ayoub

Hello @TBecktold ,

I hope you are doing well.

We would like to know the status of your connector. It has been in our repo since January 2023. Please let us know how you would like to proceed.

Thank you very much.

vmanoharas avatar Sep 06 '23 12:09 vmanoharas

It can be dropped, I am no longer available to progress development.

Thanks

On Wed, Sep 6, 2023, 7:57 AM vmanoharas @.***> wrote:

Hello @TBecktold https://github.com/TBecktold ,

I hope you are doing well.

We would like to know the status of your connector. It has been in our repo since January 2023. Please let us know how you would like to proceed.

Thank you very much.

— Reply to this email directly, view it on GitHub https://github.com/microsoft/PowerPlatformConnectors/pull/2314#issuecomment-1708302958, or unsubscribe https://github.com/notifications/unsubscribe-auth/AK54LT7KJTAFW346WCQLRBDXZBXMRANCNFSM6AAAAAAT7QLGKY . You are receiving this because you were mentioned.Message ID: @.***>

TBecktold avatar Sep 06 '23 13:09 TBecktold

Thanks for confirming @TBecktold, I am closing this PR.

vmanoharas avatar May 21 '24 12:05 vmanoharas