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.
One page of GlideRecord patterns done right: encoded queries, OR conditions without surprises, GlideAggregate, pagination, and the security layer everyone forgets.
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 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.
Same JavaScript, different discipline. When to explore in the background script box and when to ship a fix script that travels with your release.
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.
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.
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.
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.