← Home
🔥0 DAY
0 XP
Week 4 · Days 1620 · 10 min read

Week 4: ACLs, Integrations, and Interview-Ready Scenarios

Days 16–20 of the 20-Day ServiceNow Scripting Curriculum

By Week 4 you can move data around. Now you need to protect it and connect it. The last five days take you from 'I can write scripts' to 'I can answer the hard interview question without freezing.'

Who it's for: Devs prepping for a technical interview or their first solo project.

BY THE END YOU CAN

  • Write an ACL that actually denies the right people
  • Expose a Scripted REST API safely and consume one with a REST Message
  • Debug a production issue without console.log everywhere
  • Talk through a scenario question without panicking

Day 16: ACLs — The Order of Operations

GoalExplain table.field, table.None, table.* and how they evaluate together.

DrillWrite an ACL that lets only the caller and the assignment group see the work_notes field.

TakeawayACLs are AND inside one rule, OR across rules. Most-specific wins. Script returns true to ALLOW; false denies. Read /learn/acl-scripting if any of that sounded fuzzy.

Day 17: Scripted REST APIs

GoalExpose GET /api/x/yourcompany/incidents that returns the caller's open incidents.

DrillBuild the resource, set authentication, and call it from Postman with basic auth.

Takeawayprocess the request, build a response object, return it. Never trust query params — validate with the same rigor as a Client Script bypass scenario.

Day 18: REST Messages — Calling Out to the World

GoalBuild a REST Message that hits a public API and parse the JSON response.

DrillCall https://api.github.com/users/{name} and store the avatar_url on a custom table.

TakeawayUse variable substitutions for inputs. Always check getStatusCode() before reading the body. Wrap in try/catch — network failures are not optional.

Day 19: Debugging Like a Senior

GoalUse the Script Debugger, gs.info with prefixes, and the System Log to triage a bug in under 10 minutes.

DrillTake a broken Business Rule (intentionally), find the bug, fix it without adding more than 2 log lines.

TakeawayLogs are evidence, not bandages. Prefix every log with a tag you can grep. The debugger beats logs once you've used it three times.

Day 20: Interview Scenario Day

GoalSolve one end-to-end scenario like an interviewer asked it.

Drill'When a P1 incident is opened, notify the on-call manager, create a major incident task, and post to a Teams channel.' Whiteboard the design before writing any code.

TakeawayInterviewers grade clarity, not cleverness. Name the components (BR, Flow, REST Message, notification), justify the order, and only then talk code.

PRACTICE THIS WEEK