Basic to Advanced ServiceNow Interview Questions | SPOTO

There are five search interfaces in this cloud-based platform. These are -

In the form, you enter the data and when you open an incident, the page with the fields such as "Short Description," "Priority," and "Caller" is the form.

Data Sources in ServiceNow allow integration with external systems and databases. They define how ServiceNow connects and interacts with external data. Common types include REST, SOAP, JDBC, and LDAP sources. Administrators configure data sources through Integration Hub or Import Sets. Data Sources enable ServiceNow to leverage external data for processes, reporting, and automation.

- Asset Management in ServiceNow involves tracking and managing IT assets. - Create asset records and associate them with users or departments. - Utilize CMDB to maintain relationships and dependencies between assets. - Implement lifecycle management to track asset procurement, deployment, and retirement. - Use workflows for asset requests, approvals, and inventory updates. - Asset Management improves asset utilization and supports compliance efforts.

To retrieve all active incidents assigned to a specific user, you can use the following script: var gr = new GlideRecord('incident'); gr.addQuery('active', true); gr.addQuery('assigned_to', 'user_sys_id'); gr.query(); while (gr.next()) { gs.info(gr.number); } This script initializes a GlideRecord object, adds queries to filter active incidents assigned to the user, and retrieves the records.

UI policies dynamically change information on a form and control custom process flows for tasks. UI policies are alternative to client scripts. You can use UI policies to set mandatory fields,which are read only and visible on a form. You can also use UI policy for dynamically changing a field on a form.

ServiceNow Admin is a platform for developing and customizing applications, including out-of-the-box solutions like IT Service Management. It follows ITIL principles and supports modules such as HR, CSM, and incident management. The platform enables automation of workflows and processes, improving operational efficiency. Admins can also configure forms, notifications, and reports for organizational needs. ServiceNow Admin ensures centralized management of incidents, requests, and tasks. It provides scalability for growing business requirements and IT governance.

A glide report is a visual representation of the entire data available within an IT company. Experts use it to build reports, analyze data trends, extract valuable insights and make informed decisions. It also has many options for visual representation like graphs, charts, tables and more. Therefore, we can customize the reports according to requirements.

In case a user makes certain changes to the homepage, that page version gets saved as their personal homepage. The actual homepage does not get updated. For instance, the name of the homepage is Incident Review. Now, when I make any adjustments, it'll get saved as my incident review and will only be visible to them.

The key topics covered include system applications, security privileges, service level agreements (SLAs), variable types, data changes, transform maps, user roles, catalog applications, incident numbering, scheduled jobs, single sign-on (SSO), and workflow peculiarities for catalogs.

- An administrator can temporarily take over the identity of another user in ServiceNow by impersonating them, all without having to log out. - This feature helps troubleshoot by replicating the user's exact permissions and experiences. - It aids in debugging user-specific issues, ensuring accurate problem resolution. Impersonation is also used to verify that security configurations are correctly applied to different roles. - It ensures that changes made by admins function as intended for various users. The impersonation process maintains audit logs for security and transparency.

Domain separation is a way to separate data into logically-defined domains. For example a client ABC has two businesses and they are using ServiceNow single instance. They do not want users from one business to see data of other business. Here we can configure domain separation to isolate the records from both business.

While both deal with items in an organization, CMDB (Configuration Management Database) focuses on configuration items (CIs) that are part of an IT environment and their relationships, which is crucial for impact analysis and change management. Asset Management, on the other hand, tracks and manages physical assets, their lifecycle, costs, and contractual aspects.

The name of a table related to workflow typically starts with 'wf_'.

- This Determines whether the value of the field is calculated from other values. - The Calculation Type field allows you to select the script or formula-based calculation for the column value. - About business rules, calculated fields are populated first before any business rule, even a business rule, is run. - Fields display as read-only when calculated scripts are applied.

In ACL, '*' means the rule applies to all users, while 'none' means no rule is applied.

To optimize ServiceNow performance for large-scale implementations, consider the following best practices:

ServiceNow offers UI 15 and UI 16, allowing users to select the interface that suits their preference, with UI 16 providing a more modern and user-friendly experience. UI 16 includes responsive layouts, improved navigation, and enhanced mobile support. UI 15 is maintained for backward compatibility in older instances. Users can switch between UIs based on comfort and project requirements. The newer interface enhances productivity through intuitive design. Administrators can also customize the UI for organizational branding.

It's a built-in wizard that walks an Admin through the steps of setting up a new module (like HR or IT) for the first time.

Client script sits on the client side(the browser) and runs on client side only.Following are the types of client script:

I had to make two widgets communicate with each other by using the Service Portal event system. One widget would trigger an event, and the other widget would listen for that event and update its data accordingly.

An inbound email action is a process that handles incoming emails and can create or update records in ServiceNow based on the email content.

Here are some best practices to keep in mind while utilizing ServiceNow: • Collaborative workplaces should take the role of spreadsheets and email. • Every business procedure in your company should be automated. • ServiceNow makes it simple to create a contemporary work environment. • To speed service delivery, you should attempt to improve, structure, and automate the workflow.

- Select the check box to enable script objects from other application scopes to delete records from this table. - This option offers runtime protection. - For example, a script in another application can remove a record from this table. - This option is available only when the Can read check box is selected. - Clear the check box to prevent script objects from other application scopes from deleting records from this table.

A scorecard is a representation of the performance measure of an employee or a business technique. It shows a graphical representation of overtime progress. This measure belongs to an indicator. We can improve this by adding targets, breakdowns, aggregates and time series.

These are the buttons, links, and right-click options you see. "Submit," "Update," and "Resolve" are all UI Actions.

- When you create a new custom table, several fields appear in the Table Columns embedded list. - For all tables, required system fields are added automatically. - You cannot delete or modify these fields. - For tables that extend another table, fields on the parent table also appear on the Table Columns embedded list for the current table. - If you modify these fields, remember that all changes to fields on the parent table affect all child tables, not just the current table.

No, GlideRecord() cannot be called directly in client scripts because it is a server-side API. Instead, you can use GlideAjax to call server-side scripts.

To create a new table in ServiceNow, navigate to the 'Tables' module, click on 'Create New,' and fill in the required fields such as table name and label. After saving the new table, configure its columns and access controls as needed.

- Journal fields work together to create a log of changes and comments as tasks are worked on. - Journal fields work on audited tables only. - Fields of the journal_input type are multi-line text boxes which, upon saving, add the comments into the Activity field with a notation - Two fields in ServiceNow are journal fields – Additional Comments and work notes.

These are the libraries of logic that work in the background. You do not need to write the same rule five times in different places, and you have to write this once in a script.

Use a JavaScript object to count occurrences. var arr = [1, 2, 2, 3, 3, 3]; var counts = {}; arr.forEach(function(e) { counts[e] = (counts[e] || 0) + 1; }); var duplicates = []; for (var key in counts) { if (counts[key] > 1) { duplicates.push(parseInt(key)); } } duplicates.sort(); gs.info(duplicates);

Yes, you can write client-side scripts in a UI action by selecting the 'Client' checkbox and writing the script in the 'Script' field.

A Knowledge Block refers to a set of articles or content from the Knowledge Management module, helping users find solutions to common issues or get information about various topics.

A Workflow is a sequence of activities that automate a process in ServiceNow. Workflows can include approval processes, task generation, notifications, and scripting to coordinate and automate various tasks in ServiceNow.

Roles control access to features and capabilities in applications and modules. The admin role provides access to all features and capabilities. After access has been granted to a role, all the groups or users assigned to the role are granted access. Roles can contain other roles, and any access granted to a role is granted to any role that contains it. When possible, simplify user administration by assigning roles to groups. Create groups containing all the roles necessary for specific personas, then assign users to those groups. Role records are stored in the Roles [sys_user_role] table.

MID Server runs inside the customer network to enable discovery, orchestration, and integrations where outbound-only connections are required.

Business Services in ServiceNow represent essential services provided to customers or internal teams. They depict the connections and dependencies between business procedures and IT components. This understanding helps manage service impacts and prioritize IT tasks. Business Services are crucial for decision-making and aligning IT efforts with business goals. They also play a key role in monitoring performance and ensuring service levels are met.

ServiceNow provides several mechanisms to secure sensitive information: - Access Control: ServiceNow employs role-based access control (RBAC) to grant or restrict access to different parts of the system. By assigning appropriate roles and permissions, organizations can ensure that only authorized individuals can view or modify sensitive data. - Data Encryption: ServiceNow offers data encryption capabilities to safeguard sensitive information stored in the system. Encryption protects data at rest and in transit, ensuring its confidentiality and integrity. - Field-Level Security: Administrators can define field-level security rules to control who can access or modify specific fields within a table. This allows organizations to restrict access to sensitive data fields based on user roles and requirements.

Service now is a popular cloud-based information technology service management tool (ITSM). This tool provides only one software system of record for the whole IT service to perform the following tasks such as; - IT services - Operation management - Business management

Admins manage configurations, user access, incidents, request workflows, updates, and monitor instance health while supporting releases and integrations.

To show a module to a particular role only, you can set the 'Roles' field on the module record to that specific role.

The ServiceNow MID (Management, Instrumentation, and Discovery) Server is a lightweight Java application that facilitates communication between the ServiceNow instance and external systems. It is used for Discovery, Orchestration, and other integrations, enabling secure data collection and execution of automation tasks. The MID Server runs behind the firewall, ensuring compliance with security policies. It supports multiple use cases, such as infrastructure discovery, monitoring, and integration with third-party systems, enhancing ServiceNow's capabilities.

The main phases are: - Scanning – Identifying active IP addresses. - Classification – Determining the type of device or application. - Identification – Matching the discovered item with CMDB records. - Exploration – Collecting detailed attributes and relationships.

Q8. How does ServiceNow's Automation Engine enhance integrations in 2025?

The Application Navigator is a key component of the ServiceNow user interface. It allows users to navigate between applications and modules within the platform. The Application Navigator is organized into a hierarchical structure, with applications listed first, followed by their respective modules.

Roles are like VIP Passes. So a "User" role might only let you see the Service Catalog. An "Admin" role will let you make the change how the whole system looks.

UI policies dynamically change form behavior. They can make fields mandatory, read-only, or hidden based on conditions, improving data accuracy and user guidance without scripting.

ServiceNow provides various options: UI policies to dynamically change information on a form, Client Scripts for client-side scripting, UI Actions to add buttons, links, or context menu items, and Branding Editor for adjusting the platform's appearance.

The system name of a newly created table ABC will be 'u_abc'.

It's the mobile app for the workers. IT people can fix tickets, and managers can approve requests.

To check if a user has a specific role before allowing them to update a record, you can use the following script: if (gs.hasRole('role_name')) { // Allow update } else { gs.addErrorMessage('You do not have the required role to update this record.'); } This script checks the user's role and either allows the update or displays an error message.

Q9. What is a key feature of ServiceNow's integration with Microsoft Copilot in 2025?

It can be set in the following property: glide.ui.active.session.life_span.

An Incident is an unplanned interruption or reduction in the quality of an IT service, or a failure of a configuration item that has not yet impacted the service.

An import set is a staging table used to import external data into ServiceNow. Data is first stored in the import set table, then transformed into target tables using a transform map.

- To create a Data Policy in ServiceNow, navigate to System Definition > Data Policies. - Define the conditions under which the policy applies, such as table, field, and conditions. - Specify the actions to enforce, like mandatory fields, read-only access, or encryption. - Save the policy to activate it, ensuring data governance and compliance with organizational rules and regulations.

Don't just list features. Tell stories. Instead of saying "I know Service Catalog," say "I built a Service Catalog that reduced the time it took for employees."

A transform map transforms the record imported into ServiceNow import set table to the target table. It also determines the relationships between fields displaying in an Import Set table and fields in a target table.

- The Now Platform offers these extension models. - Table per class - Table per hierarchy - Table per partition

I start by identifying entities, their relationships, and required attributes. I use the Table Builder or ERD tools to map them, making sure they align with platform best practices.

The CAB is a group of stakeholders, including IT managers, technical leads, and sometimes business representatives, that reviews and approves Normal Changes. They ensure changes are necessary, planned, and low-risk. During an interview, discuss who typically sits on a CAB or how to configure CAB tasks in ServiceNow. Emphasize that the CAB's role is to minimize risk from changes by carefully reviewing them.

- An Update Set in ServiceNow is a collection of customizations and changes made to the platform. - It tracks modifications such as scripts, forms, and configurations. Update Sets are used to transfer changes between instances, such as from development to production. - They ensure consistency and support version control. Each Update Set captures a snapshot of changes, simplifying their application elsewhere. It's crucial for managing changes in a structured and controlled way.

When an import changes a table that is not the intended table for that import, this is referred to as a foreign record insert. This occurs when a table's reference field is updated.

You go to their User record and check the "Locked Out" box. This keeps their history in the system but prevents them from accessing it.

You can go to "System Properties" and "My Company," where you can upload your logo and also change the colors of the header to match the company's branding.

- Implementing a ServiceNow IntegrationHub involves creating integrations using pre-built connectors. - Connectors facilitate communication with external systems through APIs and protocols. - IntegrationHub actions are orchestrated using Flows in ServiceNow Flow Designer. - Administrators configure mappings and transformations for data synchronization. - It enables ServiceNow to automate processes involving diverse applications and data sources.

Data policies enforce mandatory and read-only states for fields and are applied before server-side logic, like Business Rules.

Discovery is a ServiceNow tool that finds computers, servers, and other devices on a network and populates this data into the CMDB automatically.

Change Management in ServiceNow ensures that any modification to the IT infrastructure is planned, approved, and implemented with minimal risk. It involves steps like raising a change request, assessing impact, obtaining approvals, scheduling the change, implementing it, and reviewing the results. ServiceNow supports different change types, such as Standard, Normal, and Emergency, to streamline the process.

Access to different parts of ServiceNow can be restricted using Access Control Rules (ACLs). ACLs define which roles have what type of access (read, write, create, delete) to specific tables and fields.

The System Dictionary contains the definition for each table and column.

An update set in ServiceNow is a group of customizations that allows users to move updates from one instance to another. This feature in ServiceNow enables admins to assemble a series of modifications into a named set and transfer them as a unit to other systems for deployment.

ServiceNow allows the creation of custom REST APIs using Scripted REST. You define a new API, create resources (endpoints), and write scripts to handle requests and responses. For example, you might create a GET endpoint /users that returns a list of users in JSON format. Your script processes a request, gets the query parameter or requestBody, queries the database, and writes a JSON response with response.setBody(). Mention that you should secure the API (e.g., using ACLs or OAuth scopes) and test it with tools like the REST API Explorer or Postman.

Orchestration automates tasks across external systems (e.g., provisioning) via runbooks and MID Server, extending ServiceNow beyond the platform.

It's a field that points to another table.

Domain Separation allows different parts or departments of an enterprise to manage their data as if they are on separate, isolated instances while actually sharing a single instance. This is useful for large organizations with distinct business units, ensuring data privacy and customization for each unit without needing multiple ServiceNow instances.

Create and maintain users on the instance. Add users to groups to allow for easy collaboration and permissions management. Assign roles to manage security and ensure compliance with regulatory or internal policies. Manage user sessions and monitor usage on your instance. Maintain consistency for table fields that refer to a company name, such as a vendor or manufacturer.

First, I check if the user's account is active and not locked or expired. Verify that the user's password is correct or reset it if needed. If using LDAP or SSO, I will ensure the authentication source is working by checking network connectivity and credentials. Look at the system logs (System Logs > Security > Login Attempts) for error messages. Sometimes, asking the user to clear the browser cache or try a different browser can also resolve client-side issues.

- A field that displays the results of a database function, such as a mathematical operation, field length computation, or day-of-the-week calculation. - Once the new function record is saved, you cannot clear the check box to make the field a regular field. - Video tutorial:- https://youtu.be/zjpOIxxXnSI

You need not build a new table from the beginning, as you can extend the current one.

Create a UI action with condition script checking state, and a client script to show/hide field. // UI Action condition: current.state == 'on_hold' // Client script on change of state function onChange(control, oldValue, newValue, isLoading) { if (newValue == 'on_hold') { g_form.setDisplay('u_on_hold_reason', true); g_form.setDisplay('on_hold_ui_action', true); } else { g_form.setDisplay('u_on_hold_reason', false); g_form.setDisplay('on_hold_ui_action', false); } }

An incident can be reopened if the issue recurs or if the user reports that the resolution was not effective.

It's a way to automatically set field values.

Use GlideSysAttachment to copy and delete attachments. var sourceTable = 'incident'; var targetTable = 'problem'; var sourceGr = new GlideRecord(sourceTable); sourceGr.addQuery('active', true); sourceGr.query(); while (sourceGr.next()) { var att = new GlideSysAttachment(); var attachments = att.getAttachments(sourceTable, sourceGr.getUniqueValue()); for (var i = 0; i < attachments.size(); i++) { var attachment = attachments.get(i); var newSysId = att.writeContent(targetTable, sourceGr.getUniqueValue(), attachment.getFileName(), attachment.getContentType(), attachment.getContent()); if (newSysId) { att.deleteAttachment(attachment.getSysId()); } } }

A business rule in ServiceNow automates actions and enforces logic on records. It can update fields, send notifications, or create records based on conditions. Business rules can run before, after, or asynchronously after data is saved, ensuring consistency and automating processes. Types of Business Rules: - Before: Runs before the record is saved to the database. This is used for validating or modifying data before it's committed. Example: If a user updates the priority of an incident, a Before business rule could validate the new priority and prevent saving if it doesn't meet certain criteria. - After: Runs after the record is saved to the database. This is useful for triggering actions like sending notifications or updating related records. Example: After updating an incident's priority, an After business rule could automatically assign the incident to a specific support group based on the priority. - Async: Runs asynchronously after the record is saved. This is used for long-running processes that don't need to block the current transaction. Example: After an incident is created, an Async business rule could trigger a background task to run a detailed system check or send data to an external system without delaying the user's workflow.

When using GlideRecord, invalid queries can be caught by checking the isValid() method after setting conditions. If it returns false, the script should skip execution or log an error. This prevents runtime issues and ensures clean query execution.

Script Includes in ServiceNow are reusable server-side JavaScript functions that contain business logic or code that can be called from other scripts. It can be Business Rules, Scheduled Jobs, or UI Actions. They help improve code reusability, modularity, and maintainability by encapsulating commonly used logic in one place. Example: A Script Include might define a function to calculate the priority of an incident based on its category and impact. var IncidentUtils = Class.create(); IncidentUtils.prototype = { initialize: function() {}, calculatePriority: function(category, impact) { // Custom logic to calculate priority return priority; } }; Other scripts can then call IncidentUtils.calculatePriority() to reuse the logic.

Create an account record for the individuals who have access to your instance. Each user account has a unique login ID, password, and set of permissions (roles) that define what they can do and access within the platform. User records establish a relationship between an individual and your ServiceNow instance. User records consist of a user name, a password, and information relating to the individual, such as contact information, location, and job title. User records are stored in the Users [sys_user] table.

Through a cloud-based solution

- Integration with LDAP (Lightweight Directory Access Protocol) in ServiceNow allows for the synchronization of user data from an LDAP directory into ServiceNow. - This facilitates single sign-on (SSO) and ensures that user information is consistent and up-to-date. - LDAP integration helps automate user provisioning and de-provisioning processes. - It enhances security by centralizing authentication and access control. The integration is configured through the ServiceNow LDAP integration module.

Installation exits are JavaScript functions that override default platform behaviors during upgrades or installs. They are placed in special script files and run at defined extension points. This allows adding custom logic without modifying core code.

To manage user roles and groups in ServiceNow:

A new table can be defined under the application scope and fields assigned with proper types. Access controls and roles are configured for security. Relationships to other tables can be established for structured data. Update sets capture these changes for deployment to other instances. Testing ensures proper functionality before production use. This allows modular development within the platform.

Capacity planning involves forecasting resource requirements based on historical data, growth projections, and business needs. Scalability strategies include implementing scalable architectures, load balancing, and automation to adapt to changing demands and ensure optimal performance and resource utilization.

The following are some examples of how to use the service now integration tool in practice:

S – Situation A few months ago, the Head of Sales approached me with an urgent and highly demanding request regarding the Sales Operations dashboard in ServiceNow, which our sales team uses to track leads, opportunities, and sales forecasts. He felt the existing dashboard was "useless" and didn't provide the real-time, granular data he needed to make critical business decisions. His request was to completely redesign the dashboard to include over 30 new metrics, complex conditional formatting, and real-time integration with an external marketing automation platform, all within a two-week timeframe, stating that it was "critical for quarter-end reporting." He had a very aggressive communication style and often bypassed normal request processes, going directly to me with his demands, which put significant pressure on my bandwidth and project queue. T – Task My task was to manage the Head of Sales's expectations regarding the scope and timeline of his dashboard request, translate his broad and ambitious vision into a feasible ServiceNow solution, and deliver a valuable, albeit potentially phased, outcome. This required strong communication, negotiation, and technical design skills. The key challenge was balancing his immediate, high-pressure demands with the practical realities of development cycles, resource availability, and the platform's capabilities, while ensuring the final solution genuinely addressed his underlying business needs without over-promising or creating a technical debt. A – Action My first action was to schedule an immediate, dedicated meeting with the Head of Sales. Instead of diving straight into technical solutions or pushing back, I started by actively listening to his frustrations and understanding the "why" behind his demands. I asked open-ended questions like, "What specific business decisions are you struggling to make with the current dashboard?" and "What critical insights are you missing that these new metrics would provide?" This helped me identify his core pain points, which revolved around needing better visibility into lead conversion rates by source and real-time pipeline changes. After listening, I acknowledged his frustration and the importance of timely data for sales operations. I then gently, but firmly, explained the standard development process, including requirements gathering, design, development, testing, and deployment. I highlighted the technical complexities involved in creating 30 new metrics, especially those requiring integration with external systems, and explained how these elements typically impact timelines. I used concrete examples, explaining that each new metric often required new reports, potentially new database fields, and data aggregation logic, which can't be spun up instantly. I also explained that complex real-time integrations need secure API setup and thorough testing to prevent data integrity issues. I proposed a phased approach. For Phase 1, I suggested focusing on the top 3-5 most critical metrics and data visualizations that would address his immediate, most pressing needs for quarter-end reporting. We could then refine and expand in subsequent phases. To make this concrete, I immediately sketched out a simplified dashboard layout on a whiteboard during our meeting, visually demonstrating what could be achieved within a realistic, albeit still expedited, timeframe (e.g., three to four weeks for the core elements). I focused on quick wins that would deliver immediate value and build trust. Technically, for Phase 1, I focused on: - Prioritized Reporting: I worked with him to identify the 5 most crucial metrics. These included "Lead Conversion Rate by Source," "Current Quarter Pipeline Value," and "Opportunities by Stage." - Existing Data Leverage: I primarily leveraged existing data points within our custom CRM tables in ServiceNow to build new reports. For example, the "Lead Conversion Rate" could be derived from existing lead and opportunity tables by joining them and applying specific filters. - Performance Analytics Widgets: I used ServiceNow's Performance Analytics (PA) capabilities to create new indicators and breakdowns for these metrics, allowing for more dynamic visualizations and historical trending, which he valued. I configured indicator sources, automated data collection jobs, and then built scorecards and time series widgets for the dashboard. - Simple Integration (Batch): For one critical metric related to marketing spend from the external platform, instead of a real-time, complex API integration, I proposed a daily scheduled import (batch processing) of a CSV file. This provided "near real-time" data without the extensive development overhead of a full API integration within the tight deadline. - Frequent Demos: I scheduled bi-weekly check-ins with him to demonstrate progress, gather feedback, and ensure the development was aligned with his evolving vision, even for the initial phase. This proactive communication helped manage his expectations and allowed for small course corrections. R – Result By taking a structured, empathetic, and phased approach, I successfully managed the demanding stakeholder's expectations and delivered a highly valuable solution. While I couldn't deliver all 30 metrics in two weeks, the initial phase delivered within four weeks included the top 5 most critical metrics and dynamic visualizations using Performance Analytics. This significantly improved the Head of Sales's ability to track quarter-end performance and make data-driven decisions. He expressed genuine satisfaction with the initial results, acknowledging the practical constraints and appreciating the collaborative approach. The successful delivery of Phase 1 built trust, transforming a demanding relationship into a productive partnership. He became more receptive to following standard request processes for subsequent phases, and we subsequently rolled out another 10 metrics in a planned Phase 2. This experience taught me the importance of active listening, transparent communication about technical limitations, and proposing pragmatic, phased solutions to even the most demanding requests.

Users can modify themes, colors, and layouts using “System” or “Instance” options. Personalization improves visibility and efficiency. Changes do not affect core system settings or workflows. Admins can enforce organizational branding if needed. Updates are reflected across dashboards and forms. Customization enhances user comfort and experience.

The CSA (Certified System Administrator) is the "entry ticket." Most employers in 2026 expect to see at least this one on your resume.

To handle a complex approval process in ServiceNow, you can use the Workflow Editor to create a custom approval workflow. Design the workflow to include multiple approval activities, conditional branching, and parallel processing as needed to meet your specific requirements. Configure each approval activity with the appropriate approver or approver group and set up notifications and escalations as needed.

Use GlideRecord on kb_knowledge table. var kb = new GlideRecord('kb_knowledge'); kb.initialize(); kb.short_description = 'Test KB Article'; kb.text = 'This is the content.'; kb.insert();

Use GlideAggregate on cmdb_ci and incident tables. var ga = new GlideAggregate('incident'); ga.addQuery('sys_created_on', '>=', gs.daysAgoStart(90)); ga.addAggregate('COUNT', 'cmdb_ci'); ga.groupBy('cmdb_ci'); ga.orderByDesc('COUNT_cmdb_ci'); ga.query(); var result = []; while (ga.next()) { var ciName = ga.getDisplayValue('cmdb_ci'); var count = ga.getAggregate('COUNT', 'cmdb_ci'); result.push({ci: ciName, count: count}); }

You cannot add these pages to the Update Sets by default. It needs to add manually to the existing update pages by unloading them.

Task Table.

Mapping Assist is used for mapping fields using the Import Log.

A Data Policy in ServiceNow is a rule that enforces data integrity by setting mandatory and read-only states for fields on a record. Unlike UI Policies, which are client-side and apply to forms, Data Policies are server-side and apply to all data operations, including API calls and background scripts. Data Policies ensure that data conforms to business rules and standards, regardless of how it is entered or modified. They help maintain consistency and accuracy across the platform.

To check if a field value has changed in a record in ServiceNow, you can use the GlideRecord object with the previous method or compare the field's current value with its previous value. - Using the previous() Method: The previous() method allows you to access the previous value of a field before it was updated. You can compare it with the current value to determine if it has changed. - Example: var gr = new GlideRecord('incident'); if (gr.get('sys_id', 'your_sys_id')) { var currentPriority = gr.priority; var previousPriority = gr.priority.getPreviousValue(); if (currentPriority != previousPriority) { // The priority field has changed gs.info('Priority has changed!'); } } In this example, we compare the current value of the priority field with the previous value to check if it has changed. - Using changed() Method in Business Rules: In a Business Rule, you can use the changed() method to check if a specific field value has changed. The changed() method returns true if the field value has been updated. Example: if (current.priority.changes()) { // The priority field has changed gs.info('Priority field has changed!'); } You can use previous() for comparing current and previous field values or changes() in business rules to check if a field has been modified.

UI policies in ServiceNow dynamically change the behavior of fields on a form based on specific conditions. They can show, hide, and make fields read-only or mandatory without writing code. UI policies are defined using conditions and actions in the ServiceNow interface. They enhance user experience by guiding users through form completion. These policies are client-side scripts that execute as the user interacts with the form. They help enforce data entry standards and improve data quality.

The import set tool is used to import data from several data sources, subsequently transformed into ServiceNow tables using transform maps. It acts as a staging area for imported data.

An example of implementing a live list using recordWatch is creating a widget that displays real-time updates of incident records. The widget uses recordWatch to listen for changes and refresh the list automatically.

A Data Policy in ServiceNow ensures data consistency and integrity by enforcing rules on how data is entered or updated in the system. It defines mandatory, read-only, or hidden fields, ensuring that specific conditions are met when records are created or modified. Example: A Data Policy can ensure that the "Short Description" field in an incident record is always mandatory before submitting, whether the incident is created through the UI, API, or import.

Discovery types include Horizontal Discovery, which finds devices and applications across the network, and Vertical Discovery, which focuses on detailed application-specific information. There is also Cloud Discovery for virtual resources in cloud environments.

A reference qualifier in ServiceNow helps to create filters that limit the data returned for a service field. Moreover, a reference field includes a connection to a field on another table. Further, it enables the form that covers reference fields to access the records within the referred table.

The two ways to open a new HR case are through the Service Portal or by using the 'New' button in the HR Case module.

A reference qualifier in ServiceNow is used to filter the options available in a reference field based on specific conditions. It restricts the records displayed in a reference field, making it easier for users to select the correct values. How it works: - Default Reference Qualifier: By default, ServiceNow limits the options in a reference field to only those records from the referenced table. - Custom Reference Qualifier: You can customize the reference qualifier by defining a condition or writing a script (either in the UI or as a filter) to narrow down the available records. For example, you can display only active users or incidents with a high priority in the reference field. Example: If you have a reference field to select a Manager in a User record, you can use a reference qualifier to show only users with the "Manager" role. This way, only relevant users appear in the dropdown list.

In ACL, '*' means the rule applies to all users, while 'none' means no rule is applied.

ServiceNow APIs and web services are a set of protocols and interfaces that enable integration with external systems and applications. These include:

Client transaction timing offers additional details about the duration of the transactions between the server and the client. For this, the - client transaction timing plugin - plugin has to be activated.

LDAP is Light weight Directory Access Protocol. You can use it for user data population and user authentication. ServiceNow integrates with LDAP directory to streamline the user log in process and to automate the creation of user and assigning them roles.

It is basically managing the individuals who can access ServiceNow instances by defining them as users in the system. Creating users, groups, and roles provides a flexible and scalable way to manage access to features on the Now Platform. By creating user accounts, assigning users to groups, and defining roles and permissions, administrators can ensure that users have the appropriate level of access to applications and data. This allows organizations to control access to sensitive data, maintain compliance with regulatory requirements, and improve overall security.

An Incident is a single event that disrupts service, while a Problem is the root cause of one or more incidents.

Impersonating a user means giving the administrator access to what the user would have access to. This includes the same menus and modules. ServiceNow records the administrator activities when the user impersonates another user. This feature helps in testing. You can impersonate that user and can test instead of logging out from your session and logging again with the user credentials.

Select the check box to enable script objects from other application scopes to create records in this table. This option offers runtime protection. For example, a script in another application can insert a new record in this table. This option is available only when the Can read check box is selected. Clear the check box to prevent script objects from other application scopes from creating records in this table.

Use JSON.parse and dot notation to access nested values. var jsonString = '{"user":{"name":"John","address":{"city":"NYC"}}}'; var parsed = JSON.parse(jsonString); var city = parsed.user.address.city; gs.info(city);

Custom reports are created with the following steps -

You can make a baseline in the CMDB, which is a snapshot of your configuration elements. You can monitor the modifications done to that configuration item since the last baseline. Multiple baselines can be constructed, and the system keeps account of the changes made to each one.

Select the check box to enable script objects from other application scopes to delete records from this table. This option offers runtime protection. For example, a script in another application can remove a record from this table. This option is available only when the Can read check box is selected. Clear the check box to prevent script objects from other application scopes from deleting records from this table.

It's a way to get information from a related table. On an Incident form, you can "dot-walk" to see the Caller's Manager's phone number without leaving the page.

- Administrators can use these tools to see the relationships between classes. - Schema map - System dictionary - Tables module

A group is a collection of users who do the same work, like the "Help Desk" or the "Payroll Team." It's much easier to send a ticket to a group than to one specific person.

Users can construct task-based records from the service catalog using a record producer, which is a form of the catalog item. A record producer, for example, can be used to generate a change or problem record. Through the service catalog, record producers offer an option for making albums.

The HTML Sanitizer in ServiceNow is a security feature designed to prevent malicious code injection, particularly defending against cross-site scripting (XSS) attacks. It cleans up HTML content, removing any untrusted or harmful tags, attributes, and JavaScript code from user-generated content, such as knowledge articles, comments, or descriptions. Role and Purpose: - Sanitization: The HTML Sanitizer removes potentially dangerous elements like