Skip to content

Conversation

@Jaspalsinghchot
Copy link
Contributor

PR Description:

Pull Request Checklist

Overview

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

@WillemZeiler WillemZeiler self-assigned this Oct 6, 2025
@rohi-v rohi-v assigned rohi-v and WillemZeiler and unassigned WillemZeiler and rohi-v Oct 6, 2025
Copy link
Contributor

@WillemZeiler WillemZeiler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for your submission. In general code looks good. 1 variable is defined, but not used. For the readme it would help if you can make it a bit more descriptive. If you can make these 2 updates you are all good to go!

@@ -0,0 +1,10 @@
(function executeRule(current, previous /*null when async*/ ) {

var usr = gs.getUserID();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unused variable

@@ -0,0 +1 @@
How often you come across cases where 'Private Task' needs to be disabled from the interceptor that shows up when New button is clicked on the Task table only for handful of users (users who are ITIL users but from XYZ department). This can be controlled by creating a 'Query' Business Rule on Answer (sys_wizard_answer) table. Script will be used in Business Rule to achieve the same.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you make this a bit clearer? The intend of the script is to be used in a Query Business Rule on the Answer table?
Can you share why Private tasks would need to be disabled? That will help others determine if this will also be needed in their instance/situation.

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.

3 participants