reetings from ServiceNow’s annual Knowledge conference! For myself, and all of the people at Crossfuze Solutions, we’re already in the thick of things assisting with pre-conference training. ServiceNow always puts on a great conference, and we’re excited to be a part of it. Crossfuze is a conference sponsor again this year so please stop by to see us at Booth 631! We would love the opportunity to say hello and show you we’re delivering world-class ServiceNow solutions with one of the highest customer satisfaction ratings in the ServiceNow partner ecosystem.
Crossfuze Solutions is pleased to partner with BDNA to host a VIP dinner at Knowledge 15. Space is *extremely* limited, so we won’t be able to invite everybody who wants to come. However, if you are going to be at K15, and you are available on Tuesday at 7:30, add your name to our request list, and we’ll try to invite as many of you as we can.
Sign up for this unique K15 VIP dinner event on BDNA’s website.
Record producers are a great piece of ServiceNow functionality that allows for the creation of records in any table via the standard Service Catalog interface. This capability has been around for quite a while and odds are that you’re already using it in your system to allow end-users to create new incidents…among other things.
Over the years I’ve worked with ServiceNow, I’ve seen several requests to be able to report on or identify the record producer used to create a particular record. This would allow for easier identification of the entry point for record producer transactions. Unfortunately, ServiceNow doesn’t give us a simple way of accomplishing this. Even though there is a record producer ‘Script’ field and a ‘producer’ script object to work with, nothing is built to be able to dynamically identify the record producer used. This means that you’re stuck hard-coding values in a script or adding unnecessary variables to your record producer forms for every single record producer in your system. Read on for a fairly simple solution to this problem!