Application Development
As Flow Designer gets more real world use, the feature set continues to evolve towards the needs of production customers. In the London release, one of those features is Subflows.
By its nature, Flow Designer is pleasingly fractal in nature. You build a Flow out of Actions. When you drill into Actions, the UI looks almost the same as the Action Steps build into the Action. Subflows are another layer of this fractal, allowing for reuse by building a piece of a Flow that can be reused in multiple Flows or even across the same Flow.
Along with the London release comes new APIs that can be used by developers. Here are a few of the ones of particular interest to ServiceNow developers. The full list is available here.
I have previously posted about starting Flows and Subflows with the startAsync() method, so if you want more detail check that out here .
Glide Security Utils There is a new API called GlideSecurityUtils. This is used for cleaning input and preventing things like script injection and cross-site scripting attacks.
If you have followed my work as a developer advocate for ServiceNow at all, you will have noticed that I love automated testing. Even before the original release of the Automated Testing Framework, I presented on testing at Knowledge15. This is really a chunk of the platform close to my heart. This year at Knowledge18, Boris BC
It is ServiceNow new release season! With the London release in Early Access, we will cover some of the features newly available to application developers. In this post, I will discuss one very specific topic - new ways in which Flows can be initiated. When originally released in Kingston, there were two ways to start a flow: on change or insert of a record or via a schedule. That has expanded, increasing the flexibility of Flow logic.
In New for Developers in Kingston - Flow Designer, Action Designer, IntegrationHub, I touched on the basics of Flow Designer.
In this post, I’ll spend some time exploring Flow Designer in more detail. Instead of trying to look at every aspect of Flow Designer in one post (that’d be a long post), I’m going to walk you through the process of creating a simple flow and we’ll touch on many of the core concepts in the process.
Jakarta introduces an exciting new feature called the Guided Tour Designer. Guided tours interactively walk users through the major components of an application. Here’s a 30 second animation that demonstrates a Guided Tour in action on the SLA Definition table.
The Guided Tour Designer allows you to build tours like the one you saw in the animation into the applications you create. In this post, I’m going to walk through the process of creating a simple guided tour for the “NeedIt” application used in the Developer Training content.
When we left Part 2 of this series, I had added an inbound email action to create GTD actions from forwarded emails. As this development project was always intended to be a demo tool as well, when it came time for us to do demos developing Angular Service Portal widgets I looked around for functionality to add. I had already done some experimentation with using ngMaterial to create a card interface for this Helsinki feature webinar so I decided to bring a similar interface into DoNow.
In my first part , I talked about the background of an application we are building. With this post, I want to get into the specifics of the first big problem I tackled.
In my previous GTD implementation, I used Evernote as the main tool. One of the features I got for free with that was the ability to receive email from arbitrary email addresses. Evernote gives you a private email address that you can use to forward email to the system, where it will be converted into a note.
I have been working on a skunkworks project with ctomasi, josh.nerius and a few other people for months now as a low level background task. One of the downsides in working in an evangelism role is that sometimes you do lots of things to communicate about developing without actually doing any development yourself. In order to change that, we carved out a problem space that all of us were interested in, had an opportunity to improve toolsets and would be something that we ourselves would want to use every day.
