
mySNstuff.com
Latest Release : Yokohama
👋🏻 Welcome to my site!
Just a collection of some of my useful ServiceNow stuff. Created for my own purposes but shared to help others. This site has no affiliation with ServiceNow®
Created by a fellow ServiceNow nerd.
Admins are often tasked with monitoring certain things such as health of the platform, licenses, integrations, ad-hoc stuff, etc. As a result, you might end up with dozens of bookmarks, favorites, dashboards, reports, etc. Reports, performance analytics, dashboards, and favorites work OK, but have several downsides that I won’t list out. I built this very

Quick snippet of how to setup flow to wait for all related catalog tasks to complete. Useful for many circumstances when you are not using the “Wait” option on the “Create Catalog Task” action. (This could also be put into a subflow for reusability.) Summary of how it works: first it’s doing a lookup to

Navigator Histories table (sys_ui_navigator_history) is useful for checking where users visited in the Platform. Helpful for troubleshooting what a user was doing at a certain time and also helpful for checking who viewed particular records, dashboards, reports, etc. instanceName.service-now.com/sys_ui_navigator_history_list.do This is also same table that stores the information in the History menu.

Simple solution to display all the related requested items attachments on the catalog task form. This approach is better than copying the attachments to each catalog tasks. Go to System Definition -> Relationship. Create New Name: RITM Attachments Applies to table: Catalog Task [sc_task] Queries from table: Attachment [sys_attachment] Queries with: Now on the Catalog

To check how many times a record producer was used, or which record producer was used to create a particular ticket, go to this table: sc_item_produced_record

On your notification you can call mail scripts using this format: ${mail_script:script_name} Mail script API examples (Note: You can also use most server-side scripts here, such as GlideRecord) Documentation

Saving the syntax for quick reference. Will expand this article later on. First make sure to create the event in the Event Registry. Then you can trigger the event from any server-side script by using the code below: gs.eventQueue(‘event_name’,current,parm1,parm2); The event can be used to trigger an email notification and/or a script action. Documentation

Simple script to check if a particular date/time is within a defined schedule.

To order to see the payload of inbound REST APIs, create a new system property (sys_properties) Name: glide.rest.debug Type: true | false Value: true Then go into Node Log File Browser Filter for Start Time and End Time within the range that the API request was sent. In the Message, add Incoming Request Body Click

Copyright © 2024 | mySNstuff.com