Skip to content

Detect oldValue, newValue and Operation type in Glide List #1763

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 11 commits into from
Oct 4, 2025
Merged

Detect oldValue, newValue and Operation type in Glide List #1763

merged 11 commits into from
Oct 4, 2025

Conversation

@SrijanPatwa
Copy link
Contributor

@SrijanPatwa SrijanPatwa commented Oct 4, 2025 •
edited
Loading

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

@SrijanPatwa
detectOldValuenewValueOperation.js
1fd6cd1 
This onChange Client script comes handy when dealing with Glide List type fields where we have to detect whether the value was added or removed and return the sysIDs of items which was added/removed.
@SrijanPatwa
readme.md
3787cae 
This onChange Client script comes handy when dealing with Glide List type fields where we have to detect whether the value was added or removed and return the sysIDs of items which was added/removed.
@rohi-v rohi-v assigned rohi-v and unassigned rohi-v Oct 4, 2025
@ravichandra1998g ravichandra1998g self-assigned this Oct 4, 2025
ravichandra1998g
ravichandra1998g requested changes Oct 4, 2025
View reviewed changes
Copy link
Contributor

@ravichandra1998g ravichandra1998g left a comment •
edited
Loading

Choose a reason for hiding this comment

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

Thank you for submitting the idea.

I know Glidelist store comma separated sys ids, but would it be possible for you to show the display values instead of sys ids?

@SrijanPatwa
detectOldValuenewValueOperation.js
3e27aaa 
This onChange Client script comes handy when dealing with Glide List type fields where we have to detect whether the value was added or removed and returns the display name of users who were added/removed along with name of operation performed.
@SrijanPatwa
readme.md
2282597 
This onChange Client script comes handy when dealing with Glide List type fields where we have to detect whether the value was added or removed and returns the name of users who were added/removed.
@SrijanPatwa
scriptUtil.js
6c56488 
This script include handles the sysIds(oldValue & newValue) of users and returns the display name
@SrijanPatwa
readme.md
66f92b7 
This onChange Client script comes handy when dealing with Glide List type fields where we have to detect whether the value was added or removed and return the display name of users who were added/removed.
@SrijanPatwa
Merge branch 'main' into detect-oldvalue-newvalue-in-cs
da2ad6c
@SrijanPatwa
Copy link
Contributor Author

SrijanPatwa commented Oct 4, 2025

Thank you for submitting the idea.

I know Glidelist store comma separated sys ids, but would it be possible for you to show the display values instead of sys ids?

Hi @ravichandra1998g , Updated the script and added screenshots. Thanks

ravichandra1998g
ravichandra1998g requested changes Oct 4, 2025
View reviewed changes
Copy link
Contributor

@ravichandra1998g ravichandra1998g left a comment

Choose a reason for hiding this comment

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

Hello @SrijanPatwa,
Thank you for making the changes. looks good now!

Can you please change the script include name from "scriptUtil" to more meaningful name?

@SrijanPatwa
watchListCandidatesUtil.js
26cdcef 
This script include handles the sysIds(oldValue & newValue) of users and returns the display name
@SrijanPatwa
detectOldValuenewValueOperation.js
299c4d2 
This onChange Client script comes handy when dealing with Glide List type fields where we have to detect whether the value was added or removed and returns the display name of users who were added/removed along with name of operation performed.
@SrijanPatwa
readme.md
f47a009 
This onChange Client script comes handy when dealing with Glide List type fields where we have to detect whether the value was added or removed and returns the display name of users who were added/removed along with name of operation performed.
@SrijanPatwa
watchListCandidatesUtil.js
6681651 
This script include handles the sysIds(oldValue & newValue) of users and returns the display name
@SrijanPatwa
Copy link
Contributor Author

SrijanPatwa commented Oct 4, 2025

Hello @SrijanPatwa, Thank you for making the changes. looks good now!

Can you please change the script include name from "scriptUtil" to more meaningful name?

Hi @ravichandra1998g , Updated. Please review again, thanks

ravichandra1998g
ravichandra1998g approved these changes Oct 4, 2025
View reviewed changes
Copy link
Contributor

@ravichandra1998g ravichandra1998g 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, approved!

@ravichandra1998g ravichandra1998g merged commit f8120aa into ServiceNowDevProgram:main Oct 4, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@ravichandra1998g ravichandra1998g ravichandra1998g approved these changes

Assignees

@ravichandra1998g ravichandra1998g

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@SrijanPatwa @ravichandra1998g @rohi-v