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.
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.
YouTube video: https://www.youtube.com/watch?v=8_yHYAPDpvw
The live coding team: josh.nerius, ctomasi
This week, we returned to the topic of OAuth and learned how to generate OAuth tokens per user instead of per REST Message/Method. When calling some APIs, sharing a single token between every user in ServiceNow is not always appropriate and instead we want each user to have their own token.
Examples: Calling the Dropbox API and interacting with the currently logged in user’s files Calling the GitHub API and forking repositories on behalf of the current ServiceNow user Video Index 00:00 - Intro
Did you know it’s easy to give your users Unsubscribe and Manage Preferences links in your outbound emails?
This can be accomplished using two new macros available with the Istanbul release:
${NOTIF_UNSUB} ${NOTIF_PREFS} To use these macros, simply place them in the body of your notification or Email Layout.
What Users See Here’s an example of what users will see.
Clicking Unsubscribe Clicking Unsubscribe launches the user’s default email client and pre-populates the email with the information needed to unsubscribe.
The Istanbul release included the Automated Testing Framework. This is the first time that the platform itself has included any significant mechanism for automated testing. There are third party solutions such as Cerna’s CapIO but none actually included in the product until Istanbul. Let’s take a look at this framework in depth to see what it includes.
Tests: A list of all Tests cases defined on the system. A Test is basically one transaction from beginning to end and is composed of a series of Test Steps.
In Inbound OAuth Auth Code Grant Flow Part 1 - Getting Started with Postman, we configured Postman to use the new OAuth functionality available in Istanbul. In this post, we’re going to implement this functionality in a real web application.
A Few Notes About the Node.js “My Work” App The ServiceNow Interfaces team has released a series of sample applications that demonstrate the use of ServiceNow APIs. These apps are available on GitHub here, and are great resources for learning more about ServiceNow APIs and getting some example code up and running quickly.
This post is the first in a series about Import/Export topics. The goal is to get you up to speed on Import Set concepts and to walk you through the process of setting up an Import Set from scratch. While this initial post is focused on building an import set, we’ll dig into the theory and what happens behind the scenes in future posts.
If at any time you get lost on a step, skip ahead and watch the animated GIF summary for that section!
As highlighted in What’s New for Developers in Istanbul - Integrations, APIs, Authentication, the Istanbul release introduced Outbound Web Services Logging. This feature is a major quality-of-life enhancement for anyone working with integrations, and some potential benefits include:
Write fewer gs.debug/log/info/etc. statements in your code and simplify the debugging process Quickly pinpoint the source of an outbound HTTP request Look at the history of requests made by a particular integration Analyze the volume of requests made by a particular integration What gets logged?
In the Fuji release, the old JavaScript debugger was removed from the interface. The functionality never quite worked correctly and led to frustration and poor user interface. Since then, a new debugger was written from scratch and as of the Istanbul release it is in the product. The focus is really on usability and performance and I expect that developers will be quite happy to see this new and improved version.
As highlighted in my New Integration/API and Authentication Features Blog Post, Istanbul introduces two new inbound OAuth 2.0 flows:
Authorization Code Grant Flow Implicit Grant Flow These flows allow you to build apps that interact with ServiceNow APIs without needing to be directly aware of an end user’s username/password. Some possible use cases include:
Building a mobile (iOS or Android) app that interacts with task records in a ServiceNow instance Building a web application that interacts with ServiceNow on behalf of your users This blog post is a quick tutorial to:
