Attachment Format Validator (Business Rule), a server‑side mechanism

[Charanjet]

PR Description:

The validator runs automatically on the sys_attachment table during record creation and checks each file extension against an allowed list defined in a system property.
If a file type is not allowed, the upload is blocked, the record creation is aborted, and a descriptive error is logged.

Pull Request Checklist

Overview

• Put an x inside of the square brackets to check each item.
• [x ] I have read and understood the CONTRIBUTING.md guidelines
• [x ] My pull request has a descriptive title that accurately reflects the changes and the description has been filled in above.
• [ x] I've included only files relevant to the changes described in the PR title and description
• [x ] I've created a new branch in my forked repository for this contribution

Code Quality

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

Repository Structure Compliance

• [x ] 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/
• [x ] I've used appropriate sub-categories within the top-level categories
• [x ] Each code snippet has its own folder with a descriptive name

Documentation

• [x ] I've included a README.md file for each code snippet
• [x ] 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

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

[ravichandra1998g]

Thank you for submitting!

We already have OOB system property to disable certain attachment types.

approving this as this enables per table restriction