The query cookbook: every GlideRecord pattern worth memorizing
One page of GlideRecord patterns done right: encoded queries, OR conditions without surprises, GlideAggregate, pagination, and the security layer everyone forgets.
the cookbook ~ scripts and patterns for daily platform work
Copy, paste, understand.
Every ServiceNow developer keeps a private stash of scripts and patterns they reach for on every project. This is mine, cleaned up and explained. Each recipe solves one concrete problem: add a button to a workspace, clean up a million junk records without melting the instance, call the server from a client script the right way. Take the code, but read the why, that part is what keeps you out of trouble.
Script include patterns: where your server logic actually belongs
The three shapes of a script include, a worked TaskUtils example, client-callable boundaries, scoped API design, and how to actually test the thing.
Scheduled jobs and events: doing work later, the platform way
Scheduled script executions for recurring work, the event queue for reacting to it, and the fire-the-event, do-the-work-elsewhere pattern that keeps both honest.
Fix scripts vs background scripts
Same JavaScript, different discipline. When to explore in the background script box and when to ship a fix script that travels with your release.
Business rule patterns: picking the right timing
Before, after, async, or display. A decision-shaped recipe for the four business rule timings, the double-update bug, the async previous gotcha, and the discipline that keeps rules maintainable.
GlideAjax done right
The client script needs server data and there are three ways to get it, two of them wrong. The complete client-callable pair, the security angle nobody teaches, and when g_scratchpad is the better answer.
Background scripts without regret
A dry-run-first recipe for deleting a few hundred thousand stale records safely. Count first, log what would change, flip one flag by hand, and keep a grep-able trail.
Add a button to a configurable workspace form
Your UI Action works perfectly in the classic UI and is simply not there in the workspace. One checkbox and one new script field fix that. A complete escalate button, start to finish.