Application Automation

GlideRecord is the primary server-side API for querying and manipulating records in ServiceNow. You MUST know this API thoroughly for the CAD exam.

Core GlideRecord Methods

Common Query Patterns

Query active P1 incidents assigned to a specific group:

• var gr = new GlideRecord('incident');
• gr.addQuery('active', true);
• gr.addQuery('priority', 1);
• gr.addQuery('assignment_group', groupSysId);
• gr.query();
• while (gr.next()) { /* process each record */ }

GlideAggregate performs database aggregation operations (COUNT, SUM, AVG, MIN, MAX) much more efficiently than GlideRecord with manual counting.

GlideAggregate Methods

• addAggregate('COUNT') — Count records.
• addAggregate('SUM', field) — Sum a numeric field.
• addAggregate('AVG', field) — Average a numeric field.
• addAggregate('MIN', field) / addAggregate('MAX', field) — Min/max values.
• groupBy(field) — Group results by a field.
• getAggregate('COUNT') — Get the aggregate result.

For the CAD exam, you need a deeper understanding of Business Rules than the CSA exam, including scripting patterns, common pitfalls, and performance considerations.

Business Rule Best Practices

• Keep Business Rules simple — complex logic belongs in Script Includes.
• Use conditions (filter) whenever possible instead of script-based checks.
• Avoid current.update() in Business Rules on the same table — causes infinite loops unless controlled.
• Use 'before' rules to modify the current record. Use 'after' rules for side effects.
• Async rules run in background — use for non-blocking operations like notifications or integrations.
• Always check current.operation() if the rule applies to both insert and update.

The 'previous' Object

• Only available in UPDATE operations (not insert or delete).
• previous.field_name gives the value BEFORE the update.
• Use to detect changes: if (current.state != previous.state) { /* state changed */ }
• previous.state.changes() — Returns true if the field value changed.
• current.state.changesTo(value) — Returns true if field changed TO a specific value.
• current.state.changesFrom(value) — Returns true if field changed FROM a specific value.

Script Includes are reusable server-side JavaScript classes/functions. They are the recommended way to organize complex logic and are essential for clean, maintainable code.

Script Include Types

GlideAjax Pattern (Client → Server)

1. Create a Script Include with 'Client callable' checked.
2. In the Script Include, create a method that reads parameters and returns a result.
3. In the Client Script, create a GlideAjax object referencing the Script Include name.
4. Add parameters using addParam('sysparm_name', 'parameter_name') and addParam('sysparm_value', value).
5. Call getXMLAnswer() for synchronous (BAD) or getXML(callback) for asynchronous (GOOD).
6. In the callback, parse the response using response.responseXML.documentElement.getAttribute('answer').

The GlideSystem (gs) object provides system-level utility methods available in all server-side scripts.

Key gs Methods

Events decouple triggering logic from response logic. A Business Rule queues an event, and a separate Script Action or Notification responds to it.

Event System

• Event Registration — Define event name and table (System Policy > Events > Registry).
• gs.eventQueue() — Queue an event from a Business Rule or Script Include.
• Script Actions — Server-side scripts that respond to specific events.
• Notifications — Email notifications triggered by events.
• Event Queue — Events are processed asynchronously from the sysevent table.

Scheduled Jobs

• Scheduled Jobs run scripts on a defined schedule (daily, weekly, cron expression).
• Useful for data cleanup, report generation, integrations, and maintenance tasks.
• Configured under System Definition > Scheduled Jobs.
• Can run Script Includes or inline scripts.