Today we are seeing almost as much ServiceNow content creation onlinethan we are seeing new ServiceNow features! Much of it, particularly older content, is not linked to versions or superceded by new best practices. I’ve reflected on this, and updated all my previous blog posts and reflected on how we got here.

I’ve been leveraging Catalog Builder recently to enable customers to better manage their own Service Catalogs. Developer resourcing is hard to find, and it is no longer a reasonable expectation that a data fix or new field added to a form should take weeks or months. If you know how to get the most out of it, Catalog Builder is a great tool for customers short on developers to make changes but they still need some guidance. There aren’t a lot of practical resources online, so I decided to write all about it.

v1.92 Bug fixes Fixed an issue where guided setup item ‘Install Additional Features’ was missing,…

Last week I was invited to join Ashutosh Munot and Dhruv Gupta on their podcast Laten We Praten, which translates to ‘Let’s Talk’ from Dutch to English. Ashutosh is a three-time ServiceNow Developer MVP, a five-time Community MVP, and a Certified Technical Architect, which is no mean feat. Dhruv is also a three-time ServiceNow Developer MVP and a Google Hall of Famer, so I was honoured to join them to discuss my journey into ServiceNow, ChatGPT, ATF and more.

You can listen to the episode on Apple Podcasts or Spotify.

https://podcasts.apple.com/us/podcast/laten-we-praten-special-guest-paul-morris/id1559908996?i=1000603023501

We are approaching upgrade time again, and it’s time to dust of your tests from last upgrade. Just like last time, you told yourself next upgrade you would have regression tests ready to go, but you probably haven’t. Why should you? And how can you do it qucker and cheaper?

Everyone has been talking about ChatGPT and the cool things you can do with it. This had me wondering – can it do something useful in ServiceNow? Can it, perhaps, improve my code?

In my blog, I try to use ChatGPT to refactor some code.

Last month I wrote a blog called 6 mistakes to avoid when using Flow designer that listed the six most common mistakes I see when reviewing other people’s flows. The post was followed by a great discussion on LinkedIn, with heaps of additional suggestions to help people write better flows.

This month I have decided to extend the list with another 6 things to avoid.

As a development lead, I have had the pleasure of reviewing many a flow, usually created by developers who are either new to Flow designer or have recently migrated from using Workflow Editor.
I would like to share the top 6 mistakes that I see.