Giving the administrator access to what the genuine user would have access to is known as impersonating a user. This will feature the same modules and menus as the previous version. When a user impersonates another user, ServiceNow captures all of the administrator's activity. This ServiceNow functionality is handy for testing. For instance, if you want to see whether or not a user can access the change form. You have permission to impersonate that user and undertake testing without logging out of your session and logging back in using that user's credentials.

Talking too much about the tech and not enough about the business value.

The UI allows navigation, data entry, task management, and access to modules. It provides dashboards, forms, and reporting capabilities. Users can personalize their interface to enhance productivity. Admins can apply themes for branding. The UI supports workflow visibility and efficiency. Proper UI design improves user satisfaction and adoption.

Navigate the system

When an import makes a change to a table that is not the target table for that import, this is when we say foreign record insert occurs. This happens when updating a reference field on a table.

Change Management in ServiceNow is implemented using workflows, approval processes, and change models. The module includes features for creating, assessing, approving, and implementing changes to IT services and infrastructure. Change Requests are categorized into standard, normal, and emergency changes, each following specific workflows and approval paths. Risk assessments, impact analysis, and post-implementation reviews ensure that changes are managed effectively, minimizing disruption and ensuring compliance with organizational policies.

Import Sets are used to load data from external sources, such as CSV files or external databases, into ServiceNow. Imported data is placed in a staging or temporary table. A Transform Map then defines how to map data from the staging table to fields in the target ServiceNow tables. After mapping, you run the transform to apply the data (inserting or updating records). It allows bulk data import with controlled mapping and transformations.

- Yes, you can remove it. - If you remove an attribute that is part of the base system, it is automatically restored during an upgrade. - To prevent upgrades from changing your system's behavior, leave the attribute on the table or field but set its value as desired. - For example, if a field has the attribute knowledge_search=true by default, do not remove it to set it to false; rather, set it to knowledge_search=false.

Yes, a client script can interact with a business rule using GlideAjax. Business rules, however, execute on the server side, not the client side. GlideAjax acts as a bridge, allowing the client script to send data to the server. The business rule processes it and returns a response. Additionally, client scripts can indirectly trigger business rules when records are saved or updated, but the business rules themselves run on the server.

The Financial Management module in ServiceNow enables organizations to manage their financial operations and expenditures effectively. It supports budget planning, cost tracking, invoice management, and financial reporting processes. By consolidating financial data from various sources into a single platform, it enhances transparency, accuracy, and compliance with financial regulations.

The Change Management module in ServiceNow plays a crucial role in overseeing the entire lifecycle of changes to IT infrastructure and services. It encompasses comprehensive planning, meticulous scheduling, and rigorous control to ensure that every change is carefully evaluated, prioritized, and implemented. This process is designed to minimize service disruption and downtime while adhering strictly to organizational policies, regulatory standards, and best practices.

The ServiceNow CMDB serves as a centralized repository for IT asset and configuration data, enabling organizations to track and manage the relationships between IT assets. It supports IT service management processes by providing accurate and up-to-date information, ensuring efficient and effective IT operations.

ATF stands for Automated Test Framework. It allows ServiceNow administrators and developers to create and run tests to ensure that instances work as expected after changes. ATF is vital as it reduces manual testing effort, ensures consistent test results, and helps in delivering changes to production with confidence.

A scoped application confines custom code and data to an application boundary, protecting global namespace, enabling versioning, and improving modularity and security.

Key components of ServiceNow include:

Key components include the database (tables and records), the user interface (forms, lists, and dashboards), the application layer (modules and applications), and the automation layer (workflows, business rules, and scripts).

A scorecard measures the performance of an employee or a business process. It is a graphical representation of progress over time. A scorecard belongs to an indicator. The first step is to define the indicators that you want to measure. You can enhance scorecards by adding targets, breakdowns (scores per group), aggregates, and time series.

- The ServiceNow Agile Development module facilitates agile project management within ServiceNow. - It supports Scrum and Kanban methodologies for software development. - Teams can manage backlogs, sprints, and user stories directly within the platform. - It integrates with other ServiceNow modules for seamless collaboration and reporting. - This module enhances transparency, efficiency, and adaptability in project execution.

It is a way to indicate global or out-of-box user preferences in the preference table. Open the record of user preference and check the system field to be true make that particular user preference a system-wide default.

A data policy in ServiceNow is a rule that enforces data integrity by ensuring data entered into the system meets specific criteria. Data policies apply to all data operations, including imports, updates, and form submissions. They can make fields mandatory, set default values, or enforce data formats. Data policies help maintain the consistency and accuracy of the data across the platform. They are similar to UI policies but apply to server-side operations. Their primary purpose is to ensure data quality and compliance.

Global Search is the most common search method in ServiceNow, located at the top of the interface. It allows you to quickly search for records across all tables, including incidents, changes, knowledge articles, and more. You can search by keywords, record numbers, or specific text. ServiceNow will return results from various tables based on the search terms. Other search techniques include: - List Search: Filters records within a specific list. - Text Search: Finds specific text within records, using Lucene indexing. - Related List Search: Searches within related lists on record forms.

After a Baseline has been produced, CMDB baselines allow us to understand and regulate the modifications implemented to a configuration item (CI). The baseline is a CI snapshot.

Creating a Transform Map in ServiceNow involves several steps to map data from an Import Set table to a target table in ServiceNow. It ensures the imported data is correctly transformed and loaded. Here are the key steps: - Ensure that the data you want to import is loaded into an Import Set Table. This table temporarily holds the raw data before transformation. - Go to System Import Sets > Transform Maps in the ServiceNow navigator and click New to create a new transform map. - Set the Name, Source Table (the Import Set Table), and Target Table (the table where data will be mapped, e.g., Incident, User). - Use the Field Map to map fields from the Import Set Table to the appropriate fields in the Target Table. - You can also use Coalesce to determine which records are considered duplicates (e.g., using a unique field like email to identify existing records). - Define any Transform Scripts (optional) to clean or manipulate the data before it's inserted into the target table. This can include field conversions, value modifications, or calculations. - After setting up the Transform Map, test it by running the transformation to check if the data is correctly mapped and imported. - Once satisfied with the setup, run the transformation process to load the data into the target table. Example: If you are importing a list of users, the Import Set Table might contain raw data with columns for name, email, and department. The Transform Map would map these columns to the User table's corresponding fields (e.g., Name, Email, Department).

Disaster recovery planning involves assessing risks, identifying critical systems and data, defining recovery objectives, and developing strategies for mitigating and recovering from disasters. Implementation includes regular backups, testing of recovery procedures, and maintaining documentation to ensure readiness for any unforeseen events.

An Event is a "flag" that the system raises. For example, when a user fails to log in, an event is triggered. That event can then tell the system to send an email or lock the account.

- Many-to-many relationships allow a list to point to a list of entries, rather than to a single field - The Many to Many Definitions [sys_m2m] table allows administrators to create custom many-to-many relationships. - Some many-to-many relationships are defined by default. - Administrators can enter the sys_collection list in the navigation filter to reference the many-to-many relationships available in the base system.

The Service Catalog in ServiceNow enhances the user experience by providing a centralized, easy-to-use platform for users to request IT services, hardware, software, or access to systems. It simplifies the process of submitting requests, managing tasks, and ensuring consistent service delivery. Key Enhancements of the Service Catalog: - Intuitive design for easy browsing and service requests. - Users can submit and track requests independently without contacting IT. - Streamlined workflows, approvals, and task assignments for efficient processing. - Tailored catalogs and dynamic fields based on user roles and needs. - Users can track request status and receive notifications for improved communication. Example: A user can request a new laptop, select the model, and submit the request directly through the Service Catalog. The request is then routed for approval, and the appropriate IT team is notified, automating the entire process from request to fulfillment.

A Business Rule is a set of instructions that the system follows when a record is changed.

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

GlideRecord in ServiceNow is a powerful JavaScript class used to interact with the database. It allows you to query, insert, update, and delete records from ServiceNow tables. Example: To query the incident table for all active incidents: var gr = new GlideRecord('incident'); gr.addQuery('active', true); gr.query(); while (gr.next()) { gs.info(gr.number); // Output the incident number } In short, GlideRecord is used for CRUD operations (Create, Read, Update, Delete) within ServiceNow, enabling efficient interaction with records in the platform's database.

Event Management in ServiceNow processes events (alerts) from external monitoring tools and correlates them into actionable information. It can suppress duplicate alerts and create incidents or alerts in ServiceNow based on defined rules. For example, if a monitoring tool sends multiple "Disk Full" alerts, Event Management can group them and generate a single Incident. In admin interviews, you may be asked about configuring alert rules and event correlation.

ITIL concepts (incident, problem, change) align directly with ServiceNow processes; ITIL familiarity helps explain process decisions and SLA handling.

To activate or deactivate an application in ServiceNow, follow the steps below: To get started, go to the "Application Menus" module. Launch the application that needs to be activated or deactivated. To enable the application, change the active value to "true." Change the active value to "false" to disable the program.

Absolutely. It's free. It shows interviewers that you are curious.

By using the “System” or “Instance” theme

Data policies in ServiceNow are pretty comparable to UI policies. By giving read-only characteristics to all fields, Data Policies make it easier for a developer to implement online data policies. The following are some critical distinctions between data policy and user interface policy: • Only data input on a form using a standard browser is covered by the UI policy. On the other hand, data policies might apply rules to any input fed into the system. • Data Policies, unlike UI Policies, run on the server. • Developers cannot apply scripts to Data Policies because UI Policy logic only applies to data input in a form.

Reference qualifiers allow filter creation to limit the returned data for a reference field. A reference field contains a link (reference) to a field on another table, allowing the form containing the reference field to access the records/fields in the referred table. For instance, the Incident table's Assigned to field refers to the User [sys user] table. If the reference lookup includes all users from the User table reference qualifier as defined in the previous example, all values for the referenced field appear by default in the reference lookup and can be accessed directly through the reference field.

A BSM (Business Service Management) map is a visual representation of the configuration items (CIs). It gives support to business services and their status. These maps are used in different business processes to ensure that business services are beneficial or not. Enterprises can work on their customer satisfaction and engagement with this information.

Use GlideAggregate with orderByDesc and setLimit. var ga = new GlideAggregate('incident'); ga.addAggregate('COUNT', 'caller_id'); ga.groupBy('caller_id'); ga.orderByDesc('COUNT_caller_id'); ga.setLimit(3); ga.query(); while (ga.next()) { gs.info(ga.getDisplayValue('caller_id') + ': ' + ga.getAggregate('COUNT', 'caller_id')); }

Client script is used to run JavaScript code on the client side (i.e., within the user's browser) to enhance user interaction with the ServiceNow platform. It helps manage the behavior of forms and fields in real-time, making the user experience more dynamic and responsive. Here are the main purposes of client scripts: - Field Validation: You can use client scripts to validate field values before the form is submitted. For example, ensuring that a phone number entered by the user follows a specific format. - Form Behavior: Client scripts can modify the behavior of form fields, such as hiding or showing fields based on the value selected in other fields. For example, if a user selects "Yes" in a dropdown for a certain question, a related field might appear. - Real-time Data Manipulation: You can dynamically update the values in fields based on user actions. For instance, when a user selects a specific department, a client script can auto-fill the related manager's name. - Improving User Experience: They enable features like auto-completion, field masking, or other interactive elements that make the interface more intuitive and user-friendly. Client scripts enable immediate feedback and interaction with the user without needing a server round-trip, which enhances performance and responsiveness.

Server-side scripting runs on the server and can access the database, while client-side scripting runs in the user's browser and is used for UI interactions and validations.

UI Policy is performed on the screen, and it might hide a field when you click a button. A Data Policy happens at the database level.

ServiceNow workflows automate business processes to improve efficiency and consistency. They define a series of steps for tasks like approvals, notifications, and record updates. Workflows make ensuring the right people do the right tasks in the correct order. They can be combined with other ServiceNow modules and customized to meet specific company needs. Workflows that are automated eliminate errors and require less manual labor. They provide transparency and traceability for business processes.

ServiceNow allows developers to capture configuration changes, including workflows, fields, scripts, and dashboards. Update sets make it easier to deploy modifications across instances safely. They also track changes and maintain version history. Update sets prevent overwriting unrelated configurations. Collaboration among developers is improved. They are crucial for structured and reliable deployments.

There are two types of UI actions: 'Default' and 'List'.

As an admin, you can click the button to become another user. It's important for solving the problem.

ServiceNow offers a variety of modules that serve different functions within the platform. Some of the key types of modules include: - IT Service Management (ITSM): Modules like Incident Management, Problem Management, Change Management, and Service Request Management focus on managing and resolving IT issues, changes, and service requests. - IT Operations Management (ITOM): Includes modules like Event Management, Discovery, and Cloud Management to monitor infrastructure, perform network discovery, and manage cloud services. - IT Asset Management (ITAM): Modules like Asset Management, Software Asset Management, and Configuration Management Database (CMDB) manage IT assets and track software usage. - Customer Service Management (CSM): Modules like Case Management, Knowledge Management, and Request Management are used to manage customer service inquiries, requests, and knowledge articles. - Human Resources Service Delivery (HRSD): Includes modules such as Case Management and Employee Service Center to handle HR processes like onboarding, employee queries, and case tracking. - Security Incident Response: Modules like Security Incident Management and Threat Intelligence help track and respond to security incidents and vulnerabilities. - Governance, Risk, and Compliance (GRC): Modules such as Policy and Compliance Management, Risk Management, and Audit Management help ensure compliance with regulations and manage risks within the organization. - Software Development: Includes DevOps and Application Lifecycle Management (ALM) to manage the development, testing, and deployment of applications. Each module in ServiceNow is designed to cater to specific business needs and improve efficiency, productivity, and collaboration across teams.

Users learn about impersonation, date formats, user profiles, and admin tools, with navigation aids like hover actions, right-click shortcuts, and filters for efficient data management. Filtering and sorting simplify large datasets. Reports and dashboards help visualize data. Users can also set bookmarks and shortcuts. These tools enhance usability and reduce manual effort. Learning these aspects improves overall productivity.

UI policies govern custom task process flows and dynamically update information on a form. Client scripts can be replaced with UI policies. Mandatory fields, which are read-only and displayed on a form, maybe defined using UI policies. You may also use UI policy to dynamically change a field on a form.

This is the "Black Box" of ServiceNow.If something is not working well or the script fails, the system logs will record the incident.

By default, the queries that have invalid field names are executed but invalid conditions are ignored. By enabling the - glide.invalid_query.returns_no_rows property - statement, a stricter query control. This will ensure an empty result set is produced for invalid queries.

UI Policies are primarily no-code tools used to make fields mandatory, visible, or read-only on a form. Client Scripts require JavaScript and are used for more complex browser-side logic (like alert boxes or field value validation).

Outline the required steps first (user account creation, equipment requests, group access). In ServiceNow, use the Flow Designer to create a flow with a trigger (e.g., a new HR record or service request). Add actions for each step: e.g., Create Record (User table), Create Task for IT (order computer), Add to Group for email, and Send Notification to the new employee. Include conditions (for example, if the hire is remote, assign remote work equipment). This answer shows your ability to design processes using ServiceNow tools.

A sys_id is a 32-character unique identifier for every record in ServiceNow. It is automatically generated and never changes, even if record data changes. The sys_id is used in references, imports, and integrations to identify records precisely.

Flow Designer is a modern tool for building automated processes without coding. You create a flow, define a trigger, and add actions or subflows. The Workflow Editor is older and uses a drag-and-drop canvas to design workflows. It is still available for legacy use cases but is being phased out in favour of Flow Designer.

A rejection notification will be sent if the request is rejected, setting the status to cancel. You can attach a service catalog workflow manually or automatically, or if no other workflows are attached.

The questions test knowledge of core ServiceNow concepts and configuration options.

A Business Rule is a server-side script that runs when records are inserted, updated, or deleted, ensuring data integrity and automation on the server. In contrast, a Client Script is a client-side script that runs in the user's browser to manage form behavior and user interactions, providing a dynamic and responsive user experience.

Business Rules in ServiceNow are server-side scripts that execute whenever a specified table action (such as insert, update, or delete) occurs. They are used to enforce data consistency, automate processes, and implement business logic within the platform.

In ServiceNow Admin, a business rule requires a server-side script when a record is presented, inserted, altered, and removed. Further, these rules help automate actions such as updating the values of form fields, creating email notifications, script actions, etc.

The main focus of the data conversion process is converting data from Excel to a specific format, focusing on the expiry date and popular date.

- An "Application" in ServiceNow refers to a set of related modules, features, and components that provide specific functionalities. - Applications are designed to address various business needs, such as IT service management, HR service delivery, and customer service management. - Each application includes tables, scripts, workflows, and user interfaces tailored to its purpose. - Applications can be customized and extended to meet unique organizational requirements. ServiceNow's App Store offers pre-built applications for different use cases.

ServiceNow upgrades are managed through the ServiceNow HI Service Portal, which provides tools for planning, scheduling, and executing upgrades. Administrators can review release notes, identify impacted customizations, and test the new version in a sub-production instance. The upgrade process includes running the Upgrade Preview, resolving conflicts, and performing regression testing. Post-upgrade tasks ensure that all customizations and integrations are functioning correctly. ServiceNow's regular release cycle ensures continuous improvement and innovation.

- Service Portal provides a user-friendly interface for interacting with ServiceNow services. - It allows users to access catalogs, forms, and knowledge articles. - Service Portal supports customization to match organizational branding and needs. - Users can request services, view status updates, and engage with IT support seamlessly. - It enhances user satisfaction by offering a centralized self-service platform. - Service Portal improves efficiency through streamlined service delivery processes.

User records are associated with records on several other tables to control permissions, preferences, and other features. Few of these records are groups, roles etc.

I chose templates for that use case because they provide better separation of concerns, reusability, and easier maintenance compared to inline HTML.

Impersonation in this cloud-based platform is a practice wherein the code is executed on behalf of another user. This tool provides the - gs.impersonateUser() - function that enables switching context to a particular user. This enables the developer to simulate as well as test scripts as if those were executed by the impersonated user.

ServiceNow offers comprehensive ITSM capabilities to streamline and automate IT service processes. Some key features include: - Incident Management: ServiceNow enables organizations to track and resolve incidents efficiently. It provides workflows to assign, prioritize, and escalate incidents, ensuring timely resolution and minimizing disruptions. - Change Management: ServiceNow's Change Management module allows organizations to manage changes to their IT infrastructure effectively. It provides a structured approach for planning, reviewing, and implementing changes, reducing the risk of service disruptions. - Problem Management: ServiceNow's Problem Management module helps organizations identify and address the root causes of recurring incidents. It facilitates the investigation, diagnosis, and resolution of underlying issues, improving service stability.

The confusion arises from the distinction between the administrator's and user's settings, which can be applied to any table, including custom tables.

A category is a grouping of catalog items, while a catalog item is a specific service or product that a user can request from the service catalog.

ServiceNow Metrics measure the performance of business processes like incident resolution or service requests. They track key indicators such as response time and completion rates. Metrics are automatically collected during record processing and often used with SLAs to ensure service goals are met. Reports and dashboards visualize these metrics, helping teams monitor performance and drive improvements. Example: You can configure a metric to measure the time-to-resolution for incidents. Each time an incident is resolved, the metric records the time taken and can be reported to track if the team is meeting SLAs or identify areas for improvement.

var gr = new GlideRecord('incident'); gr.initialize(); gr.short_description = "Test incident from script"; gr.priority = 2; gr.insert();

GlideAjax is a ServiceNow class that enables client-side scripts to send and receive data to and from the ServiceNow server. Using GlideAjax enables asynchronous server calls without reloading the page. Here's a breakdown of when to use GlideAjax: - To execute server-side code from the client-side scripts, such as UI Policies, UI Actions, and Client Scripts. - It is used to make asynchronous database calls, keeping the user's browser running smoothly. It is particularly useful when interacting with server-side functionalities without refreshing the entire page, thus providing a smoother user experience. - GlideAjax should be used as a direct replacement for client-side GlideRecord queries to prevent performance issues and browser freezing. - GlideAjax calls can pass parameters to script includes, allowing you to use them via naming conventions.

- The Reminder [reminder] table provides a way to auto-generate reminders for a task. - Any table that extends the Task table, such as the Incident [incident] table, can use the - Reminder [reminder] table. - You can add Reminders as a related list to the Incident form by opening the form context menu, navigating to Configure > Related Lists, and adding Reminders->Task. - By default, only an administrator can create or modify a Reminder record. - To enable non-administrators to create reminders, add create and read ACL rules to the Reminder [reminder] table and specify the user's role. - To access the Reminder table, type reminder.do in the filter navigator.

If a task stays inactive for a specific time, an event is triggered for the task record known as the Inactivity monitor.

To create a Scoped Application in ServiceNow, navigate to Application Studio in the ServiceNow instance. Click on "Create Application" and provide details like name, version, and description. Scoped Applications isolate customizations to prevent conflicts with other applications or platform upgrades. Developers can create tables, scripts, UI components, and business rules within the Scoped Application. Scoped Applications are packaged for deployment and can include dependencies managed through the Studio.

The document contains 20 multiple choice questions about the ServiceNow system administration.

A transform map is a field map's group that changes the imported record within the ServiceNow import set table to the destination table. Moreover, it identifies the relationships between the import set fields and the ServiceNow table fields. An admin in SNow can use these maps modules to choose the target for the data imported from any table.

The - getRowCount() - function can be used to find the row count in a glide record. Example- var gr = new GlideRecord('incident'); gr.addQuery('priority', 1); gr.query(); var count = gr.getRowCount(); gs.info('Number of high-priority incidents: ' + count);

The Configuration Management Database (CMDB) is a central store of CIs (configuration items) and relationships, used to support incident, change, and impact analysis.

Sys_id is a GUID having a unique 32 characters that are useful to recognize each record built within the ServiceNow table.

Write a recursive function to traverse the manager hierarchy. function getUserHierarchy(userSysId) { var hierarchy = []; var user = new GlideRecord('sys_user'); if (user.get(userSysId)) { hierarchy.push(user.getDisplayValue('name')); var managerSysId = user.getValue('manager'); while (managerSysId) { var manager = new GlideRecord('sys_user'); if (manager.get(managerSysId)) { hierarchy.push(manager.getDisplayValue('name')); managerSysId = manager.getValue('manager'); } else { break; } } } return hierarchy.join(' >> '); }

- Rollback contexts contain everything necessary to roll back a software upgrade or plugin activation. - They include deleted records, patch updates, Scripts-Background script executions, database actions, and plugin activations. - A rollback context is created for each patch upgrade within a family, and each plugin activation, provided that the plugin supports rollback contexts. - Activate the Restore Deleted Records and Delete Recovery plugins to use rollback contexts.

An incident refers to an unplanned interruption or reduction in the quality of an IT service. Problems, on the other hand, are the root causes of one or more incidents. While incidents focus on restoring service, problem management focuses on finding and resolving the root cause.

UI policies are client-side rules that dynamically control the behavior of form fields, such as making them mandatory, visible, or read-only, based on specific conditions.

It indicates whether this field is the Display values(appears on records that reference this table).

ServiceNow IT Operations Management (ITOM) is a suite of applications designed to manage and optimize IT infrastructure and services. ITOM includes modules for Discovery, Service Mapping, Event Management, and Cloud Management. It provides visibility into IT assets, dependencies, and health, enabling proactive management of infrastructure and services. ITOM helps organizations reduce downtime, improve performance, and optimize resource utilization, supporting efficient and reliable IT operations.

I track all test data I create during testing. Once tests finish, I delete or reset it to avoid clutter and prevent it from affecting production-like scenarios.

ServiceNow integrates with external applications using several methods, enabling seamless data exchange and workflow automation across platforms. Key integration methods include: - Web Services (REST and SOAP): Allows external systems to interact with ServiceNow using standard HTTP methods (GET, POST, etc.). - IntegrationHub: Provides pre-built connectors for easy integration with third-party systems like Slack, AWS, and Microsoft Teams. - MID Server: Bridges communication between ServiceNow and on-premise systems behind firewalls. - Data Imports: Allows importing data from external sources (CSV, JSON, XML) via Import Sets. - Scripted Web Services: Custom APIs for integrations with external systems. - Event Management: Integrates with external systems using message queues to trigger actions or synchronize data. These methods provide flexible, scalable solutions for connecting ServiceNow with external applications. Example: ServiceNow can listen for events from external monitoring tools and trigger incident creation or notifications based on specific thresholds.

I define data, process, and UI isolation needs upfront. Then I configure domain-specific records, roles, and access rules so each domain operates independently without affecting others.

If an incident is registered but you cannot contact the user, you should attempt to resolve the issue based on available information, document your actions, and escalate if necessary.

The impersonation feature in ServiceNow allows administrators to log in as users without a password. This feature is used for testing access settings and settings and can also be used for production purposes.

S – Situation About eight months ago, we began receiving numerous complaints from users across multiple departments about slow performance when accessing and interacting with our ServiceNow instance. Specifically, users reported long load times for incident and change request forms, slow searching within list views, and general sluggishness when navigating between modules. This wasn't isolated to a few users or specific times; it was a pervasive issue impacting daily operations for hundreds of users. The increased wait times were causing frustration, reducing productivity, and sometimes leading to users having to refresh their browsers multiple times, which sometimes meant losing unsaved work. Our internal SLAs for ticket resolution were also being impacted due to the delays in accessing and updating records. T – Task My primary task was to thoroughly investigate these performance complaints, identify the root cause(s) of the performance bottleneck, and implement effective solutions to restore optimal system responsiveness. This was a critical task because pervasive slow performance can erode user trust in the platform and ultimately lead to decreased adoption and dissatisfaction. I needed to act methodically, gather data, analyze it, and apply appropriate technical remedies without causing further disruption. The goal was to significantly reduce form load times and improve overall navigation speed across the platform. A – Action I began by leveraging ServiceNow's built-in diagnostic tools. First, I activated Stats.do and Debug Trace for myself and then for a few affected users to capture detailed performance metrics, including server response times, network latency, and client-side processing. This quickly showed consistently high server response times for specific forms and list views, indicating a server-side bottleneck rather than just client-side or network issues. Next, I delved into the System Diagnostics module, specifically looking at Transaction Log (syslog_transaction ) and Slow Queries (sys_query_history ). I filtered the Transaction Log by duration, focusing on transactions exceeding 5 seconds. This immediately highlighted that loading the incident.do and change_request.do forms, as well as queries on the cmdb_ci table, were consistently among the slowest operations. The Slow Queries log pointed to several complex database queries being executed by specific business rules and related lists on these forms. Further investigation into the identified slow forms revealed a few culprits: - Overly Complex Business Rules: On the Incident form, a business rule was querying multiple related tables ( sys_user ,cmn_location ,task_sla ) ondisplay to dynamically populate user information fields and calculate SLA targets, even when not strictly necessary. This was executing every time the form loaded. - Unoptimized Related Lists: The Change Request form had several related lists displaying information from tables with millions of records (e.g., sys_audit ,workflow_context ). These related lists were loading all records by default instead of using appropriate filters or pagination, leading to massive database queries. - Client Scripts with DOM Manipulation: Some legacy client scripts were performing extensive DOM manipulation on form load, which added to client-side rendering delays. - Inefficient Data Imports: A scheduled daily import for CI data into the cmdb_ci table was taking an excessively long time and locking tables during its execution, contributing to overall system sluggishness. My resolution actions were multi-faceted: - Business Rule Optimization: I refactored the problematic Incident business rule. Instead of querying multiple tables on display , I modified it to useasync business rules where possible, and only fetch data when specific fields were modified or when a user explicitly requested it (e.g., through a UI Action). I also ensured that queries within business rules were using appropriate indices. - Related List Configuration: For the Change Request form, I modified the Configure > Related Lists settings. I changed related lists displaying large datasets to use reference fields or simpler queries, or in cases where historical data was needed, I configured them to load only a limited number of records by default, with an option to "View All." I also ensured appropriate indexes were on the reference fields. - Client Script Review: I audited the client scripts on the slow forms. I identified and deprecated several old client scripts that were performing unnecessary DOM manipulations or making synchronous GlideAjax calls, replacing them with more efficient g_form methods or asynchronous calls. - CMDB Import Optimization: I worked with the team responsible for the CMDB import. We optimized the transform map, added coalesce fields, and implemented a more efficient import set strategy using multiple import sets and smaller batches, which significantly reduced the execution time and prevented table locks during peak hours. - Database Indexing: Based on the Slow Queries log, I identified a few custom tables that were frequently queried without proper indexing. I worked with our database administrator to add appropriate indexes to these tables, which dramatically improved query performance for those specific modules. R – Result The combination of these actions led to a dramatic improvement in ServiceNow performance. Form load times for Incident and Change Requests decreased by an average of 60%, from around 10-15 seconds down to 3-5 seconds. List view searches became near-instantaneous, and general navigation felt significantly snappier. User complaints about slow performance virtually ceased, and feedback shifted to praise for the renewed responsiveness of the platform. Our internal ticket resolution SLAs returned to acceptable levels. The project not only resolved the immediate performance issues but also instilled a stronger culture of performance-aware development and configuration among our team. We now regularly review Slow Queries and Transaction Logs as part of our health check routine, preventing similar issues from recurring and ensuring a consistently fast and reliable ServiceNow experience for all users. This experience solidified my ability to diagnose complex platform issues and implement holistic solutions, rather than just superficial fixes.

JavaScript can be used in ServiceNow through various scripting options, including:

If two records have the same sys_id value, it occurs as a result of the following situations - If a record with the sys_id was copied to the other at the database level outside of the Now Platform. - If a record with the sys_id was copied using an Update Set or via XML, its sys_id is the same.

ServiceNow creates a default application scope for each application. However, developers can create their update set to suit their needs better.

In ServiceNow, Data policies allow you to enforce data by making fields necessary or read-only. Data policies are similar to user interface policies. But UI policies only be applied to data entered on a form using a standard browser, whereas data policies can be applied to any data submitted into the system, including data imported via import sets or web services and mobile user interface. For example, assume you're setting up a web service that lets people from outside the platform update problems in your ServiceNow instance. These problems are not subject to the UI policies on the problem form because they are not changed through the instance UI.

High availability involves designing redundant components, such as servers, networks, and storage, to minimize single points of failure and ensure continuous operation. Fault tolerance includes implementing failover mechanisms, load balancing, and disaster recovery strategies to maintain service availability in the event of failures or disruptions.

An instance is a special platform within a cloud environment. Here individuals can store, manage and access their information. Every individual gets their own copy of an instance in the cloud. These are independent and unique and give a platform for change management, problem resolving and IT service management.

GlideAggregate is a server-side API used to perform aggregate functions like sum, count, average, min, and max on database records. Example query: var ga = new GlideAggregate('incident'); ga.addAggregate('COUNT', 'priority'); ga.query(); while(ga.next()) { gs.info(ga.priority + ': ' + ga.getAggregate('COUNT', 'priority')); }

Domain separation is an effective ServiceNow technique. It aids in the division of data into logically defined areas. It also allows for administration to be separated. For instance, Joseph is the Chairman of two firms, and he uses a single instance of ServiceNow for both. He does not want users from one firm to be able to see data from another. To keep the data from both firms separate, you'll need to employ domain separation.

Access Control in ServiceNow is a security mechanism that restricts access to data based on user roles and permissions. It ensures that only authorized users can view or modify specific records and fields, maintaining data integrity and security.

CMDB baseline is a feature of this platform. It gives the capability of controlling the modifications of configuration items. It is basically a snapshot of a user's CIs in the CMDB. They can review all of the changes made to the CIs since the last baseline.

Scheduled Jobs in ServiceNow are automated tasks that are set to run at specified intervals (e.g., daily, weekly, monthly) or at certain times. These jobs are used to execute scripts or actions in the background, allowing for regular maintenance, reporting, or data processing without manual intervention. Importance: - Automation: Scheduled Jobs allow repetitive tasks to be automated, such as data imports, cleanup tasks, or recurring notifications. - Efficiency: ServiceNow ensures system processes run without requiring active user input, improving overall system efficiency. - Consistency: They ensure that processes are executed consistently on time, reducing human error and ensuring critical tasks are not forgotten. Example: A Scheduled Job might be set to run every night to update records in the CMDB or to send out a daily status report to a specific group.

Q7. Which ServiceNow module supports IT Service Management (ITSM)?

CMDB Baselines will help you, understand and control the changes made to a configuration Item(CI). These Baselines act as a snapshot of a CI. Following steps will help you do the same:

ServiceNow supports various types of scripts, including: - Client Scripts: Run on the client side and manage the behavior of forms and fields. - Business Rules: Server-side scripts that run on record operations (insert, update, delete, query). - UI Actions: Scripts triggered by user interactions with UI elements, such as buttons or links. - Script Includes Reusable server-side scripts that can be called from other scripts. - Workflow Scripts: Scripts that run within workflows to control process logic. Each script type serves a specific purpose and is used to extend and customize the platform's functionality.

Using their username and password

Ensuring security in ServiceNow involves following best practices to protect data, maintain privacy, and control access across the platform. Some key best practices include: - Use roles to restrict access based on the principle of least privilege. - Define permissions at field and table levels for granular access control. - Enable Multi-Factor Authentication (MFA) and Single Sign-On (SSO). - Encrypt sensitive data in transit (HTTPS) and at rest (AES). - Use Business Rules for data integrity and validation during record updates. - Restrict admin privileges and monitor their usage. - Protect external integrations with secure authentication methods like OAuth. - Keep the instance updated with the latest security patches. - Mask sensitive information to prevent unauthorized access. - Enforce separation to prevent conflicts of interest. - Set up responses for fast action on security breaches. - Monitor activities through System Logs and Audit Logs to detect suspicious behavior. These practices help ensure data protection, access control, and overall platform security.

- Archived tables are not optimized for ad hoc queries. - They only contain index entries for the display value, creation date, and the primary key of sys_id. - For this reason, do not make on-demand queries against an archived table, such as searching for all priority 1 archived incidents. - Instead, only search against the indexed fields. - For example, search for incident INC100001 or incidents created on a specific date.

It is used to enhance the system logs. It provides more information on the duration of transactions between the client and the server.

Homepages and content pages don't get added to ‘update sets' by default. You need to manually add pages to the current ‘update sets' by unloading them.

The stage of HR cases when created is typically 'New'.

You can escalate an HR case by changing the priority or assignment group, or by using the escalation feature in the case record.

- Select the check box to enable script objects from other application scopes to read records stored in this table. - This option offers runtime protection. - For example, a script in another application can query data on this table. First select read access to grant any other API record operation.

A Service Catalog in ServiceNow is a collection of services and products offered to users, allowing them to request and manage services through a self-service portal. It streamlines service delivery and improves user experience by automating workflows.

Scheduled Jobs are automated processes that run at specified intervals. They can be set up to run scripts, clean up old records, or perform routine maintenance tasks.

Client script is usually located on the browser and runs only on client-side platforms. Below are important types of Client scripts such as; - On Load () - On Change () - On submit () - On Cell Edit ()

It is a single platform design, and most of the companies use it for 50 different apps that don't interact with each other. ServiceNow handles all of the things, such as IT, HR, Security, and Customer Service, on a single platform. It means everyone can see the same information on same time.

With user session management, an administrator can view and terminate individual user sessions, lock out users from the instance, and make users inactive. User records are also associated with transaction logs. Administrators can use these logs to track all browser activity for an instance.

To create or update an ACL, you need the 'admin' role or the 'security_admin' role.

ACLs define table- or field-level permissions evaluated on the server and client; they run in order and can use scripts to enforce role, condition, and context-based access.

- Select the check box to enable applications from other application scopes to create configuration records for this table that change its functionality. - For example, an application designer can select this table from the Tables list on - business rules, client scripts, or UI actions. - This option offers design-time protection. - Clear the check box to prevent application designers from selecting this table when creating configuration records.

Even for remote roles, dress "business casual." It shows you take the opportunity seriously.

Access Control Rules in ServiceNow are configured to manage permissions for accessing data and performing operations on records. To implement Access Control Rules, navigate to the Access Control module and create a new rule. Define the table, operation (create, read, update, delete), and conditions for the rule. You can use scripts to further refine the conditions based on user roles, group memberships, or other criteria. Access Control Rules help enforce security policies and ensure that users have appropriate access to data.

It's a field where you cannot save the record until you fill it out. This ensures the data stays clean and useful.

Confusion arises because administrators set default views, but users can customize their personal view, leading to different display layouts for the same tables or forms. Users may see additional shortcuts or reordered fields. Admins maintain control over system functionality. Differences are resolved using update sets or profile resets. Proper communication avoids mismatches in workflows. Understanding this distinction helps reduce errors and training gaps.

Scheduled Jobs are tasks that run at specified times, such as nightly or weekly, to perform specific actions within ServiceNow. Import Sets, on the other hand, are tools for importing data from external sources and mapping that data into ServiceNow tables.

The Discovery module in ServiceNow automates the discovery and mapping of IT infrastructure and services across an organization's network. It uses various methods like IP probing, SNMP, WMI, and SSH to identify devices, applications, and their interdependencies. This automation provides crucial visibility into the IT landscape, ensuring accurate configuration management and supporting IT operations and services.

A parent or relationship for updates can be created by a deployment team member who can automatically update it.

The User Registration Request [com. snc.user_registration] plugin allows unregistered users to request access to a ServiceNow instance. An administrator can activate the plugin. A user can request an account by navigating to the instance. The following section is added to the welcome screen if the plugin is installed.

An instance is a specific, private version of the ServiceNow for a company. Most of the companies will have three instances called Dev, which is used for playing around and buildig. The second one is "Test" instance for checking for bugs, and a "Production" instance where the real work take place.

Gauges are visible on the Service Now software home page and this consists of minute information about the current data status or records. This data status record available on the Service now tablets and these Gauges can be used on a data report and put on the Service Now home page.

ServiceNow REST APIs are a set of web services that enable external systems to interact with the platform using the REST (Representational State Transfer) protocol. REST APIs provide a simple, lightweight, and standardized way to create, read, update, and delete records in ServiceNow, as well as perform other operations such as querying, searching, and pagination. REST APIs are widely used for integration with modern web applications and services.

Describe a concrete incident or change you handled, the steps you took, scripts or transforms used, and measurable outcomes like reduced incident reopen rates.

The Service Now integration tool comes with the following significant features:

For any application scope, only one update set can be the default. Set the Default set field to true to make an update and set the default setting. When you set Default set = true, you get the following results:

The schema map displays the details of tables and their relationships in a visual manner Allowing administrators to view and easily access different parts of the database schema. The schema map can also be printed directly from a browser

Users adjust the date format and time zone through their profile settings, affecting how records, timestamps, and notifications are displayed. The change ensures accurate representation of time-sensitive tasks. It is applied across modules including incidents, requests, and tasks. Users can choose local or UTC time based on preference. This supports global teams working across multiple time zones. Proper configuration prevents scheduling conflicts and miscommunication.

The date format of an instance can be changed from the settings provided in the user profile, and this change is reflected in the form.

- A Script Action in ServiceNow is a reusable script that executes specific actions triggered by events or conditions. - These scripts automate tasks, update records, or integrate with external systems, enhancing platform functionality and streamlining workflow processes effectively.

Troubleshooting, communication, stakeholder management, JS basics, platform navigation, workflow understanding, and familiarity with ITIL concepts are essential.

Careful planning, testing, and communication are essential for managing upgrades and migrations smoothly. This involves assessing dependencies, scheduling maintenance windows, performing backups, and communicating with stakeholders to minimize downtime and mitigate risks.

The ServiceNow Knowledge Base centralizes information and solutions for common issues and inquiries. It helps users find answers to questions without contacting support, reducing resolution time. Knowledge articles in ServiceNow can include troubleshooting steps, FAQs, and best practices. It supports self-service by empowering users to resolve issues independently. Knowledge articles can be categorized, tagged, and linked to related records for easy navigation.

ServiceNow uses Role-Based Access Control (RBAC). You assign roles to users or groups and configure Access Control rules (ACLs) on tables and fields. ACLs check user roles and conditions to determine if a user can read, write, or create a record. Administrators often get asked about creating custom roles, assigning them to users, and writing ACL rules. Ensuring users have only the roles necessary for their responsibilities maintains security.

CMDB stands for Configuration Management Database, and the primary purpose of a CMDB baseline is to control and comprehend any modifications made to a configuration item (CI).

ServiceNow's PPM enables organizations to manage and prioritize project portfolios. It provides visibility into project status, resources, and financials. PPM facilitates decision-making based on real-time data and analytics. Project managers use PPM to align projects with business objectives. It streamlines project schedules and the distribution of resources. PPM enhances project governance and ensures strategic alignment.

- A table is a collection of records in the database. - Each record corresponds to a row in a table, and each field on a record corresponds to a column on that table. - The Now Platform uses a table-based data structure to store and organize information. - Pre-built tables are included for common IT service management (ITSM) processes, with their data fully importable and exportable in CSV, XML, or other formats. - Admins can also create custom tables for specific business requirements, define field properties, create relationships between tables, and extend existing tables without modifying the originals.

CMDB stands for Configuration Management Database. It is a repository that stores information about configuration items (CIs) and their relationships within an IT environment. The CMDB helps organizations manage and control their IT assets, services, and infrastructure. It supports ITIL processes such as change management, incident management, and problem management. By providing a single source of truth, the CMDB improves decision-making and service delivery. It is crucial for maintaining IT service continuity and compliance.

If a manager is on long leave, then they can appoint a Delegate. He is a person who will receive the approvals and notifications while they are gone. This won't let the work stop.

An application is a collection of modules that deliver connected data. A change application, for example, gives information on the change process. It includes modules such as create change tickets, view change tickets, etc.

User impersonation in ServiceNow allows an admin or user with the necessary permissions to temporarily assume the identity of another user to troubleshoot, test, or perform actions on their behalf. This feature is useful for several reasons: Troubleshooting: When users report issues, such as not being able to access certain records or perform specific actions, impersonation allows you to experience the issue as if you were the user. This helps to quickly identify and resolve problems. Testing and Validation: You can impersonate a user to test workflows, permissions, or access controls from their perspective. This ensures that configurations like role-based access and security settings are functioning correctly. Service Desk Efficiency: Support teams can impersonate end users to perform tasks like resetting passwords or resolving service requests without needing the user's password. It speeds up issue resolution without compromising security.

Business rules in ServiceNow have an "Order" field. The sequence in which these rules run can be managed using this field. Rules with lower order values run before those with higher values. In cases of conflicts, it's crucial to analyze the business needs, refactor the rules if necessary, and set their order to ensure the desired outcomes.

After a few days, a user can switch back to the admin view and reset to the default view.

The scope has changed from global to local, emphasising the dependency on the application when creating an updated set.

CIs are the components in an IT environment like software, hardware, documentation and employees. Assets are subparts of CIs. These are units of hardware like laptops, servers and networking equipment. CIs are big and consist of assets alongside other IT elements.

Yes, homepages and content pages can be included in update sets in ServiceNow, but homepages must be manually added to the update set. When you create or modify a homepage or content page, the changes can be captured in an update set. However, you need to explicitly select the homepage to include it. This allows you to move these configurations between different instances, such as from development to test or production. Key Points: - Homepages: Customizations to homepages, such as adding widgets or modifying layouts, are included in update sets. - Content Pages: Any changes made to content pages, such as adding new sections or modifying page components, are also included. Make sure that any changes to these pages are committed to an update set before moving them across instances.

ServiceNow's Knowledge Management module is designed to capture, store, and share knowledge within an organization. It provides a centralized repository for knowledge articles, such as how-to guides, FAQs, and troubleshooting steps. The module includes features for creating, categorizing, and publishing articles, as well as managing article versions and feedback. Knowledge Management helps improve service delivery by enabling users to find solutions quickly and reduces the workload on support teams by promoting self-service.

Client scripts run in the browser for UI behavior; business rules run on the server for data integrity—use client scripts for immediate UI validation and business rules for server-side enforcement.

ServiceNow is a powerful cloud-based platform that offers a range of IT service management (ITSM) solutions. It provides a consolidated view of various IT processes, enabling organizations to automate workflows, streamline operations, and enhance service delivery. With ServiceNow, teams can easily manage incidents, change requests, problem tickets, and more. Imagine a large organization with multiple departments. ServiceNow acts as the central nervous system, seamlessly connecting these departments and their respective processes. For instance, if a user encounters a software issue, they can submit an incident ticket through the ServiceNow portal. ServiceNow then assigns the ticket to the appropriate IT technician, who resolves the issue and updates the ticket. This integrated approach ensures efficient and transparent communication across the entire organization.

- The HR Service Delivery module automates HR processes within ServiceNow. - It includes functionalities for employee onboarding, offboarding, and case management. - HR agents use the module to handle employee inquiries and requests. - Integration with HR systems ensures data consistency and accuracy. - HR Service Delivery enhances employee experience through self-service options. - It streamlines HR operations and improves service delivery efficiency.

This module is used to recover deleted records from the servicenow instance. This module works on records in audited tables. Cascaded deleted records must be recovered within seven days of the record deletion. After seven days, only data records and references on tables that audit deletions can be recovered, which is the same functionality as prior releases

ServiceNow tables can be categorized into three main types: Core Tables, which store fundamental platform data like users and groups; Extended Tables, which extend core tables with custom fields or business logic; and Custom Tables, created by administrators to store specific data unique to an organization's needs. Each table type supports different functionalities and customization options within the ServiceNow platform.

- REST APIs in ServiceNow are created using the API Explorer. - Define the API endpoint and HTTP methods (GET, POST, PUT, DELETE). - Secure the API by setting authentication and access controls. - Document API functionalities and parameters for user reference. - To make sure the API is functional, test it with programs like Postman. - REST APIs enable integration with external systems and data exchange.

The ServiceNow Flow Designer enables the visual orchestration of processes and automation. Users can create flows by dragging and connecting predefined actions and integrations. Flows automate tasks across applications and modules without writing traditional code. It supports conditional logic, loops, and error handling for complex workflows. The Flow Designer simplifies and accelerates automation efforts in ServiceNow.

An incident is a kind of interruption that's unplanned. When the internet slow down, or your printer doesn't work, it is an incident. The goal of Incident Management is to get things back to normal as fast as possible.

The process of implementing custom workflows in ServiceNow involves the following steps:

ServiceNow Service Catalog Items are predefined services or products available to users via the Service Catalog. They represent IT or business services users can request, such as software installations, equipment provisioning, or service requests. Each catalog item includes details like description, fulfillment processes, costs, and approval workflows. Service Catalog Items streamline service delivery, enhance user experience, and improve service request management efficiency.

The field type is selected, and the user can add values to the field using a dictionary or by configuring choices. There are two ways to add choices: create a new choice, save and submit, or create multiple options.

- In ServiceNow, the "GlideRecord" API is used to perform database operations, including looking up records. - It provides methods to query, insert, update, and delete records from the ServiceNow database. - Using GlideRecord, developers can write scripts to search for records based on specified criteria. - This API is essential for server-side scripting and automating processes. It makes efficient data modification and retrieval possible. GlideRecord is widely used in business rules, scheduled jobs, and workflows.

Users often work with string and 80 fields, and Spring fields can be used for choice or reference fields for data-related items. Examples include date, date time, integer, and currency fields.

With dictionary override, a field on an extended table can be defined in a distinct manner from the field of the parent table. Many different aspects can be overridden. These include -

Users with admin or imposter roles can temporarily assume the identity of another authenticated user for testing purposes. Knowing another user's password is not required for impersonation. The admin user can precisely view what the impersonated user can see and do when impersonating another user. This functionality is helpful for testing. Instead of logging out of your session and logging back in with the user credentials, you can mimic that user and test.

To improve the quality of registered incidents, you can provide training to users, implement mandatory fields, and use templates or categories to ensure consistent data entry.

The Automated Test Framework (ATF) is a ServiceNow feature that creates and runs automated tests. It lets you record test steps, such as setting field values and clicking buttons and assertions, in a web-based interface. ATF is used for regression testing, especially before and after upgrades or significant changes. In an interview, you might be asked how you'd use ATF — for example, creating a test for a new catalogue item or validating that a workflow creates the expected records.

In Business Rules, scratchpad is a temporary storage for data that can be passed between different stages of a business rule. In Workflow, scratchpad is used to store temporary data that can be passed between activities.

It's the "Home Base" for anyone learning the platform. It's where you get your free instance, take free classes, and find API documentation.

In ServiceNow, tables are categorized into several types based on their purpose and function within the platform. The main types of tables include: - Base Tables: These are the core tables provided by ServiceNow for managing IT service management (ITSM) processes. Base tables define the structure for common processes and are extended to create custom tables. - Extended Tables: These are tables that inherit fields and properties from a base table. Custom tables are often created by extending a base table. For example, the Incident table can be extended to create a specialized Security Incident table. - Custom Tables: These are user-defined tables that are created to store specific data unique to an organization's needs. Custom tables do not extend a base table and are created using the Table module in ServiceNow. - System Tables: These tables store essential system data and configurations, such as sys_user (users), sys_dictionary (table schema), and sys_metadata (system configurations). System tables manage metadata and platform settings. - Junction Tables: These are many-to-many relationship tables used to link other tables. For example, a Task Assignment table might act as a junction table linking tasks and users. - Task Tables: These tables are used for managing tasks across various processes. Incident, Change Request, and Problem are examples of task tables. Task tables are often extended by other process-specific tables. - Reference Tables: These tables store data that is referenced by other tables. For example, the cmdb_ci table stores configuration items (CIs), and other tables, such as Incident, can reference these CIs. In short, ServiceNow tables are categorized as base, extended, custom, system, junction, task, and reference tables, depending on their purpose and how they relate to other tables in the platform.

I would go to the Discovery Schedules module. Then, I would create a new schedule, define the IP ranges, and select the MID server. I would set the run frequency (e.g., daily or weekly) and choose the applicable credentials. Finally, I would save and activate the schedule so Discovery runs automatically at the defined times.

ESS, or "End-User Self-Service", is a default role in ServiceNow which enables users to create, edit, and update their own incidents or service requests but restricts them from accessing other records or performing administrative functions.

As is clear with their names, deleteRecord() will delete a single record whereas deleteMultiple() will delete various records at once.

A Client Script runs in the user's browser on a form. An onLoad Client Script triggers when the form loads, for example, to hide fields or set default values. An onChange script runs when a specific field changes, for example, updating another field when one is modified. You could use an onLoad script to auto-populate the Caller field on an incident and an onChange script to recalculate the total cost when the user changes the Quantity field.

To write a Business Rule that sets the priority of an incident to 'High' if the impact is '1 - Critical', navigate to the 'Business Rules' module, create a new rule, and define the conditions and actions. Use the following script: if (current.impact == '1 - Critical') { current.priority = 'High'; }

To call an external REST API, create an Outbound REST Message in ServiceNow. In the message definition, specify the endpoint URL and HTTP methods. In your script, you can use RESTMessageV2() or sn_ws.RESTMessageV2(), set any required headers or parameters, and execute the call. Handle authentication (OAuth, Basic Auth) as needed. For example: var rm = new sn_ws.RESTMessageV2(); rm.setHttpMethod('GET'); rm.setEndpoint('https://api.example.com/data'); var response = rm.execute(); var responseBody = response.getBody(); Note: Interviewers may ask about handling authentication or parsing JSON responses.

CMDB baselines capture snapshots of CIs at specific times. I schedule them regularly, then compare snapshots to track unauthorized changes or investigate issues.

ServiceNow is a cloud-based platform for IT service management, workflow automation, and business process optimization. It works by storing data in tables and using applications to process and display that data. Users interact through forms, lists, and dashboards, while automation tools handle tasks, notifications, and approvals.

This task can be achieved by using the function autoSysFields() from server-side scripting as shown below - var gr = new GlideRecord('incident'); gr.query(); if(gr.next()){ gr.autoSysFields(false); short_description = 'Test from igmGuru'; gr.update(); }

To perform an upgrade in ServiceNow, first review the release notes for new features and changes. Back up your instance and ensure you have a current update set. Navigate to "System Diagnostics" and select "Upgrade Center." Follow the prompts to download and apply the upgrade package. Thoroughly test the instance post-upgrade to identify any issues. Use the "Upgrade History" module to track progress and resolve conflicts.

A data policy is a set of rules that enforce data consistency and integrity at the database level. It defines mandatory fields, read-only fields, and other constraints to ensure data quality.

Applications in ServiceNow represent packaged solutions for delivering services and managing corporate processes. Simply put, it is a collection of modules that provide information on those modules. The Incident application, for example, will provide information on the Incident Management process.

I would typically use the Service Catalog, Request Management, and Knowledge Management modules. They help guide requests from submission to completion.

A Record Producer is a special type of Service Catalogue item that allows end-users to create task-based records in a user-friendly way.

The ServiceNow upgrade process involves the following steps:

ServiceNow certification validates an individual's expertise in using and administering the platform, enhancing career opportunities and ensuring proficiency in best practices for implementation and management.

A change request is an official proposal to modify the IT environment, which usually requires risk assessment and approval. For example, deploying new server software. A Service Request is a request for a standard service that is often pre-approved, such as ordering a new laptop or resetting a password. Service Requests are fulfilled via the Service Catalog, which includes predefined workflows. Change Requests undergo the Change Management process with greater scrutiny.

Use GlideAggregate to group by category and count incidents. var ga = new GlideAggregate('incident'); ga.addAggregate('COUNT', 'category'); ga.groupBy('category'); ga.query(); while (ga.next()) { gs.info(ga.getDisplayValue('category') + ': ' + ga.getAggregate('COUNT', 'category')); }

Here's how record matching and data lookup works: Record Matching: When creating a new incident, ServiceNow checks if there's already an existing incident with similar details (e.g., same short description or affected user) to avoid duplicate records. For instance, if you report an issue with a printer, the system might automatically find a matching record if another user has reported a similar problem. This helps in streamlining incident management by preventing redundant records. Data Lookup: In the Service Catalog, when a user selects a specific item like a laptop, ServiceNow can use data lookup to automatically fill in related details. This eliminates the need for manual data entry, reduces errors, and ensures that all relevant data is consistent across records. These features help improve efficiency, accuracy, and consistency across ServiceNow processes.

There are two types of impersonations available: Impersonation logging for interactive sessions: Interactive sessions are performed through the user interface (UI). Impersonation logging for non-interactive sessions: Non-interactive sessions are performed by applications and scripts, not through the UI.

To work on repetitive incidents, you should identify the root cause, create a problem record, and implement a permanent fix or workaround.

- Database views cannot be created on tables that participate in table rotation. - It is not possible to edit data in the database view output. - Database view tables cannot be added as a data preserver in clone requests - You can still create additional ACLs on the database views. These ACLs are evaluated last and are always honoured.