Add Egain for certification(initial submission)

[aostwaleg]

---

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.

[aostwaleg]

@microsoft-github-policy-service agree [company="Egain"]

[aostwaleg]

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

[aostwaleg]

We’d really appreciate any help you can provide to help accelerate the review and approval process - this connector is time-sensitive for our delivery timelines.

[vmanoharas]

Hi @aostwaleg,

Thank you for interest in submitting the connector.

However, we would suggest you to please go through the below links before submitting your connectors. We have two types of connectors.

1. Verified Connectors - https://learn.microsoft.com/en-us/connectors/custom-connectors/submit-for-certification
2. Independent Connectors - https://learn.microsoft.com/en-us/connectors/custom-connectors/submit-for-certification

Additionally, please refer the below link to prepare the connector.

https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission

[aostwaleg]

hi @vmanoharas ,
Thanks for your review. I aimed for the connector to be Verified Connectors and followed the guidelines provided in this link: https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission#package-your-connector-files.

However, the validation failed with the following error:
"Flow solution in 'C:\eGain\copilot\Solution\ConnectorPackage.zip\package.zip/PkgAssets' is invalid. Flow solution should contain both 'Connector' and 'Workflows' folders.
Validate the flow solution has both 'Connector' and 'Workflows' components. If not so, please recreate the solution and export again."

My solution does not require any workflows, so they are not included. It solely comprises the connector solution and other solution with test Copilot agents. Let me know how to proceed.
ConnectorPackage.zip

So next I tried with Independent Connectors.

[vmanoharas]

Thank you for sharing the connector package @aostwaleg.

However, the folder structure is not as expected, kindly follow the below folder structure.

[aostwaleg]

Thank you for sharing the connector package @aostwaleg.

However, the folder structure is not as expected, kindly follow the below folder structure.

Thanks. I have resubmitted the package as per above structure as marketplace offer from Partner program. Here is the SAS URL for the same

[vmanoharas]

Thank you @aostwaleg,

Kindly fix the following swagger validation errors.

##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1core1aiservices1v31internal1instantanswers1generative/get/parameters/2
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1core1aiservices1v31internal1instantanswers1generative/get/parameters/3
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1core1aiservices1v31internal1instantanswers1generative/get/parameters/4
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1core1aiservices1v31internal1instantanswers1generative/get/parameters/5
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1core1aiservices1v31internal1instantanswers1generative/get/parameters/6
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1core1aiservices1v31internal1instantanswers1generative/get/parameters/7
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1core1aiservices1v31internal1instantanswers1generative/get/parameters/8
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1core1aiservices1v31internal1instantanswers1generative/get/parameters/9
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1knowledge1portalmgr1v31internal1portals1{portalId}1search1kb/get/parameters/0
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1knowledge1portalmgr1v31internal1portals1{portalId}1search1kb/get/parameters/1
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1knowledge1portalmgr1v31internal1portals1{portalId}1search1kb/get/parameters/2
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1knowledge1portalmgr1v31internal1portals1{portalId}1search1kb/get/parameters/3
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1knowledge1portalmgr1v31internal1portals1{portalId}1search1kb/get/parameters/4
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1knowledge1portalmgr1v31internal1portals1{portalId}1search1kb/get/parameters/5
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1knowledge1portalmgr1v31internal1portals1{portalId}1search1kb/get/parameters/6
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1knowledge1portalmgr1v31internal1portals1{portalId}1search1kb/get/parameters/7
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1knowledge1portalmgr1v31internal1portals1{portalId}1search1kb/get/parameters/8
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1knowledge1portalmgr1v31internal1portals1{portalId}1search1kb/get/parameters/9
##[error]The 'x-ms-summary' property is required. ValuePath: /paths/1knowledge1portalmgr1v31internal1portals1{portalId}1search1kb/get/parameters/10
##[error]The 'contact' property is required. ValuePath: /info
##[error]The 'x-ms-connector-metadata' property is required.