Since many of the projects I work on are integrations I'm frequently working with custom orchestration activities. Most of these also involve some sort of REST interface. The introduction of ServiceNow's REST Inspector was a huge help, but I wanted to introduce you to another tool I found extremely useful. It's RequestBin from Runscope.
The Geneva release introduces a couple of changes to business rules you should be aware of.
Tired of fumbling your way through ServiceNow processor scripts to piece together an integration endpoint? Well it's time to throw out all those hacked up solutions floating around on the community and discover scripted REST services in the Geneva release!
Most admins are familiar with reference qualifiers and advanced qualifiers that can leverage data from the current record to filter a reference field lookup. If you want to qualify or filter a list of records that display when using the edit button on a form's many-to-many related list, things are a bit trickier.
After the initial frustration with a locked down and undocumented Fuji scripted processor API I avoided them as much as possible. But sometime you just can't avoid them. I recently had a need to build a REST-like integration because the client app couldn't use SOAP, so scripted web services weren't an option. Since scripted REST services don't exist...yet, I needed to use a scripted processor to capture a POST request with JSON and return a JSON payload.
Fix scripts aren't really new in Fuji, but with the upcoming launch of the app store driving more vendors to publish applications it's worth pointing out why they exist.
Protecting your proprietary ServiceNow scripts is great option in Fuji. The problem is the customer loses the feature they love the most, the ability to customize anything they want. The customer could create their own script include that extends a protected vendor class to override methods but this solution has limited usability. It's not always possible to change the script that is instantiating the class to point it at your new class. Let's take a look at how the new GlideScopedEvaluator API can help us.
There are a few nice string utilities you might be used to using in the GlideStringUtils scriptable class. For my FujiForty followers I'm sure you know where this topic is going. You got it, it's not supported in ServiceNow Fuji application scopes.
With the introduction of application scopes there are a couple ways we can instantiate script include classes depending on the scope our process is running in and the scope of the script include.
One of the powerful and efficient concepts found in the ServiceNow platform is the ability to extend existing table schemas. This not only makes table creation faster and easier, it also allows you to inherit business processing logic and report on an aggregate of data across hierarchical tables. For example, a worker can display all of there work in a single queue even though the data appears to be in different tables.