IntegrationHub week is still going strong! The last two new Paris related features I will highlight on the blog will be the Payload Builder API and the JSON Parser action step. JSON Parser Building and extending spokes is one of my current favorite things to develop. One of the most common parts of integration is handling the response. Introduced in the New York release was the XML Parser step. With the Paris release, the other main format, JSON, is handled with the JSON parser step.
Join us as we cover a few of the new developer features in the Paris release. Chuck is joined by special guest ServiceNow Sr. Software Engineer, Dave Slusher. Dave is a familiar name (and voice) to the developer community. For several years he was a former Developer Advocate and co-host of Live Coding Happy Hour and TechNow. One detail - this discussion covers a lot of the Flow Designer and IntegrationHub features - fear not!
It is ServiceNow’s new release season! With the Paris release in Early Access, we will show some enhancements targeted around being more effective and efficient as a developer. To get access to these new things, you have to upgrade! This article will be about a new feature in IntegrationHub. To view the whole list, check out the release docs. Connection Manager Dashboard The connections dashboard is a new interface inside Flow Designer to manage connections.
I’ve got three more Flow Designer enhancements to make your lives a bit easier. They are: Action instance ordering Ghost actions Duplicate action instance Action instance ordering The first is pretty straight forward. Prior to Paris, action numbering was “outline based”. Every time you added a new if, for each, or other action that created an indent level, a decimal was added on to your action numbers. While this may seem innocuous at first, it could make inline scripting challenging when referencing action 3.
Flow Designer received many new features and enhancements in the Paris release, and I’m going to focus on the intersection of Flow Designer and Service Catalog for this post. Flow Designer is an important component in automating the process behind Service Catalog requests, and every release brings a tighter integration and additional support for the catalog in Flow Designer. Submit Catalog Item Request action The first enhancement is a new action that ships with Paris called Submit Catalog Item Request.
It is ServiceNow’s new release season! With the Paris release in Early Access, we will show some enhancements targeted around being more effective and efficient as a developer. To get access to these new things, you have to upgrade! This article will be about two new features in Flow Designer. To view the whole list, check out the release docs. Run with Roles One new enablement is Run with Roles in the trigger settings for a flow.
Use Branches on Make a decision Flow Designer continues to improve in the Paris release. If you haven’t at least started exploring Flow Designer, or made the commitment to create your new business logic using Flow, we’ve got a couple more features in the Paris release to tempt you to take another look. Existing Flow advocates are going to love this too! First, the Make a decision logic has been improved to include a simple checkbox labeled Use Branches.
We hope everyone has been enjoying the Knowledge 20 Digital Experience and great deal of associated content over the past 5 weeks. Since there is so much content it can be difficult to browse specific topics or know where to focus, so we want to help by calling out some of that content in a series of posts. This post is focused on all of the sessions we found related to Flow Designer broken down by session type.
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.
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