- 
                Notifications
    You must be signed in to change notification settings 
- Fork 1.4k
Release DS1002 for DocuSign #2648
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
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
Version add recipient
# 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
…ut selecting Workflow IDV
…il fast in case of user error
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
Bug Fix: Flow-389: Get recipient fields is throwing error
FLOW-347: DocGen: Update merge fields
Move Bug fix: Flow-389 to C2 branch
Merge branch 'microsoft:dev' into dev
Merge changes from c2_branch -> dev
reverse integrate from release-docusign->dev to sriharip-docusign->dev
Merge pull request #32 from release-docusign/dev
| @sriharip-docusign please update your branch you are deleting other connector files. | 
| 
 @Amjed-Ayoub , I have fixed the deleted file. Please review again. | 
| 
@amjed Ayoub (TEKsystems, Inc.) ***@***.***>
I have fixed the removed file. Please review again.… On Mon, May 15, 2023 at 5:27 PM Srikanth Yenagandhula < ***@***.***> wrote:
 ***@***.**** approved this pull request.
 —
 Reply to this email directly, view it on GitHub
 <https://urldefense.com/v3/__https://github.com/microsoft/PowerPlatformConnectors/pull/2648*pullrequestreview-1427518825__;Iw!!BN3BN5aqUA!5MuGppqUmZnvSNj-bwYol5OipHLSXfs2cJgZqz1rW4N1Hm4PRoNeUPgQIt1FY5XMPR8MmxyUN_vWa700FSQ6dHa7EWDgVfxAMw$>,
 or unsubscribe
 <https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AVRJBQVUZF6RBLCGPXFR55DXGLCW7ANCNFSM6AAAAAAYC4MBZY__;!!BN3BN5aqUA!5MuGppqUmZnvSNj-bwYol5OipHLSXfs2cJgZqz1rW4N1Hm4PRoNeUPgQIt1FY5XMPR8MmxyUN_vWa700FSQ6dHa7EWAbfVtY1w$>
 .
 You are receiving this because you were mentioned.Message ID:
 ***@***.***>
 | 
There was a problem hiding this 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.
Included in this release:
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.
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: