I love jelly! I love jelly! Oh wait, I'm just so comfortable with jelly that I've hesitated to even look at the new Service Portal features in fear of having to get my head around angular and portal concepts before I could actually do anything interesting. If you're anything like me, don't hold off any longer. I took the plunge and the water is great. Here's my first project.
It's not always easy to discover when and how to access orchestration and workflow input and activity output values when designing a workflow in ServiceNow.
Ok, forty-two ways might be a slight exaggeration. We'll take a look at a couple shortcuts, some frustrating limitations, and an easy consistent solution to speed up your workflow development.
The recent addition of scripted REST APIs and API version support has really made working with ServiceNow integrations as easy and robust as they should be in this day of highly connected systems. Managing, supporting, and deprecating API versions can be a challenge if you don't have access to usage statistics. The Helsinki release take API management to a new level.
"How do we backup our app and manage file versions?" This is usually one of the first questions I get when I start working with a new software vendor who's building an app for the ServiceNow store. Before the Helsinki release, developers needed to resort to exporting a copy of an application update set for offline storage, or leverage team development to copy code to another instance. The Helsinki release introduces source control from within the instance.
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!
As we saw in the last post, the ACL execution plan adds great value in helping admins understand the access control processing model. Another possibly confusing area involves the way users inherit group memberships and security roles. Let's take a look at how the new Role Inheritance Map in Geneva can help visualize a user's inheritance model and save us a lot of clicking around.
Believe it or not, after working with ServiceNow security for nearly 10 years (and being the security product manager for a while), I almost have it figured out. It didn't really take that long but understanding the laws of security rules doesn't come quickly. Finally, with the Geneva release, things are starting to get slightly easier to follow. Believe it or not, after working with ServiceNow security for nearly 10 years (and being the security product manager for a while), I almost have it figured out. It didn't really take that long but understanding the laws of security rules doesn't come quick. Finally, with the Geneva release, things are starting to get slightly easier to follow.
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.