PowerPlatformConnectors icon indicating copy to clipboard operation
PowerPlatformConnectors copied to clipboard

Published 20 hours ago • verified publisher icon microsoft

Updated apiDefinition.swagger.json

Open gulshankhurana opened this issue 10 months ago • 4 comments

Changed the name from 'FCA' to 'Financial Conduct Authority (FCA) UK' and also updated the description.

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.

  • [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.
  • [x] I attest that the connector works and I verified by deploying and testing all the operations.
  • [x] I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
  • [x] I attest that I have added response schemas to my actions, unless the response schema is dynamic.
  • [x] I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
  • [x] 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)
  • [x] 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.
  • [x] Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
  • [x] If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

gulshankhurana avatar Apr 20 '24 23:04 gulshankhurana

@vmanoharas, I have updated the apiDefinition.swagger.json as per your advice under #3242

gulshankhurana avatar Apr 20 '24 23:04 gulshankhurana

@vmanoharas , fixed the issue as advised. Thanks.

gulshankhurana avatar Apr 22 '24 16:04 gulshankhurana

[[certify-connector]]

vmanoharas avatar Apr 23 '24 09:04 vmanoharas

[[certify-connector]]

vmanoharas avatar May 14 '24 10:05 vmanoharas

Hi @vmanoharas I have fixed action errors caused by change in api definition by the api provider. I also added 2 more actions. Please approve at your earliest convenience as some people are eagerly awaiting these changes to take effect so that they can start using this connector asap.

Kind regards Gulshan

gulshankhurana avatar May 16 '24 00:05 gulshankhurana

[[certify-connector]]

vmanoharas avatar May 17 '24 16:05 vmanoharas

Hello @gulshankhurana,

This PR is failing to upload into our validation tools, kindly close this PR and create new fresh PR.

vmanoharas avatar May 17 '24 16:05 vmanoharas

Hi @vmanoharas

As suggested, I have opened a new PR #3495 .

Thanks. Gulshan

gulshankhurana avatar May 17 '24 17:05 gulshankhurana