The recent addition of scripted REST APIs and API version support has really made working with ServiceNow integrations as easy and robust as they should be in this day of highly connected systems. Managing, supporting, and deprecating API versions can be a challenge if you don't have access to usage statistics. The Helsinki release take API management to a new level.
There was a recent question on my first Form Charts post regarding advanced conditions. Since it's not really documented I did some experimenting.
In the last example I used a simple report filter. Show the "All Incidents by Category" report where the incident location is equal to the current form's incident location. Using this form chart interface limits you to a direct field mapping (location = current.location).
If you require a more advanced condition such as an OR condition you'll have to jump over to the "Advanced condition extension".
In my nearly nine years of working with ServiceNow the one request I've heard the most is the ability to report on catalog variable values. There were some ugly solutions that could get you by but Fuji introduces an easier way.
Just because reporting is so easy in ServiceNow it doesn't mean you shouldn't try to make it even easier. I would encourage customers and especially vendors to consider possible uses for the new Fuji report sources feature to make reporting even easier for end users.
Yesterday's FujiForty reporting tip was pretty basic so let's get into some cool reporting features. The ability to embed a dynamic chart in a form is a completely new concept in Fuji. Viewing related data in embedded or related lists on the form can be helpful but humans can consume data so much faster with images.
I'm a bit old to search for easter eggs this spring but I did have a little adventure yesterday when I was trying to find all of the hidden report settings. Once you know where to look the new interface is impressive.