[Music] [Music] [Music] [Music] me [Music] uh [Music] oh [Music] uh [Music] oh [Music] [Music] oh it's easier to say that when the uh the old microphone is on all right let me just double check that everything is up and running and we get some light background music going good morning happy friday welcome to the first official live stream i'm so excited to be here today and that yeah especially after the bit of technical issues that we had last week last week was actually the april fool's joke so got a little bit of a head start there so that you could enjoy today and have a relaxing uh in coming uh to your lovely weekend so uh like i said this is our first official app engine stream i'm keeping an eye on both my screens just to make sure everything's working as it should for those in the audience just because i'm still i'm working out a couple of kinks if there are any audio issues uh please let me know in the comments just so i can keep a little bit of an eye on them so what are we doing today what is the purpose of these streams uh they kind of serve two purposes hey good morning thanks for joining um they serve two purposes the first is to try a different form of content you know as a solution consultant at servicenow i'm very used to sitting down and doing heavily prepared heavily orchestrated demos with very specific beats representing specific personas and so i thought it might be fun to try something a bit more flexible something that i think answers a question that a lot of people have about servicenow which is can you really build as fast as you say you can i think that ultimately our marketing and our branding talks about that a lot uh even beau agrees they talk about it quite a bit um so i'd like to kind of put my money where my mouth is and showcase you how easy that can be uh in addition to some housekeeping i think this is at the most appropriate time to introduce uh oh it's cut off uh introduce my dog bo bo will be my co-host for the day uh when he really likes stuff he'll cheer so like good boy um he's also doing that because i did promise to make him a peanut butter stick and that's what he wants so while we're getting warmed up and we're waiting for some people to join i'll go ahead and get that ready so as far as what we're covering today um i'll cover this more deeply in a second but we're just going to do a nice simple app just to kind of start things off for today um before diving into anything too radically complicated however it will be showcasing some new stuff about san diego so if you're joining here looking to learn more about the newest release you can and i think that it showcases a lot of resources that are available to the public that's the other thing is that when i was doing these this idea for live streaming i wanted to utilize things that you could utilize as well uh so as you can see uh this is definitely uh his highlight of the day so without further ado to be a good boy we'll keep him uh satiated over there i will say uh he is not a permanent co-host if he ever behaves poorly uh he might get ejected from from the show today so with that being said let me try out another one of my screens which is this one okay perfect oh man this is such a high after how uh uh what a disaster the my last attempt was last week there was just a tremendous amount of technical issues this is actually running a software called stream labs uh prior to this i've never used it before so getting comfortable uh with a whole new type of software on top of trying a new type of presentation um you know it's been an interesting little game so let me go ahead and add some background music here we go alright so to start things off let me introduce myself if you've never met me before my name is laura mcmanaman i've worked for servicenow for almost five years and prior to that was a servicenow uh architect and developer at one of our customers which was how i got acquainted with the platform in the first place um probably the biggest blessing about having that be my starting point was the size of the customer had a lot of flexibility right it was a relatively small company and so there wasn't a tremendous amount of red tape that you find these like humongous corporations and the licensing that we had at the time allowed us to build a lot on service now so i believe we had itsm and i believe we had pieces of itom as well but that was pretty much it everything else was up to the responsibility of our servicenow team to build and so i got acquainted with app engine and that is the team i'm currently on today so if you're ever looking for me on linkedin i work specifically on the app engine product and nothing else so if you have any other questions on other products i might be a little bit murky but i will do my best to answer them if you're looking for follow-up opportunities i'm a huge qr code fan as you can probably tell you can actually scan that qr code on the screen and it'll add my contact information so if you had any questions that were the result of the follow-up or if you shared the recording of this and people had more things that they wanted to say or ask or ideas for next time too that's the other part is that um this stream is completely dependent on me coming up with a list of ideas to create for people um i am not an infinite trough of creativity so customer use cases are always preferable to my uh silly ideas on a personal level uh i'm in dallas texas if you can't tell by my rampant love of smu and oh i guess i removed it i used to have a dallas stars picture on this slide um big fan of photography big fan of scuba diving prior to the use case i came up with for today it was actually going to be a scuba diving related app but this one seemed a bit more uh like pertinent to uh corporate life and and corporate problems i was like that's probably the best so a couple of disclaimers uh it's always good to start off with a couple of disclaimers just to help set expectations the first is that i'm not a developer i am not a developer anymore i have been a developer i am not a developer anymore why do i say that what it is i say that because sorry if you can't hear that i think he got peanut butter up his nose you good you okay bubba okay um the reason i say that is because the application we're designing today is not going to be something that's going to be production ready i don't spend eight eight to ten hours a day developing i'm a solution consultant i'm here to help match the value of servicenow to customers as fast and effectively as possible so if you see instances where you're like that's not the best design decision or or that's not as flushed out as it possibly could be there's a reason for that it's not my full-time job anymore but if anything i think that helps illustrate the principles of our low-code development even better right i'm not a developer but i can still effectively build an application that solves a real world problem second disclaimer this is being done on a pdi again i want to use resources that you today have at your fingertips um if you've never used a pdi before i will be showing you how to acquire one here in just a second the pdi stands for personal developer instance it is a tool that you can acquire completely for free today on our developer website where basically you can acquire a instance of i think of the last two releases including the most recent one so if you're working for a company that doesn't have the flexibility to upgrade every time or maybe do one you know like every year and so you're waiting on tokyo to come out um this is a great middle ground where you can maybe prep some things and test out functionality that your company could use in the future hey good morning ryan k thank you so much for joining as well so this is being done on pdi the consequence of that right is that they're empty they don't come with any other applications turned on they don't come with a whole host of demo data and things like that um i will give an asterisk i did prep my instance a bit so if you were using this live stream to follow along i did two time saving uh plug-in installations um if you ever talk with me i'm very blunt about service now which i think is a good thing and also a bad thing depending on who you ask one thing that takes a ridiculously long time on our platform just because there's so many of them is to load the plug-in list the plug-in list i don't know what's going on there but it always seems like it is just entrenched in um in uh loading time so i loaded uh two types of plug-ins prior to today uh the first that i loaded was i turned on flow diagramming flow diagramming is a part of the san diego release that basically gives you the ability to have the flow chart style of view for the flows if you ever worked on workflow editor it's kind of resurrecting that view a bit and i thought it would be nice to showcase here today um so i went ahead and turned that on second and by far more time consuming was uh turning on and installing virtual agents uh topics and conversations i can show you specifically what plugins i used um but those are my two disclaimers it is a pdi but it is has two plugins turned on that aren't on by default and then lastly it's my first stream i did do a test stream a couple weeks ago if you have ever watched that um but this is my first stream i i'm a bit nervous if you can't tell um so that's why we're focusing on a pretty easy peasy use case just to get the ball rolling to also receive feedback like if this is a format that people like or dislike or if there's criticism or praise that we can focus on those aspects and make sure the next one is even better than this one currently awesome so with that being said i'm gonna i'm not gonna do that i'm not gonna be right back i'm gonna reorient my screens a little bit so that we can get you going for today's content one thing i also wanted to highlight uh if i may give me one moment please i'd really like to shout out other uh content creators for app engine specifically and one thing i saw one of the members of my team xiao he has his own youtube channel as well it's called app engine xiao i highly encourage you uh to follow it as well let me go ahead and uh let me move this around first give me one second still getting used to the uh the like push and pull of multiple screens one screen being used to monitor uh the stream and then one to present from it's a little bit different but i i think i'm getting a little bit more used to it and then nope that's for later there we go okay perfect uh so again i wanted to highlight uh some new content not only xiao's channel in general it's really really good i'm incredibly jealous of how good he is at making thumbnails uh but he released a brand new video all about san diego so if you have some time um if this live stream is like way too long and you're like girl be quiet i want something short and sweet that's a short and sweet version um and it's only on san diego's newest functionality so it's this video right here i would go ahead and add that to my watch list so i called this whoopsies i want to go back to my my big full face there we go there we go um for today's content we call it the uh the speed run right um if you don't know what that's referring to um if you can't tell i watch a lot of youtube content a lot of twitch content and a huge uh tr i don't know if it's really a trend it's more of like uh like a game i get i don't really know how to quantify it but a huge activity i guess that a lot of people on twitch and youtube do are speed runs they'll take a specific game that has like a win condition let's say um like for like mario maybe it's like making it to the end and beating bowser or something like that and they time themselves doing it and there's an entire there's worldwide competitions and conferences about speed running and who can get to the thing the fastest i essentially kind of want to do that with servicenow so essentially for every step of the building process today i'm going to be timing how long it takes on my phone i know it's a little bit scuffed i tried to get a widget that displayed the timer to the screen uh didn't quite get that working but that's a good improvement for next time and i will be using that at the end to kind of show you the grand total so i think it's time to start talking about our use case of the day so if you haven't seen the title it is called the self-service marketing application and this is an idea that came as a result of me getting in trouble essentially if you've ever worked for a company that has um some degree of is i think it's especially relevant in software because it's not like a physical hardware thing that could um that's not as easy to spoil um essentially for every release of service now whether that is like san diego or tokyo or ones in the future um there are things that we can and cannot say right um that's why when you're ever in conversations you might see that safe harbor slide it's like hey we're talking about future stuff legally we are not committing to any of this um none of this could happen it's all fake until it's actually out we can't commit to anything because we don't develop in waterfall we develop in agile essentially so the result of that is that they certain there's a seemingly constant flux to what can and cannot be said about what product and to what audience um as a salesperson it's extremely difficult to know at any given time what is really appropriate to talk about and what's appropriate to hype up especially because things move very quickly we develop on a six-month cycle so every six months we're having to like relearn what this is essentially i got a little bit of a hand slapped the other day for messing up and so i thought to myself wow it would be so much easier if i could just ask somebody or something and it would tell me if i was going into a certain conversation and i had prepped to talk about it just to validate that that was appropriate so it got me thinking i think that that might actually be kind of a nice app idea right it not only confirms to customers the most relevant information and probably what's most secure but it also keeps all the sales people in check interestingly enough the more i thought about this i thought man you could even track like uh who's asking that question and so if there is a little bit of a mess up you might be able to trace it back to its origin point and so that's the general use case we're going to be focusing on today and so the order of operations essentially we're going to i'm going to bring out my ipad and we're going to kind of sketch out what v1 and i say v1 lightly because it's kind of like the conversation starter app would be and then we are going to jump straight into building it awesome i'm glad you liked the concept i didn't know if it was relevant just to me i i figure if you're an sc too you've definitely been in that scenario of like oh nelly i probably shouldn't have mentioned that yet um but you know to each their own it happens all the time so with that being said i'm going to go ahead uh whatever i uh so this is very similar to like how i talk to customers oopsies let me pick that up um this is a very similar way uh i'll talk to customers i'll talk to them like like maybe a team or very generally about a couldn't ask me um about a specific issue and then try to produce for them what would be an adequate kind of step one an application that would get the conversation moving um for them to iterate off of in the future i'll tell you at the end of this stream if you're wondering like hey like uh what's the follow-up uh there is going to be a follow-up opportunity for you as well uh so keep that in mind so one thing i'm going to switch back over to this screen oh actually not yet because it's going to show a code that can share it in my screen i don't want any of that not seeing that i'm gonna open up reflector so i can share my ipad with my mac is that a reflector come on aha there we go and then my code don't say it out loud i got the worst that is the biggest change about um like presenting to the public live versus like an intimate demo setting um there is a lot more things i have to be cognizant of so i don't accidentally like dox myself or things like that because anyone can see it so it's a little bit of a an interesting situation there and then i'm going to make my screen bigger cannot be seen why is that so small give me one moment i'm just trying to get the old ipad up and running on my desktop i hope everyone's having a good start to their uh april fool's day and that no one's been too mean i gotta say it's not my favorite holiday i'm a pretty gullible person uh so i don't handle oh that's not what i wanted i don't handle pranks very elegantly i guess i don't know it's not it's not at my uh my all-time fave now i got my dog stealing my shoe i'm just trying to get my ipad connected give me one moment aha there we are all right cool and then i'm gonna change the view so that it looks like uh an ipad pro stop stealing my shoes no all right bo you're one you're one strike down you're gonna get kicked out if you're not good ah there it is pro okay no frame there we go all right now i can jump back into my screen share perfect so when i'm talking about kind of an application no seriously oh gosh oh man yeah i've already gotten pranked a little bit this morning um i i really like manga and there is a like a romance manga i read and it released an updated copy and there's been like it's like one of those slow burn comics where it's like will they won't they um and i totally fell for a fake chapter being published not even by the author by the translators the translators just got together and just pranked everybody i was like that's so mean you got my hopes up all right perfect so let's go ahead and let me get my timer started so we can time just kind of how long it takes to just generally kind of think about this application let me get my stopwatch and go so the first thing i think of when i'm thinking about a use case is i like to talk through the data structure first you know what is the data structure that's going to be needed to handle this type of problem well i'm thinking about like a product not only does the product exist um but the version should exist agnostic of the product so if there's multiple products right like i'm trying to think about this from servicenow's perspective there's going to be a product of like a san diego app engine san diego customer service so it would be nice to kind of group those all together it could be a drop down but then again you could always add i will say from a design standpoint i am always in lieu of creating an extra table versus doing a drop down because there's always extra info that could be appended right like you don't want to limit yourself from the beginning oh i'm glad you like the playlist um shout out to uh lo-fi leah uh lo-fi leah is where all this music comes from uh she i think it's she said anyone can use it if you're under 100 000 subscribers i was like perfect definitely me so let's go ahead we're going to start off with a product i'm going to say uh the version is going to be an agnostic table now here's the the first question is that hmm well a product will have a name a version will have a name a version will also have a number and a version will have a status that's one thing that i think could be an interesting flow is uh if the version is live like the second that version goes live all of the product statements become like it's live like whatever like who cares like uh essentially you don't have to use safe harbor anymore it's just free game that makes sense so yeah like a lot like a check box or something along the lines of that um what else well i think that uh from a what are we gonna call the actual statement i don't know if there's a good precedent for the name maybe like product state we'll keep it we'll keep it product discloser statement for now it's these days where i'm really happy i have legible handwriting um that's always helpful so the pride disclosure statement will pair a product reference a version an audience like i like again i'm speaking from experience but typically what i can say on linkedin like for example is very different than an established customer that has an nda or things like that right like you can be a bit more vulnerable if this if the environment is a bit more intimate so maybe we could also say like hey if it's with um big scary multi-billion dollar company you can be a bit more you know honest with him about how things are going so let's let's do that so let's say uh audience and that can be that could be like one-on-one or public for now we always add to it that can be a drop down um because that's just two options essentially that's like that makes sense to me for now okay um and then aside from that if it so this could be a like a ui policy from the get-go is like if it is one-on-one it showcases which customer so i'll have to double check on that if the company table is part of if it's part of the actual um [Music] like out of box like what's on a pdi let's see but i will say the we'll call it the account and then uh oh now here's the big question should the statement like the physical statement be just a fill in the blank box or something that could be like recycled elsewhere i think for now it can just be a string like a big big string whoops run out of room cool okay that makes sense so far so we have our product we have our version um we have our product disclosure statements um well i think that this will be include i think this is included it's just the company table on service now i think that's included i'll have to check i think that's pretty good to start off with okay now one thing um i kind of hinted at this at the beginning so that's the data so one thing that is reflected in app engine studio is you know when people ask us they're like what is an app there isn't like really a good answer there's not a static answer for example um like there's no legal definition on servicenow what an app is when i'm asked that question i typically say an app on service now is something that exists within its own scope it doesn't have to but it can it usually exists with its own scope and represents the four pillars of app development which are tables so some sort of data structure uh ui or i think we call it experiences i call it ui um automation and security to some extent doesn't have to have like in in spades like i've seen a lot of really awesome apps with really awful ui um typically ones i've built um but uh you know having some degree of all four of those in its own scope i would say is an application and that's kind of how i design to and i kind of work through it that way so going back to our lovely there we go so next i wanted to focus on ui i think having just the general um account uh application menu it's probably good to have so like an application menu um like what would be why would we organize that we have a we could have like a little dashboard maybe i always like to have dashboards at the top i usually call them home um so we'll have a dashboard at the top and then we'll have um hmm i think having the disclosure statements up top is probably the most valuable so we'll have like a head like a header it's like pds and or doesn't even have to be a header it could just be that filtered by grouped by product i think would probably be the most sense or version what am i saying complex version and then products and what have you um i always start with just i don't i don't really architect this out much in the beginning i kind of just go with the flow and see how it feels um like form wise and things like that um for i don't know if this kind of qualifies as ui or as automation but i think a huge part of this and i'll admit i have not built one before or at least built one um i've tinkered with it but not used it for like a customer app is um the oh my god i'm blanking virtual agent thank you um virtual agent so i think a huge part of this is going to be virtual agent basically someone plugging in and saying like hey i want to do a pro i want to know what i can disclose about a product it asks okay let's let's work through this logic first what uh and when i'm doing these conversations i always try to get out of them as fast as possible so like for example the first question should probably be what version are you asking about because if they ask about one that's live it can basically be like it's live idiot and then an end um so it's going to ask uh what version and then like if live and um it's going to ask what product and then uh what's audience and if it asks uh if they answer one-on-one then they ask the product to or ask the count what am i saying okay and then it'll look up what's happened it'll look up that and then like push that back to the user okay cool um i still think there should be a flow to basically turn on like trickle down on all of the version like the pdf statement so we'll call it uh flows um turn on live statements that could be it for now i think the last is security security again for this level you know like i said the point of this app is to get to a point where it's a conversation starter i don't do a ton of like pre-architecting role-wise um and until i'm like in media ray i usually do it like as i'm thinking about it in the moment okay i think that's a good place to start or to stop so as you can see from our timer i don't know if that's rendering frontwards or backwards but it took about 10 minutes and 15 seconds that's pretty good so i'll write that down 10 15 36 alrighty so the next stage is to pop out of i don't end up dropping everything let me set up my ipad so i can see it and use it as a working reference all right and then i will stop sharing it to the screen perfect and if you have any questions about like what i'm doing i'll do my best to answer them um i can always pause the timer of like whatever i'm doing and uh just kind of go off the cuff okay let me get up my notes page here as well give me one second before we can uh dive into that was the thing from yesterday let me go back to my face just so i don't accidentally dox anything that's the scary part with streaming is like you could just pop something up on your screen everyone knows your business that's not good at least with zoom it's a lot more flexible to turn stuff on and off all right i'll put this up side by side now if you're watching this right now and you're thinking man there's like a lot of not dead air but dead activity at the end of this i will be creating a cut up version now granted it won't show everything like the advantage of this is that there's no cuts right you can see exactly what i'm doing with proof i'm doing it in this time frame if you cut it kind of defeats the purpose but i will be creating a cut up shortened version of this video uh for your viewing pleasure afterwards so if you're thinking man i just want to get her to get to the point that's probably your best uh possible option with that being said let's go back to you okay so i told you earlier that we are doing this from a developer instance a pdi so right now i'm actually going to blow this up a little bit bigger trust me i'm not blind i just want to make sure that you can see um and showcase where i am so i am on servicenow's developer website which is probably the most like unsung hero of like my enablement and the enablement of of many others oh i'm happy i'm glad this can help you i appreciate that ryan so um the developer website does a couple of things uh the first is that it consolidates a lot of information if you're ever looking for information on our product documentation if you're ever looking for like labs and guides this is the first place i would look um they're very comprehensive they have varying degrees of difficulty um and oftentimes too it's the newest of the new they do a very good job about the second a new release is live all of the guides are also updated for that version so like for example like i i admitted i've never done anything with virtual agent prior to me attempting it with you today uh so beforehand i looked through this document just to make sure i had the right plugins turned on like i mentioned um and you can see like oh i can look how i would do this in paris versus san diego oh thank you very much it is it is a little bit of an interesting uh change up from normal demos uh uh karen because usually there's even if it's a quiet audience there's usually some some feedback so it's like all right it's like uh being an echo chamber but luckily i got my co-worker here i don't know if you can see him oh that's just my face damn we finally got him to sleep though so we might have some luck with keeping him the whole time so going back here you can see that i actually already got my instance and i got a san diego version and so if we go ahead and open it up um i will do like a light covering of san diego uh obviously this looks radically different than what servicenow looked like a couple weeks ago um that's because san diego features an entirely new ui um a little bit of inside baseball if you're curious internally we've been calling this polaris for months i think at this point um and it makes sense because like everything is astronaut themed like oh it's like space and stars and i believe polaris is a star if i'm not if i'm not uh wrong i believe it's a star um so it was funny when they released it it must have had it must have had some sort of legal problem or something like that because when they released it they're calling like the next experience i was like great now i gotta get out of the habit of calling it polaris like i've been calling it for for weeks now obviously this type of dashboard um is not available like on on your instance this is just a kind of hype up app engine studio which is where we're going to be spending our time today now i'm not going to count this part yet because i'm still rambling but don't forget i will remember to do the timer do not worry now what is app engine studio i think um the best way to illustrate what app engine studio is is to contrast it against regular studio so a couple years ago uh servicenow had a massive internal transformation there was tons of like reorganizations and reallocations of resources and money to support a new goal that we had as a company we had done a really good job of working basically when we talked to customers we really talked with it first um our founder is very much like an i.t personality like if you if you contrast it against like salesforce where like there's their founders it's not like very like sales oriented like it makes sense um so that was also reflected a lot in our product like it looked there were a lower code ways to do a lot of things but the way you had to interface with those lower code things is this interface now i don't know about you um this looks like any other ide that i would you know spend my time in as a pro coder full stack developer everything is like very very um like uh ver like overly flexible for a low code person like granted they don't have to write script includes but the fact that they're here is distracting right it makes it come off a lot more intimidating than it needed to so to essentially not like we didn't want to rob peter to pay paul we didn't want to destroy the um something that pro coders really like i really like actually i spend probably more time in studio than i do at app engine studio just because i'm used to it um but we needed a way of saying hey like there are low code ways to interact and build and because there's such a deficit and the number of developers contrasted with the automation companies would like to build um we had to offer that flexibility too so the result of that came out man was the only last release this came out i think this just came out in rome if i'm if i'm maybe one before that maybe it's paris but uh was app engine studio so this basically has two specific goals the first is to enable we wanted to create something that naturally taught people the the practices of good development um the first is embedding resources so like i think when i was a customer especially i i talked a lot of smack about service now with regards to its documentation its documentation was just scattered to the winds it was all over the place it was a heart it was like a horror story to find anything i would end up asking the community like extremely vulnerable questions i probably shouldn't have um but there was no other way to figure it out um so by embedding resources into the platform itself i think it helps with the tutelage of learning how to become a developer second there's an entirely new concept called app templates if you've built things on servicenow before hey nate things are going great we're just kind of getting started i'm just doing a high level overview of app engine studio so welcome welcome to the party um so going back to this if you've built on servicenow before one of the things that is really really helpful when you're building data structures is the concept of um basically inheriting from tables uh if you've you know done like anything computer science related you've probably heard of object oriented programming um so if you have a dog table uh if you're creating a dalmatian one it's gonna have everything that the dog has just maybe some extra stuff that's effectively what you could do you could say hey i want to inherit from a task table and then add on my extra stuff that concept though didn't exist at the app level and so we thought about that we're like what if you could create basically a template app that's completely done on its own but could be a good way for people to tinker around with the platform learn what makes a good app and then customize it a little bit just as an exercise so if you look at any of them you can say oh it comes with some pre-built ui it comes with pre-built tables pre-built flows pre-built roles um they're heavily documented they get run up and stood up in just a couple of minutes and are great learning exercises but interestingly enough for san diego you will see there is an extra button create new templates this allows you so beforehand only servicenow and servicenow partners could create templates now you can um i was talking with a partner that had a franchise type of model for their um their uh i guess their business and this was extremely attractive to them because essentially for every one of their franchises they could create a template right so let's say this is not what they did let's say they ran um burger shops around the country right every burger shop does the same thing but if they're a burger shop in texas maybe a couple of the actions are different like maybe you can't dispose of waste in the same way maybe you have to log um security footage differently i don't know i don't i don't know why i picked burger shops i know nothing about food industry um but you get what i'm saying right same practice small tweaks so um that type of model was very attractive to them and you can kind of see how how it's going you can see how they're grouped by uh what's in progress now we need to create our app so i'm i'm wondering at what point in time i should start the timer um i think for the first step so we'll again this is the first time i've done one of these so for the first um the next timed thing i'm going to make it the creation of our data structure and the scope okay that makes sense so i'm going to go ahead and reset this i'm going to go ahead and click start so um i'm gonna go ahead and click a just to create an app from scratch obviously we don't have a template to leverage here and we're gonna call this the self service marketing app i can add a description or a logo if i wanted to don't have either so it's going to build my scope if you're new to servicenow development a scope is just a fancy way of saying a membrane it can let people and information in and out we're going to create a table i'm gonna go ahead and click started again i can go back once i'm done with the stage and review what i've done if you have any questions but since we're doing this kind of a timed way i kind of want to go a little bit fast this is going to be our product table that we talked about before we're going to autonumber it so it's easy to look things up uh we're just going to call it products and go ahead and click continue i believe uh so this is another example of why working in app engine studio is nice with just how much polished up the table builder is compared to the one uh in regular studio again it walks you through because it's all about teaching but we determined that it was going to have a name field that was going to be a string perfect and that will be our display value as well um display values essentially are if this is being looked up in a like list that is the value that's shown and then also as a san diego change we can access our form views directly here as well so i can just drag this directly onto my default form by best practice i always make the auto numbering read only i'm going to make the name mandatory we are one table down now granted that was our easiest table but you know chalk it up is an easy one the next one we're going to create is our version so again we're going to create this from scratch it doesn't really inherit from anything i'm not going to auto number it because typically we just there's a specific value that we can give a version and the values that we determined we're going to be name number and status so we're going to give it a name close you out name it's going to default to string we're going to make that our display as well come on wakey wakey no not you bo bo it's like you want me to wake up no i want you to keep sleeping uh we'll call this version number i'm gonna leave that as a string as well because sometimes uh for certain types of software it's alphanumeric like i know that um yeah i'll keep it as a string just to be safe and then status should that be a check box hmm because versions can be well i think from i'm trying to think about this from the user standpoint right these are where we start making decisions from a user standpoint obviously from a production standpoint a version is going to be in flight and then like it's going to be pushed to some degree of prod but from a salesperson perspective until it's live it's not live so i will keep it as a uh a boolean for now oh i will say uh it's i hate how it's not called up really it's called true false okay um i will make name and yeah just name our display value we'll go ahead and add these to our table version number there we go um name first then version number there we go and then uh status right after perfect i will make these two guys mandatory but you can't make a checkbox mandatory because then it always has to be true which is not good we do need a bow webcam in the future i i made that little uh so funny story he loves to look out the window um but he's a very short dog and so he couldn't reach it so i basically made a little like step ladder for him which sounds so like pathetic um but he likes to sit in the window now and it's it's very sweet the next table i think this is our last one is our official product disclosure statement table okay um if i can spell it right disclosure statement um we'll auto number this and we'll call it prod stat sure ah a fun fact also beau is actually short for bonsai he is a bichon frise which is a type of dog that you have to groom all the time like a bonsai tree so that's why i named him uh bonsai we're gonna make this our first reference table to our product table okay so we have product basically this is uh this is kind of like our matching of all the things product we're gonna make a version field as well it's going to be a reference i don't know if you can hear it but this song is from probably my favorite game of all time which is called nier automata um i think it is yeah that's near automata um it's a very underrated game it's so so good if you haven't played it before i highly recommend it it's very sad it's a a game that has i think it was 26 different endings um and you can you can get them all done in one in one play through which is for a completionist like me a lot uh more helpful so this is going to be our choice field where our choices were going to be uh one-on-one and then public yeah okay that's our two choices um we are going to add an account field and then we'll have to do a ui policy for this later so that it only pops up if the answer to audience is one-on-one right so if it's saying hey we're having a one-on-one meeting with whom that might that might change the answer and that will be a reference oh this is oh shoot check beforehand i um i don't know if the company table exists on pdi so let's okay okay cool so i was like oh no i don't want to build that um okay cool so that's got the company table and then the statement itself so the statement itself is going to be a string a massive string let's make it like five thousand not five million five thousand um cool we'll go ahead and save that hey bo how are you doing bubba you're doing good waiting on a form to save all right so from here we have our number which again best practice is to make any auto numbering read only so no one can change it if it's a thing that people use to look up it does not make sense for it to be changeable we're going to add in our audience should it does it have a default value i don't want it to have a default value um this is also a new ui i haven't not used this type of ui to build forms a lot yet so it's kind of interesting why does it say one-on-one does it have a default choices huh i'll just leave it for now you can always go back and fix it um statements uh should we order these we'll do product first that makes sense oh no number first that makes the most sense um number products version audience account which will be contingent on oh yes okay i just must fill in um you ipod so i've never so this is a new thing for me um on san diego you can add ui policies in app engine studio i have not done this before uh so let us oh it would be on the account field what am i doing um let's let's click it and see what it does i've never done this before um this is all new to me so the description so this will be we'll just call this show account if one-on-one i guess sure why not uh what are advanced settings okay this is like the timing of it the condition so the conditions will be if the audience is one-on-one baby whoa okay and we will make it uh visible true and will make it mandatory true so if it is one-on-one they have to specifically say who for that makes sense because that can be part of the like look up equation if they're an existing customer uh they could learn more versus someone that is a potential customer add ui policy very cool okay okay i'm very much liking this so if you if you can't tell this is kind of um a couple releases ago we came i'm gonna pause the uh the timer um a couple releases ago we came out with ui builder ui builder is basically the future for constructing ui um at the beginning when it first came out it was just for um like workspaces and things like that and now they're branching it out and creating basically like a like a white bloods like a macrophage or like consuming more parts of the uh ui to be managed from that style of interface okay going back to it's funny because i have all these scenes which are basically what shows to you on the stream and they're all named but i a lot of the names i use a template and so this one's called like in-game which really cracks me up because it's like oh if only you knew what we're using this for it's not for fall oh not for a fortnight all right i'm gonna go ahead and start my timer again um so those are the three tables that we put a company exists so we don't have to build that and it's already accessible through our scope so actually i'm going to stop the timer so to construct so we had 10 minutes and 15 seconds for light ideation and we had 10 minutes and 38 seconds for the building of the first scope and the construction of the data structure and ui policies um one of these time stamps will be me going and adding stuff after that we missed uh like auto basically autocorrect um so we'll see how it goes so 20 minutes in we've pretty much got a good application starter which is which is good to see so let me write down these times on my notepad just so i have a reference to them yeah nate i agree it is a million times easier uh one of the byproducts of um having app engine studio was the art the argument of what is a low code activity that was not a fun discussion to be part of because basically it was just like months of arguing of like could it be a low code activity if we changed how it looked like is it just how it looked or is it the concept itself certain things are easy script includes are not low code client scripts are not low code i would argue business rules are not low code um those things were like done but for stuff like ui policies they were close but the ui didn't match and so with san diego they tried to me if they could match the ui in a way that other people could use it they included it um so this is for the scope the tables and ui and that was 10 minutes 38 seconds and then 71 milliseconds if you want to get real specific so now the question is where do we go from here hmm we could we could work on the virtual agent i think to do that though we would need some dummy data so okay let's let's make a stage called test data that's always part of building an application anyway it's called test data um we'll clear our timer let's add some test data oh if you can't tell this is my uh pillow ahead of my lap let me see that it's not another dog it's just a there's a seal in japan i think her name is yuki and she's very round i forget what type of seal she is and she went kind of viral on the internet for a while and so they made these pillows of her and i ordered one because i'm a sucker and i love stuffed animals all right so let's go ahead and add some test data we'll go ahead and click start um i believe we can do so from here if i'm not wrong oh preview so we can actually see what our table looks like that's probably good uh i don't want to start with pdfs though because that requires every other table to make so let's start with product let's add some products go away so for our products oh here's a good question what's a product uh if we're making this from a servicenow perspective is a product like the application suite i would argue yes okay so we'll call this um it service management we can see that our changes to the form worked because i cannot clicky into the number it service management let's add customer service management um what else i t business management yeah let's throw some love to itbm's way i used to demo itbm quite a lot when i worked on the demo center and it doesn't get as much love as it should it's a really good product i.t business management and then um well of course of course we have to app engine that's my product um it doesn't have a cool long name but it has a name nonetheless uh let's leave it at that that sounds good okey dokey versions ooh okay preview oh here's a good uh listener challenge uh put in the chat if you ever identify what song is playing they're all low-fi versions of nerdy nerdy music that i like so if you ever recognize the song pop in the chat and let you know if you're right or not so i think for testing purposes it's probably good to have an old release a current release and one or two that are not out yet just so that when we're doing the virtual agent conversation will be able to um arbitrate like which like piece like all the different pathways possible so we'll call this uh version number this is 19 san diego 19 i think it is i think it's 19. um we are live oh wish ooh are we already having okay um well let me i'll add a separate part for this because this will be like in the fix the fix timer is we're gonna rename status to live because it would make more logical sense as a user to see like oh is it live yes or is it live no i don't like calling it status so we'll add that as a thing to do so san diego's version 19 i think that's right i don't know um tokyo is going to be our next version so that will be version 20. it's not live so let's say that and then we'll add in rome rsti as i check my own alphabet oh my god um oh here's another question if the version is too old that it's no longer supported should that also be a flow i think it should right because we only support n minus one if someone's asking questions about something that's really old as as a sales person i should say like why are we even talking about this right now like you should be well on your way to another version well look at let's toss some in there so oh man so now the status thing is a really big question of like should it be like in prod future release and deprecated release yeah it should like i'm trying to think about this like if i was showing this to a customer right that would be something that would impress them because like they should be handled differently and this is already showing like maybe in their initial ask didn't exist but if i did it for them they would think oh my gosh it's already adding value it's not just replacing the value that already existed damn all right we're adding that to the list too we're actually going to we're not going to rename we're not going to rename status to live we're going to change status to a hey leah how are you doing we're going to change status to a choice field and then have it represent deprecated versions too okay so we need a couple more versions then um paris is version 17 it's it's well it doesn't matter because we'll we're going to change the status field anyway and then quebec this is more like a it's like turning into jeopardy of like can lauren remember all of the release names in the chat put in below um what was your first servicenow release i think mine was jakarta i think yeah i think it was jakarta or helsinki was the first version of servicenow i worked on oh no no no it was geneva it was geneva geneva was my first version yeah below put in what is your your first version of service now okay so that's our test data for version number now we can add in some product statement test data all right close some tabs on about y'all i am a serial tab adder i have way too many tabs open at any given time all righty rome was your first version ryan oh that's that's awesome y'all got so easy i'm so jealous back in back in geneva i'll be pauses for a second because it's pretty funny back in geneva um we didn't even have studio so like the big ugly studio i showed it's not ugly but it's like it's a lot more tech heavy we didn't even have studio it didn't exist yet and so if you wanted to build anything on service now you would like ping pong all over the platform you just had to know what those pieces were called so if at any given time you didn't know what something was called like you were kind of up a creek there wasn't like a create application file it's like huh what do i want to build um that didn't exist so it was a humbling experience uh to build uh and also i believe that predates oh this makes me feel like such a geezer it predates scopes even so scopes didn't exist anything that you built was in the global swimming pool it was all in one hey bo you can't escape okay a place come on there you go good boy nice job shall we see him up close wait i don't think i've shown him up close yet this is the baby say hello you guys sniff hey bo he does a special trick let's see if he'll do it hey bo can you clap for us come on yes good boy keep going good job he's a little scrunky right now he needs a bath but he's just hanging out all right bubba let's go back to your spot good boy can you sit you got sit good boy you're so smart he's a good guy i do get experience that is true that is the benefit of seeing it this way is you do get the experience and it is cool to see how um as a former customer it's nice to see like criticism that i had presented about the platform reflected in the newer versions i think that like from a product standpoint that always is why that's why i thought selling service now was that my like next path because i had a lot of faith in the product itself so big big fun yes claps for both cool alrighty um let me go back to our studio we're going to start our timer again all right so now we're going to create some product disclosure statements so if the product is it business management let's start i saw it business management love so i'll throw some love its way too uh for san diego um let's say for or let's let's talk about a oh one thing our ui policy is not working interesting so it works for mandatory so another thing to our list um so to answer leah's question did i come up with self-service marketing on my own i'm gonna pause the timer um kind of second he's got a shoe oh leave my shoes alone um i came up with it as a result of a little bit of a pickle i found myself in because i talked about a products feature um in a context which i probably wasn't supposed to uh so i'm kind of making this as a like not an apology but of like if we had something like this at our disposal maybe it'd be easier for people to know what they can and cannot say um so i'm gonna add i'm gonna click start again i'm gonna add this audience uh fix the ui policy to hide the account for some reason the mandatory thing works but the hiding doesn't so we'll go back and fix that later oh and now when it's public why is that not changing interesting we will have to fix that bubba bo you're doing a schnoot rub this might be strike two buddy you might have to go back downstairs well we'll add an account for now just so that we have to um and because we'll call this for a future release i guess well let's think about this what are the test cases that we should have for our for the virtual agent right if we're thinking about the paths the virtual agent could follow what are the paths hey stop he's gonna get the boot um i might need to take a little be right back and put him downstairs um the pass we need something that tests the version so if it's a version that is we at least need one per version and we need the both types of audiences okay so this is this is gonna let's do um go back so this is an old version so this should just stop so the second it gets to old version this one should stop um we'll leave statement as shouldn't statement also be mandatory that's another thing make statements mandatory all right so this one i'll put in parentheses what this should do this should stop at version check what do you got bo hey bubba oh you got bone okay he's good this should check at version check um but this the statement should say like this version is deprecated upgrade now silly goose sure why not alright so that one ends there so now we need one that is like on a live version that's similar and says like hey it's it's live you don't have to worry about uh i'll do app engine that's my product uh we'll make this public and we'll just say um this should end at version check and this statement will be [Music] uh products live [Music] who cares um ivk i had like a oh i didn't even realize my screen wasn't sharing oh my goodness i'm so sorry if i ever do that let me know um i i made a very interesting uh i did something at my old company where i used to write like very self-deprecating uh code checks and then i would remove them but sometimes i wouldn't i remember after i left that company a few months later the guy that ended up picking up my position he was like did you write this like because it was like the code doesn't work idiot like to myself and i was like yeah i was referring to myself i'm so embarrassed i thought i got rid of all those all right cool and then we need one where it is a future version for public and a future version for a specific customer so we're going to go ahead and is that big enough there we go that's a little bit better we'll hit preview um we'll do one for tokyo not the product tokyo we gotta do we gotta throw csm some love this morning and we'll do this for tokyo and we'll do this one for one on one so we'll make this customer we come and the statement will be because this is one one um future statement that's a bit more vulnerable because it's not live or it's not like a big public you know conference or something like that and then we'll do one for tokyo for public oh my god i keep doing that same thing well maybe that's a good thing to consider for the ui maybe the version should be the first thing the version the first thing we ask after all maybe the version is the first thing on the form let's do that um move up version on pds form it's the first thing i think of every time good little mini user check uh and then it said because we haven't done that one yet itsm for tokyo and the audience is public so we won't fill out the account and then future statement that is a bit more reserved cool okay stop interesting so out of all the steps we've done so far the creation of test data has been the longest i mean i think that makes sense because it's one of the first times that we've gotten the opportunity to also do some quality checks about what we're doing so i think that's very good so let's go ahead and add the creation of testada was 12 minutes 15 seconds and then 89 milliseconds okay so i guess the question now becomes how do i make changes that are obviously going to be used in the next step and then like aggregate all of them together in their own time of like fixing broken stuff we're not fixing broken stuff but like fixes i guess i could just add them up afterwards i have four things we need to change we have the uh change status is a choice field we have to fix our ui policy we need to make statement as a field mandatory and then switch up where version is on the form okay let's go ahead and just do that and we can just add them all together at the end to see like how much time for as fast as we built this how much time did uh it take to fix all the stuff that we missed on the first take so let me say uh fixin time cool and then i will oh he's got his easter toy i got him you got your easter chicken you want to show them no you just want to play by yourself okay i'll tell you he's only a year old so he's a little bit of a not a disaster but he's a puppy okay so let's do a refresh here yeah i love lofi leah that's the if you missed it before that's the artist that's currently playing she lets you uh if you're a streamer she lets you use any of her music if you're under 100k subscribers sounds like hell yeah perfect right my audience size yeah 100k um perfect so i'm gonna go ahead and start my timer again to start our fixes so the first was we are going to make the version a i don't know if you can hear him he's whipping that around like it is the end of the world i don't know if we can actually change it we might need to delete it and then re-add it there are certain field types that you can change after the fact um but some if they have any data in them then you can't so we're actually just going it's going to be easier just to delete the field oh man we're going to say hey bye bye bye all right beau bye bye and we're gonna add status again and this time we're gonna make it a choice field and uh choice type drop down without none without with with none uh so what should we even call this i guess live sure that makes the most sense um future what do we call ones like retired sure let's call retired again um this app is not meant to be perfect it is meant to be the conversation starter for a customer done i like that okay now let's go ahead and fix that on our form because the other one got deleted um we're going to make this mandatory yeah more choices okay and they're showing up in the right order good good good so we can cross that one off our list um we are going to we need to fix our ui policy let's go ahead and make statement mandatory because that's really easy again if you never can guess the song i'll give you lots of brownie points all right let's move up version that was the other thing that we wanted to do is say hey version at the top okey dokey and then we're gonna make statements mandatory save and then we're going to fix our ui policy with a boo-boo on our ui policy that might just because i'm not used to seeing them this way so okay let's see is there um beforehand there was like a box to check like reverse if false i don't see that anymore oh there we go reverse it falls this one we need to test out though to make sure that it works because we didn't do that last time and it bit us in the booty um preview wait did i save ah i didn't okay uh new hell yeah stop the timer three minutes i hold up for proof i'm all about proof all right that's three minutes and 11 seconds of fixing time for just a couple things not too shabby okey-dokey three 11 87. okay the next one so uh at this point in time i think it is i think it's time for mr baby to go have a little bit of a nap downstairs i'm going to refill my coffee i'm gonna put this on be right back for just a couple minutes and i will be back shortly and then we'll pick up and we will build our virtual agent conversations that will be the next big cause we've been going for a little almost an hour and a half now so let me put this on be right back i'll be back around in like three minutes or so so stay tuned [Music] so [Music] [Music] [Music] [Music] so [Music] foreign [Music] [Music] [Music] i am back the baby's on time out but he is downstairs he was getting a little randy and i needed to go get more coffee so we're all good to go so let's think let me go ahead and refresh just so that everything's nice and ready to go so the next step is the one i'm most excited and nervous for is building the virtual agent conversation like i said i've never done one um i've also never done one live so i i will i like i said this my first stream i get a couple of freebies uh if i can't figure it out no one gets to judge me fair i think that's absolutely fair i'm going to switch my scene back to our lovely area and well should we jump straight into virtual agent without building the ui yeah because i think if i was a customer i would care more about this conversation being automated than having an interface to look it up on my own yeah that makes sense to me okay so what i'm going to do is i'm going to create a new spot in my notes for uh we'll call this what we're going to call it's just virtual agent construction okay sounds good um fun fact um the way that i set this up so if you're following along with me and want to know how the pudding is made i start off by using developer.servicenow.com um yeah i can see that nate you noped out well okay like i said if i have to nope out no one can judge me um that's the fun part about servicenow is kind of hacking your way through it um i use this lab to at least make sure i had the right things turned on and that i understood the nomenclature of the system so um if you want a like a like a quick little um behind the scenes of uh thank you thank you all so much that's totally fair yeah stream three no more no more excuses um so for here the things you need to activate if you're using a pdi are the virtual agent uh conversation no that's not what i did you'd activate a glide virtual agent that's the first one um that takes both of these take a considerable amount of time i did them last night to make sure i didn't waste anyone's time today um it will look like this so glide virtual agent is first and then if you want to see some examples which this helped me a lot like start to understand how all these things work um you also can install these itsm virtual agent conversations none of none of this will incur a fee it is all still free on your pdi um so these are all uh things that you can do right now if you're interested so fun fact so if you want to do this later you can do it you can install stuff now and then you're good to go just saying all right with that being said i'm going to stop uh installing um and start building so i'm going to start my timer and i'm going to go to the virtual agent designer that is where all the designing takes place it's not in studio it's not seen as a low no low code activity because you could very easily create code so we are going to create a topic a topic is um basically something that can pop up in um one or all of your virtual agents um so we're going to give it a name of uh look up uh products um products what were you calling it disclosure statement okay um we're gonna skip description this is going to be a topic um to be honest if you ask me the question what is the difference between a topic block a setup topic small talk i don't have an answer um uh if anything this is just a further proof you don't have to master the platform to build something interesting um what is that saying it's like perfect is the enemy of good enough or something like that that's my approach 90 of time with regards to servicenow so conditions i do not believe we have to do anything there what we do have to do is add enough keywords to know or for the virtual agent to know when someone is searching for this so we're going to call this uh the keywords can be pds they can be product version accessibility no product just product version i don't know why i'm making it harder on myself product version um uh version disclosure uh future release info that's fun that's good enough like i said perfect as the enemy is good enough that's good enough okay so now we have our lovely design interface um when i was tinkering around this the other night i had like i started to panic because i couldn't figure out how to move the arrows i figured out how um but basically you can create multiple pathways for all this to exist upon so in our flow what we concluded is that we're going to ask about the version first because that's an easy out if it is one of these or if it's two of these things the flow ends there so the first thing that we need to do is we need user input we need the user to say something to us and so we're going to give them um we're going to give them a reference choice and say hey what version so we're going to uh what version is going to be the node name the prompt so the prompt is what's physically going to be said to the user so what version are you wanting disclosure information on question mark um acknowledge it message message uh that can be said back to the user if they provide something you can be like hey this is what you said don't care um so our table can everyone see okay should i blow it up a little bit bigger kind of distorts it i'll keep it that big um the table we are going to select is our version table uh which is here a condition so this is a little bit of a a weird spot i fell into when i was looking at it you have to add a condition it's mandatory um but i wanna show everything so i'm just gonna say if the name is not empty it shows up um i will say if we can't get the if working i'm just going to filter out ones where their status is not future so i will give myself that's the out i'll give myself um a response message oh so this is the message that we tell them if nothing shows up um i'll just say ain't no versions this is what i mean when i say i i write a lot of trolly comments to myself and i'm testing the only that's and that's fine to do as long as you remember to remove them at the end um that is usually where i mess up okay so that asks what version perfect i'm gonna save um basically it's kind of like flow designer where you can test it from the interface itself it'll just open up this extra tab and start the topic so you don't have to actually query it for the topic it'll just start as if the topic is active so it says hey what version are you wanting to disclose your information on um so that's that's rendering perfectly i wonder how it's ordering the data that's a question is that under condition new criteria nope i don't know how it's ordering the data um you could probably script for that but we don't need to the next thing so now that we have information the next thing that we need to do as a virtual agent is make a decision so if it is one thing do this if it's another thing do this so we are not going to do bot responses we are going to do a decision and so you can just click and drag and put it wherever i'm gonna call this um decision version decision if i can spell that right if i can spell that right i will say there is a tremendous amount of i know there's like not too many like it's not like a horde of people here um but there is something that's so intimidating about someone watching you live right because you're like oh my gosh they're gonna judge so all my bad spelling so now this is where i can start creating the multiple universes you know it's like uh like oh there's seven million pathways and this is the only one that works it's kind of the same here so i can name them so this version can be for retired version this can be for live version and this can be for um future version there we go um but just writing that doesn't do anything we actually have to build the condition so if the answer from which version is ooh interesting can i dot walk no okay oh no you were the runner up to the spelling if you don't tell me that okay so we do have to script for this so apparently in the building of conditions for virtual agent designer you cannot because usually like if you were doing a filter on anything else you could dot walk here you can not walk and the answer oh okay so we're going to have to script this awesome so we're going to toggle this to script okay let me look at the syntax for a second okay so we're gonna actually let's come back let's come back to that we have our pathway so we can keep building we won't be able to test it um i did know that raspberry does not have a z in it but any child flavoring is so deceptive because it's usually called like razz something so it really kind of throws you off it's not fair all right well if it's a retired version uh what we are going to do is we're just going to say a message back right we're going to say hey you can say whatever heck you want it's done so for our retired version we're going to use a bot response we're going to say retired version response and we're just going to say well we're going to fix this later but for now we're just going to say ayo it's not live upgrade your stuff cool um similarly we're going to go here and say uh this is called the future version or oh no for live we needed this for live so we're gonna add this over here and we're gonna say live version response hey yo it's live who cares safe so now you might be wondering okay lauren why are only one of these pathways leading to the end well that's because we need to move our little arrows so you can i was clicking on the black dot because to me that made logical sense of what to do uh you don't click the black dot you click the arrow so you can just click and drag the arrows to make sure that no matter what path you take it does result in you completing the virtual agent conversation all right yes um so after that so we let me go back to my notes that we made earlier so we've already asked it for the version now we get to ask it for the product so we're going to do another reference choice right yes reference choice so if it's not live or retired if it's a future version we're gonna say okay what's what product i just call it what product um what products should i be capitalized no what product are you wanting to disclose information on okay um that's going to look up things from our product table this guy and again it's like hey out of condition i'll be like okay i want everything uh so just ones where like the name is not empty okay uh no records response message we'll make this a cute little uh no products what gives sure save okay okay so now we don't need to do any other decisions off the product because that's going to be used to look up our information but what we do need to ask we need to ask another question is is it and this will be a static response is it for a one-on-one or is it for the public um what's called this audience size um what type of audience are you presenting to question okay um label oh let's have it match so let's have it uh match our data model uh i was under pds uh so for this one for our audience we had two choices oh that's funny oh that makes sense so you for so fun fact um you're creating things uh it creates a label and a value the value being like the unique identifier that will never be changed um apparently it can't start with a number though so it made our one-on-one just on one in public okay so uh the value will be on one but our label will be one-on-one and then our other label will be public cool and then we'll just match it directly when we're looking it up uh okay save uh i what i do like and this is something that i kind of which flow designer had is actually gonna pause because i i'm gonna ramble for a second um i wish flow designer had this capture uh save as an image because it just prints it out for you like how convenient is that and so then you have like a png version of your flow so if someone's asking you like how the hell does this all work you can just send them the image you only have to give them access to service now it's pretty cool all right i'll start again all right um so we have our so now we do need another if oh i hate these if statements on uh virtually they're kind of hard um so let's do another decision because if if it's ugly ugly um if it is an audience size of one they need to ask for what customers being talked to so this is that uh we'll just call what were we calling the other ones uh one-on-one audience and this one will be public audience i think we don't have to script these though let's see so oh yes we don't thank god okay so if the audience size is one-on-one heck yeah and this one is if the audience size is public cool like that um but similarly to the other one we need to make sure that both paths lead to the end that's kind of ugly i wish i could drag these down whatever all right if it's what i want me to ask another question which will be a reference choice um and will basically say uh what account right uh what account yeah are you presenting too uh company yeah company favorite musical uh if you if i if i continue to do these i hope i am having a fun time doing this so if y'all like it leave a like or something to let me know um but i might occasionally disclose how much i like broadway musicals company is one of my favorites um we don't need a condition what account that just uses it for the lookup okay so now at the end of both of these there needs to be a say first but a look up we look up the matching pdf so that we can display it back to the user so that would be a um oh my god idiot look up action so if it's a public audience we're going to say it's going to look up public pds yeah we're going to go to the product disclosure statement table we're gonna add a condition it doesn't look right maybe it is yeah okay never i'm talking i'm psyching myself out we don't it's this this is the public track so the audience is public yes and the version or the product is input variable what products heck yeah and the version is another input variable which is a version i think that's all we need i think we'll save it for now um after this one we need another look up and this is look up one-on-one pdfs this is going to be in the product disclosure statement table we're gonna build our condition so the account is a input variable not all input variables what am i doing um [Music] what account yes and version and product and and and and audience is 101 this is an input variable of product and this is an input variable of version save save okay and at the end they need to show it though right it doesn't just need to look it up it needs to like show it let's see this is where my ignorance plays it i don't know the difference between i guess card card because i've used virtual agent a couple of times i think card is what we're looking for we want to display them back like this is the thing and maybe it'll say the statement at the top and they can click it for more let's try that card sure um show public pds all right record that one okay okay now we can select what fields let's show our statement that sounds perfect save similar for the one-on-one okay any difference i just need to change that spelling that's so sad save um okay and this one will be look up or no no show one on one pds and then we'll select the 101 pds oh okay and the statement save so this one so i like how it shows the errors but what is the oh of course because we have to show all accounts so is there like an active can we just show active one status one's where the name ain't empty all right let's do that all right save and then we'll add in a message that says like where go away where are all of the accounts cool okay so so far in review let's look through our flow and just think if it makes logical sense we are first asked the version on our table there are three options for version there are ones that are future there are ones that are live and ones that are retired if they are either live or retired they provide a message which basically imply the same thing of like there's not a reason you need to ask us about disclosure information either a it's live and so who cares it's all disclosable or b it's retired so you really shouldn't be looking up information because you shouldn't be on it in the first place boom all right next part is okay this is a future version perfect what product are you asking about and also what size of audience so once we have both those variables if the audience size is one-on-one we will say whom whom are we presenting to is it an established customer with a built relationship that we care a lot about we want to make sure they're up on all the coolest stuff or is it someone that's like just kind of kicking the tires that we need to be more cognizant of similarly if it's a public audience right we don't want to disclose everything on mass either so we both use on both tracks the variables we have received to look up the appropriate pds i wonder what happens if there's nothing that matches i don't know if there was a let's look at these lookups is there a if nothing is found what is shown that'll be something to test for let me write that down um so like test for failed lookup because i don't know okay now that should work but if you recall we neglected to write the code for this son of a bee so so let's see if we can do that next alrighty alrighty so the syntax for this let's see oh it's on this level what am i saying okay that's odd you would think it would be all right whatever just splitting hairs so the script va inputs so like everything on service now this is using a javascript our own javascript um libraries and things like that so if you're familiar with javascript even to like a minimal sense you can be pretty dangerous on servicenow it's pretty nice like i would by no means say i'm a javascript expert but i i can do a good dent of stuff using hack and slash javascript so let's say um we'll just call this var version type i hate how grammarly defaults to just everything version type so va inputs what is that okay dot what version okay that must be the object dot do i um here's a question of does get value have any parameters like do i put give value and then put the field name inside get value or is git value just returning the value of the object version i don't know let's try the normal way first uh what is our what is the syntax on our version let's look so for our choice field that's called status so it's just stat dot stat let's try dot status i don't know um let's try so dot status semicolon the death of me i will always and forever always be the girl that forgets semicolon thank you for saying i'm making it look easy because i mean i'm sitting here sweating just being like don't don't let them know how dumb you are all right so now we're going to do an if else statement so like if the status is i don't even know which one i'm editing future version so if it's if status is future return true for this pathway that makes sense to me let's try it so if um version type why'd that not go ah go away gravity can i disable you turn off cranberry you're in timeout correctly okay um version type okay version type equals equals because we're comparing it if version type equals equals what did i say was called future all right future if that return true that makes sense for everything else return false and then we just do we copy pasta that for which is i will say this right now my computer science professors would kill me if i ever said copy and paste code never ever copy and case code unless you're doing a speed run and then definitely copy and paste codes the reason they say never copy and paste code is because obviously you could mess something up and then you've copied and pasted it throughout your entire uh stack so it is good advice but i don't want to follow it okay so var let me just speak here this far version type equals version inputs version the status field so that has the status field i think unless we have to use git uh get value if the version type is future return true else return false of like which pathway it should follow i'ma copy that and i'm gonna paste it everywhere uh except so for live version we're also gonna make that a script we're gonna say bye bye and we're going to call it just live and retired okay live and then retired i'm very scared to try this out i don't know if it's going to work i put you in timeout okay i'm hesitant but i think we should test it let's test it okay i do like the testing uh like framework because it shows all your input variables on the right-hand side okay what version are you wanting disclosure information on so i think first we should pick the ones that dead end early so if it's already out like scent oh damn it all right we gotta stop the timer because i have to go fix something all right let me write down let me write down that's current time so the current time for virtual agent we've been working on this stuff for 26 minutes i'm writing that down but we have to go fix our test data because even after i fixed the field i didn't give them the correct value so this is not going to work without those are all just blank right now so so far for the virtual agent we've done 26 minutes 49 seconds and 18 milliseconds we've got to add some fixing time so i'm going to reset that and click start i'm going to go back in this sob and fix those fields otherwise it's not gonna work okay um under version yeah preview give me gimme gimme gimme gimme gimme gimme okay um status so paris which ones are deprecated is it n minus 2 or mis-1 i think it's n minus 1. so if you're on rome you're fine but quebec and paris are retired san diego live baby uh rome live and then tokyo future that makes sense okay that was just 40 i i i said i'm all about proof that just like less than a minute's worth of fixing but it's fixing time nonetheless so we have to add i'm all about this being an accurate experiment and then go back to virtual urgent start okay and i think i have to restart this um just to be safe i don't know what i don't know if it caches the data at all so let's let's try okay first let's pick an old old boy let's pick quebec our if statement worked yes yes okay cool oh my gosh i'm so so relieved that the code worked on the first trouble it worked for one path let's try the others um let's try the other paths so the other one that dead ends is san diego because it's live oh feels good feels good okay okay okay about the v release i don't know here i will pause a little bit of inside baseball on servicenow stuff too is that we only name versions after cities we do business in so like for example i don't know what's going to happen with x because the only cities that start with x um are either a like 26 characters long because they're like an aztec named city in mexico or there's a few in china and we don't do business in china so i don't know what we're going to do with x i've heard uh rumors about where that were doing for uh for v i don't know though i know what u is but i feel like at this point they're kind of grasping at straws it used to always be cities and now they're like tossing in some other stuff i was like y'all are running outta out of space okay back to the game yes worked i'm so excited okay um so now let's start this again so now we're going to pick a path that is the future so tokyo yes okay what product are you wanting to disclose information on well of course because i'm riding the high i'm picking my own product we'll pick an app engine what type of audience are you presenting to um let's ask one-on-one just so that it follows the right path i don't think this is going to return an answer um because i don't think we made any test data for it let's say creative labs can't find a valid record okay so it just says can't find a valid record that's fine let's look for one that does exist um let's look at our test data and see if we've got it working preview i forget what product we used for tokyo okay wacom one-on-one customer service okay wacom one-on-one customer service this is the one we're gonna try to find this prod stat just to see what it renders as okay so this is for tokyo so tokyo's first customer service one-on-one wacom so we could use a little magnifying glass here black on awesome yes yes yes yes yes okay so that's what it looks like that's perfect that's exactly what we need so that's the product disclosure statement it shows the statement itself obviously you can configure that further to look a little bit more presentable or do it like a custom text block that was one thing that you did it just required more code if you look at it um that's perfect oh my gosh hell yeah i'm so i'm so excited right um fantastic so i'm gonna go ahead and stop the timer um at least for now so this add an additional like three minutes a little bit over so i'll add that to our total time for virtual agent let me type that out okay so let me open up my design document again well i think now it's time to start working on flows i think that's obviously the next logical step is to start talking about flow designer right that makes sense to me already let me see okay okay let's see [Music] heck yeah i'll dab for you [Laughter] perfect okay so let's go jump back in here and we're going to focus on creating two flows right where we can do two flows yeah one one one where a version is retired and one where a version is um made uh like live so basically it says hey it's live it nukes all the statements to just be like this is live who cares and if it's retired similarly it's like hey it's retired you shouldn't be using the first place okay so we are kind of skipping over the the second tenant of of a building but like i said before you don't have to have um all of the tenants to have a good app you can have just bits and pieces and focus on what adds the most value the fastest so i'm gonna add a new section on my timer uh for flow designer and i'm gonna click start so we are going to create a flow i do like about app engine studio that incentivizes you to recycle right it's like hey here's some stuff that's already built you don't have to reinvent the wheel but we are so cares um this is going to be called retiring a version we're going to go ahead and click start it's going to build our flow if you're new to building flows for example um they're pretty darn easy they exist in flow designer which is also where you even interface with third-party applications so if you're doing stuff outside of servicenow it can also be part of your flow which is very very nice uh flows basically consists of two pieces a trigger that turns them on and a sequence of actions and logic that they occur after it's been turned on we're gonna go ahead and skip the tour because like i said we're just trying to get it all moving um but i'm gonna go ahead and add a trigger so this is going to be when a version is hmm should it be when it's created or updated sure like either create or updated for the version table i'll be at the end okay and it's going to occur when the state or status changes to retired so when it changes to retired it's going to go through everything else and uh make additional changes now what i like about flow designer is that it writes out exactly what it's doing there's no secrets here um which make it very convenient okay so now we are going to um we're going to search for records we're going to look up all of the records that have that version so we're going to say hey um we're going to look in the product disclos disclosure statement table and the condition will be if the version is the same version as our triggered record so you can just kind of drag and drop pieces that you've used in the past as well you can limit this you can order them in a certain way i don't really give a crap i'm just gonna go ahead and click done now we need to iterate through all these versions and do something to them so that would say we need to use logic so four each is the thing we're going to say and for each product disclosure statement that we found we are then going to do a certain action um that action is going to be updating that very record to uh have a different disclosure statement okay so for each i think you use this one this is where i always get a little bit confused i'm like okay how do i reference the the specific uh for uh record that we are in the loop i believe it is just by yeah it's just by using this so the fields that we're gonna change we're going to change the statement and the statement i'm going to add a little bit of test code in here and say like this was changed by fd cool beans um and the statement itself is going to say this version uh this version has since has been retired um please consult your servicenow team to urgently upgrade your instance sure why not done uh i think that's it to be honest with you um it's a pretty easy flow i can't think of anything else that we need to do um you could always like send out a notification or things like that but usually for these early stage conversations um i would even save that to do in front of the customer like there's a lot of stuff that i will build beforehand as like a a conversation app and then say let's build something together let's see how it works so i i might even save something as simple as that for a live part of the uh conversation i will say it's it's bananas i've been uh live for like about two hours now and i can definitely feel it in my voice already i have a lot of empathy for those uh streamers that like go for like what like six hours like i don't know how they do it it's nuts uh cool now i know i just said you shouldn't copy paste anything but the flow we want to make for uh for basically uh pushing a version live is eerily similar to this one why not let's do it let's copy our flow we're going to call this releasing a version it's in the same scope so we're going to copy it and then we're just going to make a couple tweaks which is again what's nice about developing on a platform it's it's pretty easy to make these types of changes so now the status is not changing to retired the status is changing to live we're gonna click done and for our statements um this uh version um is currently live uh all information is disclosable i don't know i think that's how you spell disclosable um disclosable to any audience of any size okay done save uh one thing we need to do is activate them i'm gonna click stop because right now i'm gonna go into a little bit of a san diego showcase because there's a part of san diego that i activated on this instance specifically for today um back when flow designer was released back when flow designer was released there was a lot of praise right i think it cuts down on a lot of the maintenance by being able to write out physically what it's doing um it helped with new people it helped with non-developers becoming acquainted with automation but there was a bit of a consequence the ui was not as typical for pro coders there was like a a loud minority of like hey like i get the point but the ui now is unfamiliar to us it was a little bit of robbing peter to pay paul and so for years we like flipped back and forth internally on like how to do that and so essentially we have added a toggle to flow designer you can see it right here and like kind of the upper left hand or upper right hand corner and this supposedly will turn my flow into the old flow chart style of ui while still keeping the auto naming and auto labeling but be a lot more accommodating for people that would seek to view it in a different way i've never used it before i'm excited to see what it looks like um it i i think without further ado let's see how our flow looks in the new diagramming view wow okay it looks honestly it's kind of nice that we just came off of a virtual agent designer it looks very similar so it does still keep the auto naming but it's a bit more brief like it's a bit more like not techy but it's a bit more um abbreviated which is nice um you do your editing from the side panel that is that is like changeable well i can't change it maybe it looks like it wants to be something that you can click and drag but for some reason right now you can't um i there should be a drop shadow there i think that might help separate the two but who cares the for each statement looks a little bit different as well okay though i like this this is very interesting very cool i think i still prefer the natural language view but i will say like with any new release of functionality you usually gotta kind of wait like an extra release or a couple of patches for it to be like really flushed out so i'll leave it at that i'm gonna go ahead and restart my timer again so that we can appropriately activate our flows because until they are activated they are untouchable except from a testing purpose so we are going to activate our flows and then we're going to create a test version of them or yeah a test version and a test um product disclosure statement to make sure they're all working so if i go into our version we are going to create a new version just for the sake of testing this yeah big congrats big fun we're gonna create a new one here um we're just gonna call this the test version and it's number zero and at the moment it's gonna be future okay um here's another thing we might want to fix it would be nice from a form perspective to see the pdss for this version so we're going to add a reference list to version of the pdss just so we can see them all on one screen we don't have to ping-pong back and forth that'd be that makes sense uh for now we are going to ping pong back and forth and we're going to go over to our [Music] pds yes and we're going to create a couple just to make sure that we know the for loop is working okay this is going to be in not texas there we are test version i'm gonna go on mute i'm about to sneeze i think oh it died okay um uh products we'll just make it customer service management uh public and the statement will be this has not been changed by fd cool and we'll do another one too uh just to make sure that the loop is working uh test version products itbm we'll do it one-on-one why not and we'll make it web roots and then this has not been touched by flow designer cool we're gonna go ahead and submit that as well and pop back over to our flow designer so if you're testing flow designer obviously you should test it using the testing interface first um because it's already live i'm not gonna do that but we can monitor the executions of our flows from flow designer as well so anytime this has ever been run we can see exactly um how it has been going and all the metadata involved with doing so but the first one we're going to run is not uh retiring a version it's going to be releasing a version so i'm actually going to close these out and just reopen them so releasing a version because right now it's future so we're going to release it so it goes live so this should be the one that triggers first i'm going to open up the executions and see it first okay so we're gonna go back to our pdss and we're oh no no we're not gonna go to our pdfs we're gonna go to our versions and we're going to [Music] release to the world our test version okay so this is future we're going to edit it so that it is live so this should trigger our flow it usually takes a little bit of a beat for that to occur i stand corrected okay so this actually rants let's open this up and see the metadata inside to see like what exactly it did flow reports not available interesting okay this might be because i'm running on a pdi it looks like there's actually something i need to activate well hey this is so i know it's live uh i'll close that out for now um but let's look at our pdis that possibly were altered by us running that flow so that would be under pdis let's go through this there we go um preview so oh okay perfect they both changed this was changed my flow designer okay fantastic okay so that flow works both of those were changed so now we have a flow that when a version goes live all of the statements are corrected to say hey it's live who cares not us no one's getting in trouble so now we're going to change the version so that it is let's say it's been it's been a year and a half this is now a retired version we're gonna go ahead and click retired we're gonna click save and we're gonna go back over and here just refresh this page yeah refresh list this version has been retired whoa okay oh sorry i peeked a little bit there i think um fantastic though so now we have two working flows i'm gonna go ahead and stop that so creating flows i mean granted these are pretty simple um but to do two working flows took 11 minutes and 50 seconds so i'm going to add that to our time 11 minutes 50 seconds 45 milliseconds okay um i'm going to start going back and polishing a little bit on my forms because i think the next logical step is to build like the application navigator and then start to kind of complete this app like i think we're very close to being done with the use case that we framed out in the beginning now obviously there's lots that you can do later which will be like the challenge i kind of end on that does have prizes i will say um but for now i think we're very close to the ideal ending of our of our current scope for this app so i'm gonna go ahead and reset my timer i'm going to start it and i'm going to change my version form so that when i'm on my version form i can see my related list so related lists basically find anything with a relationship using references and can render them on the page with no code needed so i'm going to say that and it'll show anything any product disclosure statement with that um version now i can also change the list view i don't really like this list view so we're going to configure the list layout so we'll say uh we don't need to have version because it's on the version page that makes sense um we'll say product we'll say audience account and then statement yeah i like that okay perfect so let's go let's go to a release that actually has let's go to our test version why not so on our test version perfect so it shows both of our uh versions here it is retired therefore the statements have also been retired very cool okie dokie so um let's stop our timer that just added like a minute 13 to add reference lists no biggie um i'm gonna add that to fix in time and we're gonna go ahead and i think enter into the final sprint now the next thing that we need to do is add our application menus the application menu is how people access our application from the main view where is it hang on i think i actually closed it out so let me go ahead and just go back to my developer site but on top of there um that's how the general user would access your application so let me log back in so we need somewhere that they can click on all and it needs to be here in some way shape or form now uh to be honest with you this is something that i don't think you can add from this guy so we're actually gonna go back into the regular studio which will be a nice compare and contrast i'm not going to start my timer yet because i'm going to talk a little bit about the comparisons you know how this looks you know very simple just like a couple of tables a couple of flows but what really is our app so far i think you can only really see that with the formal studio itself now you can see our application scope is listed here at the very tippy top and if i click into this it looks radically different than the scope that we've been looking at on app engine studio and this really sells the value of it like you want this flexibility for your pro coders there is no advantage in the marketing person that's picked up running this application seeing all of that mess when all of this is where they could have like such a degree of control and emphasis there's no point in showing them something that looks this overly complicated and like it's just a functionality that would never get used but for pro coders that's a whole different ballgame so we can also see that you know our scope encompasses quite a lot we can see actually the virtual agent conversation within our scope so you can say oh it all exists in the same place and as well as all of our flows as well now one thing that we need to do uh is the last thing which is kind of create our application menu so i'm going to add that as our final thing of the day and we are going to start the timer now all right so the first thing we do is create a application menu we're going to call this the self service marketing app now granted most people are going to interface with our app through the virtual agent from like the requester point of view but from the you know the marketing point of view like they would need a place to actually enter in these statements so we're going to go ahead and click save and from here we need to add modules modules are the little guys that show underneath the header so in this case the application menu is this that is the module so i think that we said we are just going to create a couple light modules just to get the ball rolling again this is a not even a version it's like an alpha of like how i would start talking about an app with a customer um we're going to go ahead and add one by all of the pds's so product disclosure statements the order will be zero i always start with zero just based off of my programming background it's gonna be a list it's gonna be a list of product disclosure statements um we can filter them we're not going to filter them um let me save this here let's see if we can group them by something ah maybe not maybe i can do it on the actual page hmm okey dokey um yeah let's go ahead and update that and let's see if it pops up in our window so if i type in self service hmm i wonder if they change this with the new ui huh i don't know this is a mystery to me okay that's that's fine um are they active let's see that's what it's called is active okay interesting maybe they come maybe this polls from a different location because i'm not misspelling it i just copied and pasted it let me refresh again interesting maybe it used something new huh like i said i do get one bail per stream that might be my bail of the day because i am starting to lose my voice a little bit after two and a half hours and everything else works the virtual asia conversation works the flows work if i can't figure out the new application menu my heart's not going to be entirely broken but i would like to figure it out i'm just surprised that it's not showing up if anyone in the comments could lend a hand as well i'm more than happy to take out um hmm interesting maybe type in no it wouldn't be context menu that's something else interesting i don't know maybe it is accessible from app engine studio let's see very curious here's our marketing app everything's live huh okay logic automation experiences huh this is a surprise bite in the butt i did not anticipate this one i know i wish i knew too i've never had a problem with this before huh very interesting i don't want guidance on hmm let's let's do a fast google search of like how to add to application menu service now next new experience what's called i just keep calling it polaris i think oopsies what oh okay let's see if our docs tells us doc i don't want buys uncle back oh my god san diego there we go interesting i don't know if y'all can see that we are unable to find create an application menu in san diego but how do you add to the search bar what out of all the things to stump me it's the application in you that's infuriating that's like the easiest thing most of the time it's like doing thank all done what yes i'd like to search instead i'm pissed create an application menu yes but how do i do it not in rome in san diego what application navigator let's go to the application navigator because that's the top bar in san diego it must be called it must be using something else i just don't know what that is let's try searching the web again that's i'm not gonna quit just yet uh how to add custom application menus san diego service now that's what we are on docs you put me to quebec how to modify a menu list maybe that's it interesting this is room two huh okay okay okay y'all trying to make me look dumb at the end when i was like on my my little runner's high of like ah i built it yeah i'm almost done it's like no you're not ah i don't wanna know about just yet i'm very close i think um maybe let's i'll i'll use this opportunity to hype up another resource which is community servicenow community is a place where anyone can ask a question myself included or looked through questions that have already been asked so there might be uh someone that's already come across this problem so far so let's see um search content um how add add application menu new ui let's see if that turns out anything i guess i'll use this moment to uh plug knowledge knowledge is coming up we have the digital experience but we have both in-person experiences in america both in l.a excuse me las vegas and new york so um check those out version san diego show me wait did you say you can't link it oh so you found it nate can you describe it or like describe where to go yeah i don't think you can post links in youtube chat [Music] where is this this is so infuriating to be like uh application menus san diego service now [Music] [Music] form context menu i will say also just as like a perfectionist it really bugs me that everywhere else our new colors are featured but in our studio so like in our old studio and half engine studio it's still our old color scheme and i'm like oh guys it's changed what is this i think shoot i was hoping this is something i could right click on what is this rendering i thought it was just service no it's not service portal well there's a system menu lists specify limited perspective maybe it's menu list maybe it doesn't look right damn that doesn't look right ui context menus disclosure for anyone watching later i'm pretty sure the link doesn't answer question oh well darn it that's okay maybe context menus is it no maybe well if it is something that i can't let's see what it looks like that's not what i want how do i add it right i'm gonna give myself five more minutes to investigate this and if i can't figure it out that will be my one like give me of the day that's fair i think um no more application menu san diego service now okay what is this one enable i'm glad this song came out i love this song it's from animal crossing just say oh no if you're gonna look it up it's the song the turtle sings while you're on his boat okay assistant mobile you i don't want mobile ui that's not what i want and i don't want it to turn on classic ui um uh service now next experience maybe it's in the docs under next experience okay let's see configuring the next experience maybe that's it exploring themes configuring landing landing pages might be it um add a workspace to the configuring search banner announcements this doesn't look like what i'm looking for though hmm all right i know i said i give myself five minutes but uh but it has been two and a half hours i think that that is a pretty adequate stopping point for the context of our application so i'm gonna go ahead and click stop i will put this under the time so we spent about 12 minutes uh on something that usually would require like one to do uh that's something i'll definitely ask internally and when i make the video version of this i will append the answer because i'm equally as confused and curious as far how someone do that so like i mentioned at the beginning uh this is not the ending point for today uh one thing with the speed run is that you have to compete you have to compete on the speed button what i thought about i'm like well i can't have people just compete on the time because you can just watch me do it so you just memorize how i do it and do it faster that's no fun so what i'm going to do is that i'm going to upload this to source control um source control if you've never used it before basically allows you to download this entire application into your pdi and what i'm going to challenge you to do is extend this application the challenge isn't about timing i don't know how you can beat the time per se but what i would love for you to do and this will be uh there will be a prize to an amazon gift card for whomever i think does the most interesting extension i will start out the next live stream with your application so if you are looking for whoopsie um if you are looking for an opportunity to really shout out your app your app dev capabilities if you're looking for an excuse to kind of tinker around with a new version i challenge you to extend this application maybe that comes in the frame of building a better looking ui maybe that comes in the frame of figuring out application menus there's a lot of small extensions i think could exist with this app and so i challenge you uh to find those so let me get things uh switched around a little bit and i'll kind of uh i have a couple of closing notes for everybody involved so let me go back to one second ah don't do that uh wait wait wait wait hang on um in the game but my blank screen in conclusion there we are um so as you can tell i'm a huge fan of qr codes i've sprinkled them everywhere uh this one that you keep seeing is like the hub page uh so my rep jamie holmes and i uh we put together an entire uh basically one link i i hate when sales people send out a million links so basically we only send out one um but it's relevant for everyone that's involved with app engine and so you can get a good taste of any news there upcoming events material that you like etc um so in conclusion i'm going to add all of this code for today to github my github name is lauren dash mcmanaman it is just my name my first and last name um where you can pull this down if you'd like to enter into the challenge i don't think our next live stream will be for a month or so so there's plenty of time even to build something simple maybe it's rendering all this in the mobile ui you know the world is your oyster i challenge you to be as creative as possible um so second check out the hub website you can hold your phone up right now and show the qr code third check out the developer website get yourself a pdi of your own play around with it um see what you like uh fourth please email me if you have any questions if you're saying oh my gosh our company would get so much value from this um please email me lauren dot mcmanaman servicenow.com uh with a subject line of the app engine speedrun follow-up just so that i can track uh who is coming from these events i think one of the questions my manager had was like how are we going to even track if you know people are coming i'm like that's a good point there is a a good side to the anonymity of youtube but there is a bad side as well so uh and then last but not least uh leaving a like and clicking subscribe would mean the world to me it would let me know if you liked today's content if i should keep doing this um i'm very happy with how this went in comparison to the last one uh so i'm very very i felt very touched to have people participating in the chat so that means a lot to me especially nate and ryan out there carrying the team on their back so thank you so much for joining me here today i cannot wait for the next one i don't have a topic matter yet so if you have any ideas you'll send my email as well i'll be curious see what you say uh with that being said stay clear with pranks and have a fantastic weekend thank you for joining bye [Music] so [Music] [Music] so [Music] so [Music] you