GlideSystem.addInfoMessage()

gs.addInfoMessage(message)→ void

beginnerTested on Xanadu

What It Does

The addInfoMessage() method queues a blue informational message to display at the top of the user's form after the current server-side execution context completes. ServiceNow stores these messages in the user's session and renders them on the next page load or form refresh.

Internally, ServiceNow adds the message to a temporary collection tied to the current user session. When the browser renders the next page, the platform injects these messages into the DOM as styled notification banners. The messages are consumed during display, meaning they only appear once and are automatically cleared.

The method returns void and never throws errors, even when passed invalid parameters. Empty strings, null values, or undefined parameters simply result in no message being displayed. HTML content is automatically escaped, so raw HTML tags appear as literal text rather than being rendered.

Messages only appear for synchronous page loads and form submissions. AJAX operations, REST API calls, and asynchronous updates don't trigger message display. The timing is crucial: messages queued in before Business Rules appear after the record saves, while messages in after Business Rules appear immediately when the form reloads.

This method belongs to the broader GlideSystem message family, alongside addErrorMessage() for red error banners and addMessage() for generic notifications. All three methods queue messages identically but render with different visual styling.

When to Use This

Use addInfoMessage() when you need to provide informational feedback about successful operations, data processing results, or status updates that users should know about but don't represent errors. Perfect for confirming that automated processes completed, notifying about data synchronization, or explaining why certain fields were auto-populated.

Choose addErrorMessage() instead when validation fails or operations encounter problems. Use gs.log() for technical details that only administrators need to see. Avoid using info messages for debugging output or verbose system information that clutters the user interface.

⚠️

Don't use addInfoMessage() in Script Includes called by AJAX or in REST API endpoints. The messages won't display since there's no form to render them on.

Return Value

The method returns void (undefined in JavaScript terms) and provides no indication of success or failure. There's no way to programmatically verify that the message was queued or will display to the user. The method executes silently regardless of parameter validity.

Since the return value is meaningless, never attempt to chain method calls or use the result in conditional logic. The method's effect is purely side-based, modifying the user's session state for the next page render.

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.

Platform Behavior & Side Effects

No Business Rules, ACLs, or workflows are triggered by adding messages
Nothing is written to the database; messages exist only in server memory until consumed
Extremely fast performance with no database overhead or network latency
Messages are session-scoped and never visible to other users
Works identically in before and after Business Rules, but timing of display differs
Multiple calls accumulate messages; all queued messages display simultaneously
Messages automatically clear after display and don't persist across user sessions

Parameters

Name	Type	Required	Description
message	string	Yes	The text to display in the blue info banner. HTML is escaped automatically for security. Empty strings and null values display nothing without error.

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

Code Examples

Basic user notification after record updatebasic

// Business Rule: After update on incident table
(function executeRule(current, previous) {
    
    // Check if priority was escalated
    if (current.priority < previous.priority) {
        var priorityName = current.priority.getDisplayValue();
        var incidentNumber = current.number;
        
        gs.addInfoMessage('Incident ' + incidentNumber + 
                         ' priority escalated to ' + priorityName + 
                         '. Notification sent to manager.');
        
        // Additional processing would happen here
        // The message appears when the form reloads
    }
    
})(current, previous);

Shows how to provide immediate feedback when automated business logic executes. The user sees confirmation that the priority change triggered additional processing without needing to check logs.

Multiple messages for batch operationsintermediate

// Script Include method called from UI Action
processBulkAssignment: function(taskIds, assignedTo) {
    
    var taskGR = new GlideRecord('task');
    var processedCount = 0;
    var skippedCount = 0;
    
    for (var i = 0; i < taskIds.length; i++) {
        taskGR.get(taskIds[i]);
        
        if (taskGR.canWrite()) {
            taskGR.assigned_to = assignedTo;
            taskGR.update();
            processedCount++;
        } else {
            skippedCount++;
        }
    }
    
    // Provide detailed feedback about the bulk operation
    gs.addInfoMessage('Successfully assigned ' + processedCount + ' tasks.');
    
    if (skippedCount > 0) {
        gs.addInfoMessage(skippedCount + ' tasks skipped due to access restrictions.');
    }
}

Demonstrates queuing multiple related messages that provide comprehensive feedback about batch operations. Both messages appear together when the page refreshes, giving users complete status information.

The classic mistake - AJAX context usageadvanced

// WRONG: In a Script Include called via GlideAjax
var MyAjaxProcessor = Class.create();
MyAjaxProcessor.prototype = Object.extendsObject(AbstractAjaxProcessor, {
    
    updateUserPreferences: function() {
        var userId = this.getParameter('user_id');
        var preference = this.getParameter('preference');
        
        // This message will NEVER display to the user
        gs.addInfoMessage('User preferences updated successfully');
        
        return 'success';
    }
});

// RIGHT: Return status and handle UI feedback client-side
updateUserPreferences: function() {
    var userId = this.getParameter('user_id');
    var preference = this.getParameter('preference');
    
    // Process the update
    var userGR = new GlideRecord('sys_user');
    if (userGR.get(userId)) {
        userGR.setValue('preferences', preference);
        userGR.update();
        return JSON.stringify({success: true, message: 'Preferences updated'});
    }
    
    return JSON.stringify({success: false, message: 'User not found'});
}

Shows why addInfoMessage() fails in AJAX contexts and the correct pattern for providing user feedback. AJAX responses need explicit client-side handling since there's no form reload to trigger message display.

Gotchas

Messages queued in Business Rules only display after the entire transaction commits, which can be several seconds after the rule executes if other processing occurs.

HTML content is automatically escaped, so '<b>Bold</b>' displays as literal text rather than bold formatting.

Messages persist across redirects within the same session but disappear if the user opens a new tab or window.

AJAX operations and REST API calls never trigger message display, making this method useless for asynchronous user interactions.

Multiple calls to addInfoMessage() accumulate messages rather than overwriting them, potentially creating message spam if called in loops.

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