DeskDirector - Version 1.8

[DDAndyChen]

---

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.

[vmanoharas]

Hi @DDAndyChen,

Could you please address swagger validation errors outlined below.

##[error]The path template has been changed for the operation. ValuePath: operation/GetChatWorkflowRequestParameterSchema Source: NewSwagger
##[error]The path template has been changed for the operation. ValuePath: operation/GetChatWebhookTriggerSchema Source: NewSwagger
##[error]The path template has been changed for the operation. ValuePath: operation/GetDynamicSchema Source: NewSwagger
##[error]The path template has been changed for the operation. ValuePath: operation/GetEmailTemplateProperties Source: NewSwagger
##[error]The path template has been changed for the operation. ValuePath: operation/GetFormResultSchema Source: NewSwagger
##[error]The path template has been changed for the operation. ValuePath: operation/GetTicketWorkflowTriggerSchema Source: NewSwagger
##[error]The path template has been changed for the operation. ValuePath: operation/GetTicketTriggerAdvancedFilterSchema Source: NewSwagger
##[error]The path template has been changed for the operation. ValuePath: operation/GetCreateTicketRequestSchema Source: NewSwagger
##[error]The path template has been changed for the operation. ValuePath: operation/GetWorkflowTriggerSchema Source: NewSwagger
##[error]The path template has been changed for the operation. ValuePath: operation/GetWorkflowRequestParameterSchema Source: NewSwagger
##[error]The path template has been changed for the operation. ValuePath: operation/GetFormResultSchemaV2 Source: NewSwagger
##[error]The path template has been changed for the operation. ValuePath: operation/GetCallAdvancedActionRequestSchema Source: NewSwagger
##[error]The path template has been changed for the operation. ValuePath: operation/GetCallAdvancedActionResponseSchema Source: NewSwagger
##[error]The path template has been changed for the operation. ValuePath: operation/AdvancedEventSubscribeTriggerSchema Source: NewSwagger
##[error]The path template has been changed for the operation. ValuePath: operation/AdvancedEventSubscribeRequestSchema Source: NewSwagger
##[error]The path template has been changed for the operation. ValuePath: operation/AdvancedEventResponseHandleRequestSchema Source: NewSwagger

[DDAndyChen]

Hi @vmanoharas,

We want to change the internal schema operations in the connector which will return new schema responses. The apparent ways we can do it are:

• approach 1: change the path templates to the new ones, this triggers the The path template has been changed for the operation. error as you commented
• approach 2: change the path templates to the new ones AND the operation IDs, this affectively replaces the internal operations with a set of new ones
• approach 3: keep the existing internal operations in the connector AND add the new set of operations too, this means we will have a bunch of deprecated internal operations in the connector which will be used by now one (neither the end users nor other operations will use them)

I know that for the non-internal operations we can use operation versioning to deprecate them. For our case, all of the affected operations are internal, could you let us know that which approach we should take?

[certificationteam]

Hi @vmanoharas,

We want to change the internal schema operations in the connector which will return new schema responses. The apparent ways we can do it are:

• approach 1: change the path templates to the new ones, this triggers the The path template has been changed for the operation. error as you commented
• approach 2: change the path templates to the new ones AND the operation IDs, this affectively replaces the internal operations with a set of new ones
• approach 3: keep the existing internal operations in the connector AND add the new set of operations too, this means we will have a bunch of deprecated internal operations in the connector which will be used by now one (neither the end users nor other operations will use them)

I know that for the non-internal operations we can use operation versioning to deprecate them. For our case, all of the affected operations are internal, could you let us know that which approach we should take?

Hi @DDAndyChen,

We recommend proceeding with Approach #3, as this pertains to an existing connector that may already have active users. Implementing a different approach could result in connection failures for those users.

[DDAndyChen]

Hi @vmanoharas,

Please review the changes again.

[vmanoharas]

Dear Partner,

Congratulations your PR is approved !! We are proud to announce the Brand-New Certification experience for you to certify Power Platform Copilot Connectors & Plugins.

As next steps:

Learn about the new certification experience- Get your Power Platform connector and plugin certified - Overview
Package your connector and plugin files- Prepare Power Platform connector and plugin files for certification
Validate the package for structure before submitting the package for certification to Partner Center - Run Package Validator tool
Initiate a certification request in Partner Center- Verified publisher certification process
Ensure your connector & plugin files comply to the Marketplace policies here- 5000 Power Platform Connector Policies for Marketplace and also 1000 Marketplace policies(as applicable)
Test your connector post certification to provide go-live for deployment- Testing Guidelines
If you wish to Update your connector or plugin in future- Updating Guidelines

For any queries or concerns please get in touch with us on certificationteam@microsoft.com