Skip to content

added Zvanu Parvaldnieks #1638

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 10 commits into from
Jun 14, 2022
Merged

added Zvanu Parvaldnieks #1638

merged 10 commits into from
Jun 14, 2022

Conversation

@einarshamrihs
Copy link
Contributor

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.

Please note that we are experiencing a significant delay due to a high volume of connector submissions. It may take 1-2 weeks for us to provide comments for your connector.

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

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

@einarshamrihs einarshamrihs requested a review from a team as a code owner May 11, 2022 12:09
@ghost
Copy link

ghost commented May 11, 2022 •
edited by ghost
Loading

CLA assistant check
All CLA requirements met.

@Amjed-Ayoub Amjed-Ayoub added the On Hold We are reviewing your connector with our management, until then your PR will be on hold. label May 11, 2022
@Amjed-Ayoub
Copy link
Contributor

Hello @einarshamrihs, thank you so much for submitting your pull request. This is a new verified connector. Like all verified publisher connectors, we ask that you register your connector for certification by filling out our registration form.
Please let me know if you have any questions.
Thank you very much again for working with us.

@Amjed-Ayoub
Copy link
Contributor

Hi @einarshamrihs can you please register your connector, so we can review the pull request and move forward with the certification process.
Please let me know if you have any questions.
Thank you very much.

@Amjed-Ayoub
Copy link
Contributor

Hello @einarshamrihs, thank you so much for submitting your pull request. This is a new verified connector. Like all verified publisher connectors, we ask that you register your connector for certification by filling out our registration form.
Please let me know if you have any questions.
Thank you very much again for working with us.

@Amjed-Ayoub Amjed-Ayoub added certified-connector Validation phase Connector is being validated by Microsoft. New For brand new connector submissions and removed needs:partner-attention On Hold We are reviewing your connector with our management, until then your PR will be on hold. labels May 27, 2022
@Amjed-Ayoub
Copy link
Contributor

Hi @einarshamrihs Thank you so much for registering your connector. Our certification engineers will review your pull request very soon.
Please let me know if you have any questions.
Thank you very much for your hard work with us.

v-EgorKozhadei
v-EgorKozhadei reviewed Jun 3, 2022
View reviewed changes
Copy link
Contributor

@v-EgorKozhadei v-EgorKozhadei left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @einarshamrihs! Please check comments after the review, thank you!

v-EgorKozhadei
v-EgorKozhadei reviewed Jun 10, 2022
View reviewed changes
Copy link
Contributor

@v-EgorKozhadei v-EgorKozhadei left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @einarshamrihs! Please check a few more comments, we'll be good to go after they're fixed, thank you!

v-EgorKozhadei
v-EgorKozhadei reviewed Jun 13, 2022
View reviewed changes
Copy link
Contributor

@v-EgorKozhadei v-EgorKozhadei left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @einarshamrihs! Please take a look at this comment as well, thank you!

@v-EgorKozhadei
Copy link
Contributor

Hello @einarshamrihs,

I hope you are doing well.

Congratulations, your pull request is approved and merged. Please submit the files to ISV Studio using your latest commit id, please allow us up to 1-2 weeks to review your submission, and our Engineers will notify you in the “Activity Control” area in ISV Studio.

Please Create an environment in the Preview region. You will use this environment later to test your connector after Microsoft is done with the functional verification for your connector.

We expect all tests to be completed within 1-2 weeks.

If your connector passes all tests, the deployment process begins, and it typically takes up to 3 to 4 weeks to deploy your connector to all of our regions.

Please let me know if you have any questions.

Thank you very much for working with us.

@v-EgorKozhadei v-EgorKozhadei merged commit 808bcb1 into microsoft:dev Jun 14, 2022
@Amjed-Ayoub
Copy link
Contributor

Hello @einarshamrihs,

I hope you are doing well.

This is to inform you that we will reschedule our deployment for production until Tuesday June 28th & Wednesday June 29th.
Your connector is in our registration backlog with the status "In Partner Verification/Testing".
We have high volume of connectors in our pipeline. Therefore, we need to clear our backlog. We tested your connector, and everything looks good on our side. We would like to proceed forward with Production Deployment for your connector 😊.

Please let us know if you want us to stop deploying your connector or if you still need time for testing.

Feel free to reach out with any questions you may have.

I look forward to hearing from you soon.

Thank you so much for understanding.

Best regards,
Amjed Ayoub

lindarecfut pushed a commit to recordedfuture/PowerPlatformConnectors that referenced this pull request Feb 14, 2023
@einarshamrihs @lindarecfut
added Zvanu Parvaldnieks (microsoft#1638)
4483e81 
* added Zvanu Parvaldnieks

* fixed voicemail triggerConfig

* fixed record_id param

* fixed group by id type

* fixed dial response

* fixed summaries

* fixed swagger issues

* created readme from template

* fixed grammar

* fixed polling trigger policy titles
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer

@v-EgorKozhadei v-EgorKozhadei v-EgorKozhadei approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

certified-connector New For brand new connector submissions Validation phase Connector is being validated by Microsoft.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@einarshamrihs @Amjed-Ayoub @v-EgorKozhadei