LogiUpSkill

Service-now Interview Questions

Service-Now Interview Questions Question & Answers What is difference between UI Policy and Client Script Client Script will execute first than UI Policy. UI Policy has condition but Client script does not (we need to write manually through code) UI Policy has condition where we can access the fields which are not on the form but client script does not, Client script can access only the fields which are on the form. What is import set table? Import set table is a temporary table where we will put the data for temporary purpose and later we can move the import set data to target table using transform map. Whenever we are pulling the data from external source, it is a standard process to get data into import set first and then validate the data using transform scripts and then transform the data into target table. Import set table always extends import set row table. By default import set table fields are of string type. Import set table can be used to debug the integration where we are pulling the data from external source. Update Set? Update set is used to capture the customization i.e. development in servicenow. Update set will capture the versions of every development components. Only the table data, which has update_synch attribute =true, get captured into update set. Only completed update set can be moved to another instance. We should not change the update set state from completed to in progress as per standard practice. Display business Rule? Display business rule will run when the data is getting populated on the form from server. Here we can use g_scratchpad global variable to send the service side information to client side script. For display business rule, we don’t have option like update, insert, query and delete in business rule form. Client Script will execute first than UI Policy. UI Policy has condition but Client script does not (we need to write manually through code) UI Policy has condition where we can access the fields which are not on the form but client script does not, Client script can access only the fields which are on the form. Import set table is a temporary table where we will put the data for temporary purpose and later we can move the import set data to target table using transform map. Whenever we are pulling the data from external source, it is a standard process to get data into import set first and then validate the data using transform scripts and then transform the data into target table. Import set table always extends import set row table. By default import set table fields are of string type. Import set table can be used to debug the integration where we are pulling the data from external source. Update set is used to capture the customization i.e. development in servicenow. Update set will capture the versions of every development components. Only the table data, which has update_synch attribute =true, get captured into update set. Only completed update set can be moved to another instance. We should not change the update set state from completed to in progress as per standard practice. Display business rule will run when the data is getting populated on the form from server. Here we can use g_scratchpad global variable to send the service side information to client side script. For display business rule, we don’t have option like update, insert, query and delete in business rule form.

ITSM

ITSM Question & Answers Processes in Service Operations Incident Management Problem Management Change Management Incident Management Any interruption in service is raised as an Incident Purpose is to restore normal service operations Purpose is to minimise the effect by workaround if restore is not possible Impact and Urgency are defining the Priority Challenges Detect an incident as soon as possible Incident workaround or resolution should get documented Incident assignment for L1, L2 and L3 support Correct assignment of priority in automated generated incidents Example: Not able to login in system Not able to swipe the swipe card Not able to send an emails Problem Management: Two or more incidents will raise problem Problem is to find out permanent solution for incidents through change. Reactive and Proactive Problems Known Error Workaround Examples: If we got more than one incidents like 10 users incidents that they are not able to login into system, it means something wrong with system. If we got more than one incidents for swipe card, it means the swipe machine has an issue rather than the swipe card, so we will raise one Problem for all the incidents and instead of working 10 engineers on incident will assign one engineer on Problem to fix all the incidents. Change Types Change is to enable beneficial changes to be made with minimum disruption to existing services. Definition: Change is “the addition, modification or removal of anything that could have an effect on IT services”. Normal Change – go through routine change go through all the process Any service change that is not a standard change or emergency change. Standard Change –  pre-approved change— relatively low risk A pre-authorized change that is low risk, relatively common and follows a procedure or work instruction. Emergency Change –  must be deployed as soon as possible within 24 hours like system go down, serious defect. IT should have different group of approval(CAB=Change Advisory board) A change that must be implemented as soon as possible, for example to resolve a major incident or implement a security patch. Incident Management Problem Management Change Management Any interruption in service is raised as an Incident Purpose is to restore normal service operations Purpose is to minimise the effect by workaround if restore is not possible Impact and Urgency are defining the Priority Challenges Detect an incident as soon as possible Incident workaround or resolution should get documented Incident assignment for L1, L2 and L3 support Correct assignment of priority in automated generated incidents Example: Not able to login in system Not able to swipe the swipe card Not able to send an emails Two or more incidents will raise problem Problem is to find out permanent solution for incidents through change. Reactive and Proactive Problems Known Error Workaround Examples: If we got more than one incidents like 10 users incidents that they are not able to login into system, it means something wrong with system. If we got more than one incidents for swipe card, it means the swipe machine has an issue rather than the swipe card, so we will raise one Problem for all the incidents and instead of working 10 engineers on incident will assign one engineer on Problem to fix all the incidents. Change is to enable beneficial changes to be made with minimum disruption to existing services. Definition: Change is “the addition, modification or removal of anything that could have an effect on IT services”. Normal Change – go through routine change go through all the process Any service change that is not a standard change or emergency change. Standard Change –  pre-approved change— relatively low risk A pre-authorized change that is low risk, relatively common and follows a procedure or work instruction. Emergency Change –  must be deployed as soon as possible within 24 hours like system go down, serious defect. IT should have different group of approval(CAB=Change Advisory board) A change that must be implemented as soon as possible, for example to resolve a major incident or implement a security patch.

Client Script In Service-now

<h2>Client Scripts in ServiceNow – Fundamentals Explained</h2> <h3>1. Alert Full Name of Logged-in User</h3><pre><code>function onLoad() {    var p = g_user.getFullName();    alert(‘This is my first client Script = ‘ + p);}</code></pre> <h3>2. Alert If the Record Is New or Not</h3><pre><code>function onLoad() {    if (g_form.isNewRecord()) {        alert(‘This is new Record’);    } else {        alert(‘This is not a new record’);    }}</code></pre> <h3>3. Use of Different APIs</h3><pre><code>function onLoad() {    g_form.setReadOnly(‘u_email’, true);    g_form.setValue(‘u_description’, ‘hiiiiiii’);    g_form.clearOptions(‘u_category’);    g_form.getLabelOf(‘u_number’);    g_form.addInfoMessage(‘hi’);    g_form.setMandatory(‘u_first_name’, true);    g_form.setMandatory(‘u_last_name’, true);     if (g_user.hasRole(‘admin’)) {        g_form.removeOption(‘u_state’, ‘Maharashtra’);    }}</code></pre> <h3>4. Show Field After Record Creation (Hide in New Record)</h3><pre><code>function onLoad() {    if (g_form.isNewRecord()) {        g_form.setVisible(“u_convert_to”, false);    } else {        g_form.setVisible(“u_convert_to”, true);    }}</code></pre> <h3>5. Populate Email & Short Description When Assigned To Changes</h3><pre><code>function onChange(control, oldValue, newValue, isLoading, isTemplate) {    if (isLoading || newValue === ”) {        return;    }     var p = g_form.getReference(“u_assigned_to”).email;    g_form.setValue(“u_email”, p);    g_form.setMandatory(“u_first_name”, true);    g_form.setValue(“u_short_description”, ‘This is :’ + g_user.getFullName());}</code></pre> <h3>6. Populate User’s First Name in Short Description</h3><pre><code>function onChange(control, oldValue, newValue, isLoading, isTemplate) {    if (isLoading || newValue === ”) {        return;    }     var name = g_form.getReference(“u_assigned_to”);    g_form.setValue(“u_short_description”, ‘This is ‘ + name.first_name);     alert(newValue);    alert(oldValue);}</code></pre> <h3>7. Confirm Details Before Form Submit</h3><pre><code>function onSubmit() {    var a = g_form.getValue(“u_first_name”);    var b = g_form.getValue(“u_last_name”);     var con = confirm(        ‘You Entered below details -\n’ +        ‘The first name is: ‘ + a + ‘\n’ +        ‘The last name is: ‘ + b + ‘\n’ +        ‘Do you confirm the details?’    );     if (con == true) {        return;    } else {        return false;    }}</code></pre> Client Scripts in ServiceNow – Fundamentals Explained 1. Alert Full Name of Logged-in User function onLoad() { var p = g_user.getFullName(); alert(‘This is my first client Script = ‘ + p); } 2. Alert If the Record Is New or Not function onLoad() { if (g_form.isNewRecord()) { alert(‘This is new Record’); } else { alert(‘This is not a new record’); } } 3. Use of Different APIs function onLoad() { g_form.setReadOnly(‘u_email’, true); g_form.setValue(‘u_description’, ‘hiiiiiii’); g_form.clearOptions(‘u_category’); g_form.getLabelOf(‘u_number’); g_form.addInfoMessage(‘hi’); g_form.setMandatory(‘u_first_name’, true); g_form.setMandatory(‘u_last_name’, true); if (g_user.hasRole(‘admin’)) { g_form.removeOption(‘u_state’, ‘Maharashtra’); } } 4. Show Field After Record Creation (Hide in New Record) function onLoad() { if (g_form.isNewRecord()) { g_form.setVisible(“u_convert_to”, false); } else { g_form.setVisible(“u_convert_to”, true); } } 5. Populate Email & Short Description When Assigned To Changes function onChange(control, oldValue, newValue, isLoading, isTemplate) { if (isLoading || newValue === ”) { return; } var p = g_form.getReference(“u_assigned_to”).email; g_form.setValue(“u_email”, p); g_form.setMandatory(“u_first_name”, true); g_form.setValue(“u_short_description”, ‘This is :’ + g_user.getFullName()); } 6. Populate User’s First Name in Short Description function onChange(control, oldValue, newValue, isLoading, isTemplate) { if (isLoading || newValue === ”) { return; } var name = g_form.getReference(“u_assigned_to”); g_form.setValue(“u_short_description”, ‘This is ‘ + name.first_name); alert(newValue); alert(oldValue); } 7. Confirm Details Before Form Submit function onSubmit() { var a = g_form.getValue(“u_first_name”); var b = g_form.getValue(“u_last_name”); var con = confirm( ‘You Entered below details -n’ + ‘The first name is: ‘ + a + ‘n’ + ‘The last name is: ‘ + b + ‘n’ + ‘Do you confirm the details?’ ); if (con == true) { return; } else { return false; } }

What is Software Testing? Complete Guide (2025)

1. By Testing Method (Manual / Automation) Manual Testing Exploratory Testing Ad-hoc Testing Usability Testing Monkey Testing Error Guessing Compatibility Testing Automation Testing UI Automation API Automation Mobile Automation Functional Automation Regression Automation Performance Automation Tools: Selenium, Cypress, Playwright, Appium, Postman, JMeter, K6, Rest Assured, TestNG, JUnit 2. By Level of Testing (Very Important for QA) 1️⃣ Unit Testing2️⃣ Integration Testing3️⃣ System Testing4️⃣ User Acceptance Testing (UAT) 3. By Type of Functional Testing Smoke Testing Sanity Testing Regression Testing Retesting End-to-End (E2E) Testing Interface Testing Localization & Internationalization Testing Database Testing Installation Testing Validation Testing Verification Testing 4. By Type of Non-Functional Testing Performance Testing Load Testing Stress Testing Volume Testing Scalability Testing Security Testing Vulnerability Testing Penetration Testing Reliability Testing Compatibility Testing Recovery Testing Accessibility Testing (A11Y) 5. By Test Design Techniques (ISTQB Standard) Black Box Testing Equivalence Partitioning Boundary Value Analysis Decision Table Testing State Transition Testing Use Case Testing White Box Testing Statement Coverage Branch Coverage Condition Coverage Path Coverage Experience-Based Testing Exploratory Error Guessing Checklist-based 6. By Life Cycle SDLC Models Waterfall Agile Scrum V-Model Spiral DevOps STLC Phases Requirement Analysis Test Planning Test Case Design Test Environment Setup Test Execution Defect Logging Test Closure 7. QA Documentation Formats These are important for blogs & course content. Test Plan Test Strategy Test Case Test Scenario Test Script Traceability Matrix (RTM) Test Summary Report Bug Report (Defect Report) 8. Defect / Bug Life Cycle New Assigned Open Fixed Retest Verified Closed Reopened Deferred Rejected 9. Most Used QA Tools (2025) Test Management Tools JIRA TestRail Zephyr QMetry Bug Tracking Tools Bugzilla MantisBT RedMine Automation Tools Selenium Cypress Playwright Appium API Testing Tools Postman Rest Assured Swagger Performance Tools JMeter K6 LoadRunner 10. QA Roles (Job Profiles) Manual Tester Automation Tester QA Engineer QA Analyst SDET Performance Tester Mobile Tester Security Tester Test Lead Test Architect What is Software Testing? Software Testing is the process of evaluating a software application to identify defects, ensure quality, and verify that it meets the required standards. It helps improve performance, security, and user experience. Why Software Testing is Important? Detects bugs before users find them Ensures smooth performance Improves customer satisfaction Reduces maintenance cost Ensures product stability Types of Software Testing 1. Manual Testing Manual Testing is a process where testers execute test cases manually without using automation tools. 2. Automation Testing Automation involves using tools like Selenium, Cypress, and Playwright to execute test cases faster and more accurately. SDLC vs STLC SDLC is the Software Development Life Cycle. STLC is the Software Testing Life Cycle. Key Differences: SDLC focuses on development STLC focuses on testing activities Popular Testing Tools Selenium JIRA Postman JMeter TestRail Conclusion Software Testing is a promising career with high demand, competitive salaries, and excellent growth opportunities. Whether you’re a beginner or aiming for automation, QA offers a stable and rewarding path.

Getting Started with Power BI – A Complete Beginner’s Guide

🏷️ Keywords: power bi tutorial, business intelligence course, power bi for beginners 📝 Intro: Power BI is Microsoft’s leading business intelligence tool used to visualize and analyze data.This guide helps you understand its basics and how to create your first dashboard. 🔹 Key Points: 🔚 Conclusion: Power BI empowers professionals to turn data into decisions. Learn it step-by-step to boost your analytics career.

What is Generative AI? A Beginner’s Guide (2025 Edition)

Generative AI is transforming industries — from art and code to business analytics.This beginner’s guide explains what Gen AI is, how it works, and why it matters for future careers. 🔹 Key Points : 🔚 Conclusion: Gen AI isn’t just about automation — it’s about creativity powered by data.Start learning today to stay ahead in the AI-driven world.

Top 10 Software Testing Interview Questions and Answers

Software Testing interviews can be challenging, especially for freshers and professionals who want to prove both theoretical knowledge and practical understanding.This article compiles the top 20 software testing interview questions and answers that will help you get ready for your next job opportunity — whether it’s Manual, Automation, or QA role. 🧠 1. What is Software Testing? Answer:Software Testing is the process of evaluating a software application to ensure it meets the specified requirements and is free of defects. The goal is to identify bugs, errors, or missing functionalities before deployment. 🧠 2. Why is Testing Important? Answer:Testing ensures product quality, reliability, and performance. It helps detect defects early, saves cost, and improves user satisfaction. 🧠 3. What are the Different Levels of Testing? Answer: Unit Testing – Testing individual components. Integration Testing – Verifying combined modules. System Testing – End-to-end testing of the entire system. Acceptance Testing – Validating the product with client requirements. 🧠 3. What are the Different Levels of Testing? Answer: Unit Testing – Testing individual components. Integration Testing – Verifying combined modules. System Testing – End-to-end testing of the entire system. Acceptance Testing – Validating the product with client requirements. 🧠 3. What are the Different Levels of Testing? Answer: Unit Testing – Testing individual components. Integration Testing – Verifying combined modules. System Testing – End-to-end testing of the entire system. Acceptance Testing – Validating the product with client requirements. 🧠 4. What are the Types of Software Testing? Answer: Manual Testing Automation Testing Black Box Testing White Box Testing Smoke Testing Regression Testing Sanity Testing 🧠 5. What is the Difference Between Verification and Validation? Verification Validation Ensures product is built correctly. Ensures right product is built. Done during development. Done after development. Example: Reviewing documents. Example: Functional testing. 🧠 6. What is a Test Case? Answer:A test case is a set of conditions or variables used to determine whether a system works as expected. It includes test steps, expected results, and actual results. 🧠 7. What is a Bug / Defect? Answer:A bug or defect is an error or flaw in software that produces incorrect or unexpected results. 🧠 8. What are Severity and Priority? Term Meaning Severity Impact of a defect on the system. Priority Urgency to fix the defect. Example: A spelling error in the homepage has low severity but high priority. 🧠 9. What is Regression Testing? Answer:It ensures that new code changes do not adversely affect the existing functionality of the application. 🧠 10. What is Smoke Testing? Answer:Smoke Testing is a basic check to verify that the critical functionalities of an application are working. It’s often called “Build Verification Testing.”