FujiForty series concludes with a list of recommendations that will help you make the most of your ServiceNow technology partner offering.
I spent the past year dedicated to working with ISVs building apps on Fuji EA and GA releases. I realized that I have a pretty consistent and structured checklist that I follow for building and reviewing applications, although it's all been an auto-pilot process in my head. Some may say I’m giving out my secrets, but since CAVUCode is all about empowering vendors so they can manage their own applications, I’ll share my process.
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".
I've mentioned the marketplace or store in plenty of earlier posts. Yesterday during the Knowledge15 conference the ServiceNow Store was officially launched. CAVUCode was involved in launching two certified application which are now available in the store. Here's a run through of what it takes to get an application into the store.
Whether end users or QA engineers believe it or not all developers perform tests on their code. Sometimes it might not be as accurate or detailed as it should be, and sometimes it's not even documented. A developer knows the use cases they are coding for and can be sure to test for those cases. Handing an app over to QA may not always include a list of the tests performed or the expected results. This somehow needs to be captured by the product manager and/or the developer depending on the organization structure.
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.
I've been lucky enough to be involved in many of the Fuji development tools since early alpha stages. One tool I've seen a lot of progress in is a conversion tool that allows you to convert pre-Fuji application update sets to scoped application.
Visual task boards received some minor updates for Fuji and they are starting to get more traction with users. As an application builder you might be interested in including boards with your application. Unfortunately it's not that easy.
Administrators have been "personalizing" lists and forms in ServiceNow for years. It's time to mix up your lingo a bit. Now administrator "configure" list and form views when they want to define the global default for all users.