Get all RITMs from a service catalog…

Server-sideintermediateTested on Xanadu

Chrome Extension

Sourdough: ServiceNow Monitoring and Analytics

A Chrome extension for ServiceNow Admins and Developers with essential tools, analytics, graphs and monitoring features.

Instance HealthGraphs & ChartsAPI HealthDeveloper ToolsQuick SearchInstance Switcher

Add to Chrome

Free to install. Pro $5/month after a 14-day no-card trial.
Pro requires the ServiceNow admin role. Upgrade inside the extension.

Overview

Tasks

CMDB

API

Metrics

Monitor

Internals

Instance:sourdoughdev·Version:Yokohama

Instance StateONLINE

System StatusFully Operational

Session Timeout90 minutes

Logged-In Sessions2 (20 active)

Build Nameyokohama-12-18-2024_p1

IP Address10.159.128.43

Instance HealthHealth Score: 90%

🔥 5dSourdough (Chrome Plugin)Dark Mode

Query all Requested Items that belong to a parent Request record

Business Rule

(function executeRule(current, previous) {
    
    var request = current; // Assuming this runs on sc_request table
    var ritmGR = new GlideRecord('sc_req_item');
    ritmGR.addQuery('request', request.sys_id);
    ritmGR.query();
    
    var ritmIds = [];
    var ritmData = [];
    
    while (ritmGR.next()) {
        ritmIds.push(ritmGR.sys_id.toString());
        
        // Collect RITM details - state is integer
        var ritmInfo = {
            sys_id: ritmGR.sys_id.toString(),
            number: ritmGR.number.toString(),
            cat_item: ritmGR.cat_item.getDisplayValue(),
            state: ritmGR.state.toString(), // 1=Open, 2=Work in Progress, 3=Closed Complete, etc
            stage: ritmGR.stage.toString(),
            assigned_to: ritmGR.assigned_to.getDisplayValue(),
            variables: []
        };
        
        // Get catalog variables for this RITM
        var varGR = new GlideRecord('sc_item_option_mtom');
        varGR.addQuery('request_item', ritmGR.sys_id);
        varGR.query();
        
        while (varGR.next()) {
            ritmInfo.variables.push({
                name: varGR.sc_item_option.item_option_new.name.toString(),
                value: varGR.sc_item_option.value.toString(),
                display_value: varGR.sc_item_option.getDisplayValue()
            });
        }
        
        ritmData.push(ritmInfo);
    }
    
    gs.info('Found ' + ritmIds.length + ' RITMs for request ' + request.number);
    
    // Process each RITM as needed
    for (var i = 0; i < ritmData.length; i++) {
        var ritm = ritmData[i];
        gs.info('Processing RITM: ' + ritm.number + ' - State: ' + ritm.state);
        // Your processing logic here
    }
    
})(current, previous);

The relationship between sc_request and sc_req_item is straightforward, but catalog variables live in a third table most developers miss: sc_item_option_mtom. This many-to-many relationship stores the actual variable values that users submitted, and you need to join through sc_item_option to get variable metadata. The pattern above handles both the RITM enumeration and variable extraction in a single pass, avoiding the N+1 query trap that kills performance when you have requests with dozens of items.

When to use this pattern

Processing approval workflows that need to act on individual RITMs within a request
Business rules on sc_request that need to validate or modify child items before completion
Scheduled jobs that process batches of requests and need RITM-level detail for reporting or integration
Fix scripts that need to bulk-update RITMs based on parent request criteria

When NOT to use this pattern

Client-side scripts — use GlideAjax to call a Script Include that implements this pattern
When you only need RITM counts or aggregates — use GlideAggregate with addAggregate('COUNT')
Inside loops over other GlideRecord results — you'll create a query storm that times out on large datasets
Processing requests with 50+ RITMs in synchronous business rules — use events or scheduled processing instead

Key behaviors and gotchas

RITM state values are integers: 1=Open, 2=Work in Progress, 3=Closed Complete, 4=Closed Incomplete, 7=Closed Skipped
Catalog variables require joining through sc_item_option_mtom — they're not fields on sc_req_item
Variable values are always strings, even for numeric and boolean catalog variables
RITMs inherit ACLs from their catalog items — not all RITMs in a request may be visible to the current user
Multi-row variable sets create multiple sc_item_option_mtom records per RITM — group by row_index if needed
The request field on sc_req_item is indexed — queries by request are fast even with thousands of RITMs

⚠️

Never use dot-notation like current.ritems to navigate from request to RITMs — it returns a GlideElement, not a GlideRecord, and you can't iterate or query it. Always query sc_req_item explicitly with the request sys_id.

Free Newsletter

Enjoying this? Get one deep-dive per week.

Join 1,000+ ServiceNow pros — scripts, GlideRecord patterns, Flow Designer techniques, and career moves. Free.

Alternative Approaches

Direct variable query by request

// Get all catalog variables across all RITMs in a request
var varGR = new GlideRecord('sc_item_option_mtom');
varGR.addQuery('request_item.request', requestSysId);
varGR.orderBy('request_item');
varGR.orderBy('sc_item_option.order');
varGR.query();

var currentRitm = '';
var ritmVariables = {};

while (varGR.next()) {
    var ritmId = varGR.request_item.toString();
    
    if (currentRitm != ritmId) {
        currentRitm = ritmId;
        ritmVariables[ritmId] = [];
    }
    
    ritmVariables[ritmId].push({
        name: varGR.sc_item_option.item_option_new.name.toString(),
        value: varGR.sc_item_option.value.toString()
    });
}

Use when you only need catalog variables and can skip RITM field data entirely.

Trade-offs: Fewer queries but loses RITM metadata like state, assignment, and catalog item details.

API Methods Used

GlideRecord.addQuery()GlideRecord.query()GlideRecord.next()

Test Your Knowledge

Quick 3-question quiz — see how your ServiceNow skills stack up.

Question 1 of 3Performance

A list view on a table with millions of records is slow. Best fix?

Select an answer to continue

Get all RITMs from a service catalog request