[Music] thank you [Music] thank you [Music] hi everyone welcome to Creator toolbox a show brought to you by us the developer program at servicenow in Creator toolbox we demo new servicenow features for your for your toolbox any kind of tool functionality that might be unknown or new or even just need more expanding on just so that we can equip you all as developers a little bit better uh we are in the middle of our Utah release Lauren if you can pick the right corner to point to oh goodness oh goodness there we go whenever you see that logo that means we are at the Utah release and that is indicating that we are in the middle of content that you can find on devlink.sn Utah so go ahead and check out that link and you'll see all the different things that we have planned for the Utah release before um we jump in let's do some introductions uh I'll start off My Name is Earl Duque I am a developer advocate here at servicenow I was I am about almost two years with the company now and before that though I was with a bunch of customers mostly in higher ed I was a developer and engineer for servicenow for four or five years before I joined servicenow proper uh and then go ahead and Lauren introduce yourself hey good morning good evening good night everybody uh my name is Lauren mcmenamin I am also a developer Advocate on this team uh I'm coming up on around like five and a half years at servicenow but very similar to Earl I worked at a customer beforehand being just a regular service now developer uh and then kick things off to pranav hi everyone my name is Chrono I'm the newest developer advocate here and I was also working as a with a customer before joining service now and yeah that's about me all right so what we're going to be jumping into today is a demo via Lauren to to Showcase uh well I'll let I'll let Lauren introduce the content and we'll jump right into it uh if you have any questions or comments uh the reason why we do these live is so that we can address anything that any viewers might have come up um as a question or even comment or even excitement or even critique uh we uh as developer Advocates we're not necessarily always tied to a particular product so we like any of the comments we always want to take that and we try to get those kind of comments uh support and uh feedback to the right people so be in the chat uh if you are watching this and you are not subscribed please subscribe to the video like it um all that good stuff but Lauren go ahead and start kick us off awesome thank you Earl so today as you can tell by the title is all about table Builder table Builder is probably one of the most foundational aspects of building applications because typically that's where all applications start is someone has a data sellers that maybe is being tracked in a manual sense maybe it's being tracked on like an Excel sheet or just like in a legacy program that you're wanting to migrate to servicenow um so obviously having table Builder be a growing and ever improving piece of software is very important and luckily with Utah there are three major improvements to table Builders so I'm going to switch over to just a very quick deck it's not too uh too intensive I promise we're going to dive straight into the demo but if you're coming just for the quick highlights I'd like to make sure that you're clear on what we are covering before we show it so there are three major improvements uh probably the first and most uh important is how we import these data sources I just mentioned beforehand um obviously if you've developed own service now before you know that you can use spreadsheets and even PDFs to basically build the data structure however there's also a really important aspect of servicenow which is the concept of extended tables so basically servicenows creates some really nice archetypes of very common types of data sources you know the task archetype or the user archetype and you can build off of those so it can save you time in building all those fields that are pretty much the same maybe just simply renamed but also give you some default forms some default lists you can report on all of them together so it's very important however if you wanted to import data and use that imported data in an extended table you couldn't do them elegantly together now in Utah you can so they'll probably be most of the demo today so not only can you do that but map the appropriate fields which was what we'll be showing and in addition to that if my uh deck there we go my deck goes a couple more um now this is a very simple change but will save you a lot of time there are a ton of extended tables that we have by default so that's not even counting the ones that you build yourself now the most common ones are not only moved the very tippy top of the list when you're picking uh but they're actually described so you can see now that task configuration item asset and service are now actually described and moved to the very top of that list just to save you time on consistently scrolling you know throughout that list I think that's up to I think it's around 70 extended tables and then lastly offering a very new uh but also a somewhat uh familiar Viewpoint which is the schema view so if you've looked on servicenow in the past in the regular admin view there are schema diagrams for your data sources and your tables however they were embedded directly into table Builder and now they are so now if you have a data source that has all these different relationships to all these other tables on the platform you can really get a grasp on what that looks like and you can see that all from one read-only diagram within table Builder so it really shows the impact of what you are building and the network of tables that you are creating in and outside of the scope that you're currently working on so that will be what we are focusing on today gentlemen did I miss anything is there any questions that we see in the chat that I can address before jumping straight into the demo unless we want to talk about Bluey and all that kind of stuff that's what's happening in the chat right now um fair enough uh uh Lisa's talking about integration Hub Imports such a cool thing uh she also mentioned that she came across the scheme of you this week when exploring cable building that's pretty neat to have in there so a lot of cool stuff that's happening in in every release so I'm glad people are finding it by exploring um click little plug as you know we're in the early release cycle currently for uh for Utah which means that it's available on pdis I will give it asterisk to that so the on developer.servicenow.com uh you can acquire a servicenow personal developer instance or a PDI however there is a little bit of a wait list for Utah just because it's so new so if you're looking to get a Utah instance ukn I would put my name down for one now just to ensure that you get one as expediently as possible so what is a demo without a use case I wanted to pick something that was uh very soon to be relevant which was creating a nice little uh you know a management app for a person's experience at k23 uh the call for Content just recently closed so all those labs and all those breakouts and things like that are right on the horizon of coming out so I figured you know maybe creating a little management application for knowledge was you know a nice little way to kick things off so in this circumstance don't forget to zoom in a little bit uh you are my hero and I always forget to do that uh so for our default uh we've been storing some things in a spreadsheet obviously the agenda is not out yet so you know maybe these are things that we've heard from Word of Mouth maybe from Earl or Lauren that have kind of you know maybe leaks a couple things that are coming out for knowledge 23. who knows it could all be fake but you never know uh and so maybe these are the things that were peaking our interest so maybe we wanted to create a little application based off this data source that we've got here so we're going to jump into an instance of service now so we have our our default view here and we're going to get things started straight from App engine Studio I already created a scope for this knowledge 23 planner just to save us a little bit of time and we'll get started from here so everything's pretty much the same as far as the experience of building a data source or excuse me building a table on servicenow you're going to go ahead and always click add next to the data header and it'll give you a couple of options for what you would like to build and how you would like to build that uh just because we're using a spreadsheet today that's what we're going to be using but know that this can also work with things like a PDF and also a data integration so after selecting our spreadsheet we're going to actually select our k23 agenda which is the one that we had just looked at and it'll go ahead and upload that file now as always we can also choose to import our spreadsheet data straight from the fact of you know building this table so we're going to go ahead and do that as well just to save us on some time this field here also indicates specifically what will be the uh the field names and obviously those were stored in the first row on my table now here is where things start to differentiate this is something new exclusive to Utah not only will we say where do you want to import your file into but what that will entail so are we going to invite import our file into a new table or an existing table in our case we're building a new one and from here we can see not only concrete we could create a completely blank table based off the fields in our spreadsheet but we can create this from an extensible table so doing this will allow us to build all that data that we just import from our spreadsheet into a new table that extends off what we pick and allows us the flexibility to change the field names and things like that from there on so clicking continue will bring up our list of extensible tables again this will indicate a change on the Utah version because the second that we select from that list we can finally see the recommended tables are at the top the only thing I would change is maybe add something like sys user versus infuser just because that's always such a confusing Point uh for at least for me when I'm building but I'll stick with these key four for now I'm going to go ahead and select tasks since these are things are that were being registered they are assigned to a specific presenter there's a specific date that they are occurring so it it seems similar enough to task that would be appropriate and I'm going to go ahead and click continue so again very familiar here I'm just going to call this my agenda table uh I'm not going to make this extensible and I'm also not going to Auto number this because the labs themselves have their own unique identifier and then go ahead and click continue so as we sit tight and let our table build itself are there any uh questions that we're seeing in the chat so far or are we moving it along at a pretty consistent Pace we can keep going awesome well now that that is settled we can go ahead and click continue again and it'll bring up the mapping interface so if you've ever built a transformation map or something like that it looks very similar so on the left hand side you see our source so these are all the fields that were brought in from this expel Excel spreadsheet and servicenow's best guess at what their field type is nine times out of ten it's probably gonna guess string but sometimes it does it sometimes it uh guesses like date time and things like that and then on the right hand side we're going to see the target so this is the what would normally be a blank table but because we extended off of task it now includes every single task um field as well now what's very interesting is that based off the names that we had from our expel Excel spreadsheet and say that 10 times fast it will actually guess so because we had called a field location and say hey it's probably going to the location field right and the circumstance that's not correct uh but so we can remove that but you can see that for actually for number is reconciling that lab number is the best possible option so that seems really appropriate um I will say when I was experimenting with this in the past there are a couple of things to remember uh it is best to add your custom Fields first um when I was playing around with this uh beforehand I had added some default fields in here I went to add my custom fields and actually wiped out my other fields there's no saving mechanism at the moment uh so if you're gonna you know process through this I would go ahead and add custom Fields first so uh we could add a custom field and you can select for which ones and they'll actually show ones that are unmapped at the moment so if I want to do one for all I do not I would like to do one for a location and I'm going to call this um like room number or something like that to like that's more oriented around this being at a like a convention center but everything else should be able to be mapped so I'm gonna go ahead and click add fields um also similarly to like the data pill picker which is still like the the funniest custom name we've given something you can either drag and drop these fields or use the data pill picker to select so for example um if I'm gonna say maybe registered since it's a true or false field is the same as active I can drag drag and drop it there um for event time I'm going to use that as expected start date so I can go here click and then event time uh for a short description uh I think that's probably the best for the lab name uh lab name and then the assigned to could be the presenter is is so I can go ahead and click continue and it'll go ahead and map all those fields for me so as we sit here uh one thing to note is that if you don't map any like if you skip over mapping a field it will prompt you and let you know beforehand um that was one thing I was planning on demoing but I realized I matched them all so just know that it does add a little bit of a safety net in case you've forgotten to map something serviced out will let you know if that is something that can be done and also we can go ahead and click edit table and see what all was brought in so doing this will actually create two things within your app home so if we go back to the app home we can see that not only did it create our agenda table but it also created the mapping so this is what I mean when it's very similar to transformation map if you import a spreadsheet again you don't have to remap all those fields you can utilize that mapping that you already created so it's it's a big Time Saver in that regard if we go back over we can see we have all of our new uh fields that were created and if we go ahead and actually I'm going to go back here and preview our agenda table it imported our our Labs appropriately as well which is fantastic so Pat myself on the back didn't mess it up so far which is always nice to see uh one thing that we did we made a sign to was a reference field so we're saying that that is a reference to another table which will give us an interesting opportunity to see the third uh change to our Utah table Builder which is the schema View so if we open up our our data view here once more we can see some familiar faces right in the past we've had this data tab here um I think it was an addition ins I think it was in San Diego where we added the forms it might have even been earlier but we added the forms view so now you're not having to ping pong all over the app engine Studio you have everything relevant for this uh table right here at your fingertips you also have flow so if there was any automated flows that were occurring that were triggered by this table they would be accessible here as well but one thing you might also notice as there's a couple new little ellipses so if you click on the ellipses next to data and I'm actually going to blow this up because I don't I don't know how clear it's coming through if you click on the ellipses next to data you will now see that is where the schema view lies so if I click on the schema View and zoom out a little since I've zoomed in um mega mega uh tight it'll go ahead and load our agenda our new agenda table and all the relationships that it represents now because we extended off of task a lot of those yeah I didn't really factor that in um it didn't just bring up the schema View for the filled in fields it brings up all the reference Fields so this really shows when you create something off of task um you're creating a lot of uh possibilities to extend into other tables as well now you can zoom in so there's like a little zoom function here uh and so you can actually read what you are what you're wanting to and if you follow the arrows too it'll highlight them uh which makes it a little bit more uh navigatable if that is a word um but yeah so are there any uh questions about uh are there any opinions about scheme of you I know that when I was building things I would oftentimes use the other schema view that's built into like the default platform so having it directly in app engine studio um is very nice and also it's a nice thing that you can simply like print out things like that for uh or or save as like a PDF for anyone that's interested mostly just praise for the scheme of you being added into app engine Studio we have one person catching up uh to the video wanting to mention uh preferred tables uh pranav also put in the comments uh loving the recommended table feature uh it's a good point um I wanted to highlight this so CIS user uh be careful about extending this user um usually there's a lot of uh if you're especially if you're a citizen developer or you're under a team organization uh check the architecture of how your users are set up before extending it that's it that that is very fair it is usually better to create like a many-to-many relationship between something you're building and like a user table versus like just creating a whole other user subset there's also a lot of out-of-box tables for it customers users a bunch of different things so just be careful about I think that's why it's not under the recommended one just because that is more of a architecture for the entire instance thing fair enough simply Expedia began to create our toolbox however it's definitely you know things worth noting especially as people are getting into uh possibly prepping their labs for knowledge and things like that these are small nice aesthetic changes I think build in a tremendous amount of uh like a frictionless experience to building probably the most foundational step of any app um so if there's nothing else that I can plug I will kick it back to the group and that is new Utah's table Builder nice so the the beauty of Creator toolbox is we uh we want it to be a slow live stream so that we can get nice comments and praise um even the things like we love schema Builder like we'll we get to tell that to the product managers and they always love hearing those kind of comments but also uh Creator toolbox we just want to demo it and then bounce off if you want to just hang out with us and stuff like that we have other shows don't forget to hang out on live coding happy hour we have a new show called you and I Builder uh we do random streams for different things and you can always find us on social media uh so that being said thank you for joining us today uh thank you Lauren for showing us all the new stuff in Utah for table Builder and for now thank you for hanging out so uh catch it catch us next time I think if you go to our YouTube channel we have we've actually started posting our live shows more in advance so that you all have more preparation to press that little notify me button and so go ahead and get to the servicenow dev program YouTube channel and you will see like four more shows already lined up uh coming in the next couple weeks only and so make sure to look at those and join us and we'll see you then thanks everybody have a great day or night yeah [Music] thank you [Music] foreign