Week 7 shifted gears from AI to the foundation behind much of ServiceNow customization: JavaScript. This week I completed the Introduction to JavaScript course and the Scripting in ServiceNow Primer, both on the Now Learning platform — and picked up some valuable lessons along the way, including a few from mistakes. 

Getting Back to Basics: PDI and JavaScript Fundamentals. 

The course kicked off with a refresher on how to launch and request a Personal Developer Instance (PDI) — a good reminder that having your own sandbox is step one for any hands-on ServiceNow learning or development work. 

From there, I moved into core JavaScript concepts:

• Statement syntax — the basic building blocks of a JavaScript program

• String variables — how to declare, assign, and manipulate text data

• Arithmetic operations — performing calculations within scripts

• Comments and comparisons — documenting code and evaluating conditions

• Conditional logic statements — directing script behavior based on conditions

• Loops and functions — repeating actions and building reusable blocks of logic

These are the fundamentals that everything else in ServiceNow scripting builds on — whether it's a client script, business rule, or script include. 

The Lesson in the Mistake: Camel Case Matters. 

That last task turned out to be the most valuable one — not because it went perfectly, but because it didn't. I ran into a validation error and, after digging in, found the culprit: I had written LogFormValues (capital L) in my Script Include, but referenced it as logFormValues (lowercase l) in my Business Rule.

JavaScript is case-sensitive, and a mismatch like this — even a single letter — breaks the connection between a Script Include and the code calling it. It was a great hands-on reminder of why consistent Camel Case naming conventions aren't just a style preference in ServiceNow development; they're functionally critical. Lesson learned, and one I won't forget. 

Key Takeaway: 

Week 7 was a great reset back to fundamentals. AI tools and agents are powerful, but they still run on top of a platform built with scripting logic — and understanding that logic (down to the letter case) is what makes troubleshooting and customization possible. Small details like camelCase naming can make or break a script, and catching that early is a skill in itself.