Three weeks ago, I built an app without writing a single line of code. Last week, I was linking my work to GitLab and debating who should be allowed to see which fields. That's the jump Rise Up took me through, and it taught me a lot. 

Week 8: An App in an Afternoon. 

App Engine Studio let me go from a spreadsheet to a working app, no code needed. I imported data into a ServiceNow table, built a request form with a Record Producer, routed requests with Flow Designer, and set up automatic email notifications. 

The takeaway: you can go from idea to working workflow faster than you'd expect.

Weeks 9 & 10: Slowing Down to Build It Right. 

Then came the other side of the platform: application development fundamentals. Before writing anything, we asked the questions that separate a good app from a messy one. Is ServiceNow the right fit? Global or scoped? How should the schema and interface be designed? 

Those questions led straight into the Loaner Request app. 

Building the Loaner Request App. 

After reviewing the design document, I used ServiceNow Studio to create the app, its module, a Loaner Request Users group, and a form with an Employee Self Service view. 

Then I made the form smarter:

• A UI policy that shows and requires an "other" field only when needed

• A client script that fills in and locks fields based on other fields

• Server-to-client data to auto-populate a field

• A business rule for data validation

My Safety Net: GitLab. 

I also did the optional lab to connect the app to source control. I created a private GitLab repo, generated a Personal Access Token, and added my credentials in ServiceNow. My existing update sets stayed intact, and now every change I make is tracked.

The Concept That Humbled Me: Controlling Access. 

I'll be honest: access control has been the most important and the most confusing topic so far. It decides who can open the app, who can touch which records, and how scripts and web services interact with your data.

It finally clicked in Lab 5.1.1. I applied access strategies across the app's modules, records, fields, and views, then committed the changes. Configuring table-level application access (CRUD, web services, scripts) made it real. 

What I'm Taking With Me

1. No-code and pro-code work together. One gets you moving; the other gives you control.

2. Design first. Early schema decisions shape everything after.

3. Use source control from day one.

4. Security takes practice. It only makes sense once you apply it.

Next up: finishing the Loaner Request logic. I'll share more as I go.