Scenario Based Servicenow Interview Question - Solutions
Scenario Based Servicenow Interview Question - Solutions
in
• Solution:
1. Check the Assignment Rules in the Incident table to
ensure they are correctly configured.
2. Verify the Assignment Group field on the incident
form to see if it was manually set or auto-populated.
3. Review the Business Rules or Workflow that might
be updating the Assignment Group.
4. Use the Debug Business Rules feature to trace the
logic.
5. If needed, update the Assignment Rules or Business
Rules to ensure proper group assignment.
• Solution:
o Assignment Rules:
▪ Define conditions (e.g., category, priority) to
automatically assign incidents to the correct
group.
▪ Example: Assign all "Network" category
• Solution:
o Lifecycle:
1. Request: A user submits a Change Request.
2. Review: The request is reviewed for feasibility
and risk.
3. Approval: Approved by stakeholders (e.g., CAB).
4. Implementation: The change is executed.
5. Validation: The change is tested and verified.
6. Closure: The request is closed.
o Approval Workflow:
▪ Use the Workflow Editor to create a flow with
approval tasks.
▪ Example: Add an "Approval - CAB" task with
conditions based on risk level.
• Solution:
o Client Scripts:
▪ Run in the user’s browser (client-side).
▪ Example: Validate a field on a form before
submission.
o Business Rules:
▪ Run on the server-side when a record is
inserted, updated, or queried.
▪ Example: Automatically update the "Priority"
field based on the "Impact" and "Urgency"
fields.
• Solution:
1. Open the Script Debugger in the browser console.
2. Add console.log() statements to trace the script
execution.
3. Check for errors in the console.
4. Verify the script’s conditions and ensure it’s triggered
on the correct event (e.g., onChange, onSubmit).
• Solution:
• Solution:
• Solution:
1. Open the Catalog Item in ServiceNow.
2. Go to the Workflow tab and select an approval
workflow (e.g., "Catalog Item Approval").
3. Configure the workflow to include approval tasks
(e.g., Manager Approval).
4. Test the workflow by submitting the catalog item.
• Solution:
1. Open Service Catalog > Catalog Items > Create
New.
2. Add fields:
▪ Name of the Requestor (Default: Logged-in
User)
▪ Type of Laptop (Dropdown: Standard, High
Performance)
▪ Justification (Text Area)
• Solution:
o Components:
1. SLA Definition: Conditions for when the SLA
applies.
2. Schedule: Business hours for SLA calculation.
3. Breach Time: Time limit for resolution.
o Configuration:
1. Go to SLAs > Create New.
2. Set conditions (e.g., Priority = High).
3. Set breach time to 4 hours.
• Solution:
1. Create an SLA Definition with conditions: Priority =
High.
2. Set breach time (e.g., 2 hours).
3. Add a notification in the workflow to send an email
on SLA breach.
• Solution:
1. Check the Notification record to ensure it’s active
and conditions are met.
2. Verify the Email Script for errors.
3. Use the System Logs to trace the notification
execution.
• Solution:
1. Go to System Notification > Email > Create New.
2. Set conditions: State = Resolved.
3. Add email content:
▪ Incident Number: ${incident.number}
▪ Resolution Notes: ${incident.close_notes}
Scenario-Based Questions:
function onSubmit() {
var leaveType = g_form.getValue('leave_type');
var startDate = g_form.getValue('start_date');
if (leaveType === 'Sick Leave' && !startDate) {
alert('Start Date is mandatory for Sick Leave.');
return false;
}
return true;
}
function isValidEmail(email) {
var regex = /^[^\s@]+@[^\s@]+\.[^\s@]+$/;
return regex.test(email);
}