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.

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

HighGear Workflow Connector #2743

Merged
merged 2 commits into from
Jun 22, 2023
Merged

HighGear Workflow Connector #2743

merged 2 commits into from
Jun 22, 2023

Conversation

dhands5312
Copy link
Contributor

HighGear Workflow Connector

This is the initial submission of the HighGear Workflow connector for certification.

The following files are being added:

  • apiDefinition.swagger.json
  • apiProperties.json
  • readme.md

The following items have been verified:

  • 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.
    • HighGear brand color is #404545

@dhands5312 dhands5312 requested a review from a team as a code owner June 21, 2023 15:06
@dhands5312
Copy link
Contributor Author

@microsoft-github-policy-service agree company="HighGear Software, Inc."

@Amjed-Ayoub Amjed-Ayoub added certified-connector Validation phase Connector is being validated by Microsoft. needs:partner-attention New For brand new connector submissions labels Jun 22, 2023
@dhands5312
Changed operationIds to use Camel Case
06c74f0 
- Removed the '_' between controller name and action
- Fixed Titles for Contact properties
- Added descriptions for Contact properties
- Corrected typo
Amjed-Ayoub
Amjed-Ayoub approved these changes Jun 22, 2023
View reviewed changes
Copy link
Contributor

@Amjed-Ayoub Amjed-Ayoub left a comment

Choose a reason for hiding this comment

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

Hello @dhands5312 ,
I hope you are doing well.
Congratulations, your pull request is approved and merged. Please submit the files to ISV Studio or update your submission 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 make sure that the icon meets all the requirements, that it’s size is 230x230, icon background is not white or transparent and it matches the iconBrandColor property in apiProperties.json file.
After making the submission in ISV Studio, please attach an intro.md file in the activity control section. This file is required and it's different from readme.md. You can find an example of intro.md file on this page at step 6.
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 or run into any problems while creating or updating your submission.
Thank you very much for working with us.

@Amjed-Ayoub Amjed-Ayoub merged commit c24a3f3 into microsoft:dev Jun 22, 2023
@Amjed-Ayoub Amjed-Ayoub removed Validation phase Connector is being validated by Microsoft. needs:partner-attention New For brand new connector submissions labels Jun 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Amjed-Ayoub Amjed-Ayoub Amjed-Ayoub approved these changes

Assignees
No one assigned
Labels
certified-connector
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@dhands5312 @Amjed-Ayoub