[Music] so [Music] so [Music] hello and welcome to creator toolbox this is the show for servicenow builders developers and admins and curious individuals wait i'm borrowing from another show we are going to equip you with tools you can use for your toolbox on servicenow so you know more about what's available otherwise you fall into the trap that i do and you keep using the same hammer for everything when really maybe a screwdriver works better i you know i could watch that little robot at that opening animation all day but there's better things to do like getting on with our content good morning my name is chuck tomasi i am a senior developer advocate with servicenow been with the company since 2010 was a customer for a couple of years before then and my computing history goes way way back into the stone ages which we won't get into here we're here to look at new stuff not old stuff let's go around the horn to the man to that direction for introduction right yeah hey everybody i'm brian bim schlager principal product manager here at servicenow and uh i've been here for about two years working on things like flow designer and process automation designer and some new automation products that we are working on and i'm excited to demo some cool things that we launched in the san diego release for you today for flow designer we'll go down to the person beneath me that's me uh thanks vim my name is brad tilton i'm a senior developer advocate uh here at servicenow i've been building on the platform for a while and i am excited to get into some of these flow designer enhancements that are pretty awesome today hi everyone i'm earl 2k and while they're senior developer advocates i'm a baby developer advocate so uh new newer to servicenow about this official title baby developer the interview process was wild um but yeah new to servicenow but not new to the platform been here around for almost five years now uh mostly with higher ed and i just want to point out that the tag above brian's left shoulder says san diego so if you see that tag on any of our videos you'll know what's yeah it's not up here this time you'll know what release of video you're watching in the future what we're showing you here is part of our san diego early availability release we've got two main topics to show you today one is save as a flow template so you can create a flow temp flow and then say i want to make this a template this is a common use case the other is our new flow diagramming view which i'm going to save all the fanfare for brian he's our subject matter expert today and want to give him all the glory he and his team deserve for creating such wonderful features that make all of our developer lives easier so over to you brian all right well thanks for the intro chuck i appreciate it uh the first thing that we're going to tackle today is saving a flow as a template like chuck mentioned the use case is pretty reasonable if you are an admin or your app developer within your company and your company's starting to creep into the citizen developer space there's probably a good chance that you want to have a warm start for your new developers that are coming into servicenow now previously in quebec i believe when app engine studio came out uh when you create an app and you say you want to create a flow one of these screens that you get the first thing that you see is a bunch of templates that that pop in so in this example i don't have the necessary spokes installed but these are all pre-configured flows so i could click on it and it would have the trigger and actions and everything all configured now this is nice if you're working on creating an incident and posting to jira or sending a notification to a workspace or you you have one of these use cases that is on the screen but today oh let's let's see if this one will work what happens when you click on one of these templates is there is a little bit of a guided experience that walks you through the buttons and switches that you need to to set up in this early wizard so the user can just get up and running with their flow so in this example you choose the table that you want to to trigger from and then what's interesting about this is when you when we present our our flow templates to the user you can only or you can optionally present a small subset of the fields that you want to collect the user's input from to fully configure the flow so again we're just walking through a quick example of how flow templates work right now and then we'll get into how to build your own so we'll just say this is example template now when i click continue this is going to build a flow behind the scenes and as our helpful copy mentions this may take a few seconds so hopefully the thank you for the animation part and let us know it's not frozen you have to do something sometimes the spinning circle just doesn't cut it i want to see the guy on the right type like he's actually creating the flow for you come on uh live demos yeah fun stuff so while we're talking about that the the create flow template is this only available within app engine studio or is this available for flow designers outside of aes yeah great question so for this release which is our first release of saving a flow as a template you can access your flow templates that you've created within app engine studio but currently the only way to create them is in standalone flow designer oh i realize that's that's that's a little bit of you know a little bit of a switcheroo but i assure you we're working on it was kind of for technical implementation but you know what let's let's take a look at how that works with creating or saving a flow as a template and then we can come back to this app and walk through it okay so is this available in ea or or are you working on a special instance that's a little bit ahead i want to get the availability and timing right on this because i didn't see it on my pdi this morning right so saving a flow as a template is going to be available in the store it's available in the store right now but it'll start working once san diego patch one comes out just because there were some technical things we needed to iron out but it'll be in the store as flow template builder and then yeah so so here's what we are going to do um while this is still running in the background uh we're going to create a new flow and let's say you know brad or oral are in my organization and i know that brad and oral build apps we're going to build a basic flow that when a new record gets created we're going to send someone an email notifying that the record got created it's pretty basic but when we save a flow as a template we can make it so this is a really easy flow to get up and running and we can really focus on one or two questions to ask brian can i have you bump up your font size one or two notches how about that that'll work until until flow designer starts misbehaving we'll do that all right um here we're gonna we're gonna do this just as a trick to make sure it bumps to the top of our flow templates [Laughter] yeah we uh we have a couple enhancements coming to that flow templates page in app engine studio that allows more granular control over how stuff appears you know search sort filter all that good stuff categories uh yes perhaps um a bunch of different things are coming we've been releasing a lot of content packs for a variety of flow templates so i think there are about 200 float templates out there available via the store right now that were created by servicenow so we uh we definitely acknowledge the need for better categorization and organization of that stuff so uh [Music] all right what a good developer puts in a description yeah we could all learn a thing uh you know because i i found when uh you know you're going through these in a demo environment you try and create the same thing a couple times and it turns out you have a lot of bim creates a send email template so you need some way to as developers we're not real original with our data tutor the able tutor so in this example we're going to say all right when an incident is created we're you know we're not even going to send a notification because that might be you know too much legwork for this demo we're just going to send an email and to start we'll send it to me but when i save this flow as a a template will enable the author to enter whatever recipient they want in this field okay um and we'll try and use some pill pick values here there's another uh quick glance out of san diego enhancement is the data pill what do you call it truncation where the dot dots appear for the longer data pills yeah you know what it was one of those things where we heard zero customer complaints about it but it was one of those ui things that drove everyone on our team up the wall when you'd add a really deeply nested data pill and it takes up four or five lines and your subject field takes up half the screen like if no no one had prioritized it for a while but every time we demoed something you could just hear everyone just go like so if it's bothering you imagine who else is bothering oh yeah so we're here's what we're gonna we're gonna do now this is this is pretty basic right so incident is created we'll send it to someone directly we have a couple pill values right here um now this is obviously really straightforward like work nothing super complex but you know if someone is new to uh new to servicenow new to flow designer new to app engine studio there are a couple concepts in here that are new to that developer you know uh thinking about understanding what the triggers are and how they work how to configure them additionally sending an email you know using the data pill picker might be not intuitive for the very first time someone comes in if they're more citizen developer or lower on the technical skill level so even though this isn't the most complex flow that we're showing there's a lot of leg work that we can do to make it easier for people who are building new flows if they have low familiarity so we have our trigger we have our action now we're we're going to save this flow as a template and if you have flow template builder installed via the store once we click on our more menu our more actions menu up here save flow as template is going to be an option for you directly beneath flow stages now let's click on it see what happens boom we have a modal that comes up it kind of tells you how this is going to work so you know behind the scenes we're technically creating a new thing now we're creating what is is a flow template object so we have the opportunity to rename it something else if we want so we'll append that and i'm going to make this available in global for now all right so we have our template and we have our application so all the steps that were at the bottom we could read them or we could do it live so let's do that instead um okay so what we see now is our flow template view right looks similar but maybe a little bit different in some areas to flow templates most notably we have this little guy up here this little switch to go between flow view and template setup so this is showing what our flow looks like right now and you know we can go and click in and there's there's information in there but when i go into template setup that's where the power of this this feature gets gets really augmented and this is where all the magic really happens so when we go into template setup we have a similar view that shows all of our our actions or all of our steps within this flow and if i click into incident created i get an option for what i want to do with the values or the the inputs for each one of those steps now there are a couple different options here one is we can use the default value which is what i defined when i built the flow in the first place so we can see that default value is incident or i can collect a new user input which means during that wizard process in app engine studio i can prompt the user for what table they actually want or i can use a template variable we'll we'll get to that in a second so we're going to say the first thing that we need to know for this template that i'm creating is like what what table do we want to listen for like when a record is created on this particular table then we're going to send an email so we can ask the user for that but if we're in a wizard and someone comes in for the first time and all they see is a table and then a little selection field it's not super specific and it could might get a little confusing for for users so we actually have a fancy little advanced options menu oh look at that this is like where what record producers do to normal field labels you can put a real humanized question on this i love it you just won me over woo that's all it took an advanced options section all right that's that was one of the things that you're talking about when i first saw service now back in 2008 it's like we can ask human questions yeah i don't only ask three of them nice cool so we have a couple options here that make it a little bit more contextual for the end user so you know a lot of what flow templates are all about is you know reducing that time to value for someone who might not be as familiar with the guts of how flow designer works and if your admins are working on or your pro developers or you know your it department is working on building out a couple of these templates if they add these nice touches of a temporary of a field label right here and making things mandatory adding a hint it really does reduce that friction of learning what the heck is going on so next thing that we are going to do is uh we're going to collect an input for the user for who they're going to send this email to so we'll we'll do this again and we'll make that that mandatory now once we get down here we get into the subject and and the body here's what we're gonna want to do we're going to well i think for this example what we can do is we are going to use a template variable much like normal pill values or or flow variables temple of variables are a similar concept so we're going to be able to see a template variable of 2 a template variable of table in here so in this example we can it's a little bit crude just for this this demo but we can take the subject of our email and we can say hey the subject of this email is going to be that name of the table that we accepted in the first step of our wizard it might not be super practical at for this example um but believe we can go back and look at our flow here and you can see how it kind of populates and updates our our flow or i can look at send email action and my template variables are two and the subject has been replaced with the table now you'll you'll note that this flow is in read-only mode and part of the reason for that is once you save your flow as a template it's going to put that flow in read-only just so your your flow and your template itself don't get out of sync it is something that we are working on uh for future releases to really allow you to update and modify your flow as you're building the template and you may want to go back and make revisions to your template go oh they needed an email but we also needed this other action in here is that not possible at this release uh for right now you can take your your flow that you have built and you could save it as a new template oh okay if you really wanted to like add an additional action here but for right now for for this this initial release once you kind of create that flow template uh that flow is going to be the flow that's associated with it is going to be locked in okay all right so we have our flow template now and when the user attempts to create a flow in app engine studio from this very uh creatively titled template bim creates a send email template live uh in theory when the user clicks on that will prompt them for two values one will be the table and then the other one should be the to field for our email so the first thing that we're going to need to do is to activate our flow template fingers crossed it all goes according to to plan all right our initial flow was was still running so we'll we'll cancel out of that all right so now we are going to add uh a new flow into our app and once we click on this oh no it's very refreshing it should be showing up for us right now yeah if it doesn't oh there we go there it is it took a second so this is the template i just created and it's bumped to the top because it's ordered by the name of the template right now but all right so this is our first thing all right now we can see our custom description what table should we listen for that we uh we each we define a question mark next to it for your hand too this is our our little little help icon as well so just to show you how this will actually work let's update this to we'll just say it's a interaction i don't know if you have just chuck i don't think that's a valid one there was a time when i could get away with first name at my old company so i was like the guy who created email accounts yeah yeah uh okay uh i think i still have a business card that says that chuck yourcompany.com wow 30 years ago was a fun time okay so look at this uh compared to the first flow template that we tried this one actually got created so once i click on edit this flow it's going to open up in flow designer in app engine studio and it actually created this flow for us now what's cool is we can see that my trigger now has interaction populated and once i go into send email chuck's name is in there and then the the table from our that we selected during that wizard process is also in here and everything else wow so you know once uh the user enters that information during the wizard it'll kind of flatten all the information so the user when they plop in here they don't need to know the concept of a template variable or a template input or anything like that all they know is they selected a table and they selected an email and voila they're in their uh their flow ready to go so um see what use cases customers come up with for this yeah well some of the big ones um that we we tend to get a lot of questions about with people that are newark to servicenow or getting into the role or like how to correctly build approvals in flow designer or if they you know if an approval comes in and it's above a certain amount it's going to require two approvals or if it's less than a certain amount you know it doesn't require any approval it just kind of gets auto approved so i know some of the kind of the business units that we've been working with on this a lot of the use cases are creating uh an approval kind of template where the user enters in like hey what's your first threshold for uh requiring an approval and what's your threshold for requiring a second approval and we'll plot those values into like if statements to kind of handle all the the routing um so that's probably one of our big use cases right now but uh we also see um we've seen a lot of examples where people need to copy their flows um like they have some new business case that opens up and they have a flow that's working and they just want to like duplicate it and tweak some values so instead of really relying on duplicate copy functionality and then manually editing things we're hoping that people adopt the the template model a little bit more because it kind of opens the doors for a lot of newer developers to contribute to building automation in the workplace so good good any other comments or questions brad earl we just got a question um about can template use decision table oh of course yeah um so kind of the way to think about it is uh anything that you can add into a flow you can use in that well there are a couple ways i could interpret your question the first is can i include a decision table in a flow that turns into a template and the answer is is yes now another way to interpret your question is during the the wizard and setup can i include a decision table in there and route to different flow templates the answer for that one is is no we'd have to select a single flow template that you want to to build from and it's always gonna that flow template will always point to one particular flow [Music] now i see another comment in the chat from uh right above tariq asking how about versions in flow designer steve yeah yeah so if your app is is hooked up to source control you know you hook it up to github or something like that we certainly support versioning and flow designer right now but that's kind of uh not a great answer because i know it's not super intuitive to know how to do that um and we we don't have any controls within the ui to handle version versioning but what i can say is app engine studio is leading the charge on how to incorporate better source control into builders from a ui perspective and i believe that they are releasing that in san diego or one of the san diego store releases so we're hoping to have more clear and understandable ways to go back to prior versions of your flow at some point in the future it might not be full on source control it might be a you know a redo type of thing or go back to a snapshot or something like that but we certainly understand the need all right so any other questions on flow templates before we are saving a flow as a template before we jump into diagramming nope nope no one knows it all right let's do it uh flow diagramming oh we weren't talking for 30 minutes oh different instances i know we get long-winded but that was ridiculous yeah all right so flow diagramming uh very cool concept our entire team here is is super excited about it because ever since i've joined two years ago it's been kind of the number one thing that people have been asking for and the one of the top inhibitors of customers not moving over from workflow into flow designer and one of the reasons is if you have a flow that has a decent amount of logic in it and you know obviously this this example that we're looking at is not the most uh complex example but it has you know a couple nested if statements in here uh once you really start nesting this logic and adding a lot into it it can be difficult to follow where you you go um and part of the reason here is you know if you go into your if statement and ask for approval and the task is approved you run step four once step four is done you would actually pop out to something that that's down here uh we found through a lot of customer and internal user testing that if if people don't have that development or programming background uh that kind of relies on some of that indirect you know jumping back out to the parent following logic was really tough for people to to figure out with uh flow designer so one of the things we really wanted to do is make a more visual approach that kind of doubled down on obviousness it's become a little bit of a running joke internally because i've said it so many times but uh our indicator of success for this project was if you could put your finger on the start node on the trigger and trace your path all the way down to the end uh that would be how we how we know if we're successful uh we wanted every path to be obvious everything to be direct a line takes you to where you are going to go and if there's multiple lines like in a if statement we include labels that tell you how you go on down each path now we think this is a big improvement for visually representing sequence and logic within flow designer sometimes each of these views have to have different strengths uh we certainly know there's a large portion of flow designer users that really love this this type of view because it's it can be faster to to read especially if you know you're the one that built it and kind of know how things are put together and really fast to create but we found that this view right here is really good for sharing your work with others or bringing people up to speed on the what's happening within your flow and even honestly we found internally we'd like to toggle back and forth when we're building flows because you know one might be faster for building but this view right here is much easier for debugging how your logic is actually working that was one thing that i found interesting too was the the debugging capability in here uh if you have an if and an else that both have an end your flow isn't going any further you're done at that point and and you can see this like disconnected what it says something like not connected branch or something like you'll never get here indicated on this view which i thought was really helpful for people who may not be you know real familiar and the other thing that i didn't realize was maybe it was because i was watching an old video from october and the feature snuck in later but i thought this was a view only thing at first just to represent what was in the other view but no there's little plus icons all over the place to add actions oh yeah now here's here's what we'll do we'll show how this works again you know we'll we'll do it live uh [Music] [Laughter] your names are more creative than mine might end up being like asdf [Laughter] well you know i kind of had to start creating more unique names because i had too many flows that were named asdf and i randomly get cannot create a flow with the same name type of warnings so asdf for g yeah it's like oh all of my flows are named just the the home row of my keyboard so all right so [Music] yeah as chuck mentioned uh the initial plans for flow diagramming were to have it be read-only at least you know for the first release as we kind of get our feet under us a little bit but once we dug into it we realized that it was achievable to really allow building of a flow in a diagram view we'll get into like some of the repercussions of that and what that what that means for future releases but um what i really wanted to show is how we actually build a flow and we'll show some examples of how we can toggle back and forth as well so the the first thing that you can do is you can create a trigger just like you normally would have and you know instead of a panel opening up in the middle section right here uh we're fine we're following a convention pattern that i think was kicked off by virtual agent and is used in ui builder and other builder tools like process automation designer as well and really leveraging this side panel to handle a lot of our our editing and configuration now that you mention it the main stage canvas what are we calling it now looks a lot like va i hadn't thought about that before yeah well that's one of the things that we're exploring as well you know from a back end technology perspective they're they're a little bit different and how they're constructed but there are efforts internally to really unify how our our builders look and feel and you know start trying to identify are there places where we can incorporate functionality so we can reduce unique builders no no movement publicly on that yet but it's something that that interests us and trying to make it easier for our end users is there a print button or a easy way to print the diagram man earlier coming in with the uh the heavy hitter questions here that a it's so interesting because um print is one of those features that we don't hear anything about we we don't hear about it from customers for the standard diagramming or for the standard view of flow designer um we i don't hear anything about it on community or in a you know the the dev slack nobody talks about it but as soon as we uh introduce diagramming it was the no matter where we talked about diagramming one of the first comments was can i print it and it's like damn we don't have that for version one but uh i think we we do need to prioritize it because it um it's a common request that we're getting with diagramming now and a lot of the feedback that we get is hey this looks perfect to be able to print and show the business stakeholder exactly the business analyst or the c-suite you know who whoever it is that just needs to like double-check how stuff is going from like a business process perspective if i can give you an anecdote um when we when i was working for a higher ed uh customer um i this was before flow designer way back then um i was creating a workflow and workflow you would think is already very visual and you can trace your finger from beginning to end but um i wasn't able to convince stakeholders and upper leadership of the benefit of that workflow until i drew additional diagrams i literally screenshotted the um the workflow brought it into photoshop and drew boxes around certain sections and said this is stage one where the user will be doing this this is stage two so like the until i was able to like give them a visual print of it that had a little bit more explanation out like more like this where it's much more cleaner and not the details and stuff like that um it wasn't until then i was able to convince them to go for it i could also interesting you know i'm sorry go ahead brian no i was gonna say it's uh it's interesting we have some other projects that we're working on and we've come across that exact same insight with with everyone that we've talked with as well you know when you're planning on how something is gonna work just uh visual boxes and arrows or whiteboard sketch you know of how it works at a abstract view is so critical to getting everyone to understand how it works uh so yeah that's one of the things we're going for with this diagram view and uh seems like print is the next next step for that i guess ninja's also being very very helpful for uh as an option for the execution details you want to see what happened people are used to the old classic workflows like ah there's the green box and oh yeah blue line and the green box like which way did my flow go and why that would that might also be a good diagnostic tool as well yeah yeah yeah well we are you know some of the stuff that we're thinking about in the the future is um you know right now when you when you test the flow or view the execution you go to that kind of top down view where it it shows each step of your flow that that's running and it has you know green for success and red for error you know we're hoping to explore ways to bring that type of concept into the diagram view as well so even at a zoomed out level you could you know follow the green line for the the path to see which path your flow actually took through logic or where that error occurred and so we think that would be a pretty cool enhancement uh okay so here's one thing i actually wanted to show i got a couple things that we can a couple things that we can walk through but one of the key things that i want to talk about we're going to show how this information syncs between the the two views so this is just a random data pill again kind of compressed so it doesn't take up multiple lines but we've created a basic flow here that just has a trigger and a log if i switch back to my standard view we can see that whatever i entered in the diagram view is is already in here you know i didn't need to click oh thanks grammarly uh i didn't need to click save to make that happen i didn't need to click activate you know i can add a few more characters here and once i go back there they're already visible now this was a high priority for us because once we started building this we noticed that people were wanting to switch back and forth to view their flow different ways at different points of creation so i don't know it's like one of those small things but i think it's it's super handy love it all right so let's let's add some logic oh actually we'll we'll talk about some of the content that's in here first so when we uh released in san diego and i saw some folks asking in the the chat you know one version the initial version of this plug-in released with san diego and is included in your automatically in your upgrade but to actually enable the diagramming you have to go to the plug-in and install the updated version of the plug-in now since we're you know approaching flow diagramming in phases the first phase of diagramming includes our core logic so this would be your if else else if end flow and and for each now we were able to get in a couple others like get flow outputs and dynamic flow as well but really the the if uh and for each and you know once we add an if you can add an alice and else if basically if and for each we found comprised over 80 of all flow logic used uh in in customer flows so those were the kind of the critical ones that we knew we needed to land um and then everything else that comes after that is you know in a priority order so when you start using flow diagramming you'll be able to use any actions with the exception of data streaming actions right now we're working on it we'll be able to use these logics that you can see on the screen with more coming with each uh with each release and you should be able to use any subflow as well so we get a decent amount of content out of the box and with each successive release we'll be introducing more to get it up to content parity with your diagram or with your standard view brian what what will happen if your flow has something that doesn't um exist for the in that menu that you have open right now does it disable the diagramming view or does it still try to render uh earl i could tell you the answer or i could show you the answer show us the answer show us the answer yeah cool so right now we have press tab or click to toggle views let's do this example let's say i'm going to [Music] do the following in parallel and you know just for the purposes of this demo we are going to have two parallel branches all right so i've done the following in parallel which is not supported in the diagram view now if i attempt to go up into diagram view oh no diagram view is unavailable because of the following unsupported logic type is present so right now it doesn't tell you very specifically what that logic type is but our documentation certainly notes what what logic is in and out and we also just talked about what logic is is available so we do prevent you from getting yeah yeah so let's get rid of that action and we'll go back in oh it's a little interesting so theoretically speaking we can um if you want a flow that is compatible in diagram view just make your entire you can basically make your entire flow within the diagram view at this point yes yeah absolutely yep you can build your your whole thing up if it's not on the menu you can't be incompatible yeah so uh one other thing that will oh my my trigger disappeared it's not not good uh all right so if i click on my my if i can click to add conditions like i normally would be able to do it's great great condition right here one of the things we've heard from initial feedback is when we add a condition right now this just switches from add condition to modify condition uh we're working to make it more visible so you can preview what the condition is or make it clear that that something is behind this this button at this point oh please don't print an encoded query [Laughter] no it uh well we talked about a couple times before we're going to try and make it obvious uh so either you know human readable or just uh even it might just be something that says a condition is already exists here and you can click to view it so we have a couple ideas um so all right once we click on that we can even see how my logic node updates to represent the label that i included on that that if node so earl kind of going back to your example how you might need to print this out or we might need to show what's happening to stakeholders for certain pieces of logic on here we can add that that descriptive label where you know we can mask a little bit of the complexity uh and and show exactly what's happening at that step now could you go back to the um older view and flip the flip the view switch i want to see did that go into okay that went into the view not into the annotation okay correct got it yep yeah do annotations appear on the diagramming view not yet uh okay you know it's been a source of internal debate i suppose of whether to include annotations or not because a lot of times customers were adding annotations to describe like how logic was working or how something was working or explaining how certain paths were being taken um and the whole purpose of this diagram view is to make that more obvious visually so annotations on this may get a little messy depending on how they were implemented yeah and you know we've we've talked about a couple different options where maybe you know we click on this and if there's an annotation it shows up in the in the side panel or you know maybe you hover on this and it it shows it as a tool tip or something but sure you know the more discussions that we had there the more we realized we might be solving for a problem that the current layout already solves so you know for the customers listening in on this call test it out let us know we're happy to explore annotations but as of right now it's a little bit lower on the priority list just because we felt it already kind of solved some of that use case it's been thought about though so you you didn't miss it yeah there's lots of thinking lots of sketches and and you know prototypes and stuff like that so um now what what's cool with this one of our favorite parts of uh the diagramming view is it especially if you're new to something like flow design or new to logic we try and be smart and handle the emphasis on try to be smart and handle some stuff for you so in this example we have we're going to have a log and we'll have an if statement you know we have an if that automatically produces a then so let's uh we'll have a send notification as part of our our then right and if we go back to our diagram view we can say if the short description contains bim we're going to send our notification and there's nothing on this this false path so if the short description does not contain bim we we go to the end of our flow and in flow designer you know there's that like implied else where if if the if evaluates to false we continue on now once we're in the diagram view we still have this branch but as soon as i click the plus and i say hey i want to it's going to add the else for you automatically exactly so we don't necessarily show the else here but once we come back to this view since we've added something on that that false path will automatically add in the else into your standard view so this kind of concept of building out the the else within your standard view we just kind of take care of that for you it's faster yeah you click one thing and added a task instead of yeah add else then add tasks so save a little bit exactly this way so and you know we we feel that this type of representation of if it's false then go directly here and once you're done with create tasks then you kind of loop back to the end especially once we um like let's say the end will create some some record so after notification or after create task all all roads lead to create record with uh with this type of visualization like i mentioned before we frequently found that people didn't get or lower code users didn't get that once three successfully completed they went to six and we feel that with this type of diagram representation now it's much more obvious that that three goes to to six so um now it's it's uh it's kind of nice as well because you know we differentiate between our our arrows on here so we can see that this create task when it it it loops back and it kind of this arrow rejoins right here and it closes off your your if statement so we try to be clear of when you're building on the true path and when you are building after that that if condition i like it so obviously this is a very simple example um but you look at something that's just a hair more complex with this business approval i was about to ask show us the worst ones this is just a little more complex out of the box just just a little bit more complex but uh you know it's a reasonable amount of business logic in here but we do have you know zoom controls if you do want to zoom way out for a complex flow and uh ah well oh it's once we zoom in all the way i forgot so you know we have like mini map controls if you really need to zoom in or out or really control that that canvas uh and search should work as well which i don't believe is something that we have in standard flow designer but if you want to hunt for a very specific action and you have a really big flow which we don't necessarily recommend but we know that it happens um you know you can search specifically for whatever action you're you're looking for um oh nice you can go to it so and it'll highlight it for you on the the in the panel so lots of cool stuff coming with diagramming um i can say from a roadmap perspective uh the stuff that we are working on that is uh numbers well number one two and three on our list is uh do the following in parallel which uh we've already started development on we have great prototypes in place we feel really strong about it support for flow stages so we can build all your service catalog flows and marking stages and what stage requests are at and all that type of stuff all within the diagram view and then finally building subflows and a diagram view so right now that we only have support for building flows as a diagram but i know the people that are on this call probably are designing flows in a more modular way and our rely heavily on subflows so we're we're working on it obviously no we could go on with questions yeah i got all kinds of ideas but you guys are always way ahead of me so keep them in mind i see some great comments in here and like you know stuff that warms my heart like this will be my new favorite view for building flows you know that's exactly the type of response our team was was hoping for so yeah yay validation [Laughter] uh cool not directly related but when will dark mode come to flow designer um not currently on on the roadmap right now uh not saying it can't be done uh but we have a couple of the things that we're working on from like a collaboration and sharing perspective that are a little bit higher on the our priority list right now but uh certainly understand your your want for that because my computer and phone are all in dark mode as well so i get it [Music] see uh jc had a question search functionality is cool is that available in normal flow view not right now but it is something that we are looking to incorporate um this was uh something that kind of came with our our library that we were using for flow diagramming some other teams internally had kind of built out some of the framework for like this diagram view and it kind of came with search so we got it for free and we are [Music] you know if people like it we'll look for ways to to port it over to the standard view then steve says where can i send a wish list idea portal yeah go to the community idea portal right at the top if you just categorize it as flow designer uh i get email notifications for those ideas if you're on the servicenow dev slack i'm on there as well i monitor the flow designer channel and alternatively uh i have a podcast coming out with chuck i think tomorrow that talks about flow designer and what's coming up and uh all my contact info is is in there as well so great announcements [Laughter] we've got another flow designer video on friday around error handling the new try feature so looking forward to seeing that unfortunately i will not be here i'm going to be on pto paid time off vacation holiday whatever you want to call it and uh i may have to watch from a remote location so if timing is right i'll be in the chat and hopefully have a beverage at my side to join people on live coding happy hour this week so have fun thank you so much brian we do need to we've we are at the top of the hour but uh i want to thank you again you are always full of great information kudos to you and your team for all of the features that have come out a lot of hard work goes into that and uh nice to see the interaction between you and the community and the idea portal the slack channel all of that works out so well it makes that that that warms my heart at least thank you brad and our whole team great people yeah and uh thanks for everyone in the community that submits great ideas and attends sessions like these it's a big part of how we influence our roadmap and make stuff that's better for you okay till next time everybody stay safe we'll see you real soon learn a lot and share it wherever you can take care bye [Music]