Skip to content

Conversation

@DavidMarcial
Copy link
Contributor

PR Description:

This UI action will help you print a printer-friendly version of the record you are currently on. Instead of having to take multiple screenshots of a RITM or Catalog Task, you can use this UI action to capture all the data in one go and have the option to print on paper or save as a PDF

Pull Request Checklist

Overview

  • Put an x inside of the square brackets to check each item.
  • I have read and understood the CONTRIBUTING.md guidelines
  • My pull request has a descriptive title that accurately reflects the changes and the description has been filled in above.
  • 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

@snamjosh snamjosh self-assigned this Oct 30, 2025
@snamjosh
Copy link
Contributor

Thank you for your contribution.
However, same functionality is available with reports on the platform using export feature.

Can you provide more details about business use case for this UI action?

@DavidMarcial
Copy link
Contributor Author

@snamjosh Absolutely, while the export feature on the platform does provide a similar solution, if a user does it on, let's say, a RITM or Catalog Task that has the Intake form variables, those do NOT show up using the export. This feature actually does allow for the intake form variables to populate.

@snamjosh snamjosh merged commit a13298f into ServiceNowDevProgram:main Oct 30, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants