Skip to content

Conversation

@sriharip-docusign
Copy link
Contributor

Included in this release:

  • PowerPages changes for Microsoft C2
  • Template prefill
  • DocGen for PA
  • Get Envelope fields
    And some bug fixes

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.

  • [ x] 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.
  • [ x] I attest that the connector works and I verified by deploying and testing all the operations.
  • [ x] I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
  • [ x] I attest that I have added response schemas to my actions, unless the response schema is dynamic.
  • [ x] I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
  • [x ] 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.

sriharip-docusign and others added 30 commits August 11, 2022 14:31
Send envelope using template versioning and text custom field support
Show options for setting recipient type and support 'in person signer' recipient type in the add recipient flow step
# Conflicts:
#	certified-connectors/DocuSignDemo/apiDefinition.swagger.json
#	certified-connectors/DocuSignDemo/script.csx
…g template" and "create envelope" actions

List custom fields shows up as an enum
# Conflicts:
#	certified-connectors/DocuSignDemo/apiDefinition.swagger.json
FLOW 200 : Error checking in case meta data for chosen verification type is missing
Merge SMS related code changes from Angel + Custom field bug fixes
@sriharip-docusign sriharip-docusign requested a review from a team as a code owner May 15, 2023 23:23
@Amjed-Ayoub
Copy link
Contributor

@sriharip-docusign please update your branch you are deleting other connector files.

@Amjed-Ayoub Amjed-Ayoub added certified-connector needs:partner-attention On Hold We are reviewing your connector with our management, until then your PR will be on hold. labels May 16, 2023
sriyen-msft
sriyen-msft previously approved these changes May 16, 2023
@sriyen-msft sriyen-msft self-requested a review May 16, 2023 00:14
@sriharip-docusign
Copy link
Contributor Author

@sriharip-docusign please update your branch you are deleting other connector files.

@Amjed-Ayoub , I have fixed the deleted file. Please review again.

@sriharip-docusign
Copy link
Contributor Author

sriharip-docusign commented May 16, 2023 via email

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 @sriharip-docusign ,
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 ed1d6c2 into microsoft:dev May 16, 2023
@Amjed-Ayoub Amjed-Ayoub removed needs:partner-attention On Hold We are reviewing your connector with our management, until then your PR will be on hold. labels May 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants