Skip to content

Conversation

@raghavs046
Copy link
Contributor

@raghavs046 raghavs046 commented Oct 23, 2025

PR Description:

  1. This scheduled job will run according to the frequency, mostly daily EOD.
  2. This will look for articles rated one, 3 or more than 3 times and will retire them.

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 23, 2025
@snamjosh
Copy link
Contributor

Thank you for your contribution.
But, this functionality will cause process issues since KB article content should be improved instead of retiring them.

You should take a look at implementing https://www.servicenow.com/docs/bundle/zurich-servicenow-platform/page/product/knowledge-management/task/configure-act-know-feedback-properties.html to improve KB article quality.

@snamjosh snamjosh closed this Oct 23, 2025
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