Skip to content

Conversation

@Rampriya-S
Copy link
Contributor

PR Description:

Pull Request Checklist

Overview

  • [x ] I have read and understood the CONTRIBUTING.md guidelines
  • [ x] My pull request has a descriptive title that accurately reflects the changes
  • [ 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

Counts all application CIs where operational_status = 2 (non-operational) and install_status = 1 (installed). Outputs the total count to system logs for quick health and compliance checks.
@WillemZeiler WillemZeiler self-assigned this Oct 2, 2025
@WillemZeiler
Copy link
Contributor

Thank you for your contribution. This CMDB health check script is a cool idea! 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+snippetfolder guidelines and include a readme.md file explaining what the code snippet does.

Folder is in the right place, but naming of the sub-folder should match guidelines. In addition, see if you can give the script a descriptive name (instead of script.js).

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.

(It would be helpful to others, if perhaps you can include a bit more info on why you are running this check and why it could help improve the CMDB quality. You could tell a bit more why non-operational applications that have a installed status would degrade the CMDB. In addition, would similar checks be applicable to other CI's/types?)

@Rampriya-S
Copy link
Contributor Author

Absolutely, I will adjust it.

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