Mastering UI Action Button Migration: A Comprehensive Guide for ServiceNow Workspace

Introduction

In the realm of enterprise solutions, ServiceNow stands tall as a powerful platform that streamlines workflows and enhances productivity. With its recent introduction of the Workspace interface, ServiceNow has taken a significant leap forward in modernizing the user experience. However, for organizations accustomed to the traditional standard UI, migrating UI Action buttons to the Workspace can be a daunting task. Fear not, as we’ve prepared a comprehensive guide to walk you through this transition seamlessly.

Understanding the Significance

UI Action buttons serve as essential tools within ServiceNow, enabling users to perform various actions with a single click. With the introduction of Workspace, it becomes imperative to migrate these buttons to ensure continuity and efficiency in workflows. Failure to do so may result in disjointed user experiences and decreased productivity.

Key Differences Between Standard UI and Workspace

Before delving into the migration process, it’s essential to understand the differences between the standard UI and Workspace interfaces. Workspace offers a more modern, intuitive user experience with enhanced navigation and functionality. Migrating UI Action buttons ensures that users can leverage these benefits seamlessly.

Step-by-Step Migration Process

1. Assess Your UI Action Buttons: Begin by identifying all UI Action buttons currently in use within your ServiceNow instance.
2. Evaluate Compatibility: Determine if your existing buttons are compatible with both standard UI and Workspace. If not, consider making necessary adjustments.
3. Custom Button Creation: Create custom buttons with simple functions that work across both interfaces. This ensures consistency and compatibility.
4. Aligning with Out-of-the-Box Buttons: Properly align your custom buttons with out-of-the-box buttons within the Workspace interface for a cohesive user experience.
5. Configuration and Testing: Configure the buttons within ServiceNow, ensuring they function correctly in both standard UI and Workspace environments.
6. User Training and Feedback: Provide training to users on the new Workspace interface and gather feedback to make any necessary refinements.

Best Practices and Tips

• Prioritize user experience and consistency across interfaces.
• Test thoroughly in sandbox environments before deploying changes to production.
• Communicate changes effectively to users and provide ongoing support.

Conclusion

Migrating UI Action buttons to ServiceNow Workspace is a crucial step in maximizing the benefits of the platform’s modern interface. By following our comprehensive guide, you can ensure a smooth transition, enhance user experience, and unlock the full potential of ServiceNow’s capabilities.

Stay tuned for more insights and tips on optimizing your ServiceNow experience. Subscribe to our blog for regular updates and industry insights.

Script Include:

var SNowitSOWAjaxUtils = Class.create();
SNowitSOWAjaxUtils.prototype = Object.extendsObject(AbstractAjaxProcessor, {
    /*
    Function that returns DisplayName and SysID of the Group Members
    @param {String} group_id - SysID of the Group
    Return {Object} - Returns object as {displayName {String}, sys_id {String}}
    */
    GetGroupMembers: function(group_id) {
        var groupID = this.getParameter('group_id') || group_id;
        var result = []; // [{displayName, sys_id}]
        if (groupID) {
            var memGR = new GlideRecord('sys_user_grmember');
            memGR.addQuery('group', groupID);
            memGR.orderBy('email');
            memGR.query();
            while (memGR.next()) {
                var temp = {};
                temp.displayName = memGR.getDisplayValue('user');
                temp.sys_id = memGR.getValue('user');
                if (temp.sys_id)
                    result.push(temp);
            }
        }
        return JSON.stringify(result);
    },
    type: 'SNowitSOWAjaxUtils'
});

Workspace Client Script:

function onClick(g_form) {
    var groupID = g_form.getValue('assignment_group');
    var ga = new GlideAjax("SNowitSOWAjaxUtils");
    ga.addParam("sysparm_name", "GetGroupMembers");
    ga.addParam("group_id", groupID);
    ga.getXMLAnswer(function(response) {
        try {
            answer = JSON.parse(response);
        } catch (e) {
            return;
        }
        if (groupID && !g_form.getValue('assigned_to')) {
            var choices = [];
            for (var i = 0; i < answer.length; i++) {
                choices.push({
                    displayValue: answer[i].displayName,
                    value: answer[i].sys_id,
                });
            }
            g_modal.showFields({
                title: 'Select Assigned to and move to Assess',
                cancelTitle: 'Cancel',
                confirmTitle: 'Assign',
                cancelType: 'default',
                size: 'md',
                confirmType: 'confirm',
                fields: [{
                    type: 'choice',
                    name: 'assigned_to',
                    label: 'Assigned to',
                    choices: choices,
                    mandatory: true
                }],
            }).then(function(fieldValues) {
                g_form.setValue('assigned_to', fieldValues.updatedFields[0].value);
                g_form.setValue('state', '102');
                g_form.save();
            });
        }
    });
}