Orlando IntegrationHub Changes The Orlando release has been in Early Availability for weeks and GA is right around the corner. I previously covered the Flow Designer changes in Orlando and in this post I will do the same for IntegrationHub. Dynamic Outputs New York introduced Dynamic Inputs and now with Orlando we have Dynamic Outputs. These allow developers to define the data structure of a complex object programmatically and then use that as the output of an action.
Orlando Flow Designer Changes The Orlando release, as with every release since the original introduction, features a number of new features and improvements in Flow Designer and IntegrationHub. In this post I will look at Flow Designer specifically with a future post covering InterationHub. Create a flow with an SLA Task trigger In Orlando there is a new trigger type SLA Task and new actions that work with SLAs. This allows for SLA based logic to be written and maintaqined in flows.
Our Spoketoberfest celebration has come and gone. It was a spontaneous event prompted by a conversation in a hotel lounge in Bengaluru India. We hoped for the best but had no real expectations what the participation would be like. In the final analysis, we had six projects that attracted contributions from six developers (including myself). Although the numbers match, we had a developer commit to two repos and one repo with multiple committers so it wasn’t just one developer per repo.
Spoketoberfest is wrapping up. Some of you earned your shirt from Digital Ocean (I did this year). Some of you will continue to work on your Spoke to achieve publishabilty after the month has ended. Once you reach the point of feeling ready to publish your Spoke to Share, what then? In this post, I will walk through the steps. Pre-Publishing Checklist The following are some of the lessons digested from the Spoke best practices document
In the Developer Program, we have been soliciting platform feedback for some time now. Your feedback has gone into product planning around developer tools in the New York, Orlando and Paris releases. We absolutely want to continue to get your feedback but there is a more permanent and robust place for that now - the Idea Portal in Community. Not only can you submit your ideas there, but you can vote on other submissions and track the state through its lifecycle.
In a recent Live Coding Happy Hour we attempted to create some Dynamic Choices and Data Gathering Actions. That effort ran into some technical hurdles during the session but they have been sorted now. There are parts of this that are a little finicky, so I will walk through the necessary pieces. Why Use Dynamic Choices? The use case of this example is a good one for showing the power and necessity of Dynamic Choices.
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.