Application Development

Andrew Barnes

8 minute read

The ServiceNow Developer Program recently went on the road to visit London. NowForum: London edition featured one full day of content just for developers with 800 attendees. The second day which was for all things ServiceNow had 2,500 attendees. Dave Slusher, Chuck Tomasi, Jason Mckee, and Andrew Barnes were all teaching workshops on day 1 of the event. You are welcome to jump down to the event proper if you don’t want to read about my travels!

Andrew Barnes

2 minute read

Developer Days From now until the end of the year ServiceNow and the developer program will be hosting events at several locations around the world. Dave Slusher and Andrew Barnes will be at several of these events. We hope you are able to attend and meet in person while learning more about ServiceNow! The one day events are typically focused on the new developer. The 2nd of a two day event is targeted towards moderately experienced developers.

Dave Slusher

3 minute read

Over the weekend I ran into a problem that gave the “too many errors: 88% scanned” error in one of my Script Includes. I had to figure part of it out on my own and then lo and behold andrew.kincaid also answered it in the community yesterday. When I presented at the inaugural ServiceNow Developer Meetup in Seattle, I did a demo of the Istanbul Script Debugger. I noted that in the application I am currently developing, almost all of the serious logic lives in Script Includes.

Dave Slusher

8 minute read

This is a continuation of the trip report of our trip to India for Developer Days. Part 1 is here. After concluding the Hyderabad Developer Day event, we rolled right into the evening program. The reason for having a separate event in the evening was two-fold. It both allowed for us to serve the population of people who couldn’t take the whole day off work but also was intended to build an organization around an ongoing Hyderabad ServiceNow Developer Meetup.

Dave Slusher

8 minute read

The ServiceNow Developer Program recently went on the road in the form of a road trip to India. This will be a bit of a departure for blog posts here in the form of a trip report. We will return you to your regular diet of nerdy technical posts shortly. India is an important market for the Developer Program. By any metric you choose to examine, it is always the second largest demographic behind the USA.

Dave Slusher

23 minute read

In the developer program, we have a program where on many Fridays a group of us get together and broadcast ourselves working through code problems. If you’d like to get notification of when we go live or post a new episode, you can subscribe to our YouTube Channel. Here is a list of all the shows to date, grouped by subject matter. Note that episodes may contain multiple subjects and may appear in multiple lists.

Dave Slusher

8 minute read

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.

Dave Slusher

6 minute read

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.

Dave Slusher

4 minute read

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.