Port DocuSign Demo -> DocuSign connector for DS1002 release #2728
Conversation
* Bitskout Connector * Requested changes
Show build number for a deployed connector
…soft#2150) * Added orderby parameter * Added orderby parameter * feat: add x-ms-pageable extension * feat: add updatenextlink policy instance * refactor: whitespace refactoring * Update apiProperties.json * fix(EC-14395): Integrate the patch schema endpoint * fix(EC-14395): Add specs for the schema endpoint's responses * fix(EC-14395): Add required fields to the schema Co-authored-by: Johannes Heesterman <johannes@elfsquad.io> Co-authored-by: johannesheesterman <heestermanj@gmail.com> Co-authored-by: Stan van Rooy <stanvanrooy6@gmail.com>
FLOW-270: Phone Authentication verification failing with INVALIDPHONE…
FLOW-275 - Restore v1 Create Template Step and rename action names
FLOW-278: Get Envelope Custom Fields Step
…hub.com/harshitav-docusign/PowerPlatformConnectors into FLOW-29-TriggerStatuses
Flow-29 trigger statuses
…pdated instead of the array
FLOW-276: Update Envelope Custom Fields Step
…2 version of create from template action
FLOW-282: Add unique tab label for all tab types
Bug Fix: Flow-402
Convert template input to a template dropdown
Rename actions to make it more readable for the user
Merging release dev to harshita dev
Merging Bug Fix Flow-402 to release/dev
Reverse integrate from release-docusign/dev to sriharip-docusign/dev
Merge pull request #36 from release-docusign/dev
identity verification added for Phone number
reverse integrate
Recipient info lookup bug fix
Reverse integrate release-docusign/dev -> sriharip-docusign/dev
Porting changes from DocuSign Demo -> DocuSign Connector
Port DocuSign Demo -> DocuSign connector for DS1002 release
There was a problem hiding this comment.
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.
7 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: