Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field
Hi there,
Did you notice that when you set Breakpoints or Logpoints to a script field on the Platform UI, these stay "set" until you manually remove them? Even if you woould start a new browser session, the Breakpoints and Logpoints are still in place.
So how does this work?!
Breakpoints and Logpoints
A small recap for if you are unfamiliar with Breakpoints and Logpoints. There's some good reading about both on the Docs: Set or remove breakpoints and Set or remove logpoints. Also recently I've written an article about the Logpoints functionality which got added in the Orlando release: Forget about adding log statements to Server Side script, use logpoints! [Orlando].
Tables
Because it didn't seem session related, I thought might Breakpoints and Logpoints actually be stored on the database? A quick search on the tables gave me:
"sys_js_breakpoint" and "sys_js_logpoint"
So these though tables hold all Breakpoints and Logpoints set in your instance! So what can you do with this?! Well this is just a short article finding out some unfamiliar territory in ServiceNow and how some things have been set up 😀. Though what you can do with this is up to your imagination. For example:
- Instantly removing all Breakpoints / Logpoints;
- When cloning instances, cleaning-up Breakpoints / Logpoints;
- Change a line number quicker for a Breakpoint or Logpoint set;
- Change Breakpoint conditions quicker;
- Keep Breakpoints though only remove the condition;
- Etcetera.
So what you can do with this is up to your imagination!
---
And that's it actually. Hope you like it. If any questions or remarks, let me know!
| C |
If this content helped you, I would appreciate it if you hit bookmark or mark it as helpful.
Interested in more Articles, Blogs, Videos, Podcasts, Share projects I shared/participated in? |
Kind regards,
Mark Roethof
ServiceNow Technical Consultant @ Quint Technology
1x ServiceNow Developer MVP
1x ServiceNow Community MVP
---
