Html input field in Glide modal window

[Sriharsha19]

Note on previous PR :

[https://github.com//pull/1898]

A previous pull request containing this implementation was closed due to concerns about missing attribution and similarity to a community post.
I want to clarify that I am the original author of both the pull request and the related community post:[ServiceNow Community: Add HTML Input Field in GlideModal Window]
POST LINK : [https://www.servicenow.com/community/developer-forum/add-html-input-field-in-glidemodal-window/td-p/3326479/page/2]

#visual Proof


This submission is a properly documented resubmission of that work. Feedback is welcome to improve further.

PR Description:

This contribution demonstrates how to add an HTML input field (including rich text inputs) inside a GlideModal window in ServiceNow. The approach uses a UI Page containing WYSIWYG editor fields like TinyMCE, rendered inside a GlideModal triggered via a UI Action.

Use Case:

-Create a UI Page (e.g., rich_text_modal) containing input fields such as short description (string) and description (Rich Text/HTML).
-Create a UI Action (e.g., "Add Details") on a target table (e.g., Incident) to open the UI Page in a GlideModal.
-User opens the modal and inputs data without navigating from the record page.

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

VIsual Proof

[github-actions]

Thank you for your contribution. However, it doesn't comply with our contributing guidelines.

As a reminder, the general requirements (as outlined in the CONTRIBUTING.md file) are the following: follow the folder+subfolder guidelines and include a README.md file explaining what the code snippet does.

Validation errors:

Folder structure violations found:
 - Move 'Core ServiceNow APIs/GlideModal/README.md' under a valid folder hierarchy (Category/Subcategory/Use-Case/your-file). Files directly inside 'Core ServiceNow APIs' or its subcategories are not allowed.

Review your contribution against the guidelines and make the necessary adjustments. Closing this for now. Once you make additional changes, feel free to re-open this Pull Request or create a new one.