Top ServiceNow Administrator Interview Questions | SPOTO

Applications in ServiceNow represent packaged solutions for delivering services and managing business processes. In simple words it is a group of modules which provides information related to those modules. For example Incident application will provide information related to Incident Management process.

- Tables created by servicenow in the now platform. - Examples- incident, problem, task,cmdb_ci etc - admins can't delete these tables.

- For a table in a scoped application, the name is prefixed with a namespace identifier to indicate that it is part of an application. - For a table in the global application, the name is prefixed with the string u_ - For a remote table in a scoped application, the name is prefixed with a namespace identifier and the string st_ to indicate that it is remote and part of an application. - For a remote table in the global application, the name is prefixed with the string u_st_ - You cannot modify the prefix; however, you can modify the rest of the table name. - The name can contain only lowercase, alphanumeric ASCII characters and underscores (_).

In ServiceNow, the method next() helps to move the record to next within the GlideRecord. The method _next() also has similar features as next(), but it is only valid when we query a table with a column name "next".

To create a Service Catalog in ServiceNow, follow these steps: - Define catalog items: Identify the services you want to offer and create catalog items for each service. Catalog items can represent tasks, requests, or offerings. - Design the catalog: Organize catalog items into categories and subcategories to improve navigation and user experience. - Configure variables: If your catalog items require user input, define variables to capture the necessary information. Variables can be dropdown lists, checkboxes, text fields, etc. - Create workflows: Establish workflows that govern the approval, fulfillment, and tracking of catalog requests. - Publish the catalog: Once configured, publish the Service Catalog so that users can access and request services. Benefits of the Service Catalog: - Streamlined Service Request: The Service Catalog allows users to browse and request services easily, reducing the need for manual requests and improving efficiency. - Standardization: By defining clear catalog items and associated workflows, organizations can standardize service delivery processes and ensure consistent experiences for users. - Self-Service: The Service Catalog promotes self-service, enabling users to find and request services independently, reducing dependency on IT personnel, and freeing up resources. - Transparency and Tracking: The catalog provides transparency into the status of service requests, allowing users to track the progress of their requests and stay informed.

HTML sanitizer is mainly used to clean the Hypertext transfer protocol markup data in HTML fields and is also used to eliminate suspicious errors. This also defends the security process like cross site scripting attacks. This HTML also active for all the data instances starting from Eureka releases.

A table can be made audited by checking the 'Audit' checkbox in the table's dictionary entry. Auditing is the process of tracking changes to records in a table, including who made the change, what was changed, and when.

ServiceNow is a cloud-based ITSM tool that allows users to define views of different arrangements of fields on forms and lists. Access control lists (ACLs) define the data a user can access and how they can access it. Applications in ServiceNow are groups of modules that provide related information for processes like change management.

- ServiceNow's Knowledge Management module is designed to capture, store, and share information within an organization. - Users can create and manage knowledge articles, making it easy to find solutions to common problems. - It supports multiple knowledge bases with controlled access, ensuring the right people have the correct information. - The module enhances efficiency by reducing the need for repetitive inquiries.

An update set in ServiceNow is a collection of customizations that can be transferred from one instance to another. Update sets are used to move customizations between development, testing, and production environments, ensuring a consistent and controlled deployment process.

- A Catalog Item in ServiceNow represents a requestable service or product available in the Service Catalog. - Define Catalog Items with details such as description, category, and pricing. - Specify fulfillment details, including assignment groups and workflows. - Use variables to customize options available to users when requesting the item. - Test Catalog Items to ensure functionality and user experience.

ServiceNow offers three types of Client Scripts: onLoad, onChange, and onSubmit. OnLoad scripts run when a form is loaded, which is useful for initializing variables or making UI adjustments. OnChange scripts trigger when a field value changes, allowing dynamic updates or validations. OnSubmit scripts execute when a form is submitted, which is ideal for final validations or actions before saving data.

The CMDB is a fundamental component of ServiceNow, serving as a centralized repository for storing information about configuration items (CIs). CIs can be hardware, software, network devices, or any other item that is part of the IT infrastructure. Imagine a scenario where a critical server fails unexpectedly. By referring to the CMDB, ServiceNow can quickly identify the affected server, the applications relying on it, and the users impacted. This allows IT teams to respond swiftly, minimizing downtime and ensuring smooth business operations.

Traverse cmdb_rel_ci recursively. function getCIParents(ciSysId, level) { if (level <= 0) return; var gr = new GlideRecord('cmdb_rel_ci'); gr.addQuery('child', ciSysId); gr.query(); while (gr.next()) { var parentSysId = gr.getValue('parent'); gs.info('Parent: ' + parentSysId); getCIParents(parentSysId, level - 1); } }

A Business Rule is a server-side script that runs when records are inserted, updated, deleted, or queried. Business Rules enforce data consistency or trigger actions like automatically setting fields, sending notifications, or preventing specific actions. For example, a Business Rule might set an incident's priority based on the affected service. Business Rules can run Before (before saving), After (after saving), Async (asynchronously after the transaction), or on Display (when a record is displayed). Before rules are used for field validations, while after rules are used for related record updates.

Creating a Custom Application in ServiceNow involves several steps: defining the application's scope, creating tables and fields, designing the user interface, and developing business logic. Developers use ServiceNow Studio to build and manage custom applications, utilizing tools like Form Designer, List Designer, and Flow Designer. Application files, such as scripts, workflows, and UI components, are created and organized within the application scope. Testing and debugging ensure the application's functionality and performance before deployment.

Workflow and Flow Designer in ServiceNow are both tools used for automating processes, but they have distinct differences in terms of design, functionality, and use cases. Key Differences: Aspect | Workflow | Flow Designer | | User Interface | Older, complex UI with drag-and-drop elements. | Modern, low-code interface for easy design. | | Design Focus | Automates task-based workflows (e.g., approvals). | Automates cross-platform processes with integrations. | | Ease of Use | More complex, requires technical expertise. | User-friendly for both developers and non-developers. | | Customization | High customization but requires manual coding. | Focuses on out-of-the-box integrations with less coding. | | Use Cases | Task automation, like approval chains. | End-to-end process automation and service orchestration. | | Integration | Limited external integrations. | Easy integration with third-party applications. | | Execution | Tasks triggered by record changes. | Flexible triggers based on various business events. |

Users can change the date format and time zone for any record through the settings in their user profile.

We can use the addNotNullQuery function to perform this operation as shown below - addNotNullQuery('name');

Listen For: Most resources have experience with the core ITSM apps so listen for things like Discovery, Orchestration, Project & Portfolio Suite, Service Mapping, Human Resources & Performance Analytics. Make a list of each application they mention for follow up later.

Prioritize tasks based on factors such as urgency, impact, and dependencies, using techniques like Eisenhower's Urgent/Important Principle or Kanban boards. Regularly review and adjust priorities as needed, communicate expectations with stakeholders, and delegate tasks when appropriate to ensure timely delivery and effective workload management.

The HTML Sanitizer is a tool that cleans up HTML markup in HTML fields, removes unwanted code, and protects against security threats, including cross-site scripting. The HTML sanitizer is enabled for all instances. The HTML sanitizer works by looking for markup that you always want to keep in the built-in inclusion list. Administrators can edit the built-in inclusion list using the HTMLSanitizerConfig script included by the sanitizer. To eliminate HTML markup, items can also be put on the exclusion list. The exclusion list's contents take precedence over the inclusion list's contents.

Updating existing records and creating new ones based on a primary key, such as a product name, is suggested to avoid creating duplicate records.

To write a simple Client Script to display an alert when a form is submitted, navigate to the 'Client Scripts' module, create a new script, and select the form. Use the 'onSubmit' function to trigger the alert with the following code: function onSubmit() { alert('Form submitted!'); return true; }

The latest version of ServiceNow Admin is named after cities such as Jakarta, Orlando, Paris, and Cuba. The latest versions are Q Back, Q B, and C.

Client-side and server-side scripting in ServiceNow differ in where the scripts run, the type of tasks they handle, and how they interact with the platform. Key Differences: Aspect | Client-Side Scripting | Server-Side Scripting | | Execution Location | Runs in the user's browser (client) | Runs on the ServiceNow server | | Languages | JavaScript (UI Scripts, Client Scripts) | JavaScript (Business Rules, Script Includes) | | Purpose | Handles user interface interactions and form behavior, such as field visibility, validation, or dynamic content updates. | Manages business logic, data processing, and interactions with the database. | | Performance | Affects user experience; executes on the client side, so it's faster for UI changes. | More suited for handling large-scale data operations and complex logic. | | Data Access | Cannot directly access the database; interacts with the server using GlideAjax for server-side calls. | Directly interacts with the ServiceNow database using GlideRecord. | | Example Use Case | Hiding or showing fields based on user input. | Querying records, updating data, or sending notifications. |

An SLA is a timer. If a "High Priority" ticket isn't solved in 4 hours, then the SLA "breaches" and turns red. Also, this can help the admins to make sure that the team is meeting its goals.

Domain Separation allows for multiple tenants or 'domains' to exist in a single instance of ServiceNow, ensuring that each domain's data, processes, and configurations are isolated.

- 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

ITSM stands for IT Service Management – a set of practices for delivering IT services effectively. ServiceNow supports ITSM by providing applications for incidents, problems, changes, service catalogues, and more, all aligned with ITIL's best practices. ServiceNow ITSM modules automate workflows such as incident escalation, change approvals, and service request fulfillment using predefined rules and intelligent routing. This streamlines processes, reduces manual effort, and accelerates resolution times. The CMDB underpins ITSM by tracking configuration items and their relationships, enabling more intelligent decisions and improving overall service delivery efficiency.

The Service Catalog is a module in ServiceNow that allows users to request IT services, hardware, software, and other services. It provides a user-friendly interface, streamlining the request process and ensuring IT can track and fulfill them effectively.

Each update set is stored in the Update Set [sys_update_set] table. The customizations that are associated with the update set, are stored in [sys_update_xml] table.

ServiceNow Performance Analytics is a simple-to-use integrated application and a process optimization tool. It allows users to build management dashboards, resolve complex business queries, etc. It helps improve the quality of Service provided to the users by reducing costs.

Access Control Rules (ACLs) in ServiceNow define permissions and control access to records and fields in the platform. They ensure that only authorized users or groups can view, create, update, or delete specific records. Example: An ACL might be configured to allow only users with the admin role to delete records in the incident table, while allowing all users to read incidents.

In ServiceNow, data exports can be performed using the "Export to PDF," "Export to Excel," or "Export to CSV" options available in lists and reports. Users can customize the export format and content based on their requirements. Scheduled exports can be set up using Scheduled Data Exports to run at specified intervals. Data exports can include filtered records, specific fields, or aggregated data based on user-defined criteria. Exported files can be downloaded or shared with stakeholders for further analysis or reporting.

I would open the Incident workflow in the Workflow Editor. Then, I would insert an Approval activity before the resolution stage. The approval table would be set to the required group or manager. Once approved, the workflow would continue. If rejected, it would return to the assigned group.

Business rule is a server side script. It executes each time a record is inserted, updated, deleted, displayed or queried. The key thing to note while creating a business rule is, when and on what action it has to be executed. The business can be run or executed for following states

I start with stakeholder interviews, workshops, and process walkthroughs. I document needs, pain points, and priorities clearly for both business and technical teams.

Dictionary overrides in ServiceNow allow administrators to customize field properties for a specific extended table without altering the parent table's dictionary entry. They enable field-level control and flexibility in child tables. Overrides can modify attributes like default value, mandatory status, read-only status, and choice list. This feature supports the inheritance model by ensuring specific requirements of extended tables are met. It helps maintain the consistency and relevance of data fields across different table extensions.

This monitor triggers when a task remains inactive for a specific time. Here an event is activated for a task record called an inactivity monitor.

There are several types of searches available in ServiceNow including lists, global text search, knowledge base, and navigation filters.

Implementing CMDB gives many benefits including -

To create a custom application in ServiceNow, follow these steps:

Your adaptability in fluctuating business environments is crucial. Use an example to illustrate your flexibility and willingness to learn while integrating best practices or update sets within ServiceNow's cloud-based platform.

To automate user onboarding and offboarding in ServiceNow, follow these steps:

S – Situation Last quarter, our organization experienced a major disruption to our primary customer service portal, which is built entirely on the ServiceNow Service Portal. At approximately 10:30 AM on a Tuesday, users began reporting that they could not submit new cases or access their existing case records through the portal. They were encountering a generic "An error occurred" message upon submission or when trying to load specific pages. This was a critical P1 incident because our customer service operations heavily rely on the portal for all inbound requests and customer communication. The inability for customers to log issues directly or check on the status of their requests meant our support agents were immediately overwhelmed with phone calls and emails, leading to significantly increased call hold times and potential SLA breaches for critical customer issues. The financial impact of this downtime was substantial, as it directly affected our ability to service paying customers and process new requests, halting key business operations. T – Task My immediate task as the primary ServiceNow Administrator was to identify the root cause of the portal malfunction and restore full service as quickly as possible. This involved rapidly diagnosing the technical issue, communicating effectively with stakeholders, and implementing a solution under high pressure. The objective was not just to fix the immediate problem but also to minimize customer impact, prevent data loss, and ensure a stable environment going forward. I was expected to lead the technical resolution, coordinating with our development team if custom code was involved, and providing regular updates to senior management and the incident commander. The clock was ticking, with every minute of downtime directly correlating to lost productivity and customer dissatisfaction. A – Action Upon being alerted to the P1, I immediately logged into our ServiceNow instance and navigated to the Service Portal configuration. My first step was to check the system logs in syslog for any recent errors or warnings related to the portal or associated business rules, script includes, or UI pages. I filtered the logs by recent events and searched for keywords like "error," "failed," and the portal's specific scope. I noticed a recurring JavaScript error specifically pointing to a widget responsible for rendering the case submission form. Simultaneously, I opened a separate tab to Active Transactions to see if any long-running queries or processes were hogging resources, which could also lead to unresponsiveness. I then used the "Impersonate User" feature to experience the issue firsthand, confirming the exact behavior reported by users. I opened the browser's developer console while impersonating a user on the portal to capture client-side errors, which further confirmed the JavaScript error within a specific custom widget. Reviewing recent changes, I checked the sys_update_set table for any recently committed update sets that might have introduced the faulty code. I found an update set deployed just an hour before the incident, which included changes to the "Customer Case Submission" widget and an associated Script Include. Collaborating closely with the development team member who deployed the update set, we quickly identified a syntax error in a newly added function within the Script Include, which was being called by the widget. This error was causing the entire widget to fail rendering, thus preventing form submission. We discussed the fastest rollback strategy. Given the critical nature, we decided the quickest and safest approach was to revert the problematic update set. I prepared a rollback of the specific update set in a non-production environment first for a quick test, ensuring no further dependencies were broken. Once confirmed, I executed the rollback in production using the "Revert" UI action on the update set record. While the rollback was processing, I actively communicated with the incident manager, providing updates on my diagnosis and the planned resolution. I also monitored the system performance metrics in the System Diagnostics module to ensure stability throughout the process. After the rollback was complete, I re-tested the portal functionality by impersonating a user and successfully submitted a test case. I then asked a few key stakeholders and frontline support agents to verify the fix as well. R – Result The problematic update set was successfully reverted, and the ServiceNow Service Portal functionality was fully restored within 45 minutes of the P1 incident being declared. Our customer service team was able to resume normal operations, and the backlog of phone calls quickly diminished. The prompt resolution prevented further escalation of customer dissatisfaction and avoided potential SLA breaches. Post-incident, I documented the root cause, the resolution steps, and recommended an enhancement to our change management process to include a more robust automated testing phase for critical Service Portal widgets before production deployment, especially for those affecting core business functions. We implemented a new pre-deployment checklist for developers focusing on client-side script validation and server-side log monitoring post-deployment. This experience significantly improved our incident response playbook and highlighted the importance of a meticulous update set review process, specifically for changes impacting user-facing portals.

I break down each requirement into process steps. Then I align them with existing ServiceNow modules or design custom workflows if needed.

Developers work in separate teams to promote changes to the high environment, which are tested and advanced to the UAT or stage environment. Once the test team approves, the development is promoted to the live environment.

A ServiceNow Business Analyst gathers requirements and translates them into actionable configurations. They are also required to create user stories, process diagrams, or wireframes to clarify requirements. They conduct workshops with stakeholders to understand needs like approval processes or custom reports) and document functional specifications. For example, a BA might interview HR to map out their onboarding process and then design the corresponding ServiceNow flow.

The nobody role means that nobody has access, not even admin, or maint users. Warning: Applying the nobody role may be irreversible if applied to some important system functions.

A Scheduled Job in ServiceNow is a background task that runs at specified intervals or times to perform automated actions. To create a Scheduled Job, navigate to the Scheduled Jobs module and click "New." Define the job properties, such as name, schedule, and script. The script defines the actions to be performed by the job, such as updating records, sending notifications, or running reports. Scheduled Jobs help automate repetitive tasks and ensure timely execution of important processes.

It's usually for companies with 500+ employees.

Coalesce in Service Now is a feature of a data field used to the transmission map fields. These map fields are later used for mapping and enable us to use them as a unique key. Suppose if any of the matches are using the Coalesce filed, then automatically record will be updated and imported. If you can't able to find the Coalesce field, then the new data field will be inserted into the database table.

Access control involves defining policies, roles, and permissions to restrict access to sensitive resources and data based on user roles and responsibilities. Usage of principles such as the principle of least privilege and implement authentication mechanisms like multi-factor authentication to ensure security and compliance with access control policies.

Instead of creating scripts, we may use the record matching and data lookup functionalities to set a field value depending on the given criteria.

Notifications in ServiceNow include email notifications, SMS notifications, and push notifications. These can be configured to trigger based on specific conditions and events within the platform, ensuring timely communication and updates.

Follow a structured approach that includes evaluating the importance and impact of updates, testing in a controlled environment, scheduling maintenance windows to minimize disruption, and implementing rollback procedures in case of issues.

S – Situation Approximately a year ago, our organization underwent a significant restructuring of its sales and marketing departments. This led to numerous employees changing roles, departments, or even moving to entirely new teams. Simultaneously, we were preparing for an upcoming external compliance audit (SOX, specifically) that required stringent controls over data access, particularly concerning customer financial information and marketing campaign data stored within our custom CRM module built on ServiceNow. The existing access control setup was somewhat decentralized, with various managers granting roles without a fully standardized or documented process, leading to a complex web of permissions that was difficult to audit or even understand at a glance. There was a significant risk of over-provisioning access, creating potential security vulnerabilities and non-compliance issues. T – Task My primary task was to review and rationalize the existing user access, roles, and permissions within ServiceNow for the newly restructured sales and marketing teams, ensuring least privilege access and strict adherence to internal security policies and external compliance requirements (SOX). This involved a complete audit of current access, identifying and revoking unnecessary permissions, standardizing role assignments, and documenting the entire process. The goal was to establish a robust, auditable access control framework that could scale with future organizational changes while maintaining operational efficiency. I needed to ensure that no user had more access than absolutely required for their job function, especially concerning sensitive data. A – Action I began by initiating a comprehensive audit of all existing users, roles, and ACLs (Access Control Lists) within the ServiceNow instance, specifically focusing on the custom CRM module. I utilized the "User Administration" module to export lists of users and their assigned roles. I then cross-referenced these with the new organizational chart and job descriptions provided by HR for the restructured teams. This initial review immediately highlighted several instances where users retained roles from their previous positions or had been granted broad, administrative roles unnecessarily. My next step was to create a standardized role matrix in collaboration with the department managers. For each new role (e.g., "Sales Rep Tier 1," "Marketing Campaign Manager," "Sales Operations Analyst"), we defined the precise data access and functional capabilities required. This involved detailed discussions about which tables, fields, and even specific record types each role needed to interact with. For instance, a "Sales Rep Tier 1" only needed read access to certain financial fields on customer records but full write access to their own opportunities. Once the role matrix was approved, I began the process of cleaning up and reassigning roles. I primarily focused on: - Revoking Unnecessary Roles: For users identified with over-provisioned access, I systematically removed redundant or unauthorized roles. Before revoking, I would always check the sys_user_has_role table and cross-reference with their current job function to confirm. - Implementing Custom Roles: Where out-of-the-box roles were too broad or too restrictive, I created new custom roles with specific permissions, ensuring they followed the principle of least privilege. For example, instead of granting itil to a user who only needed to see certain incidents, I created a custom roleu_sales_incident_viewer with specific read ACLs. - Refining ACLs: I reviewed existing ACLs on the custom CRM tables. Many were too permissive (e.g., allowing write access based on a broad role). I refined these ACLs to be more granular, often using field-level ACLs or condition-based ACLs (e.g.,gs.getUser().isMemberOf('Sales Management') ). This ensured that even if a user somehow obtained a broader role, the ACLs would still restrict their access to sensitive data unless explicitly permitted. I used theDebug Security module extensively to test the efficacy of these new ACLs, impersonating various users to verify their access was correct and restricted as intended. - Implementing Automated Role Assignment: To prevent future drift, I worked with HR to integrate role assignments with our Active Directory groups. For critical roles, I configured user criteria for specific departments or groups within our HR system, allowing for automated role provisioning/de-provisioning when a user's department or group changed, reducing manual intervention and error. - Documentation: I meticulously documented every role, its purpose, the associated permissions, and the corresponding AD group mapping. This documentation was stored in a knowledge article within ServiceNow and became the standard for future access requests. R – Result The comprehensive review and restructuring of user access in ServiceNow for the sales and marketing teams were highly successful. We successfully transitioned over 300 users to their new roles with appropriate, least-privilege access within a three-week timeframe, minimizing disruption to their day-to-day operations. The compliance audit passed with flying colors, specifically highlighting our improved access control mechanisms and detailed documentation as a best practice. The risk of unauthorized data access was significantly reduced, and our security posture improved dramatically. Furthermore, the new standardized role matrix and automated assignment processes streamlined future onboarding and offboarding, reducing the administrative burden on IT by approximately 20% and ensuring consistent application of security policies. This project not only met the compliance requirements but also built a foundation for a more secure and manageable ServiceNow environment.

- A UI Macro in ServiceNow is a reusable script that renders UI components on forms, lists, and UI pages. - It helps standardize UI elements across the platform and promote reusability. UI Macros can include scripts, HTML, and references to other macros or UI elements. - They are managed through the UI Macros module in ServiceNow. UI Macros simplify UI customization and enhance user experience by providing consistent UI elements.

Business rules are scripts built on JavaScript. These scripts enforce the business policies and into the In this cloud-based platform. It is also automated, which executes in case the developer modifies, omits, queries or displays any record.

The skills field is used to specify the skills required to handle an HR case.

UI Policies run on the client side in the user's browser and change form behaviour, such as showing or hiding fields based on conditions. Data Policies run on the server side and ensure data integrity by enforcing conditions during data import and in scripts. For example, a UI Policy can be used to hide a field on the Incident form for specific categories, and a Data Policy can be used to require a field even if the form is bypassed.

ServiceNow Virtual Agent is an AI-powered chatbot that provides automated, conversational support to users. It helps reduce the workload on service desks by handling routine inquiries, performing common tasks, and guiding users through troubleshooting steps. Virtual Agent integrates with ServiceNow applications and external systems, enhancing user experience with 24/7 support. It supports natural language processing (NLP) for understanding user intents and provides personalized responses, improving efficiency and user satisfaction.

There are mainly five types of Search options available in the service now tool; - Lists search -> this type of lists search is used to find the records. - Global text search -> this type of search option is used to hold the multiple data records and task tables in a single search field. - Knowledge base Search -> this option search helps users to find any knowledge of business articles. - Navigation filter search -> this option allows the user to filter the application navigator. - Search scenes -> this is a custom module search type created only by the service desk administrator.

In ServiceNow, the _next() and next() methods are used to iterate through records in a GlideRecord query, but they serve different purposes. - next(): The next() method is used to move to the next record in the result set when iterating through records. It returns true if there is another record, allowing you to continue looping, and false if you've reached the end of the results. Example: var gr = new GlideRecord('incident'); gr.query(); while (gr.next()) { // Process each incident record } - _next(): The _next() method is internal to the GlideRecord class and typically not used directly in regular scripting. It's used by the next() method in the background when ServiceNow is processing a GlideRecord object. _next() works similarly to next() but is generally hidden from standard scripting.

When impersonating, I make sure to only do it in non-production if possible. I note the start and end time, use it briefly, and document actions taken. I avoid making irreversible changes unless necessary and stop impersonation as soon as testing is done.

Tables can be related to each other in the following ways - Extensions: A table can extend another table. - One-to-Many: There are 3 types of one-to-many relationship fields - Reference Field: allows a user to select a record on a table defined by the reference field. - Glide List: allows a user to select multiple records on a table defined by the glide list - Document ID Field: allows a user to select a record on any table in the instance. - Many-to-Many: Two tables can have a bi-directional relationship so that the related records are visible from both tables in a related list. - Database views: Database views enable virtual joining of two tables to report on data that might be stored in more than one table.

- GlideAjax in ServiceNow is a server-side API used for asynchronous communication between client scripts and server-side scripts. - It enables client scripts to call server-side scripts without reloading the entire page. - GlideAjax requests are sent asynchronously, allowing the user to continue interacting with the interface. - It helps in performing server-side operations like database queries or updates based on client-side actions.

ServiceNow's Visual Task Board visualizes tasks and their statuses, facilitating task management and tracking. Users can drag and drop tasks across customizable columns (like To Do, In Progress, Done) to update their status. It provides a clear, real-time overview of task progress, improves team collaboration, and enhances workflow efficiency by simplifying task assignment, prioritization, and monitoring.

- A GlideRecord is a JavaScript class in ServiceNow used for database operations. - It enables developers to work with tables in CRUD (Create, Read, Update, Delete) fashion. - GlideRecord provides methods to query, insert, update, and delete records programmatically. - It simplifies interaction with the ServiceNow database using script logic. - Developers use GlideRecord in server-side scripts like Business Rules and Script Includes. It's a powerful tool for manipulating data within the platform.

- The ServiceNow Mobile App allows users to access ServiceNow functionalities on mobile devices. - Users can view, update, and create records, incidents, and tasks directly from their mobile devices. - It supports push notifications for alerts and updates. The app provides offline capabilities, allowing users to work without an internet connection and sync data later. - Users can access the ServiceNow Mobile App from app shops, enter their login information, and additionally start using it.

In ServiceNow, a transform map is a field map set that governs the connection between the shown fields in the import set table and the existing fields in the destination table, such as "detectHand":false or "detectHand":false. After creating the transform map, you may use it to map data from another import set to the same table. An administrator can use a transform map to specify the end destinations for data loaded into tables. This will make establishing connectivity between the source fields of the import set table and the destination fields of the target table easier. Transform mapping allows you to map source and destination fields arbitrarily.

Select this check box to designate this user as a non-interactive user.

User-specific settings override global settings for email and notifications, while the default system date format applies to all users unless individually modified. This ensures personalized communication. Default formats maintain consistency for reporting and auditing. Changes do not disrupt workflows for other users. Email notifications inherit the user's preferences for language and format. Administrators can enforce mandatory formats if needed.

It's just a fun tradition! It started with Aspen and Berlin and has gone through the alphabet

A dictionary override allows you to customize the attributes of a field on a specific table without affecting the base dictionary entry.

We extend a table while creating a new table to inherit the fields, configurations, and behaviors of the parent table, allowing for reuse and customization.

Flow designer is, the modern way is to build the logic in ServiceNow and there will be no need for writing the code.

Workflows in ServiceNow are automated processes that define a series of tasks, approvals, and notifications designed to streamline business processes. They ensure tasks are completed in the correct order. They are visual representations of business logic, automating repetitive processes and improving efficiency. Example: A Change Request Workflow might automatically generate tasks for impact assessment, assign approval tasks to managers, and notify users of updates. This eliminates manual intervention and ensures each step of the process is followed consistently.

To conduct text searches, Zing provides a variety of search interfaces and search operators. | Search Interface | Description | | Global text search | From a single search field, find records in several tables. | | Lists | Search for entries in a list by going to a specific field, searching all areas, or searching a particular column. | | knowledge base | Find articles in the knowledge base. | | Navigation filter | Filter the objects in the application navigator using the navigation filter. | | UI pages | Create a custom user interface page to search for records in a table. | | Live feed | Filter, search, and sort messages in the live feed. |

Users access their instance using their username, password, and personal ID received during registration. Role-based access controls determine permissions. Multi-factor authentication may also be required. Access can be via browser or mobile. Sessions are tracked for security and compliance. Admins manage account activation and deactivation.

In ServiceNow, a viewpoint refers to a specific perspective or angle from which data and processes are analyzed and presented. It allows users to focus on relevant information tailored to their roles or needs. Viewpoints can be configured through dashboards, reports, and filtered views to provide actionable insights. They help in simplifying data interpretation by highlighting critical metrics and trends. Viewpoints enhance decision-making by providing targeted information.

ServiceNow is a cloud-based IT service management (ITSM) platform that provides digital workflows to manage IT and business processes. It includes modules for incident, problem, change, asset, and knowledge management. ServiceNow helps organizations streamline operations, improve service delivery, and automate tasks.

I search for the user in the User table and click Impersonate. This lets me test permissions, UI policies, and workflows as that user. I keep impersonation sessions short and exit once the test is complete.

This is used by companies that manage IT for other companies. It allows them to have one ServiceNow instance but keep each customer's data completely invisible to the others.

A MID (Management, Instrumentation, and Discovery) Server is a lightweight Java application that runs within your network to communicate with on-premise systems on behalf of ServiceNow. It's commonly used for Discovery (scanning internal networks for devices) and for integrations that need secure access to internal resources (like running PowerShell scripts on servers). In interviews, you might explain setting up a MID Server for Discovery or LDAP imports.

It's a user-friendly form that looks like a catalog item but actually creates a technical record.

Opened For refers to the user who opened the HR case, while Subject Person refers to the person who is the subject of the case.

There are two ways to configure labels and dictionary values: one configures labels, and one configures dictionaries.

Dictionary overrides provide the ability to define a field on an extended table differently from the field on the parent table. For example, for a field on the Task [task] table, a dictionary override can change the default value on the Incident [incident] table without affecting the default value on Task [task] or Change [change].

GlideRecord is a JavaScript class used in ServiceNow to perform database operations such as querying, updating, and deleting records. For example, to query the 'incident' table, you can use the following script: var gr = new GlideRecord('incident'); gr.query(); while (gr.next()) { gs.info(gr.number); }

- In ServiceNow, a transform map specifies the link between fields in an import set and fields in the target table. - It specifies how data should be mapped, transformed, and loaded during an import process. - Transform maps support data transformation rules, scripting, and field mapping. - They ensure that data from import sets is accurately inserted into the appropriate fields of the target table. Transform maps facilitate data normalization and consistency.

To create a new user in ServiceNow, you can use the following script: var gr = new GlideRecord('sys_user'); gr.initialize(); gr.user_name = 'new_user'; gr.first_name = 'First'; gr.last_name = 'Last'; gr.email = '[email protected]'; gr.insert(); This script initializes a new GlideRecord object, sets the necessary fields for the new user, and inserts the new record into the 'sys_user' table.

Script Includes are server-side JavaScript modules, classes or functions that define reusable code. They are accessible within their application scope and can be called from other server scripts or via GlideAjax from client scripts. For example, you could create a Script Include with a function to perform complex calculations and call it from multiple Business Rules. It avoids code duplication. Interviewers may ask how to make Script Includes client-callable (by enabling Client Callable and using GlideAjax).

A Workflow in ServiceNow defines the sequence of activities that automate business processes such as approvals, notifications, and task creation. This helps to ensure consistency, reduce manual effort, and help execute tasks based on predefined logic.

ServiceNow provides a cloud-based platform and suite of applications designed to automate IT service management (ITSM), business processes, and operations. It offers tools for incident management, change management, problem management, and more. Because of the platform's significant degree of adaptability, businesses can customize it to meet their requirements. ServiceNow also includes modules for IT operations management (ITOM) and IT business management (ITBM).

Metrics, record and measure the workflow of individual records. With metrics, customers can arm their process by providing tangible figures to measure. For example, how long it takes before a ticket is reassigned.

In ServiceNow, only users with the admin role or users with specific roles like security_admin have the authority to create or modify Access Control Lists (ACLs). These users can configure who has permission to access or modify specific records, fields, or tables in ServiceNow based on roles and conditions. Typically, ACLs are managed by security or system administrators to ensure proper access control and data security.

- Implement user authentication in ServiceNow by configuring Authentication Sources under System Security. - Choose authentication methods like LDAP, SAML, OAuth, or local ServiceNow authentication. - Configure settings such as server URLs, credentials, and attribute mappings. - Test and validate the configuration to ensure users can securely access ServiceNow with proper authentication methods aligned with organizational security policies.

Update set is a platform where you can move all of your changes over to the "Production" instance safely.

- You can change the type of a field. - To preserve existing data, only change between logical types that map to the same physical type on the database. - For example, Choice and String

- Business Rules in ServiceNow are server-side scripts that execute automatically when specific conditions are met. - They are employed in the implementation of business logic, process automation, and data consistency enforcement. - Business Rules can run on database operations like insert, update, delete, or query. - They consist of four types: Display, Before, After, and Async. These rules ensure data integrity and streamline workflow automation.

Business Rule on case_task table, before insert. (function executeRule(current, previous) { current.due_date = gs.daysAgo(-3); })(current, previous);

ServiceNow supports ITIL (Information Technology Infrastructure Library) best practices by providing a robust ITSM (IT Service Management) framework that aligns with ITIL principles. ServiceNow's ITSM modules, such as Incident Management, Problem Management, Change Management, and Service Catalog, are designed to follow ITIL guidelines. This ensures that organizations using ServiceNow can effectively manage and deliver IT services, improve efficiency, and reduce operational costs while adhering to ITIL's best practices.

Potential issues with the system include creating duplicate records based on a unique key.

ServiceNow's IntegrationHub is a framework that allows you to build and manage integrations with external systems. It provides a set of reusable integration components, such as spokes, actions, and connectors, that simplify the process of connecting ServiceNow with other applications and services. IntegrationHub supports various protocols and standards, such as REST, SOAP, and JDBC, enabling seamless data exchange and automation across different platforms. It helps extend the capabilities of ServiceNow and streamline business processes.

A scorecard is a tool for evaluating a team member's or a business process performance. It's a graph that shows how far you've come over time. A scorecard is a type of indication. The first step is to determine the presentation you'd like to track. Targets, breakdowns (scores by group), averages, and time series can all be added to scorecards to improve them.

ACL stands for Access Control List. The purpose of ACLs is to control user access to records, fields, and functions in ServiceNow.

ServiceNow's Incident Management module helps quickly restore normal service operations after disruptions. It manages the lifecycle of incidents from identification to resolution. Users report incidents, and the system assigns them to the appropriate teams. Incident Management includes prioritization, categorization, and escalation features. It ensures timely resolutions through workflows and automation. The module also provides metrics and reports to monitor incident trends and performance.

Installation exits are employed to insert customized actions in different events as per what's listed in the ServiceNow doc. These events could be password changes, login, logout, etc. There are plenty of use cases for these exits.

ServiceNow releases an update two times in a year. You can follow the ServiceNow community for getting updates, and the Release Notes can also help in this.

It's a "sandbox" where regular employees can build simple apps safely, without the risk of breaking the main company system.

Cloning involves copying data from one instance to another. It's useful for keeping test environments in sync with production. Update Sync, however, is about moving customizations (like update sets) between instances without copying data.

A new table can be created by making a small table under the application and moving it to another system.

Cities such as Jakarta, Orlando, Paris, and Cuba

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.

HR and CSM

You can use addActiveQuery() method to get all the active records and addInactiveQuery() to get the all inactive records.

ACL stands for Access Control List, which defines what data users can utilize and how it is accessible within ServiceNow.

Daily tasks include reviewing incidents, validating changes, monitoring scheduled jobs, checking update set progress, and collaborating with stakeholders on tickets.

Yes, an admin is able to create an ACL.

Non-interactive users can only use their credentials to authorize API connections such as JSON, SOAP, and WSDL. They cannot log in to the ServiceNow UI. Non-interactive users can only connect to a ServiceNow instance from an API protocol. Use this feature to set up user accounts for web service authentication purposes. Non-interactive users cannot log in to an instance or a service portal or connect through single-sign-on but can be used as a MID Server user if they are flagged as an Internal Integration User.

ServiceNow offers various extension points to customize and extend its capabilities. Some notable methods include: One way to extend ServiceNow is through the creation of custom applications. Let's say a company wants to automate its employee onboarding process. By developing a custom application on the ServiceNow platform, they can create tailored workflows, forms, and business rules specific to their onboarding requirements. This custom app seamlessly integrates with the existing ServiceNow modules, offering a unified experience to users.

A Scoped App is a self-contained application namespace in ServiceNow that isolates custom tables, scripts, and UI from other apps. It prevents naming conflicts and protects code. For example, if your team builds a custom HR app, you create it in its scope so its tables and scripts don't interfere with others. Scoped apps facilitate modular development, packaging, and upgrades. Interview questions may cover how to publish a scoped app or the benefits of scoped vs global scope.

The Coalesce option in ServiceNow allows updating existing target table records when transforming import data. The coalesce option on a field map lets you define whether the selected Target field should be used to coalesce when import set records are modified. When the field map Coalesce checkbox is selected, the import set row is changed, and the instance searches the target table for an existing record with the same Target field value as the import set row Source field.

- The ServiceNow Notifications module manages notifications. Administrators can configure notifications for various events, such as task assignments, approvals, or system alerts. - Users receive notifications via email, SMS, or through the ServiceNow interface. - Notification settings can be customized based on user roles, preferences, and urgency. - Users can manage their notification preferences through the User Preferences section.

Flow Designer is a low-code tool for designing business logic and integrations; use it for clear, maintainable flows instead of complex scripted workflows.

The Event Management module in ServiceNow helps monitor the health of IT services and infrastructure by collecting and processing events from various sources. It uses connectors to integrate with monitoring tools and gather event data. Event Management applies rules and filters to identify and prioritize significant events, correlates them with existing incidents and changes, and generates alerts. This module helps proactively manage IT issues, reduce downtime, and improve service availability by enabling timely responses to critical events.

An Update Set in ServiceNow is a container for grouping configuration changes that can be moved between instances. To configure an Update Set, navigate to the Update Sets module and create a new Update Set. Ensure the Update Set is marked as "Current" so that changes are captured. As you make changes in the instance, they are added to the Update Set. Once complete, you can export the Update Set as an XML file and import it into another instance for deployment. This process helps manage and track configuration changes across environments.

The Service Catalog is a self-service portal where users browse and order IT or business services, for example, new hardware and software access. It allows the structuring of services into categories and items. A record producer is a type of catalogue item that creates a standard record, such as an incident or service request, through a simplified form. For example, a "Report an Issue" Record Producer could gather user input, issue descriptions, and create an Incident behind the scenes.

A record producer is a unique catalog item that enables end-users to build task-based records like incident records. It allows us to create these task-based records from the service catalog. The record producers are similar to the catalog items and give a better user experience. These are better than the traditional task-based form used to build records. You can also create record producers for various tables and databases within the same range.

- To create a Scheduled Job in ServiceNow, navigate to Scheduled Jobs under System Definition in the ServiceNow instance. - In order to add a new Scheduled Job record, click "New." - Specify details such as script, frequency, start time, and recurrence pattern for the job. - Scheduled Jobs execute server-side scripts at specified intervals to automate tasks like data cleanup or maintenance. - Jobs can be monitored and managed through the Scheduled Jobs module for status and execution history.

Service Now offers various products, they are; - Business management application - Custom service management - HR management - IT service automation application.

Some common modules in ServiceNow include:

- The Event Management module in ServiceNow monitors and manages IT infrastructure events. - It consolidates event data from various sources into a single platform. - Event rules classify and prioritize events based on predefined criteria. - Automated actions or notifications can be triggered based on event types and severity. - This module enhances IT service visibility, incident response, and proactive problem management.

- To set up email notifications in ServiceNow, go to "System Notification" and choose "Email." - Create a new notification by setting conditions for when it should be sent. Define the recipients, subject, and message content, using variables to include dynamic information. - Test the notification to ensure it functions correctly. Save and activate the notification to start sending emails. This ensures timely communication based on specific triggers.

Prioritization involves assessing the impact and urgency of service requests based on factors such as business impact, severity of issues, and SLA requirements. A ticketing system or service desk software can help in tracking and managing service requests efficiently, ensuring timely resolution and customer satisfaction.

Metrics help to measure and record the individual record's workflow. They help track the changes that occur in any field on any table. Also, it helps to estimate the effectiveness of ITSM processes.

GlideRecord is a server-side script API that allows for the querying and manipulation of data in ServiceNow tables. It's the primary way to interact with database tables in server-side scripts.

You can click on the "Create New" tab to create a report by navigating to the reports section.

The ServiceNow Access Control List (ACL) is a set of rules that determine the access permissions for users within the platform. ACLs are used to control access to records, fields, and actions based on the user's role, group membership, or other attributes. ACLs help ensure that users can only access and perform actions on data that they are authorized to view or modify.

Resolved means the incident has been fixed, but the user has not yet confirmed. Closed means the incident has been confirmed as resolved and is no longer active.

ServiceNow Agent Workspace is a unified interface designed for service agents to manage and resolve tasks efficiently. It provides a consolidated view of cases, incidents, and tasks, along with contextual information and actionable insights. Agent Workspace includes features like agent assist, task routing, and real-time collaboration, enhancing productivity and decision-making. It supports multi-channel interactions, enabling agents to handle requests from various sources seamlessly, improving service quality and customer satisfaction.

I create real-time dashboards with widgets for key metrics. Reports are scheduled to highlight SLA compliance, backlog trends, and resolution times.

- Metrics in ServiceNow are quantitative measures used to track and assess the performance of processes and services. - They help in evaluating efficiency, quality, and compliance with service level agreements (SLAs). - Various KPIs (Key Performance Indicators), such as resolution time, incident count, and customer satisfaction, can have metrics defined. - They are essential for continuous improvement, as they identify areas that need enhancement.

It is a unique 32-character GUID that identifies each record created in each table in ServiceNow.

- UI Policy controls the behavior of fields on forms based on conditions. - It hides, sets as mandatory, or makes fields read-only dynamically. - Data Policy enforces data consistency and standards in ServiceNow. - It validates and formats data entered into fields. - UI Policies affect form interactions, while Data Policies focus on data integrity. - Both are essential for enhancing user experience and maintaining data quality.

Below are the major roles and responsibilities of Service Now administrator; - They can create a basic user interface and navigations in Service Now platform - Create tables, data fields, form layouts, and views. - Create and administer various users, Groups, and Roles. - Import data into service now tables and configure the applications - Able to create security rules (ACL) to restrict user access.

UI policies control specific process flows for tasks and change information on a form in real-time. For example, UI policies can make a form's number field read-only, the short description field obligatory, and other fields hidden. Basic UI policies do not require scripting; however, the Run scripts option should be used for more elaborate operations.

Yes, it is possible to call a business rule through a client script. You can use glide ajax for the same.

A gauge refers to a widget that has a specific purpose. It enables making a report available to be used on a homepage.

To grant the admin role to a user, you must also have the admin role. To grant the security_admin role to a user, you must also have the security_admin role and must elevate to the security_admin role before granting the security_admin role to other users.

BMC Remedy

The Generate activity in a workflow is used to create a record in a specified table, such as a task or approval.

The BSM Map in ServiceNow visualizes the relationships between business services, applications, and the underlying IT infrastructure. IT teams can use it to identify impacted services during outages and improve incident resolution. The map also aids in analyzing the overall health of services and their dependencies, enhancing service management and decision-making. For example, the BSM Map shows that the Email Service (business service) depends on the Mail Server (application) and the Database (IT infrastructure). If the Mail Server goes down, the BSM Map helps identify that the Email Service will be impacted. This allows IT teams to prioritize the resolution of the underlying issue.

ServiceNow is a cloud-based ITSM (IT Service Management) application that combines business management, operations, and IT services into a single system. The ServiceNow ecosystem contains all elements linked to the organization's IT services. You can get a complete picture of the programs and infrastructure available. This allows you to regulate resource allocation better and develop a more efficient process flow. HR, security, business applications, customer care, and IT (Information Technology) services are all provided by ServiceNow. It is regarded as a unified cloud solution in which we may get all these services in one location.

In ServiceNow, "coalesce" refers to a setting used during data imports to determine if existing records should be updated or new records should be created. When a field is set to merge, the system uses it as a unique key to find matching records. Should a match be discovered, the current record is updated; if not, a new record is created. This is crucial for maintaining data consistency and avoiding duplicates. Coalescing helps in accurate data integration from external sources. It simplifies data management and ensures up-to-date information.

First, log an Incident to track the outage, noting severity (e.g., P1) and impact. Notify on-call support immediately. Since it's urgent and after hours, the team works quickly to restore service, restart servers, etc. If a code or configuration fix is needed, create an Emergency Change to apply it rapidly. Ensure stakeholders are updated. After service is restored, perform a post-incident review to identify root causes and preventive actions, and document the outcome in the incident record.

CMDB is a most required component of an ITIL framework. It is particularly important in a service transition phase. ITIL gives different guidelines and best practices for IT service management. CMDB is basically a support system for these practices that maintain CIs records and their relationships.

The priority of an incident is defined by combining the impact and urgency, typically using a matrix to determine the priority level (e.g., Critical, High, Medium, Low).

The below table explains the major differences between Service Now and Salesforce :

Follow established incident management procedures, which include incident detection, categorization, prioritization, investigation, resolution, and communication. Ensure clear communication with stakeholders, adhere to SLA requirements, and conduct post-incident reviews to identify root causes and prevent recurrence.

Q3. What is the purpose of Workflow Data Fabric in ServiceNow's Yokohama release?

Use GlideRecord with setLimit and deleteRecord. var gr = new GlideRecord('incident'); gr.addQuery('sys_created_on', '>=', gs.beginningOfToday()); gr.orderBy('sys_created_on'); gr.setLimit(5); gr.query(); while (gr.next()) { gr.deleteRecord(); }

An Import Set in ServiceNow is a temporary staging table used to import and transform data from external sources (like spreadsheets, CSV files, or third-party systems) into ServiceNow tables. It helps to map, clean, and load data into ServiceNow in a controlled manner. How it works: - Data is first loaded into an Import Set Table, a temporary table designed to hold the raw data. - After data is imported, you can use a Transform Map to define how the data from the Import Set table should be mapped to the target table in ServiceNow (e.g., importing user information into the User table). - Before importing the data into the target table, you can apply transformations to clean and validate the data. - Once the data has been transformed and validated, it is transferred from the Import Set table to the target table (e.g., Incident, User, Asset). Example: If you're importing a list of employees from a CSV file, the Import Set table holds the raw data, and a Transform Map is used to map the fields (like name, email, department) into the User table in ServiceNow.

The latest user interface is UI16 interface. It came in Helsinki release.

Impact refers to the extent of damage or effect on the business, while urgency refers to how quickly the incident needs to be resolved.

onSubmit client script refers to a scripting feature that is mostly used in web development. It has been crafted in a way that a specific function or action is executed when a form is submitted by the user. It aids software engineers or developers in validating and customizing the form data prior to sending it to the server for further processing.

Ability to create robust scripts to manage and rectify failed import sets can demonstrate technical proficiency.

Business rules are server-side scripts that run when a record is inserted, updated, deleted, or queried. They are used to enforce business logic, perform calculations, or trigger actions automatically.

Certified System Administrator (CSA) is foundational; specialization and role-based certifications follow for career growth and are frequently recommended.

A script include is a reusable server-side script that stores functions or classes. It is used when you need to call the same logic from multiple server-side scripts or from client-side scripts via GlideAjax. This reduces code duplication and makes maintenance easier.

A Change is a planned update or addition to the IT environment.

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.

To count the number of incidents in a specific state, you can use the following script: var gr = new GlideRecord('incident'); gr.addQuery('state', 'specific_state'); gr.query(); var count = gr.getRowCount(); gs.info('Number of incidents in specific state: ' + count); This script initializes a GlideRecord object, queries the 'incident' table for records in the specified state, and counts the number of records.

All text searches in ServiceNow are performed by Zing (a text indexing and search engine).

- Administrators can delete custom tables that are no longer needed. - A table is custom if an administrator created it and it is not part of a system upgrade or plugin activation - Custom table names always begins with u_, or x_ for scoped tables - You cannot delete base system tables. If you inadvertently delete such a table, it is automatically recreated when you upgrade an instance. - You cannot delete a table with associated tables extending from it. - Deleting all records for a table also deletes records from tables that extend the table

Binary images, such as logos or icons, ensure the visual interface is clear and consistent. Updating images maintains branding and reflects organizational identity. Proper formats prevent distortion across dashboards and forms. Binary images support accessibility and responsiveness in UI. Admins can schedule updates for branding changes. Correct image management enhances user experience and professionalism.

The main change types are Standard, Normal, and Emergency. A Standard Change is a low-risk, pre-approved routine change (for example, a scheduled backup). A Normal Change follows the whole approval process, often requiring CAB review and testing. An Emergency Change is for urgent fixes, such as a security patch after a critical incident, and bypasses some customary approvals to restore service quickly. For instance, a database restart might be a standard change, while deploying a hotfix after hours could be an emergency change.

If one person's computer is slow, that's an Incident. If 500 people's computers are slow because a central server is overheating, that's a Problem. An Incident is about fixing the "right now," while a Problem is about finding the "root cause" so it doesn't happen again.

The Configuration Management Database (CMDB) stores details of all Configuration Items (CIs) such as servers, applications, and network devices. It helps IT teams understand relationships between components, assess the impact of changes, troubleshoot faster, and ensure better decision-making.

The CMDB (Configuration Management Database) is a central repository that stores information about configuration items (CIs) like servers, software, and business services. It defines relationships between CIs, enabling impact analysis for incidents and changes.

ServiceNow notifications alert users about system events like record updates or specific actions. System events trigger them and can be delivered via email, SMS, push notifications, or instant messaging. Notifications use templates that include dynamic content for personalization. Users can set preferences to choose how and when they receive alerts. Conditions and filters ensure notifications are sent based on specific criteria, making communication timely and relevant.

Use system logs, gs.log for server-side, console.log for client-side, Script Debugger, and the Query Business Rule logging; reproduce with minimal data and trace function calls.

A rollback context is created when: - GlideRecord.delete() or GlideRecord.deleteMultiple() delete records. - There is a patch upgrade. - You activate a plugin that supports rollback contexts. - A script executes using the Scripts-Background module, and rollback was enabled by selecting the Record for Rollback. check box.

ServiceNow is a cloud-based IT Service Management (ITSM) tool that provides a comprehensive platform for managing digital workflows. Its primary functionalities include incident management, problem management, change management, asset management, and service catalog management.

Regular reporting tells you what's happening now. Performance Analytics looks at data over months to show you trends.

ServiceNow provides REST and SOAP APIs for inbound/outbound integration; design secure endpoints, handle auth (OAuth), and validate payloads with transform maps.

Compliance with regulatory requirements and industry standards is essential to protect sensitive data, ensure privacy, and maintain the trust of customers and stakeholders. This includes enforcing access controls, encryption, data retention policies, and conducting employee training and awareness programs.

A Delegate is a user who is assigned to perform tasks or approvals on behalf of another user.

Demonstrating familiarity with business rules and analyzing data flow is crucial.

If a company has a type of server that won't be available on the internet and ServiceNow will not be able to see this. So, a MID server is a small part of software that can be installed easily on the company's local network.

A Service Administrator is responsible for managing and maintaining the systems, applications, and services that support an organization's operations. This includes tasks such as installation, configuration, troubleshooting, and ensuring the availability and performance of IT services.

HTML sanitizer cleans up a markup in HTML fields automatically. It aids in the removal of code and the prevention of security issues like cross-site scripting attacks.

ServiceNow is a cloud-based IT Service Management (ITSM) platform designed to automate and manage enterprise IT operations. It's used to streamline service operations, improve service delivery, and automate routine tasks across various departments in an organization.

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.

Client scripts reside on the client-side (the browser) and are only used by the client. The following are the different kinds of client scripts: • OnLoad() • OnSubmit() • OnChange() • OncellEdit)

BMC Remedy is the key competitor, offering similar IT service management and workflow automation solutions. Both platforms follow ITIL principles. BMC Remedy is preferred in legacy on-premise environments. ServiceNow is cloud-focused and modern in approach. Decision depends on organizational requirements. Integration and scalability also influence choice.

Q4. Which feature in the 2025 Yokohama release provides real-time storage analytics?

It's an email or a push alert sent by the system. Admins configure these to make sure people know when a ticket is assigned to them.