Generate PDF API

[SrijanPatwa]

Pull Request Checklist

Overview

• I have read and understood the CONTRIBUTING.md guidelines
• My pull request has a descriptive title that accurately reflects the changes
• I've included only files relevant to the changes described in the PR title and description
• I've created a new branch in my forked repository for this contribution

Code Quality

• My code is relevant to ServiceNow developers
• My code snippets expand meaningfully on official ServiceNow documentation (if applicable)
• I've disclosed use of ES2021 features (if applicable)
• I've tested my code snippets in a ServiceNow environment (where possible)

Repository Structure Compliance

• I've placed my code snippet(s) in one of the required top-level categories:
  • Core ServiceNow APIs/
  • Server-Side Components/
  • Client-Side Components/
  • Modern Development/
  • Integration/
  • Specialized Areas/
• I've used appropriate sub-categories within the top-level categories
• Each code snippet has its own folder with a descriptive name

Documentation

• I've included a README.md file for each code snippet
• The README.md includes:
  • Description of the code snippet functionality
  • Usage instructions or examples
  • Any prerequisites or dependencies
  • (Optional) Screenshots or diagrams if helpful

Restrictions

• My PR does not include XML exports of ServiceNow records
• My PR does not contain sensitive information (passwords, API keys, tokens)
• My PR does not include changes that fall outside the described scope

[rohi-v]

Thank you for your contribution . However, this snippet is already available OOTB via sn_pdfgeneratorutils.PDFGenerationAPI().convertToPDF()

https://www.servicenow.com/docs/bundle/zurich-api-reference/page/app-store/dev_portal/API_reference/PDFGenerationAPIBoth/concept/PDFGenerationAPIBothAPI.html#title_P-convertToPDF_S_S_S_S:~:text=SVGToPDFConversionAPI-,PDFGenerationAPI%20%E2%80%93%20PDFGenerationAPI(),-Instantiates%20a%20new

As per our guidelines code reused from ServiceNow Documentation or API References is acceptable only if it is expanded in a meaningful way (e.g., with additional context, documentation, or variations)

Closing this for now. Once you make additional changes, feel free to re-open this Pull Request or create a new one.