- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2025 06:56 PM
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2025 07:05 PM
Hi @Di Zhang ,
When manipulating DOM elements, interactions often involve classes and IDs. The risk arises that ServiceNow may alter these names in a future update, potentially causing the script to no longer function as anticipated.
Also, you can take this official KB , which also talks about As per the best practises it is not recommended to use DOM Manipulation techniques in the client-side scripting : https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0954537
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2025 07:05 PM
Hi @Di Zhang ,
When manipulating DOM elements, interactions often involve classes and IDs. The risk arises that ServiceNow may alter these names in a future update, potentially causing the script to no longer function as anticipated.
Also, you can take this official KB , which also talks about As per the best practises it is not recommended to use DOM Manipulation techniques in the client-side scripting : https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0954537
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-26-2025 10:25 PM
Hello @Di Zhang
Maybe this could be helpful: How to hide Form Annotation until specific field condions are met
Hope this helps!
"If you found my answer helpful, please like and mark it as an "accepted solution". It helps future readers to locate the solution easily and supports the community!"
Thank You
Juhi Poddar