Announcing the Contextual Search Results Widget

UPDATE: Now with updated pricing! Available now in the ServiceNow app store! With the NewRocket Contextual Search Results Widget your company can achieve incident deflection in the Service Portal. As self-service users enter details about their issue, search results appear within the form, allowing the user to view relevant knowledge articles, catalog items, or social Q&A thread instead of submitting an incident. The result: less incidents submitted and more satisfied users. Key Features - Integrates with existing record producers - View search results while typing - View individual result items without navigating to a new page - Simple to configure to show relevant knowledge articles, pinned articles, social Q&A and/or catalog items https://www.youtube.com/watch?v=HodilTSd6rg Click here for more details and pricing information!

Communicating between the Client Script and the Server Script of a widget

We've had a lot of questions about how the client side and server side of a widget can communicate, so this week I thought it would be a good idea to offer a quick demonstration. In this tutorial we will create a widget that allows the user to add or remove items from a list. In this case it's just a simple Array, but it could just as easily be using GlideRecord against a table. Here is the sample code used in the video: HTML: [crayon-5974cea218249862597736/] Server Script: [crayon-5974cea21827c229969224/] Client Script: [crayon-5974cea21828a290889531/]

Service Portal “Gothenburg” Theme

A quick demo of one of our themes for Service Portal. Features include: Shopping cart Multi-level categories (for both service catalog & knowledge base) Connect chat integration Create incident Contextual search Almost every page and widget has been redesigned to help improve the user experience. Let me know what you guys think.

ServiceNow Point of Sale System – Hackathon 2016

Last week at Knowledge I partnered up with Robert Fedoruk and Travis Toulson for the CreatorCon Hackathon. We had a blast and I think we did pretty well for only having 8 hours to put the application together. Our application was a real-time point of sale system on ServiceNow. In many organizations, a good percentage of employees will still approach the help desk directly without going through self-service. This forces the help desk to manually create the requests on the spot. There isn’t really a quick and easy interface for this, so having a point of sale system would greatly expedite the process for face-to-face transactions with the help desk. We built our application using Service Portal making use of record watchers and integrated it with the native mobile app for bar code scanning. It uses the Service Catalog and with no custom tables needed. The application was built with touch screens in mind with support for gestures. And best of all the whole application operates across multiple devices all in real time. When the transaction is complete, it sends a push notification receipt to the users mobile device. Could your organization use an application like this? If so I would love to hear about it. It’s not just limited to point of sale, could also be used for inventory management, supply chain management, warehouse management, etc.

Geneva Service Portal – Creating a “Hello World” widget

In this tutorial I create a simple Hello World widget that makes a call to the server to retrieve the "name" of the user based on the "username" entered in the input. This tutorial is specific to the Geneva version of Service Portal. Also in case you missed my big announcement made earlier today: I'm now available for contract work. HTML Template: [crayon-5974cea21ac10637152468/] JSON Data Producer: [crayon-5974cea21ac23294201547/] Client Script: [crayon-5974cea21ac2f810599387/]

Custom Content Block Types

This is one of those secrets I wish I would have discovered years ago because it really opens a world of possibilities within the CMS. This method was revealed to me by Brian Alson. There's a few other ways of creating custom blocks types like this, but this one is by far the easiest. If you're creating a block that will contain "child" records, such as a slideshow, then I would suggest extending the child table from "content_link" table and either create a M2M table or a parent reference field back to the content block. I would love to hear your comments or feedback if you guys find this useful.