doo doo [Music] hello and welcome to live coding happy hour it is that time of the week when we get together and share a beverage share some servicenow developer tips and have a good time let's begin with by going around the room and doing introductions a little bit better than that hi everyone my name is earl duque i am a developer advocate here at servicenow i've been on the platform for about five years but only at servicenow for about six months uh before that i was in the higher education space mostly jumping around the university of california and we'll pass it off to julia all right hey everyone i am julia perlis this is zeus he may join for part or all of our happy hour today um i am a principal product manager here at servicenow and um i focus on decision management and and specifically decision builder which we're gonna take a look at today so super excited to be here zeus is too but he might get bored she makes all the decisions in service now every one of them actually she said she's in decision management so i thought that's what that was well i thought we were talking about zeus we're changing the name it's live cat happy hour my name is chuck tobasi senior developer advocate at service now been here since mid 2010 and the customer for a couple of years before that and a whole long history going back into the early 80s of computer programming development and software engineering so let's have some fun here today i am turning it over to earl oh wait we gotta do our beers first earl do your beer uh i have a repeat uh modern times um i have a hazy tropical ipa with me it's called cosmic rays so cheers julia what are you drinking i am drinking okay i actually bought this specifically because i knew we were going to be doing happy hour it is a lady friend ipa um it's from elora brewing in ontario and you can see that it has a bear and a pretty cool bingo is that uppercutted by the lady here you can there we go that way gabby's threatening us he says i've only known zeus for two minutes but if anything happens to him i will reboot everyone's instances don't worry he's a tough cookie i've got the uh 805 from firestone walker brewing works best this way i don't know where it came from it wasn't in the fridge a couple of days ago my wife said she was gonna get beer but it's weird because there's only three of them i don't know if she drank the other three or just got three or what happened there she's trying to send a message so with that now we can begin our topic so earl what are we doing today all right so it is we are in the middle of our san diego content we are we almost went like this [Laughter] chuck is so used to being in the one spot with the list because i don't think people realize but um on our youtube channel uh one of our um colleagues tanvi she controls post she tried to tries to post on the community page for our channel um with upcoming episodes and stuff and she we love to grab animated gifs of chuck pointing at random things on air especially the logo thing so we have so many clips of chuck pointing up there that chuck is not used to being in the first slot anymore i think as soon as you went this is part of our san diego season when you see this you know what season you're in this is something new we're doing with san diego see the link below underneath the chandelier julia julia's got the the there you go caption duty oh this is why i love life coding happy hour everyone's more relaxed it's the end of the week we're all winding down um but this week because we're in san diego and what just released yesterday um with our the ga release of san diego um uh patch one or was uh yeah patch one of san diego became available um and uh across everybody's pdis also so you can up update your pdi and be and get access to decision builder 2.0 as of i think two days ago or yesterday yeah wednesday yeah wednesday i definitely said thursday on the breakpoint podcast but is that why i kept thinking that's why it was a personal problem that shows who listened you know we used to we used to do store releases only on thursdays and now they changed it and i just my brand can't compute i know that's why it's like i thought this was it says it's already available but oh all right um but this is brand new stuff that we're gonna be looking into and talking about um it's not a new tool but it has been enhanced uh 2.0 um uh it was uh when did decision builder come out um november decision tables as a functionality on the platform came out in madrid but decision builder as something to create decision tables that look like a table came out in um september of last year nice yeah so um as i get ready to jump into an instance um in san diego um for those of you that don't know decision builder and decision tables is a way for you to move hard code well this is the use case i tend to associate it with if you have hard-coded like decisions built into your your flows or into your business logic um stuff like if it's if this thing is worth more than x dollars or if this was um if these certain values are selected do this instead and you have this long if else statement of things to do um decision builder and in the decision tables are a way for you to abstract that away from the um like a single flow or anything and put it on a table where you can adjust without having to touch the flow anymore or having to um adjust a big part of your script and stuff like that because the decision builder the decision table itself is api callable and it can give you the results you can plug it into flow um it just makes things a lot easier for um technical debt and honestly to visualize what the decisions are and stuff like that but a lot of that you'll see as we get into it now so let me log in real quick beautiful description oh good i'm glad i can't remember my password that's step one okay so um [Music] i am going to show you all a back-end process of something that has launched this year uh the mentorship program so shout out to our mentorship program if you haven't signed up for it yet please go check it out at devlink.sn slash mentorship we are looking for more mentors so all of you out there that feel like you have something to share with the world we need more of you please we're going to do another round of pairing next week so now is a great time to submit your application um but we one of the processes that we have in the mentoring program is what we do with pairs that don't fully accept the program so we have a whole list of members um this is a real data turned into demo data so these are fake names i i spent time to make sure they're all fake names now can you bigger the font oh yeah sure on a live code happening hour without reminding the driver to increase their font um so we have everyone all these people sign up um for the survey for um for the mentorship program and then our mvp volunteers uh and our developer program team go in and figure out who would be good pairs and once those pairs are found we create these records of who's being paired together uh and then uh at that point it automatically emails each individual person that's in that pair mentee and mentor and tells them hey you need to accept the program terms to continue on with the program um if you don't after um a certain amount of time um this is the part that we're gonna transit we're gonna try to move to decision builder because this is a the process that i want to get to enhance basically to make better um is if a week passes and um a person hasn't accepted it emails and does a notification reminder so the person that hasn't accepted then after another week it emails them again and lets them know like hey this is your final warning um to update it and then after i think i have it as three days but i want to change it to seven days and this is why it's a good use case um it says hey we're gonna catch you tomorrow if you don't do this and you'll be removed from the program and then your the others whoever did accept already they'll be placed back into the queue um but that process itself i've been doing based off of um i keep changing the times to see what would be better for um uh like feel like where i'm not nagging them too fast but also reminding them that they have something pending um so i keep changing the days between the notifications and i also keep changing the notification themselves and so tying all those things to flow designer has been kind of hard for me because once it's there and they the pair gets active and the flow gets into flight i'm basically like a sitting duck in the water and hoping and have to figure out what to do with those already in-flight flows um some of it i have moved to um templates instead some of it i've moved into subflows instead but then i thought but then i was like oh decision builder this will be a great use case for that so that's some little that's a little bit background of the the application that we're trying to improve today is that um that timing process of when uh notifications go out so the flow itself it used to say right when this flow right when this pair was created wait one week and if it's still not completed uh email the per email whoever's not accepted um and then wait another week and then do it again and then wait five three days and then do it again um i want to take that away from flo um from that individual flow per thing per [Music] uh record and i'm going to make them a different flow that just basically says every week check all the pending pairs and then um based off of the decision builder decide who gets what email that's what i'm going to try to convert so are you are you making the decision builder figure out what the interval is or no i'm having the decision builder um determine which notification is supposed to get um ah okay okay gotcha all right so one um for this one new thing that is going this is actually a real use case so this is great for live coding out there um one of the new things about decision builder in san diego is it is now available in app engine studio so it's integrated right into app engine studio um i can load right into the mentorship program app and it's available under logic and automation so you'll actually see before i click on that um you can see the many amount of different flows and different um items that are behind this app i'm trying to get rid of basically like three of the flows for one decision builder flow and so that'll save some headaches in the future especially if some if we want to make the reminders go faster because um like three weeks it might actually be too long um for the reminders to go out but we were uh wanting to give everybody an ample amount of time to actually decide um this time and but we might reduce it in the future but i'm gonna go ahead and create a new decision and um this is nice little gives us a little bit information about it i saw this on the screen i was like i love these new graphic screens in app engine studio it just makes the app look more you should have seen the uh sausage making of that graphic oh yeah right graphic right thirty different images we were like do we do arrows or colors or values that designers are honestly like miracle workers my brain can't create something that nice uh we're gonna say um pear except it's never the technical things that take a long time what does the graphic look like oh please what are we calling this product [Laughter] speaking of graphics everyone's favorite um programmer just flashed on the screen uh one of our colleagues jason always makes fun of the is that what they is that what people think of developers just i don't know if that's the programmer because he's not wearing the hat oh he's wearing a ponytail and a beard that's right he um and he's sitting in a bean bag too at the same time right oh the one with the that's on the t-shirt with the guy yeah i bought my mom one of those t-shirts and she was like i'm never gonna wear this take it back that's great and she's she's always begging me for service now shirts she's like they're so soft i love them buying more i brought her this and she was like no thanks she starts making requests can i get the aes one seriously she's like wait what about that release one why don't i get one of those and i was like sorry mom it's not happening okay so i'm in decision builder that kind of stuff should go in the store okay we've made our table or we're making it now we're in our decision builder decision table for specifically for our app and now um we have our inputs up here that we're going to get um to feed into the decision table and then we'll build the conditions and results after i add some stuff up here so let me get started pass the whole record i don't know i just said pass the whole record no thank you wait is that right you might have to pass the whole record it's usually i try to pass records as best practice because it makes it easier on the implementation side oh okay i've been doing it the long way then oh yeah if you need more than one parameter from a record pass the whole record the main reason that we have the other input types where you don't have to pass a whole record is a if you're just like calling you know you're using maybe like an integration hub action to get external data and you want to pass that into an input or if um if the person creating your decision table doesn't really know your architecture then they can create one totally agnostic of your service now architecture and you can kind of wire it up later oh sure that would make sense you know it's like what's mine like someone might say i know there's a string field but they don't know what table it's on or what field it is yeah if you just need to figure out some interest rate based on an amount and a time frame or something give me an amount of time frame i don't care where they're from all right so i know so how the logic of which emails go out is sent is based off of these four true and false fields basically of if they've agreed or if they've declined and so let me grab those four fields real quick and then the last field i want to make sure i grab is when was this pair when it was when was this pair created so earl one thing i noticed while you're doing that it's super interesting for me to watch this but the we set a default label for each of these columns based on your input but yours are actually all different so you can go through and edit each of your headers using that edit icon and change it to the right the right label for what you're actually doing so it doesn't always say currentrecord.com exactly thank you for seeing that you are so welcome for the rest of the show we're going to call you phyllis you have to know the fred luddy origin story for that one to be funny i know phyllis is just like the infamous servicenow name i didn't know that i'm too young i guess phyllis and abel tutor abble is it really no it's what he said on his twitter feed no dutch wow that's really changed the way i see the world it's like watching the harry potter potter movie for the first time [Laughter] realize you've been pronouncing all these words wrong in your head for years so i'm gonna so on this stitch on this first row i'm gonna just make one real quick um if the mentee has um declined no if the men if the mentee hasn't done anything yet so neither of these have been pushed to true but the mentor has agreed and that pair was created oh i can i can actually set the default for this for a date field too right you can't set the default you can set the default operator yeah that's what i meant uh and i want to do it on a relative so that whenever i click on here it's already on relative and so relative after seven why isn't this going up there there you go all right so if um because i'm going to run this basically every friday is what my goal is and if it if the mentee still hasn't acted um after and the pair was created um more than wait should it would be before before seven days ago um it was created before seven days ago yeah that's right more than more than seven days ago yeah uh the result is going to be okay this is where i was going to ask for your your both your opinions so i have the notifications already set up um do i need i don't need to reference the notification do i you can you don't have to you can make your result a reference result and it can point to the table that the notifications are stored in or you can just make it a choice result and then based on the choices go in different like based on the result branches going differently let's do that for right now and then if we can take a look later i mean i think we can go more complex and do the notification and julia don't feel bad none of us knew how to pronounce hermione outside people who live in the uk it's a real challenge you know um oh something earlier that i forgot to point out too was up here when you're doing inputs something new in san diego is you um you can reference uh wait oh that's actually down here i was gonna say i don't think we added anything new for inputs in san diego unless my developers went rogue yeah um we can actually do two things i'm gonna show two new things actually right here is um you can output multiple results on for each decision now so you'll see i can actually make it's gonna provide two i think we'll um that's pretty mind-blowing to a developer who thinks you know functions can only return one result we'll call it oh max length is 40 that's fine and then um the other part is uh i just made it a string instead of a referenced field so now now in decision builder 2.0 your results can have both an addition have multiple uh result options and also output non-referenced results so that's um we we kind of talked about earlier like you don't have to do a reference we could just name this the branch and just work off of that so that makes it a lot like more flexible basically to handle your decision builder outputs yeah it also makes life easier if you were trying to create a decision for like a promotion level or a discount percent and in the past you would have to create a whole new custom table just to contain that and have a different record for each result so there was there's some uh extra steps that we've removed the need for now i'm going to decrease my size so i can see the full notification here real quick yeah at least the whole internet loves it that we don't need to create custom tables for results anymore you're still welcome to if you want but you know i mean you know there's there's value in that for some of the use cases if you want to have one record that contains a bunch of fields and you do something with it or you're pointing to an existing record then it totally makes sense which is why we kept in the reference option there's yeah there's a really a lot of solid use cases for it it's just we don't want to force you anymore i like delegating data management to somebody else all right so i'm just doing the fun data building and i heard on this during the breakpoint episode that there isn't a copyright feature yet there is not but it's as i was i think i said a break point like as somebody who's been creating hundreds of these decision tables i personally would love the ability to just clone rows so uh i think watching anyone else do it too would it would save some time um [Music] really while i'm filling up this table um do you want to talk about the uh oh my my mind blinked for a second talk about the um delegated development support added for it yeah absolutely so um one of the things we released in san diego along with this aes integration and the results changes is excuse me the ability to um set up delegated developers for decision tables so in the same way that you can have a delegated developer who for a specific application can use flow designer you can now have a delegated developer who for a specific application can use decision builder and we the delegated permission is decision tables um because really at the end of the day what decision builder's doing right now is letting you author decision tables so the great thing about that is that if you have a person in your in your company who's working on one custom app you don't need to give them the keys to the logic kingdom you can just say all right for your app for your mentorship pairing app you can create and modify those decision tables um and and definitely like works nicely in partnership with with working in app engine studio nice um the other thing um i wanted to ask is i know when you plug this into flow designer uh it get you have an option it defaults to the option of finding the first um matching uh condition and then executing that one um it has the it has the ability to um [Music] activate multiple branches at the same time yeah nice perfect then that actually solves for um the extra rows i was about to make so i'm not going to do that yeah so the way it works is that if you set it up to do find the for like fine first decision that matches then you'll only get one result and you'll see that your result in the flow designer kind of data pills is just a single record but if you choose to evaluate all rows then it gives you the possibility of having more than one result from the decision and then you get a set of result records and you can loop through them right i like that you're sending back the notification earl yeah because then i don't know how you plan on setting this up you could potentially collapse the tree of results and just say exactly you don't even need the branches yeah no no branches is the that's my favorite kind of decision tree yeah i mean tell me about it i'm like at the first every time i open flow designer i'm like get rid of these branches yeah that way this this really becomes a decision engine then you just go hey i'll give you some inputs you tell me what i'm supposed to do because if all the actions are the same like send a notification use the results send a notification use the results and like you don't need any branches on that thing exactly it's like if you want to follow the same action path you just want the data in each action to be different then branching doesn't help you i was just chatting with mark scott he had a recent post that had a cartoon that had this booth two booths of people one had a sign above it says if else and the line is a mile long the other one said switch case and there was nobody standing at that booth i said we need a third booth for decision builder also i just remember to press save for the first time so everyone drink i'm half done where have you been building i mean i did bring a backup beer so i got a couple more in the fridge you're already a life coating happy hour veteran i don't yeah all right so i'm gonna jump in and make a new nope you must have watched previous episodes to study i watched the first five minutes i was like all right preparation know the product you work on got it yeah our pms love this show they don't have to really prepare for anything i just talked to uh next week's guests they said what do you need for me your knowledge show up be a smart aleck i don't whatever you want yeah i feel i feel bad for you julia i'm actually asking you more questions than we're usually asking our guests oh it's good i love it all right so i said earlier i'm going to do this weekly and i'm going to do this at least all lunch and i just said remember to save yeah uh ola pointed out on your decision table it says row four before seven ago did we forget days thank you i wonder what that does what does that do wow that's interesting that you're able to do that it's true julia writing furious it's seven argos uh favorite ago his favorite uh unit of measure by abel is that abel's brother one quick one quick question on your decision table yeah do you want the mentor decline to ever be true i want so i put that there as a failsafe because okay if if it ever is not false then it shouldn't be hitting this up at all got it that makes sense they're all the same why is it a part of the condition though because it's like i'm using this to make sure that it's not true does that make sense i thought of this earlier and i remember thinking to myself okay okay otherwise you'd have to have an if before your decision builder yeah exactly that's like this means that if at some point you wanted to add a scenario where the decline is true then you don't need to change your flow right yeah okay that's another good reason it's a good fail save yeah um otherwise yeah i would have had to put that logic else elsewhere so that this doesn't run for it all right so i think i can just jump oh okay so i need to first look up records yep no lookup records is an action ah yeah yeah i always knock the wrong one always trick the wrong car i did this like six times this morning i'm sorry oh no my big fault was i forgot a table here and then you know before each really wasn't happy and then the action wasn't happy it just got to be a big mess oh you don't have the uh diagram review turned on oh i don't i don't actually i need to i'm trying to keep myself to do everything in diagram reviews i i hate to break this one to you chuck but um make a decision is coming in a future release of diagramming so currently if you're when you're using decisions you can't be in diagram or view okay but he could be doing this part of diagram this part yes nice for each of these lookup records yes going to make a decision decision all of my decisions are labeled wtf that's my internal monologue for most things actually not even just decisions you can make your phone bigger now okay now you can't see gosh i'd be we're gonna be hammered by the end of this episode then um i'm gonna challenge one of our viewers to make an official rule book now well here's the otherwise it it only it's only an available option when you're using branching oh okay you don't need branches though there's the input aren't you doing the same action every time uh no uh oh wait yeah because we're already we already have the notification that's why i commended you on returning so turn branch is off and it goes you can't undo that and that's fine okay you have nothing in them anyway and then the action that goes below is the action that will happen so you're gonna do send notification send notification send an email send notification right they are different yeah and then make decision i think you're sending it for each of those pair records so you have to go up one action well there it is yeah yeah oh this is the record yes you're right yeah that's the record exactly and then this is the notification yeah good call out i would have tripped over that no where are you where's the yeah you saved it right you don't have to activate the decision table or something right can you open your sidebar in flow designer or go panel yeah what's the data panel have for data pos wait what where's the data panel it it got squished oh wait where'd it go it's there it's you got to reduce your fonts oh gosh there we go take a drink all right so make a decision oh i see so you you know what you need to do you need another you need another for each loop you're missing a for each loop because you've outputted a list of results so it doesn't know which notification to send because your decision output is a list of records it's not an individual record so what you need to do is say make your decision find all the true results then for each result that's outputted then you send the notification yeah exactly and then i i need an if statement how did you get a list of notifications because every time that uh just like he's not evaluating the decision table to find the first thing that's worked okay he's looking for each thing so if you had said just give me the first result then we would have been okay yeah exactly so now you just want to choose your um where are we here i don't even i don't need another if you're making this no you can just send your notification sweet so yeah if you're if your decision table had been set to only evaluate to the first true result then you wouldn't need this for each loop right chuck i feel like we're cheating we have like it's it's not we run into so little less errors when we have an extra call with us we're hitting them we're just solving them a lot faster yeah that's true sitting here silently sipping my beer no no no no please don't this is actually improving the process for me goes on mute sits back waves at the camera and that's nice just watch the world burn how about that happy hour all right next nether loop so this is how'd it go julia oh it's great for each yes notification it's beautiful look at this i think that's it that's it that it that does it that's the whole thing sometimes these flows are surprisingly simple yeah i mean it's incredible you look and flow and realize how many actions are just accounting for the fact that you have so many if else statements and then whatever you do with that if else you have to do like six times yeah that's annoying or you throw up flow in it and you get the same subflow six times exactly i want to run the test but i also don't want to flood my email table why not it's just going in the out box that's true yeah don't have deliberately turned on you're fine i do this all the time well that was fast okay maybe too fast ah what happened here invalid failure i need to i need to adjust the notifications back to um to not have conditions on them anymore oh the notifications themselves have conditions well remember i'm translating this from an old process to a new process so i haven't actually gone back and sanitized the notifications no it looks like the the the trigger on them the send when is wrong go check one of your notifications it says it's looking for triggered but it found engine interesting now we're getting into live code territory i already have it saved open up one of those uh the first one that could be found is mentee accept reminder okay check the send when send when record inserted or updated that's why that's the reason it's got to be triggered yes so i was saying i i haven't gone back and changed the all right all right we'll let you off the hook uh yeah i'll go to go ahead and say send i'd send wen you're gonna have to you have to change the rest of them too yeah let me make sure you all reset it mark's got mark's funny how much you want to bet deliveries turned on always check first kids i trust it you know it can't be too smooth it'll make it seem like we rehearsed this at no time if we rehearsed i was going to say which i can certainly confirm did not happen yeah i might have rehearsed drinking beer last weekend shut up phil no you didn't don't make me nervous like that there's a winner i just i love these people these are these are more than customers out there these are just sassy friends that's just cruel so we're getting through the logic of it and then the notification saying it's not running so let me actually check the email table just to see if there's anything there it is running through the amount of pairs that i'm expecting okay you got 50 records right but the decision is coming back with nothing yeah let's see what's the 139 next to zero yeah do you mind opening up that decision table action remember action three yeah what does the 139 represent that's what i'm trying to figure out um amount of pairs yeah i think that's that's i think i think 139 out of 188 um had actions okay uh output data count zero you got nothing are you sure yeah go to yeah all of them are coming up with nothing yep okay which means your condition didn't match count zero order ids ordered ids no cis id is there a way to debug or test the decision table itself on the roadmap there is oh tune in next year [Laughter] that's good i like that's good to know and say what are my outputs yeah exactly like do simulation testing um i'm so curious okay check my data then yeah let's open a record and then just cross reference that with the decision uh so this one was looking at what pair okay here's a record again fake names don't worry it's not uh sort of faking um so you know what let's force it to match one of the things and run the test again see if it pops up that's a lot of checkboxes on that form yeah because that's how i was handling emails beforehand wish i was able to jump to a specific record because i don't remember what that record was 1623. lisa had an interesting idea she said you could write a custom atf test step that calls the decision table api and test your decision to make sure you don't have debt rows sounds like she's done something like that before way to sneak a hack into the apis well even well i if if it ran properly we would actually be able to go straight to the email table and see oh no no that's not it can we take a look at your decision table for a sec no oh wait is this the one yeah yeah so it must be it's a data problem your data oh here comes i remember now it's a this is real data and we've already sent out the notifications for all these people so they're all they wouldn't there wouldn't be any pending pairs anymore because they're already been activated test your data kids anyways that's probably it not explained i've done that i've also sanitized to the point where people don't have email addresses and then the engine goes i'm not sending you anything yeah so i could probably yeah it's because they all they've already got to the point where none of these will actually satisfy the decisions see but isn't that beautiful now you've learned that your flow will just keep on rolling for the situations where the decisions don't apply yeah and if it ever goes back to that then it should activate it again so what sort of changes do you need to make to your app now that you have this wonderful decision table i need to get rid of the um extra columns and the flows that are doing that we're doing this manually you need to you need to flip your notifications over to triggered you need to flip your notifications to triggered instead of uh a condition base or event base yeah um you need to if you were dynamically figuring out who to send the notification to in flight in the flow i think if you're doing send email instead of send notification then you need to make sure that who gets it is configured in the notification and not in the because it's not you'd be calling the notification at that point no email uh that's the main things i'm thinking about anything else hello hi alan i'm cheering for you the crowd is going it nuts oh wait we it started to work [Applause] you'll have to drink cheers um but okay so i always try to at least when i'm driving i always try to bring it back right it's um i'm sweating it's hot here guys [Laughter] um so i i want to make sure to bring it back because when i was first making this app um back in january in february when we were launching the um mentorship program i had to basically like go i was trying to make it as quickly as i could possibly could and make sure it worked and i hit some hiccups and some people got the wrong notifications and stuff like that and that's my bad um [Music] but if i if i had only known or even thought thought of to use this it's so funny the one episode of creator toolbox i was supposed to be on and i missed was the one that talked about decision builder back in november and so i never went back and re-watched the episode but if i had known i would have solved so much time and like now when i have plans to change this timing of 7 14 21 days like i i might i want to make that three three days and then seven days and then 12 days or something like that i want to make it a lot shorter and now i don't have to go through a bunch of weight uh wait timers on a flow and i don't have to um [Music] i don't have to check against all these different things like the these are why these are why we have people like julia um and her team figuring out these tools because uh servicenow is all about abstracting the annoying things away so that we have time to do the things that we want to do add value yep take away those non-value-add things and like lisa said this is this is a great use case and i love seeing how the tools that are created get cr used in in creative solutions like oh you never would have thought of that before that's a great use for that i feel like every time i like talk to anyone or do any of these sessions something comes up where i'm like i really hadn't built anything that did it that way before like choosing a notification and doing that like i know that you can you can use decision tables to choose sub flows and then pair that with dynamic flows oh cool so that you can automatically run different subflows based on different decision actions which is your different decision results which is super cool but yeah it's awesome to see this uh making your life a little easier there thank you and you're helping hundreds of mentorship potential players out there in the future too great i'll just claim all good that comes from membership [Laughter] you're part of it i'm gonna put your name on it like thank you thank you to julia for helping us figure out this thing again it's in the footer of every notification please email julia if you don't do not like your mentor or mentee [Laughter] she's responsible good or bad if you believed you received this notification inappropriately reply to you've received this notification care of julia so no that's that's why i wanted it at first i was going to have live coding happy hour talk about um i was gonna go through um artifact our artifact manager tool that we used to just and make some decisions based off of that but then i was thinking like no that's i'm gonna sit there and think about an actual thing we need to improve because there's so many places that we have more that we have if else if else if else like long if else statements and those are like the bread and butter of converting over to something like this and i'm going to sit there and figure out what a good real use case is that would improve a process for us and this is what came up for me because um mentorship has been my life for the past couple of months trying to watch this program but um [Music] i don't know i just we internally we keep talking about like oh how did servicenow change your life and stuff like that and um it's these kind of situations where it's like people realize that they can do tech they can do development they can do building and coding and all this kind of stuff because um that kind of skill isn't being an expert coder or expert technologist or something it's just being a hard worker and being creative enough to know what tool to use what uh route to go on when you're trying to make something and that's the best developers out there are the ones that are just working hard and trying to solve the problem and more and more service and servicenow is allowing us to do that and if i if i think about how easy it was for me to join um and the servicenow ecosystem five years ago when i first started out um with all the tools that we had back then and now all the tools that we have since then like it's even easier and so i hope there's more people like me five years ago are figuring that out now and stumbling upon these kind of videos and seeing like oh i don't have to code a decision tree or a switch case for certain things and um if i'm working in a vacuum that might be helpful but hey you might like in a real world scenario you're working with a team once i build this decision table i can i can give this to somebody else you know like that's the delegated development kind of side of things too like i don't does this i set up the decision table and now other people can make the decisions for them and i i don't have to i might not be the one who even has to update the factions on this one they could do that themselves because it's all in app engine studio and more and more app engine studio is becoming a a tool where multiple roles and multiple jobs come in together to work on the same app work on the same functionality just at different times anyways that's my talk thanks for thanks everyone for coming to my ted talk [Laughter] wow what an inspiring note to start the weekend on do we have any announcements next week's topic is aes aes speaking of aes so creator toolbox we'll be doing just a high level overview of a lot of features going through some of the demos with those we've got friday's live coding happy hour will be about app template authoring so that will be fun and if you missed it julia is on the [Music] break point that came out a couple of days ago on march 23rd and our next one is the week after that is rpa hub so in case you forgot we are going through the san diego season okay so lots of fun having there if you've missed anything where is it where is it where's the banners san diego banner there it is if you missed anything you can go to our blog article that has all of these and there is still more coming there's a yes there's rpa hub there's mobile and uh also don't forget that registration is open for knowledge at knowledge.servicenow.com and you want to make sure you're going to attend the creatorcon stuff we are putting together some really cool plans we're doing it really fast because we don't have much time for the in-person events so we've got in-person events at the hague in the netherlands and new york on may 11th and 12th and then two weeks later is sydney australia and las vegas so hopefully you're close to one of those and you can attend in person because you know it's been a long time since we've had an in-person knowledge looking forward to seeing a lot of people at those events so knowledge.servicenow.com is where you can sign up for those any anything else i might be missing no announcements for me second that though sign up for knowledge there'll be a decision builder session there if you want to dig in even more and just so much great content coming at you that's awesome the um rating of the beers go ahead earl um i think i you know last time i didn't like this as much but today i am actually liking it um so with the success factor the success factor that you go that's probably it um i'll give it a a 3.75 are we writing on five yes out of five it's it's the untapped scale by quarterback that makes sense you know what this given that i only bought it because of the label on the can it's um significantly better than i expected like i would call this a solid 3.75 or four it's not as um as citrusy and ipa as i usually like being a former new england resident but um yeah i would drink it again how was the the ibus or the hoppiness of that it wasn't it's not like west coast hoppy okay i don't remember what the scale is i would say it's like medium it's not it's not a low ibu but it's not like a pine tree in your mouth as many ipas can be it's like it's kind of kind of like the scoville units on hot peppers like how how can we make it how happy can we make this beer yeah i wonder what like the hot ones equivalent of like ipa tasting would look like the carolina reaper of beers i've got the firestone 805 i like this good uh easygoing session beer it's not a neighbor what's that it's an everyday kind of beer yeah it's an everyday coating beer uh i give that a 4.0 with that quarter point success factor as well so it goes down easy i could you know wash down some burritos or pizza with that easily too oh i was in california last week and i would kill for one of those burritos again come to phoenix we got good burritos all right i mean if the store ends with etos it's it's robertos or tullio bertos or chuck bertos i don't know it it's usually really good they're just these little burrito stands all over the town that sounds like a dream i'll be right back i'm going to make a chuck berto's uh mark is reminding me oh where's ernie in berto's oh never mind [Laughter] i would be a regular patron of that as soon as the word started coming kind of right out of my mouth i changed direction on that joke because it actually wound up better that was weird [Laughter] i was going to go with berto bertos but bernie better at the moment uh that takes care of it for us i think we're just uh nothing left to do but sign out somewhere in here i have some banners and whatnot so thank you once again julia for guiding us through this thanks earl for a very interesting and useful use case that 100 earl what a champ yeah way to come up with the imaginative you know might have to steal that for a demo at some point till next time everybody stay safe hope to see you soon at knowledge creator con that's gonna be a lot of fun and uh take care i lost my cursor now where are we going we're going here bye [Music] you