[Music] thank you foreign [Music] hello everyone and welcome to Creator toolbox a show brought to you by the servicenow developer program where we demo the newest latest and greatest servicenow features for every developer's toolbox we are in the middle of our Vancouver release officially on week two of the content so be sure to check out the content calendar at devlink.sn Vancouver thank you so much Earl for putting down the link before we jump into the content today which you can tell I am extremely excited for let's go ahead and do some introductions first because we have some new faces on today's live stream I'll kick things off my name is Laura McManaman I am a member of the developer Advocate team alongside the likes of Chuck tomasi Earl 2K and Prana bhagat um I just had my sixth anniversary at servicenow which is very exciting and was formerly a member of the Creator workflows SC team so that's why a little bit of my bias shows through on some of these low and no code features so I will kick things over to the gentleman on my race hi everyone My Name is Earl Duque I am a senior developer advocate here at servicenow I just had my two year anniversary here at the company but before that I was doing servicenow development for three different customers over the course of six years-ish uh from anywhere I think I started from an admin and then went all the way to team lead as a developer uh mostly in higher ed so multi-tenant space is my my the name of the game for me uh and all that kind of extra organizations all over the place and for them hey I'm Brian bimschlager I am a PM for some of our workflow automation products here at servicenow uh I've been here about three years now a little bit more and I've worked on everything from a flow designer to pad and I'm working on some cool new stuff now so uh very excited to join thanks for having me well we're excited to have you uh so for last year I believe it was Jake Berman that we had on the flow designer specific call and I kind of used it as an opportunity to kind of test my own Acumen and overall like proficiency of flow designer so you can kind of sit back and relax and help me kind of dive into the deeper facets of what has changed in the Vancouver release so sound good for you sounds good awesome well the first thing I wanted to call attention to is one of the intangible or at least there's no UI representation of this change which is the overall performance enhancements made to the speed of flow designer this was something I kicked off in the Vancouver Tech now presentation was that there was some substantial reductions in time due to kind of some not Renegade API calls but just some more like back-end API calls that were going longer than intention so do you have any like background on that or like how'd that process go yeah so one of the things we identified you know both from our own internal testing and from a lot of discussions with customers was that big flows took a long time to load or flows that had a lot of subflows in them and yeah or behind the scenes it was something like we were just trying to load everything all at once a lot of repeated calls to make sure we had everything and we just took a better look at how we were trying to get all that content in the first place and now it's a little bit more sequential a little bit more Progressive uh with really an emphasis on getting you to see anything in your flow a lot sooner and having it be a lot more responsive when you make changes so there's a lot of stuff under the hood but as you noted Lauren it's really one of those intangible things where the overall feel of using flow designer should just be a little bit snappier and not as sluggish as you may have recognized in previous releases well I love that that's I think the specific numbers called out where like a 95 reduction in time to like load flow designer I think it was 98 to like overall logic and then 99 for the like relationship between subflow and flow which was really that part in particular I was like oh my gosh that's phenomenal yeah I mean it was one of my old things notice when people were loading in flows that had a lot of subflows it was a big big performance hit and that's you know frustrating because a lot of what we communicate out to our customers says hey you should build modular you know operate in subflows first and use those within your parent flows and we had accidentally created an environment where that was a sluggish process so we're really pleased that now what our recommendation is for building flows is actually a fast and usable experience as well yeah I'm still in my past Works uh chat and maybe every month I see them say this flow takes so long to load no I like the trend I think I think so excited about Vancouver is I mentioned earlier that I was on because I'm so excited for people to try out flow designer but there's always two specific like reasons that they usually like oh we'll just stick the workflow editor one was the speed right of like oh like I can do things I can code faster or the thing loads faster sometimes in workflow editor which I don't think is true anymore and also the kind of grand finality of today's thing which I'll I'll leave towards the end as I've teased it I think people can probably guess what I'm talking about but we're gonna see that today as well which is exciting so enough kind of waxing uh poetic about the intangible or like hopefully intangible like speed is one of those things where like if it's great you shouldn't notice it right you won't miss it when it's done when it's not really up to par so let's talk about the things that are visibly tangible changes to flow designer so I'm going to go ahead and actually showcase my instance one thing that I like to do with flow designer because it is a platform feature is I really like to Showcase it from a personal developer instance PDI as they are also known are instances that you can get today for free that is a remarkable asset that people do not take advantage of enough so today if you go to developer.servicenow.com you can get a free instance of Vancouver to play around with that is what I'm using here today so everything that you see is something within your bounds now the first thing that I notice as someone that's used flow designer a lot is we have finally gotten The Branding up to date which is really really exciting so no more pastels no more um like what was the the color name was it Mint or uh yeah mint I think the the new color is uh wasabi green Wasabi I hope nobody from brand is watching because ironically I we haven't updated the background for this show yet great now we're the ones behind well beforehand we had excuse of like well it matches the platform um so now I know I know we'll we'll find we'll we'll make it on canva we could do our best all right so the other thing that I noticed aside from this now being wasabi green is the fact that this is a new homepage beforehand which if we scooch on over I actually have an instance of Utah up ignore how The Branding also changed on Utah but this was the previous home page which was very similar to just a list on servicenow now granted it was It was kind of tabular with what you're looking for but this is no different than opening up just a generic list that kind of is the it was kind of like an outlier compared to how everything else was moving much towards a dashboard-like experience you saw that with app engine Studio you definitely saw it with um like uh the UI Builder and things like this it's all becoming more modular and wizard like in design so we see that now reflected in flow designer so we have our standard list here however on the right hand side we see some interesting things one thing is I see what I was testing before the this call so you can see exactly where I left off so you don't really have to even go into the list if you're working in the same one or two things alternately this I will say has not been configured however you can add in execution metrics so if you're running a lot of flows and need heuristic data on how they are performing well or poorly that can be embedded directly into the home page and this obviously says everything is from sysadmin because this is my PDI I'm the only one who has access to this however if this was a team environment you could also see what your teammates are working on what was the design choice and adding kind of or in prioritizing adding the team activity aspect to the home page yeah yeah for sure um so we we have research partners that we work with internally and we're always reaching out to customers and internal business units to see how people actually use flow designer in all of our workflow automation products and especially when working with teams like app engine Studio or people that might be creating flows for other business units like customer service management or CSM it's always like a team aspect somebody might start on a float like I might start to build a flow and then Earl might come in because he's uh he's building a custom action that I need so between the two of us we're achieving one outcome for our business um and we realized with the old flow designer homepage it was just really hard to understand when other people from your team did something to one of your flows and sure like the old view had an updated buy but but on what you know yeah you know like it's it's a like a simple piece of information and we opted to go for a more modern approach where we almost have a feed of of updates and make it clear who was the person what did they edit um in a really you know facilitates a lot of that that team uh environment where it's a collaborative building experience and I think it also kind of it also showcases the maturation of the product like when I first started using flow designer it was very common for like one person at an entire company to do all of the flow Designer work um someone was like judged during executioner which obviously today isn't not necessarily the case or hopefully is not the case to be the goal right you want to be able to easily um democratize development and I I like seeing stuff like that right on like the home page to see now one of my favorite Parts on this page as well is like we have recent activity which you know certainly optimizes for team environment team awareness but one thing that kept coming up as well is like pick up where you left off is is great but you know bugs happen defects happen someone's gonna ping you and say hey this this flow is broken unexpected outcome whatever if we click on that all work toggle in the top right of that page you can quickly filter to just stuff that you have created and it's like a one-click filter for just your flows and that was like a single very specific request that came up over and over and over and over from people like I work in a big company hundreds of servicenow developers here I just need to find the things that I made because I forget the name of it I made it a while ago you know whatever um so that you know it's just one little drop down in the top right but it's one of those things that has resonated uh really really positively uh in our early testing that's why we we bring the team on for these types of calls yeah absolutely um and then the last thing too which is it's not worth like not drawing attention to it right is that resources are embedded directly into the home page like we saw that with app engine Studio I think was one of the first to kind of say hey if you are building here are the resources that servicenow kind of certifies and recommends um so I like having all these things directly embedded into the platform for easy use for for help for reference for for whatever you need and that kind of covers the home page did I miss anything other than this lovely created by toggle well yeah there was a a comment uh from Ola saying is recent flow is configurable uh for example he wants to show the last five instead of the last two um I believe this will show three uh and the only reason it's showing two I think is because this is a PDI and you just got in and there maybe only have been two flows that yeah um so so it'll show a maximum of of three and at this moment I don't believe that is a user configurable property okay to tease some stuff for upcoming releases we have uh big continued big changes coming to the home page that uh have have a real focus on tying our Builders together so expect to see better integration between flow designer pad decision Builder workflow editor action designer um one space where you launch into all those things and you get better visibility into how they all connect so this is the problem with having y'all product guys on this team you make me greedy for the next one I'm like what about Washington UTS yeah well you know you got we got to keep you coming back we got to give you just a taste of the new home page and then we you know give you the good stuff so yeah well let's move past the homepage I think we've covered everything that mostly that it that it showcases if anything I've missed please let me know in the comments of this video as well um but let's dive into the actual changes made to flows so the first thing that I'm gonna do is I'm gonna use the recently used tab to open up this log count change I've been working on a social media Tracker app this was it's counting the the changes and followers so uh if you're wondering what this flow is doing that is its purpose but I already see uh one opportunity to showcase a change in this action here which is looking up a series of Records if I go ahead and open it I see that it showcases two data pills data pills are essentially when you utilize one of these guys over here to access values stored within objects on service now so inside of this record if I wanted something inside of this account create selecting this add this as a data pill that can be dragged and dropped throughout this interface now previously on Utah these were not editable entities so as I kind of look at it it's kind of a it's kind of hard to tell at the pill level right without hovering over what it represents and so if I needed to change it there was a likelihood that I could make some human error there as well now on Vancouver if I click the pill itself not only can I get a very clear representation of that data path but it is editable so if I want to change this to the count table instead I can beautiful yeah very nice because I've goofed up on a lot of those yeah especially if you're not walking through like eight menus too oh yeah like this is actually not the best like example because it's only three three like pills there's been occasions when it's been like eight nine Pathways just to get to the thing that you are looking for and that's not atypical at all yeah and a little bit of a like behind the scenes storytelling this is one of the like obviously it's a it's a smaller feature relative to some of the other stuff that we're building and it was a little bit more like unheralded when we were talking about building it and planning out the work um but when we did our demo to the our wider engineering team this is one of the features that legitimately got Applause from uh the engineers on on the team who aren't like in flow designer but they're on other products because this is such a point of frustration from you know fat fingering or trying to click on something you just got the wrong value and you got to go back and do it all again um so sometimes it's the small stuff that that really uh just makes things a lot easier so when it's when it's your interface day to day it makes sense that those little things make the biggest change absolutely yeah no kidding I mean like I don't even use a day-to-day and I was applauding to see something like that because it just shows some like a Polish like on the platform um I I love seeing stuff like that improved I'm not going to save those changes but I am going to jump into subflow so um I've got a lot of questions I've got a lot of questions at knowledge about the difference between flows and subflows I would articulate the difference between them is they're basically doing the same thing right they're utilizing actions and logic to do things regardless of human interaction on or off of servicenow the critical difference between the two is that flows are triggered by specific events within that you define within the platform so for example a flow can be triggered by editing or changing or creating a record so if you add an incident that could trigger a flow an event within the system so could also trigger a flow and then probably one of the more common ones as well is that it could be time oriented right it could be every Tuesday at six o'clock for example the difference is that subflows exist as entities within flows right so they cannot be called they have to be strategically placed inside flows to be arrived at through the logic is that an accurate description Bim yeah yeah absolutely I love using this as an opportunity to polish up on my own accumulator the interesting like hidden features of normal flows as well like your description is is accurate where they they trigger off of a record Being created or you know being scheduled or something like that but if you have your flows that are scheduled or that that run whenever a record is created or updated there's actually a setting that you can update where you can use those Flows In in your flow as well you just pass a record in it almost like it's a subfloat oh it's a little bit hidden the use case is a little bit Niche but technically it's possible to use flows inside of flows and if you just want to have a it operating off of a single record you can get really recursive with it really confuses or is it just like you know it's running in the background because you set it to create a record uh well it'll it wouldn't run on the record created it would run on the record that you pass into it yeah so interesting well regardless I will say that the the prescripted reason so I also then got the question of like why build subflows right if they're just the same thing as flows why build them well there's a couple reasons one thing is that we love to recycle entities right so if you find a pattern that's existing across multiple of your flows that needs to be the same for all of them it would be nice if it was a subflow because then you can change it just one place and it Cascades throughout all of the flows that are calling it um another reason is that for flows that were very very lengthy compartmentalizing that logic I believe and correct me if I'm wrong help speed up the flow loading and things like that correct yeah yeah yeah absolutely so it runs a little bit cleaner a little bit faster as well and really to support this uh this model of like a subflow first mentality really having it be modular I believe it was in Utah that you release the ability to select several actions and convert them to a subflow from directly within the Builder canvas yes So Gone are the days of building out a flow realizing that steps four through nine you actually need them in your next flow and you need to manually rebuild them all you just select four through nine convert to subflow Boom it maps all your data pills it generates inputs for you it's uh it's handy I believe there was a lot of attention on that knowledge so if you haven't checked that out yet I highly highly highly encourage you to do so um so now that there's been more and more a focus on flows there is a greater desire to kind of catch them up right they were a newer entity um they only came out a couple of releases I mean I say a couple it's probably been like five or six um but they are relatively newer entity in comparison so there are were a few things that needed to be made feature parity with their parent entity with flow designer um here is a simple test flow I've created so you can see from the get-go it is a little bit different looking so instead of having a trigger it says inputs and outputs that's because you can pass in values and also give values back to the parent flow that might be calling it um but one critical difference I see which I can prove is the case if I open up a subflow over here so I could already tell how much faster of a um version the other one is there is no diagramming view so this is showing all the inputs and outputs for this subflow there's no diagramming view toggle and there is in Vancouver so diagramming view was kind of made as a response the people that really loved workflow editor for its UI if you've never looked at workflow editor before it was the predecessor spiritual predecessor to flow designer and had a flowchart kind of oriented look that look was very preferred by like a good group of people and so the diagramming view is made to satisfy that need of like hey I like the natural language stuff I want to see a diagram totally fine and now you can see that in subflow views as well and in addition to this there is also the concept of adding stages so this is actually NC I'm not super well versed in what is the primary purpose of stages within flow designer yeah so stages are primarily used for catalog fulfillment um when someone requests a catalog item you can use a flow to kind of power that step through process and get all the approvals and things like that and within the flows and now subflows as well you can use stages to communicate back up to the request what stage the the request is at um it's it's pretty handy and uh you know stages being limited to the the classic flow designer and not subflows was a a frustrating limitation for a lot of folks who used flow designer to power a lot of their service catalog fulfillment but also wanted to not repeat themselves use subflows and they wanted to you know get into a more modular creation experience so um you know between subflow stages and editing subflows in a diagram we're really trying to to get subflows up to that same level uh as as flows as well it's a it's such a small thing but because of that idea of subflows are meant to be uh the things that you want to repeat um a lot of people expressed oh we can't it not having stages and subflows dictates how we build our flows now because now you have to handle stages at the top level of the flow and so now your subflows are now divided by stage instead of by functionality and so that's that was happening even in my last workplace of like oh we can't do subflows in stages so I guess we're going to design around that and that's not the intent of what you want to be doing in a subfloat necessarily so it's a good good updates to um bring again like parity to what a lot of our workflow editor holdouts were because they stages are important for catalog fulfillment love that that's probably why I wasn't clear I'm like I haven't done much catalog experience when I was a customer so I was like I know I what they mean but I don't want to speak out of turn um well I wanted before we switch over to bim's point of view I wanted to make sure were there any questions in the audience that I hadn't addressed yet um the the relevant to Vancouver questions uh Bim did a good job at answering live uh things that are just kind of side stuff we're answering in the chat perfect I appreciate that guys well now we're going to be switching over to bim's point of view why is that well the last two features one is not available just yet it's very very close a suit like soon available and the other is something that is in limited relief so uh back when we did the tech now webinar um I made a slight Boo-boo in saying that now assist was available with the general release of Vancouver um similar to all of the Gen AI things for app engine and flow designer it'll be available in the second store release so it'll be coming out in November so it's not too far away but I made a slight error so it won't be available on your PDI which is what I'm trying to communicate second which I got a lot of questions about already like on Twitter and stuff is the go back action or excuse me the go back flow logic that was added in Vancouver this is available however it is in limited release which means you can call customer service today and have them turn this on on your platform if you're really really interested in testing it out but there's no way to turn it on yet on a PDI um so I just want to clarify like one of these things is out just not on pdis and one will be out in November thank you yeah so yeah like you mentioned both of these are like highly requested items uh and both of them are kind of available right now um you know to differing levels but uh that's because these are these are hotly requested items you know these especially go back to has been in the idea portal forever you know since I started you know three and a half years ago it's been one of the top ideas people want to go back go back go back up until now that recommended guidance has been like well we'll just you know put it put it all in a giant loop with a doing too you know which is like it's fine but it's not exactly what people want um so we're we're going to be making that a little bit more declarative but there are some kind of under the hood changes behind the scenes that we are polishing up and getting ready for full public availability in in the Washington release but if you do contact support for go back to they'll walk you through some of the things to be aware of and what some of the implications are because there's a couple underlying changes with the the flow engine itself if you enable it um but when those flow engine changes are made widely available uh in the Washington release uh all all sorts of excellent runtime performance implications are going to be there like a much faster easier to to log and Report data with less flows are less heavy so it less impact here your instance when they're running so I can I can visualize the PowerPoint slides now with the comparing times [Laughter] cool so uh let's check out what we've got uh so this is a sample flow business process approval flow and the first thing that we are going to show is now assist recommendations um we've you know it's been a big push in in AI um in a lot of companies now it's you know all the rage uh but this is something we've actually been working on uh for you know about a year or two now really trying to make it easier for people to build their flows faster and more accurately and like those are those are our two objectives with this uh so it's really fun to see this come to fruition because we know as soon as you try and build a flow there's hundreds of actions there's a lot of different Logics so many subflows you know I'm just trying to build a standard uh catalog approval fulfillment requests like there's got to be some some guidance there yeah so one of the things that we are launching uh in you know later this year as Lauren mentioned is the ability to show recommended actions and the recommendations are really nice for this Vancouver release they're going to be based exclusively off of an internal servicenow model so any customer that that uses this it's all the same model everyone's getting the exact same uh recommendations but these recommendations are based on flows that us servicenow use to to power all of our instances all of our out-of-the-box stuff all of our business units so these are you know the the Best in Class examples of the right sequence to add uh add steps together add logic chain actions together now what's really cool about this is you know right now we are looking at recommendations at the end of a flow but anytime I click into add an action I can see recommendations at that step as well so anytime you click in it always looks for what what are the actions that occurred before this moment in time one of the highest probability of actions that should be added right here I love that too because like that's such a common thing to wait for wait for something to happen after the approval and it's already suggesting that as one of the recommendations for sure for sure you know and the if is like all right is it if it's approved do this if it's decline do this or I'm going to wait for it to be either you know approved or declined so it's um it's it's pretty handy but if we go to the the bottom right here we can see that I added this flow starts with an if at the top and the top recommendation is an elsif so it's already helping me to continue or close the loop on logic that I've started which is really nice yeah and like intellisense for a UI basically yeah yeah it's it's super handy and you know we realize that we know how our internal flows have been built but we don't know exactly what our customers are going to build they might have you know organization specific design patterns or they're trying to accomplish something that you know is is unique to them so there's a lot of debate internally but hey should we just Auto populate what we think is the best action next but what we realized is there's only so much that we can know so we kind of give you the top X the the top you know for top five that we think are the best fits for what you're trying to do and it was exactly for that you know approval step up top we don't know I'd be I'd love to know is it um is it like a a logic tree where it's deciding what to recommend is it built off of a model based off of what people have made on these flows how what what goes into the recommended yeah so we actually do an audit of all of the flows that we create internally across all of our instances that we use for support and our internal instances and uh any out of the box flows a business unit ship and we tag each one of them so we try and identify what uh what each flow is looking to accomplish we identify the specific sequence of actions within those flows so anytime we click add on a step right here well we're looking for the things that came before it and we're trying to pattern match with that sequence of stuff across the entire model of all of our flows so it's not a hard logic tree and it would evolve if you know we ship more servicenowflows out of the box cool which is actually even cooler than I thought because that means it's recommending based off of what we internally have determined as a good practice with our products yeah that's actually that's cool nice yeah and future releases will have enhancements so it's more customer specific so it will adapt to customer flows that that they create so this is helpful because some companies have uh very specific patterns where you know they need certain items in a certain sequence or they always want to audit a step or log some data after they use specific actions so it will be more adaptive to each individual customer in upcoming releases that's really cool so um this is nice it's it's very handy this is part of a lot of the larger now assist uh push that is being released and you know this time frame and later this year Within servicenow um but then the next one is what are we talking about next oh yes one of the most top uh voted features since I've been here yeah during Tech now so here here we go um if I go into flow logic boom we have go back to now go back to is is really fun because it effectively acts as a as a loop but we only allow you to go back to places that won't get you in trouble from like a data flow or from a looping perspective so as soon as you add in your go back to we kind of curate that list because I can't go back to if I'm in an else if Branch I shouldn't be able to go back into step four right here because there was a lot of other logic and pathing that happened before then so you can always go up to your kind of the parent level or you can go to anything that immediately preceded you as well and it was through a lot of user testing and actual data testing and runtime testing that we really wanted to get this right because we didn't want to create an experience that allowed our users our customers the the deer Watchers of this video stream we didn't want you to get into trouble if you're actually if you're using this and you're building something so we try and create a couple guardrails that allow you to achieve achieve some outcomes without you know getting yourself in a bad place you don't want people to use it to bypass like like in this case it's for an approval so you wouldn't want someone to jump into a part where like they didn't approve it right and so you don't want to use it as like a workaround it's supposed to be for your like benefit not for like nefarious purposes now what what else is uh we talked about some of the nice touches earlier you know uh expanding a data pill or having a nice little toggle for my flows versus all flows on the home page this one is like a personal favorite of mine um because we see customer built flows all the time A lot of times there's 20 30 steps and the reason there are so many steps is because you Branch it step five and then each branch of the if has 10 steps in it all of a sudden your flow is really big but if we click on this button right here it will scroll you up to where you're going back to and highlight it and it's got this little icon that says it you can come back here from Step eight so we have these nice visual indicators uh and affordances that tell you exactly how you're getting there and where you're going it's small but when you have big complex flows especially in this view where a lot of things are indented and it's kind of hard to see pathing this was a nice touch that really resonated possibly positively with our internal team that's lovely I wish more yeah yeah and right now with this instance I'm having a little bit of a bug where the diagram view is is not working with go to uh but as Lauren mentioned earlier if you go and contact uh support to enable this the the feature fully works with the diagram View and it has a line that will take you all the way back just like we do with everything else in diagram view you can kind of Trace with your finger where you're going um so it's it's pretty handy and it we got this request a lot and a lot of people so yeah we're really happy to introduce it it unlocks a lot of different outcomes and use cases for for folks that use flow designer that was amazing I'm so especially since one's still kind of like you know it's not even out yet that's really really exciting um is there anything flow designer change wise we've missed in the Vancouver release or is there something in particular you'd like to tease for in addition to uh like analysis for any of the store releases well what I would say is since we launched the diagram view in San Diego um we've recognized that there's been like a Content Gap specifically with uh some of the flow logic and what is supported in the diagram View and in recent releases we've gotten you know do the following in parallel we've gotten our looping uh and then in Vancouver we also have do the following until and this go back to logic as well so I believe at the end of well uh uh in an upcoming store release we will be supporting the uh the try flow logic as well in the diagram review so you can kind of have the try catch Behavior both in the text View and the diagram View and then at the by the time Washington release comes out all flow logic should be supported in both the text View and the diagram View with the adding of all these things like try catcher the recommended and stuff like that um it feels like a design philosophy of like basically it's visual almost like a visual scripting um yeah aim kind of thing is that one of the goals well I mean kind of one of our Visions for our team is we allow people to automate work with clicks not code um so if you can do something in code generally our goal is to figure out a low code way to do it and we recognize that a lot of the people that build with flow designer are people that don't identify as as app developers they might be someone who is more comfortable in a clicking a low code way rather than than scripting their own Solutions so anytime we introduce new Concepts like a like a trilogic a lot of care and dedication goes in from an engineering and product and and design team on how do we make this concept that is traditionally developer focused approachable to people who don't necessarily have that same background and you know certainly some concepts are very Niche and very uh like like technical uh error handling can be one of those and if you dig deep into the the bowels of action designer there's all sorts of buttons and switches on fancy error handling scenarios um but yeah we're really trying to make automation uh understandable and available for a wider group of people and there's a lot that that goes into that shows that's that's really nice I always like to point out to like that's a it's great for the ones that don't want that don't want to dive into learning the code or I mean asking a citizen developer to learn all the in and outs of scripting is a tall order but for like people that have been doing development or people that do know how to do coding or JavaScript and stuff I would I still would rather go into a low code interface to do some of these things because like I can't drag and drop steps when I'm in my script I can't visualize the diagram I can't do those kind of things like I'd rather a lot of these things make my job so much easier because who like abstract away the nonsense that I don't want to deal with every day please do that right a lot of those things I would want to jump into and then like you said like when you jump into actions or when you jump into certain interfaces inflows and subflows you still can access scripting so it's like oh you can yeah do a lot in this tool and I think um you know we talked about analysis recommendations and flow designer right now but there's some other analysis work coming that comfortable talking about because it will be in November but it'll be compatible in Vancouver um but we'll be able to create a flow from a text description so and and that really enables people who have almost zero experience with flow designer if they can describe what they're trying to accomplish uh they're able to create functioning flows from there now that might have to map some data pills to make things work but we're really hoping to reduce that time from I have an idea for something that I can automate to getting an automation up and running and saving the time of having to find the right update record or update records or look up the customers shouldn't have to to care about that you should not have to know what you want to accomplish and if we know that intent what you want to accomplish we should help you get there absolutely I remember that spreadsheet from months ago being sent around hey what are all the use cases for building Tech um flows and stuff like that I was like what is this for okay what in the world yeah well I think it really showcases too how like I think that there's a lot of like there's a lot of Doom and Gloom news around AI right like there are bad ways that it can be employed I think as a like servicenow user I'm really excited with how our company in particular is utilizing it right to to remove the like the gunk from working right that's the ultimate goal of AI right is like oh humans should be able to work on things that they naturally have the capacity to be you know creative and better at but let machines kind of handle the stuff that's like I don't really I don't I shouldn't have to do that anymore right yeah um so like being able to describe a flow in text and so basically like take something that you could get from a design meeting with a bunch of your colleagues and have that turn into like the beta or even like like version of your flow that you can then springboard off of the fine tune that's unbelievable that's amazing and one of the big use cases we we see this with flow designer and definitely with process automation designer as well and in the life cycle of creating automated work there's always someone normally on the businessy side that says hey we we need to achieve this outcome when this happens we need to talk to these people we need to get the approval from this person yeah and then there's normally a developer or an engineer who's responsible for bringing that to life and something like using AI to automatically create like a skeleton of a of a flow from a text description is something that helps bridge that Gap from person who knows it in in text terms to person who knows how to build it in low code um yeah so really like facilitating that teamwork and getting you to a real solution quicker those are the types of things that want to to implement in all of our automation products well I think that's the the the perfect and inspirational note to end things on for today um I don't think there's anything else on that we could showcase um I'm certainly grateful for your time today Bim I think you've really not only showcased some stuff that people were dying to see but helped us like see also some things that maybe weren't like specifically written in like the tech now presentation right like like the filtering down of the list and like showing how things bounce back like adding in that like like polish was like so so so helpful to see very cool well hey uh thanks for having me on I hopefully I was able to communicate my enthusiasm for this type of stuff because uh stuff like like low Code and low code automation with flow designer process automation designer decision Builder you know you know it gotta plug all the products in the family um they're totally my jam like this is stuff I'm really interested in and uh really our whole team is focused on making it a lot easier to use so anytime we can jump on and kind of evangelize the work that our team is doing everyone from product to time engineering and research uh always happy to jump on and sing the good good Praise of the work yeah we gotta keep getting you on this show because we apparently you're apparently building a good reputation on these shows because people are starting to play if you saw at the beginning of someone in the chat my favorite PM you can come in here with all this good stuff no wonder yeah yeah well I'm also in that SN Dev slack so you know if that's Linked In the notes or whatever if anybody wants to get in touch afterwards I'm in there every once in a while and talking about new features and what's coming so happy to chat there as well awesome and it on SN does is it just it's at bin right I believe so yeah yeah yeah if you um at them then you'll call you find them awesome well thank you for joining us and thank you to all of our audience members also joined us early in the morning to cover this um again we are in the middle actually very at the very beginning of our Vancouver release cycle there's more to come in fact there's even more for flow designer kind of photo designer Jason's more action designer coming in the later weeks so if you'd like to have a deeper look into what that calendar looks like you can go to devlink.sn Vancouver for everything that's here and thank you Earl for for managing everything behind the scenes and for joining the chat today it was really really appreciated as always and thank you all for and have a fantastic rest of your day bye everyone [Music] foreign [Music]