Updated existing PDF.co connector with version 2.0 with all missing functionality from pdf.co.

[hiren-byte]

---

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]

Hello @hiren-byte,

Please resolve review comments, additionally, please check swagger validation errors and fix them duly.

[hiren-byte]

@vmanoharas , Thank you for review! I have updated apiDefinition.swagger.json file to fix the issues.

[vmanoharas]

Hello @hiren-byte,

Thank you for fixing previous comments, however, can you please look into below swagger validation and confirm that Existing flows may not affect? please

##[error]An enum value has been removed from the input field. Existing flows may have this value chosen and will continue to send it. ValuePath: operation/PDFFromEmail/parameter/body/schema/embedAttachments/enum Source: NewSwagger
##[error]An enum value has been removed from the input field. Existing flows may have this value chosen and will continue to send it. ValuePath: operation/PDFFromEmail/parameter/body/schema/convertAttachments/enum Source: NewSwagger
##[error]An enum value has been removed from the input field. Existing flows may have this value chosen and will continue to send it. ValuePath: operation/PDFFromEmail/parameter/body/schema/async/enum Source: NewSwagger
##[error]An enum value has been removed from the input field. Existing flows may have this value chosen and will continue to send it. ValuePath: operation/PDFAddSecurity/parameter/body/schema/allowAccessibilitySupport/enum Source: NewSwagger
##[error]An enum value has been removed from the input field. Existing flows may have this value chosen and will continue to send it. ValuePath: operation/PDFAddSecurity/parameter/body/schema/allowAssemblyDocument/enum Source: NewSwagger
##[error]An enum value has been removed from the input field. Existing flows may have this value chosen and will continue to send it. ValuePath: operation/PDFAddSecurity/parameter/body/schema/allowPrintDocument/enum Source: NewSwagger
##[error]An enum value has been removed from the input field. Existing flows may have this value chosen and will continue to send it. ValuePath: operation/PDFAddSecurity/parameter/body/schema/allowFillForms/enum Source: NewSwagger
##[error]An enum value has been removed from the input field. Existing flows may have this value chosen and will continue to send it. ValuePath: operation/PDFAddSecurity/parameter/body/schema/allowModifyDocument/enum Source: NewSwagger
##[error]An enum value has been removed from the input field. Existing flows may have this value chosen and will continue to send it. ValuePath: operation/PDFAddSecurity/parameter/body/schema/allowContentExtraction/enum Source: NewSwagger
##[error]An enum value has been removed from the input field. Existing flows may have this value chosen and will continue to send it. ValuePath: operation/PDFAddSecurity/parameter/body/schema/allowModifyAnnotations/enum Source: NewSwagger
##[error]An enum value has been removed from the input field. Existing flows may have this value chosen and will continue to send it. ValuePath: operation/PDFAddSecurity/parameter/body/schema/async/enum Source: NewSwagger
##[error]An enum value has been removed from the input field. Existing flows may have this value chosen and will continue to send it. ValuePath: operation/PDFSecurityRemove/parameter/body/schema/async/enum Source: NewSwagger
##[error]An enum value has been removed from the input field. Existing flows may have this value chosen and will continue to send it. ValuePath: operation/PDFFromXLSXLSX/parameter/body/schema/async/enum Source: NewSwagger
##[error]An enum value has been removed from the input field. Existing flows may have this value chosen and will continue to send it. ValuePath: operation/XLStoCSV/parameter/body/schema/async/enum Source: NewSwagger
##[error]An enum value has been removed from the input field. Existing flows may have this value chosen and will continue to send it. ValuePath: operation/XLStoJSON/parameter/body/schema/async/enum Source: NewSwagger
##[error]An enum value has been removed from the input field. Existing flows may have this value chosen and will continue to send it. ValuePath: operation/XLStoHTML/parameter/body/schema/async/enum Source: NewSwagger
##[error]An enum value has been removed from the input field. Existing flows may have this value chosen and will continue to send it. ValuePath: operation/XLStoTXT/parameter/body/schema/async/enum Source: NewSwagger
##[error]An enum value has been removed from the input field. Existing flows may have this value chosen and will continue to send it. ValuePath: operation/XLStoXML/parameter/body/schema/async/enum Source: NewSwagger

[hiren-byte]

@vmanoharas, yes, I confirm that this won't affect existing flows. Also, these validation errors are in the new modules which are not in public domain.

[vmanoharas]

Hello @hiren-byte
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.