Week 1: General Overview of the ServiceNow Platform

Week One of ServiceNow RiseUp Advanced Foundations was a lot of "okay, where is that button" - In a good way. I went in knowing ServiceNow by reputation (I've worked with ServiceNow at a previous employer) and came out actually being able to navigate a developer Instance without guessing. 

Getting my bearings. 

The first real task was setting up my personal developer Instance (PDI) from a user story. I used Theme Builder to relabel the browser tab "CD DEV" so I could tell it apart from anything else I had open. This helps if you have multiple tabs open across labs, and it actually saves you from editing the wrong instance at some point. 

Users, groups, roles, lists, forms, records, tables, applications - these are key terms used throughout the platform, and week one Is really just learning to speak it. Nothing here is hard conceptually. What's hard is remembering which noun does what when you're three menus deep. 

Locking things down: 

The access lab was the first one that made me slow down. I granted a role access to an application, then had to actually verify that it worked - not just assume It did. It's a small step, but It's the difference between configuring security and knowing your security configuration actually holds. 

This was probably my favorite part of the week, mostly because it reframed something I thought I already understood. 

I created Incidents the "old" way first - Classic Lists and Forms - which is basically ServiceNow's equivalent of learning stick shift before automatic. Then I did the same task within the Service Operations Workspace, which Is faster and more modern, and the difference was noticeable immediately: less clicking, more context In one screen. Then I switched hats entirely and checked Incident status through the Employee Center - as the person who submitted the ticket, not the person working It. Seeing the same record from the requester's side made something click: agents and end users are often looking at completely different amounts of Information, and that gap matters more than I expected. 

I also built a custom list view from scratch - new core lists, plus a new application and module to just give people a way to navigate to It. It's a small thing, but It's the first time this week I built something rather than just configuring something that already existed. That distinction mattered more than I expected It to. Two smaller labs rounded out the week: adding a new field to a form (no code, just configuration - still felt slightly magical lol), and setting up category/reference values with auto-assignment so records could start routing themselves to the right team. 

What I'm taking into week two: 

If I had to boil the week down: ServiceNow's core objects (lists, forms, records, tables, fields) aren't complicated on their own - the skill Is knowing which lever to pull for a given business need, and week one was mostly about building that Instinct