ServiceNow® Yokohama release - Top 5 new features

[Mark Roethof]

Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field

Hi there,

It's Yokohama family release General Availability week (Patch 1). With that, you cannot miss the massive amount of posts, articles, videos on parts of the Yokohama release, new features, top 10 picks, etcetera. I thought, let's also give it a try!

Attached the full PDF, and below an extract of my top 5 picks.

#1: CICD Update Set API

#2: Data Management Table Cleaner

#3: Debug flows and subflows

#4: Evaluate the performance of a portal page

#5: Workflows in Workflow Editor deprecated

Bonus: Release Notes 

---

That's it. 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? - Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field

Kind regards,

Mark Roethof

Independent ServiceNow Consultant
10x ServiceNow MVP

---

LinkedIn

[mandamni]

Hi team,

The workflows will be totally decommissioned ? 

[Steven Parker]

I just found this doing a Google Search...

Workflow Editor is always our primary way of building a workflow in ServiceNow.  Flow Designer has too many issues and inconsistencies to ever consider it to be used fully (compare Input Strings in a subflow in an If Statement for example).  I can't rely on something that is inconsistent.  Flow Designer default limitation on activity count per flow (unless you change a system property), performance issues on larger flows, version history is bad, setting or changing stages in general is aggravating, visually hard to follow for someone not use to it, etc, etc, etc...

[brandonharp]

I think one of the biggest oversights in Flow Designer is the lack of string utils needed for comparison to trigger rules to help simplify strings and not just do really thoughtless comparisons on strings.  That one thing alone makes it borderline unusable.

Easily the biggest offender is not being able to compare things using case insensitivity.  So if someone emails Me@Domain.com me@dOmain.com etc, its impossible to make even simple email rules reliable and work correctly as you would have to click + 9000 times and add each case variation you can think of rather than just write a simple function to convert the string to lower case, or run any string functions on it in general.

Maybe that's been fixed in newer versions as I haven't had to work on a flow in a bit, but it seemed like the matching logic was overly simplistic as you can't normalize strings/have ways of dealing with arbitrary strings and compare them to other strings in ways that are normal if you could just write code instead.