Updated HYAS Insight #2017
Updated HYAS Insight #2017
Conversation
|
Hello Partner, |
|
Hello Amjed,
Thanks for reaching out. I have submitted the files via ISV Studio.
Best Regards,
Venkat. R | Project Lead-Cyber Security Operations
***@***.******@***.***>
[cid:88cf0362-f4df-43d3-a8a1-ed48c65f0592]
…________________________________
From: Amjed Ayoub ***@***.***>
Sent: Monday, October 10, 2022 10:13 AM
To: microsoft/PowerPlatformConnectors ***@***.***>
Cc: Venkat Rambatza ***@***.***>; Author ***@***.***>
Subject: Re: [microsoft/PowerPlatformConnectors] Updated HYAS Insight (PR #2017)
EXTERNAL EMAIL: DO NOT click on links or open attachments unless you know it is safe.
Hello Partner,
I hope you are doing well.
Congratulations, your pull request is approved and merged. Please submit the files to ISV Studio<https://docs.microsoft.com/en-us/connectors/custom-connectors/submit-for-certification#submit-to-isv-studio> or update your submission<https://docs.microsoft.com/en-us/connectors/custom-connectors/certification-updates> 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<https://docs.microsoft.com/en-us/connectors/custom-connectors/certification-submission#design-an-icon-for-your-connector>, 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<https://docs.microsoft.com/en-us/connectors/custom-connectors/submit-for-certification#submit-to-isv-studio> at step 6.
Please Create an environment in the Preview region<https://docs.microsoft.com/en-us/connectors/custom-connectors/certification-testing#create-an-environment-in-the-preview-region>. You will use this environment later to test your connector<https://docs.microsoft.com/en-us/connectors/custom-connectors/certification-testing#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.
—
Reply to this email directly, view it on GitHub<#2017 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQN2RCJASNFKBBY5AJ5AAT3WCONHVANCNFSM6AAAAAAQ2XHL34>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
* Update apiDefinition.swagger.json * Update apiProperties.json * Update readme.md * Update apiDefinition.swagger.json * Update apiProperties.json
3 participants
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.
apiDefinition.swagger.json, by runningpaconn validatecommand.apiProperties.jsonhas a valid brand color and doesn't use an invalid brand color,#007ee5or#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: