- All right, welcome to Knowledge. Hope everyone's enjoying their second day here at Knowledge. I'm excited to show everyone a little bit about Creator Studio. My name is Brooks Hawkins. I am a inbound product manager on the App Engine team. I have been with ServiceNow for a little over three years, and prior to ServiceNow, I worked in IT as an IT admin. I have run some citizen development programs, or before citizen development programs were a thing, we called it self-service. And then I'm bringing all that knowledge here to ServiceNow and hopefully creating products that you all can use. And so first I wanna talk a little bit about App Engine. So our vision within App Engine is to empower everyone to build and automate workflows. So if you can imagine it, you can build it. Regardless of your skillset, regardless of your aptitude for ServiceNow, we want you to be able to make your life better at work and build that automation, get out of Excel spreadsheets, and make yourself more productive, make your teams more productive. So how do we do that? We have three pillars, really. The first is our unified, intelligent development. So leveraging GenAI and helping our existing ServiceNow developers move faster. The next piece is unlocking citizen development. I'm sure you've all heard multiple times that there's a huge shortage of developers out there. You might be experiencing that as well, but the IT backlogs continue to grow. And one way to actually reduce that is to bridge that talent gap and unlock citizen development programs. But ultimately, without the third pillar, governance and ALM, the other two are not possible. We wanna provide the tools and processes for our platform owners to actually unlock the platform and scale development in a sustainable way. So the products that we want to use to actually get us to our vision are threefold. So the first is ServiceNow Studio, which is coming out in November of this year, which will be for our existing ServiceNow developers, taking the best of both worlds of IDE and AES and making it even more modern one-stop shop to do all of your development work. The second one that we're gonna be talking a little bit more about today is Creator Studio. This is our new no code product that is going to allow those non-developers to build, request fulfill apps very quickly and not require a ton of ServiceNow knowledge to do so. And lastly, App Engine Management Center, which is already available today, is how our admins and platform owners are able to manage all of the custom development in one place and make sure they have a bird's eye view of what's going on across their dev instance, their production instance, and making sure they're keeping their platform safe. But let's talk a little bit more about Creator Studio. So when we looked at the most common apps on our platform, they were service requests. So I'm sure everyone here has requested something on ServiceNow, and I'm sure there's many people that have also been a fulfiller of one of those requests on ServiceNow. That is what ServiceNow is known for, those service requests. It's what we think about when we think about ServiceNow. And it's also the main source of IT's backlog. And for most customers, this is where citizen development starts. So a few years ago, we released a product called App Engine Studio to try to address this problem. And what we found was there were all these Lego blocks, but it wasn't clear to citizen developers on how they put 'em together. And that was one of the biggest downfalls of App Engine Studio. So we were like, "We have to figure out how to make sure these people that are not as familiar with ServiceNow can put the blocks together really easily." And that's where we came up with Creator Studio. We want it to be a straightforward and simple process to create a simple request fulfill app, and we want it to be guard-railed. We want admins and platform owners to feel comfortable implementing Creator Studio and know that you can invite someone from the line of business or someone outside of your team, and they can start to reduce that IT backlog, but you don't need to be concerned about your production instance and the impact these apps are gonna have. So let's get into our demo. So I am here in Creator Studio. On our homepage, and you can see all different apps that have already been built, and I can go ahead and create a new app. I'm gonna give it a name. So we're gonna do a gift card request app, and this is gonna be for requesting both internal and external gift cards for employee recognition. And we'll go ahead and create that app. And here, I can choose from a couple of different templates. For this, I think we're just gonna go with our creator studio default template, and we're gonna apply that template and decide which catalog we want this to go into. So we're gonna check the service catalog item. And since we're talking about financial things, buying gift cards for people, we definitely want to go through our finance department, and that's the catalog we want it to use. So we're gonna Save and continue. And now we're able to start working on our form. So we already have our basic form here. First thing I wanna do is add a picture and maybe a description. And then I wanna modify my questions. So the first thing is, is this a company store gift card? This is gonna tell me if it's internal or external. And I want this to be a yes or no question. Save and close that. As you can see, fast forward a little bit, but added an Amount field, who's the recipient of the gift card? But I also want to know why do you want to get this gift card for another employee. So let's go ahead and add a multi-line text field so someone can enter the justification. We'll Save and close that and mark it as ready. All right, so now we have our form ready to go, let's add some automations. This is definitely gonna require a couple of approvals. So we're gonna create a playbook, call it our Auto approval internal gift cards, selected our form that we just created. And our trigger is gonna be when the form was submitted. Go ahead and create that. And now I'm gonna start adding some fulfillment steps. So the first thing I wanna add is I wanna make sure that the requester's manager approves the gift card. So we're gonna set that up, Save and close. And then again, 'cause we're talking about financial stuff, we definitely wanna make sure that this is on the up and up with finance. So we're gonna make sure the finance group also approves. Save and close, activate this playbook, and we are done with our automations, that quick. All right, so let's go back to preview what our app looks like now. So here's our portal preview. Everything's looking pretty good. Let's look at our now mobile, also looks good. I'm gonna go back into Edit mode because I'm ready to now submit this for deployment to production. So I can submit this for review. First, I'm gonna see some information about what to expect once I submit this app for deployment. How long is it gonna take to get this to the production instance? Takes just a second to load. All right, here we go. So we only have one form. So already selected, we marked it as ready for review. If there was another form that had not been marked ready for review, we would not deploy that. And we obviously wanna make sure it's visible to other people. And then on our playbook, we wanna make sure this runs on production. So if that's not checked, the playbook would get deployed to production, but it would need to be manually activated there. All right, and lastly, make sure we have our version, our release notes, and we are good to go. So once I submit this, this is gonna create a new deployment request in App Engine Management Center for our App engine admins to manage. So I'm gonna close this and now we're gonna jump to a new view. So Kristy can manage the deployment to production. So she sees that there's a new deployment request here. And for this demo, since we're focused on Career Studio, we're gonna fast forward through a little bit of the governance piece. If you are interested in more governance, we have a session at 3:00 PM in Knowledge Theater 2 that will be on App Engine Management Center and deployments. But for this case, Kristy's able to review what's in the request She can approve it to go to test, run some ATF test suites, instant scans, approve it to go to staging, go through UAT, use change requests to approve and send the app to production. And so we're just gonna go ahead and fast forward this to production, and let's go ahead and see what this app looks like in production. So Jake here is logged into his employee portal, and he wants to go request a gift card. So he's gonna put in some information to request a gift card to celebrate Noah's five year anniversary, and he's going to submit that request. Jake is also a fulfiller on this app, so he actually can go into the fulfiller workspace and he can review that request. For anybody that is a fulfiller in these request apps, everything will be in one workspace. So if you're a fulfiller on one app, you'll just see the information for that one app. If you are a fulfiller on 10 apps, you'd be able to manage that all in one place. So Jake opens a task, and then double checks all the automations ran, and all the approvals were done. And now Noah can get his gift card and celebrate his five-year anniversary. So, ultimately, with Creator Studio, request forms and automations are made easy. It's super simple. You can do it in a couple minutes. If you wanna get your hands on it, you can stop by the Low Code Intelligent Automation in the center of the expo floor and actually run through creating the app in Creator Studio. And then the fulfillment experience is also simplified. You have a single workspace. You don't need your citizen developers going into UIB to try to configure a workspace for them to manage these. We've taken care of the workspace. You can just, if you, as a professional developer or admin or platform owner, wanna modify that workspace, you can, but then it's a one-stop shop for all your fulfillers to manage those requests. And then there's governance at every step. So first, if you are familiar with App Engine Studio and our unlimit, our un, our, I'm sorry, our restricted users and AES, they can't create apps, but they can actually work on them, but you have to assign the app to them. We took that in Creator Studio and we made it a little bit better. So if somebody's a restricted user in Creator Studio, they can click on the Create app button, but they have to request that app, and that request will be sent to AEMC so someone can approve it, helping you manage that app sprawl and dev. Also, as a developer in Creator Studio, you'll be able to see all the other apps that have already been built. So if you ever, as a platform owner, admin, looked at a bunch of apps and you're like, "Wow, there's like seven of these that are really, really similar." Well, now people can actually request to expand an app from Creator Studio, become a collaborator there. And then we're leveraging our pipelines and deployments to make sure that you're automating the deployment to production, but that you're going through that governance process. And so how does Creator Studio fit into all of this? Anything that's built in Creator Studio can be opened in AES. It can be opened in Studio IDE. Eventually, it'll be also be able to open in ServiceNow Studio. So you can start your citizen developers there, but then if you need to expand the app, you can add other developers in there and let them open it in more advanced tools. As I said, visit us at the Low Code Intelligent Automation Center in the middle of the expo floor if you'd like to get your hands on the Creator Studio demo. And you would like to join our ServiceNow Product Lab Insiders Program, scan the QR code, and you will be contacted about looking at some of our products before they're actually built and giving us feedback at the earliest possible stage. Thanks, everyone.