German Parliament (Independent Publisher)

[krautrocker]

---

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.

[krautrocker]

*Test UI results and proof-of-life in a flow.

Test UI:

GetPlenarProtokollTextById:

GetPlenarProtokollTextList:

GetAktivitaetList:

Proof-of-life in a flow:

[troystaylor]

Hi Dan,
Connector looks good except for two things:

1. Security doesn't need to be set at both root and action level, with root level being enough if all endpoints require it.
2. Definitions are missing titles at the property/parameter level.

[krautrocker]

Thanks, updated!

[vmanoharas]

Hi @krautrocker,

Please change all the German strings to English before we proceed for the review. However, please note that your connector will be translated to different languages once it is certified and eligible for the translation.

[krautrocker]

Ah, I see! Will the terms be auto translated or translated by a human? Curious, as I'm a German speaker. Pretty cool, regardless.

Which strings need to be changed? Action names (Ex: Vorgangspositionen), summary prefixes (Ex: Vorgänge - ...), everywhere except the actual field names, I assume?

[vmanoharas]

Ah, I see! Will the terms be auto translated or translated by a human? Curious, as I'm a German speaker. Pretty cool, regardless.

Which strings need to be changed? Action names (Ex: Vorgangspositionen), summary prefixes (Ex: Vorgänge - ...), everywhere except the actual field names, I assume?

Yes @krautrocker, the strings will be translated by our internal Localization team. Yes except actions and triggers, please change to English.

[krautrocker]

@vmanoharas Beautiful, thank you. I did make an update yesterday that removed strings from the readme and the short strings that were at the start of action names to make them only English. I'll change the operation IDs to reflect the English equivalents as well. Lastly, I'll change the title "Deutscher Bundestag" to "German Bundestag."

Do let me know if I need to change anything else.

[vmanoharas]

Hi @krautrocker,

Please refer the below link the title and the description must be in English.

https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission#give-your-connector-a-title

[krautrocker]

2. Definitions are missing titles at the property/parameter level.

@troystaylor paconn returns an error when adding titles at the parameter level:

When removed, no errors returned.

[krautrocker]

Hi @krautrocker,

Please refer the below link the title and the description must be in English.

https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission#give-your-connector-a-title

@vmanoharas All set, made updates to title and description.

[vmanoharas]

Hi @krautrocker,
Please refer the below link the title and the description must be in English.
https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission#give-your-connector-a-title

@vmanoharas All set, made updates to title and description.

Hi @krautrocker,

The PR title still has Proposal word, kindly update it.

[krautrocker]

Hi @krautrocker,

Please refer the below link the title and the description must be in English.

https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission#give-your-connector-a-title

@vmanoharas All set, made updates to title and description.

Hi @krautrocker,

The PR title still has Proposal word, kindly update it.

Done, thank you!

[vmanoharas]

Hello @krautrocker,

Please resolve review comment.