(Spoiler: This article isn’t about how to get access to the hidden pages, just an explanation of them – sorry)
Let me start this one by saying that pretty much everything of what you see in ServiceNow is written in Jelly. Recently many of these Jelly scripts include AngularJS but the core rendering engine is still Jelly (no idea if this is ever going to change because it’d be a huge undertaking – but one I’d definitely welcome with open arms!).
This goes for every field on a form, every UI action, the whole navigation, every dialog page, everything.
So the next question is then if it’s all Jelly pages, where are they stored? Even if we haven’t thought of fields on a form as UI macro before, we’ve all seen a part of the UI that the client wants us to change, and we spend ages looking for it in UI macros and UI pages only to come to the conclusion that it’s magic and somehow ServiceNow just makes it happen. Continue reading