Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update publisher edatalia sign online #3652

Open
wants to merge 5 commits into
base: dev
Choose a base branch
from

Conversation

marpedroche
Copy link
Contributor

@marpedroche marpedroche commented Sep 17, 2024


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.

@marpedroche marpedroche requested a review from a team as a code owner September 17, 2024 07:18
@marpedroche
Copy link
Contributor Author

Connexion
integrationAPI
AxazureLogo
APIKey

@marpedroche
Copy link
Contributor Author

Please note, this is an update to the Publisher of the previously validated connector. Kindly ensure the connector name remains unchanged.

@marpedroche
Copy link
Contributor Author

Hi @vmanoharas,
I’ve created the new pull request with the updates you requested. I’m currently waiting on a small change to be finalized. Is there anything else you need? Thank you in advance

@marpedroche
Copy link
Contributor Author

@vmanoharas any update about this PR?

@vmanoharas
Copy link
Contributor

Hello @marpedroche,

Could you please update your PR according to the documentations here - https://github.com/microsoft/PowerPlatformConnectors.

Additionally, you have added and deleted many files. Kindly follow the above documentation and submit your connector either Independent or Verified publisher connector. As we are not able find out the connector in this PR.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants