Week 4 (Modules 7 & 8)

Scripting, Migration, and Instance Security: 

Client scripts live in the browser and handle things like showing a message or updating a field in real time. Server-side scripts run on the application server and handle the heavier lifting - database changes, real business logic. Every time the client has to ask the server something, that's a round trip, and round trips cost time. Good ServiceNow admins default to client-side when they can, and only reach for the server when they have to. 

UI Policies vs. Data Policies vs. Business Rules - three tools that can look Interchangeable until you actually need one of them: 

• UI Policies control what a field looks like (required, hidden, read-only) - client-side, and about experience, not security. 

• Data Policies enforce the same kind of rule, but on the data itself, server-side - so it holds even if someone skips the form entirely

• Business Rules run on the server when a record Is Inserted, updated, deleted, or displayed. The [Async] option is the one worth remembering: It queues the process so the user Isn't stuck waiting on the server to finish. 

In Lab 7.1.1, I put all three to work: a UI Policy that surfaces an "Escalate to Manufacturer' option only for Priority 1 Incidents, and a Business Rule that reacts when that box gets checked. The lesson buried in there: before writing a Business Rule, check whether Workflow Studio already solves it. Code should be the last resort, not the first Instinct. 

Update Sets are how configuration changes travel between Instances - dev, test, production - without anyone manually rebuilding the same change three times. I captured a change, exported it, then in a second lab retrieved it, previewed exactly what it would touch, and committed it.  Previewing before committing turned out to matter more than I expected - It's the difference between knowing what you're about to change and finding out after. 

Security Center in ServiceNow encrypts data at rest and in transit by default; however, the platform's security still depends on someone actually watching it - reviewing hardening settings, checking recommendations, keeping the security contact current. I spent Lab 8.2.1 in the Security Center dashboard, adjusting a hardening setting and a best-practice selection, and came away with the same takeaway that's shown up all month: Security Isn't a setting you just configure once. It's a habit you keep up.