Divyajetti9 br

[divyajetti9]

PR Description:

Auto-create a Knowledge Article from a resolved incident’s resolution notes.
But — if multiple incidents share the same issue, only one KB should be created.

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

[github-actions]

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

❌ Invalid File/Folder Names Detected

Your contribution contains file or folder names that will break when syncing to local file systems (especially Windows):

Folder structure violations found:
 - Invalid folder/file name '"Server-Side Components' in path '"Server-Side Components/Business Rules/Auto-create a Knowledge Article from a resolved incident/342/200/231s resolution notes/README.md"': Contains characters that are invalid on Windows file systems (< > : " | ? * or control characters).
 - Invalid folder/file name '"Server-Side Components' in path '"Server-Side Components/Business Rules/Auto-create a Knowledge Article from a resolved incident/342/200/231s resolution notes/script.js"': Contains characters that are invalid on Windows file systems (< > : " | ? * or control characters).

Common issues:

• Folder/file names ending with a period (.) - not allowed on Windows
• Folder/file names ending with spaces - not allowed on Windows
• Reserved names like CON, PRN, AUX, NUL, COM1-9, LPT1-9 - not allowed on Windows
• Invalid characters: < > : " | ? * or control characters

Please rename these files/folders to be compatible with all operating systems.

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.