While we’re talking about Table Builder, we should also address the new Formula Builder! Going off of Matthew’s comments about Tokyo’s focus on capturing the capabilities of newer developers, one attribute taken into consideration was how many people’s first exposure to coding is through using applications like Excel. Developers can also create Flows here as well, with their Trigger options limited to those pertinent to the selected table. Any flow triggered by your table will be visible here, including its status and other properties. In Tokyo, Table Builder truly represents a unified experience and fully enables that table-centric approach so many apps take. Naturally, the next inclusion to be made was that of Flows. All independent Application Files on the platform, finally elegantly organized to allow the developer to naturally bounce back and forth as we so often do when noodling on a development problem.“Many take a table-centric approach when it comes to building simpler applications,” said Matthew Ripley in his episode of Break Point, which couldn’t be more accurate! First, it was the inclusion of forms, then the inclusion of UI Policies and other rules. However, over time, Table Builder has acted like a macrophage: absorbing more and more things pertinent to the table itself. When it first came out Table Builder was just that - a place to construct a table. The author of an app template now has the ability to define which audience, either by role or group, has access to it if not everyone. Tokyo, however, has begun to lay the foundation for better governance around these templates. At the time, this meant developers could create a library of reusable application templates for anyone internally to deploy and build from. In addition to Flow Diagramming, San Diego also saw the release of Template authoring. asUser() runs the flow or subflow as the user specified (rather than the system).withRoles() temporarily grants the roles specified in the Flow Designer UI.This API, which enables developers to run flows, subflows, and actions from server-side scripts, gained new methods for the sake of impersonation. In addition to the improvements made to Flow Diagramming, there have been additions made to the ScriptableFlowRunner API as well. As promised, more triggers, actions, and flow logic are now available. Most of these changes revolve around Flow Diagramming - the new visual render released in San Diego. Similar to AES, Flow Designer gets a fresh coat of paint with every release - Tokyo is no different. These subsequent changes can then be imported back into ServiceNow with the click of a button! This enables the business to empower their users to make meaningful changes without the hurdle to learn about the platform, allowing people to work in an environment they are comfortable in. Tokyo has further expanded the audience of “decision developers,” in that these tables can now be exported into Excel worksheets. Instead of a dozen if-else statements, a developer could extract these complicated decisions in table to be interpreted instead. Within Action Designer, when the developer goes to add a new Step, the wizard displaying the various options is now a single column list (in contrast to the side-by-side columns it was in before).Įxporting & Importing Into Decision Builderĭecision Builder was recently released to abate the headache of countless nesting logic blocks within Flows. Let’s start things off simple! This may not make it to the headlines of the release notes, but to those who spend time building Flow Designer Actions, their lives will have been made slightly easier with a layout reorganization. Updates Layout of Steps in Action Designer
0 Comments
Leave a Reply. |