HAHAHUGOSHORTCODE-0xc00104d400-1-HBHB For the past several years, we have piggy-backed on the Digital Ocean event of Hacktoberfest. It started in 2017 when Josh Nerius and I put together a system to allow ServiceNow developers to accept GitHub pull requests. This year, again we are attempting to parasitically attach ourselves to the event but with a twist. Because it is a ServiceNow goal to increase the number of IntegrationHub Spokes in the world, that is what we want to focus on this month.
Developer Days In India The ServiceNow Developer Advocacy team just completed a lovely and extended visit to India. India has the most significant number of ServiceNow developers outside of the United States of America. Having so many developers makes it a pivotal place to visit to engage, empower, inspire, and listen to developers. The key events were developer meetups and all-day workshops at multiple locations. Dave Slusher - an experienced hand at India trips - and Andrew Barnes traveled from the east coast of the USA.
As we wrap up our coverage of the developer features of the New York release, we would be remiss if we didn’t talk a little about Studio itself and the developer tools it enables. Conditional Breakpoints Speaking for myself, I am a heavy user of the Script Debugger. It is a natural part of the way that I develop to want to watch values as they change in the actual running code.
Dynamic Inputs One of the great features in the New York release is the inclusion of Dynamic Inputs. It can be tedious to develop a Flow when it requires a script step to transform data from one form to another. Dynamic Inputs to the rescue! Imagine the case where the inputs to an Action inside of a Flow are based on the data outside of your instance such as creating a record in an external system.
As the tour of New York features continues for Early Availability season, we come to one of our favorite features around here - IntegrationHub. Over time as the feature set becomes more robust, more and more of the functionality we create is via IntegrationHub. OpenAPI Support As of New York, there is now support for Open API. For those familiar with the WSDL concept in SOAP, this is much the same type of thing.
Over on the Acorio blog, Meghan Lockwood published a list of 27 ServiceNow professionals to follow. All of the present and former developer advocates of this program were on that list: myself, Andrew Barnes and Josh Nerius. It is a great honor to be included in this list. Speaking for all three of us it is a proud moment for everyone. Thank you Meghan! If you are looking for information and inspiration related to the Now Platform, that list is a very good one to follow on social media.
Guided Tours is a ServiceNow feature that doesn’t get quite its due as the powerhouse it is. It is really a great way to increase user satisfaction and remove that bit of frustration when rolling out new functionality in your instance. Inside the Developer Program itself, when we rolled out a feature for Meetup reimbursements we added a Guided Tour to explain all the steps. In New York, there are a few key enhancements to make this great feature even better.
As we discuss the new features of New York, it is only natural I should discuss first one of my great loves in the platform - the Automated Test Framework. Every release since it was introduced expands the capabilities of this tool and New York is no exception. Here are the highlights but the full list is here. Parallel Testing and Mutually Exclusive Tests In previous releases, ATF ran effectively a single thread of testing.
New York is Released!! It is that time of the year, new release Early Availability time. It’s my favorite season of the year! New for Developers in New York Studio - JS Beautify, Conditional Breakpoints, Context Menu updates Automated Test Framework - Mutually Exclusive Tests, Create User step, Rollback Browser Flow Designer - Complex data and scripts, Inline Scripts and Editor, Inbound Email Triggers Mobile Studio - for migrating Madrid mobile apps to the New York paradigm Those are just a few of the highlights you will find in the New York ServiceNow release.
One of the unsung features in the Automated Test Framework is that you can use it to test your Scripted REST APIs. I’m a fan of having as much robotic coverage as possible, so backstopping API development with tests is a good thing. Let’s look at how to do that. I will use an example of a relatively recent API that I developed, the commenting system on this very blog. I’ll create a test that: