Update Flotiq connector definition

[WHLukasz]

---

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.

[vmanoharas]

Hi @WHLukasz,

Could you please remove all other files except files mentioned below?

1. apiDefinition.swagger.json
2. apiProperties.json
3. readme.md

[WHLukasz]

@microsoft-github-policy-service agree company="Flotiq"

[WHLukasz]

Hi @vmanoharas
Thank you for your review and feedback. I've made the changes accordingly and removed all unwanted files.

[vmanoharas]

Hi @WHLukasz,

Unfortunately, I can see the below files, kindly update the files as mentioned above to proceed for the review.

[WHLukasz]

Hi @vmanoharas
Thank you for the feedback. However, I believe there may be a misunderstanding. The image files shown in your screenshot already existed in the microsoft:dev branch prior to this PR — this PR actually removes them, which is why they appear in the diff with a - sign.
If what you meant is that there are images in connector description, I’ve updated those as well — they now reference external URLs instead of using local asset files.
Please let me know if anything else needs to be changed.
Regards

[vmanoharas]

Hi @WHLukasz ,

Thank you for your clarification, that makes sense, however, we expect only files mentioned below, additionally, please refer the link below.

https://github.com/microsoft/PowerPlatformConnectors/tree/dev/templates/certified-connectors

[CiotkaCierpienia]

Hi @vmanoharas.
I've changed the README file to lowercase to adhere to the naming convention. We do not need to change anything in the apiDefinition or apiProperties files, so they are not in this PR. The Flotiq connector is already in the library; we only needed to make changes to the README to adhere to the new design of the Flotiq editor. We want to avoid confusion when Power Platform users use Flotiq and see the new editor, as they are expecting the old one, based on the images in the README here. I hope this clarifies the purpose of this PR.