FujiForty - Must Have App Publishing Checklist

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.

FujiForty - Form Charts (advanced conditions)

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".

FujiForty - Getting in the ServiceNow Store

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.

FujiForty - Test Management

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.