okay um let's go ahead and get started uh welcome everyone to the what why and how of deploying app Engen studio uh so today we're going to discuss how to actually get appen Studio into your instances and what that looks like um before we get started quick safe heart notice in the event that I talk about anything that's Bo facing obviously don't make any purchasing decisions based on that information um just for your information today's session is part of the live on service now um interactive event series and it's a curated series to connect you with service now experts like myself and peers that can help you deploy your products um so so feel free to uh you know scan the link on the screen and uh see the schedule for other other events that are coming um next up a little bit of housekeeping uh try to keep all of your questions in the Q&A if for some reason we're unable to answer your questions live we will get to them um after the session the presentation is going to be recorded and that should be shared on the community um along with the PowerPoint deck and then uh after the event you will be prompted to fill out a survey please fill that out it helps us to kind of determine what sort of content you're interested in and what helps you and what doesn't um also you know obviously thank you for joining us today h a little bit about me so I'm Paige stuffy I will obviously be the one presenting today I'm a principal product success manager here at service now I've been here for about a year and a half uh prior to that I worked as a customer in the service now ecosystem since about 2009 um so I've done a lot of things in that time I've been an admin a developer um platform owner helped put together a citizen development program you name it I've I've probably done a little bit of it um now I focus on helping to drive the adoption of products that customers own uh so things like app engine studio app engine management center um obviously as you can see in the expertise I have a lot of experience with the platform in general building custom apps managing Dev teams establishing citizen de development programs um all all of the above uh today we're going to talk a little bit about first what is appenine studio um why you want appenine Studio what is the value that it brings to your company uh next we'll get in depth with deploying app inent Studio including a short demo on how to deploy apent Studio there will be some key resources at the end um and then of course Q&A so first things first before we really get started uh we have a poll for you how familiar are you with app engine studio is it something that you've used is it something that you know about but you've not used um you don't know how to maximize its value or you you don't know anything about it so looks like we're already getting a lot of responses it looks like a lot of you know about appen Studio but haven't used it or um you you've never seen it before I I so hopefully we can help uh help educate you on on its purposes there are quite a few YouTube videos out there um um about it uh all right um we're still getting a few more responses so we'll give you guys just a a couple more seconds all right it looks like it's slowing down so I think we can go ahead and close the poll um so it does look like the highest percentage have have uh seen it but not used it followed closely by not not having seen it at all so that's that's exciting um all righty so first thing what is app appenine studio for those of you that have never experienced it we're just going to briefly cover what it is um app engine studio is basically a low code visual development environment um it allows users to create modify and customize all aspects of applications so you're talking about creating tables permissions to tables um experiences logic and automation to you know Drive what those tables are supposed to be doing but all of that is wrapped up in the studio and then um wrapped in guardrails it also allows for the collaboration of other while building that application and we'll get a little more in depth with that as we go through the next slides but first I want to talk a little bit about um what I mean by it allows access to all the Lo code Builders so appin Studio at a very very basic level is a guided wrapper for your low code Builders so everything that you see on the screen is available in engine studio um but it's not just a collection of Builders it presents those builders in a logical way uh so it shows you these different builders in a way that makes them relevant to what you're doing so table and form Builder While You're Building data for your application uh process automation designer decision Builder flow designer While You're Building Automation and Logic for your application and um if you've ever used studio in um service now you might wonder what the difference between appage and studio and service n studio is um there are two different environments obviously app Studio as we as we discussed is a low code development environment whereas the service now studio is an integrated development environment um one is geared more towards that low code development um for either um you know your lood developers or even your procode developers whereas service enough studio is really more targeted for your pro code developers um I know sometimes it may not seem like appen studio is really for those you know all skills but um appen studio is really good for a starting point for your procode developers so it's a good place to start building your app and then you can always move over to Studio or outside of um either one of those environments to continue working on the app so you are not um restricted to app engine studio just because you create the app there but as you can see in the screenshot there are a lot of things that they each do separately and there are a lot of things that they all do together uh so both of them can publish to the app repo both of them take advantage of all of the different Builders one of the biggest difference between studio and ENT Studio as far as the builders are concerned is again ENT Studio provide you those builders in a logical way whereas studio just provides you access to those Builders um so next real quickly we'll kind of cover the value of app engent studio so above and beyond the fact that it is a nice starting point for your procode developers what about your loow code developers um what value does that bring so I'm going to throw some numbers at you um obviously anytime we start talking about low code and no code development we start talking about citizen velopment or delegated development um and these are some numbers obviously from several different research organizations talking about app development outside of centralized it so as you can see here you know four 51 research found that 82% of firms say custom app development outside of it is important Gartner found some similar numbers um that 80% of those will be built outside of it by 2024 so it's something that is continuing to grow um and is expected to continue to grow but more important than kind of the research numbers are the customers that we have that are seeing actual results um so all of these numbers are from customers that are actively participating in citizen development the first one of on health um so and I can speak a little bit more to that because I was actually involved in creating their citizen development program but um you know there was a 41% increase in development capacity after they started bringing in delegated developers uh so you went from a giant backlog that was never getting uh never never shrinking to a significant amount of um um a significant amount of that being taken on by those delegated Developers for jabil they saved around 4,600 hours just by automating processes using their citizen development program and then bonco to Brazil um obviously they have about 1,200 citizen developers right now they have a goal to get about 10,000 citizen developers in total uh and they have 990,000 employees so that's a good well it's more than 10% I'm bad at math on the fly but uh it's it's quite a few citizen Developers for the the size of the organization so it's kind of some of the value Behind appin studio so why why you want to implement it um but let's really get into the meat of the discussion how we deploy it before we get talk get into talking about the deployment of appenine Studio we do have one more poll um which is do you plan to install igin studio and here we're really looking to see if you've already already got it installed or what your plans are to install in the next 6 months to a year or whether you're not going to install it at all so as the numbers are coming in it actually looks like quite a few have already got it installed so it'll be interesting to see um we'll talk a little bit more about not just installing it but the steps to take to actually get it ready for use um so hopefully that'll be relevant to everyone give you just a couple more minutes to finish out that poll all right it looks like the answers have slowed down so we can probably go ahead and close that out um just as a recap so yeah most of you almost 50% have already installed it uh good portion of you plan to install it and a few of you don't want to install it at all so some of the first steps to deploying appen studio so not the actual installation but deploying it is deciding how you're going to use it um and this is kind of a valid step for all custom app um creation but before you start creating those apps and before you start delegating out the creation of those apps should really have a defined application lify cycle and that is all the way from the very start so how are you going to intake those new apps how are you going to um you determine if an app actually belongs in service now how are you going to determine if an app already exists in service now that's your intake step and it's really important to you know helping with um with you know that app sprawl that we often see anytime you start um giving people the option to create whatever they want uh so this really helps with the governance around appspro next obviously is build uh and that is really where AES is going to shine um but while building an app one thing to keep in mind is how to support the people building an app especially if those individuals are not part of your core team um so if you are extending out into delegated or citizen development how are you going to support them uh next is the validation of those apps what are your plans to validate them this may fall along the same lines as your normal validation for any of the things that you put into service now any of the enhancements or defects that you're fixing uh but it is important to understand how you want to do that validation are you looking um to use automation things like instant scan ATF is there some um manual testing that's required and how are you going to track that validation next is the deployment method um how are those going to be deployed do they have to follow a regular release cycle what does that look like and of course the maintenance of those apps uh so once the apps are deployed who's going to maintain them again this is especially important if you're doing something like citizen development you want to establish who's responsible for the maintenance and support of that app before it goes into production uh you don't want to try and do it on the fly as incidents are starting to come in um next is really the monitoring of the health of the app um we'll very briefly cover uh some stuff that you know you can install through AMC that helps with the monitoring of the app but you want to know that that app is being used and then if that app is not being used you want to know when it's time to retire it some applications have a short life cycle you're only intending to use them for a period of time we probably saw a lot of that during coid apps that were only going to be used for a period of time uh so knowing when it's time to remove that application or retire that application is equally important you don't want to leave a bunch of technical debt on your platform once you have defined your application life cycle you really kind of want to Define your instant strategy you may find that your inst instant strategy for app engine studio is the exact same as your instance strategy for any other app or any other thing on um on your instance it may also be different um I know in my experience we had our citizen and developers on a different development instance so you may have a pipeline that's a little bit different for your appen studio apps um so it's just important to know what that looks like for your environment um one other thing to note on here well obviously in the image we have app engine studio and development um that is where all the work is done in appin studio but it is equally important to go ahead and install it production not for use in production but for clone Downs so you don't have to reinstall everything after a clone all right so I wanted to show this image real quick we're not going to go too far into this because we're going to cover part of this in a live demo here in just a couple of minutes but um this is a really good highlevel over guu of the different steps to installing as AMC which is the app engine management center as well as pipelines and application intake all four of those are different apps but they all come together to provide governance with your system and then one last thing before we get to the demo um so this looks obviously a lot like our application life cycle um slide back a few slides the thing I wanted to note here um thing I wanted to note here is that each of these steps in that application life cycle we do provide out of the box um plugins or applications that help support those so obviously again we're really focusing a lot on the build today which is AES but we do have application intake which covers that intake portion and um app engine management center which help which helps to cover um the monitoring retiring and then pipelines for deployment and validation um so so and again if you look back at this slide each one of these boxes covers a different one of those applications so again they all work together to kind of provide that seamless in toin governance for those applications right so um I am going to switch over to a live demo so give me just a second and while I do that um there was a question that came in about the presentation and whether or not be available for replay or will the deck be shared yes it will be um out on the community I believe that link might already be in the chat all righty so the first step is obviously actually installing appenine studio if you have if your instances are entitled for it um going into the application manager and this is the application manager as a Vancouver if you are on an older version it may look a little bit different but when you search for app engine Studio you should either get a product like this or if you're in the older version you'll want to scroll down quite a bit until you get the one that involves all of the applications uh you do want to make sure that you install that as a package the reason being there are quite a few plugins involved in this application and you do not want to have to install them each individually if you do not have to one thing that is important to note as far as what's being installed as part of this um the application intake plugin is being installed and the development pipelines plugins are being installed app engine management center does not get installed as part of the AES bundle but they do all work together all right so I have actually already installed AES because if I hadn't we would be sitting here waiting for that to install for pretty much the entire presentation it's a lot of plugins so um there are guided setups for every step of the the installation or deployment of aent Studio obviously installing it very very easy once you get it installed though you basically follow these guided stepup uh guided setups um in the order that they're presented in your application menu so we start right here which is this screen it will guide you through everything that you need to do to actually configure it um including connecting spokes so that you can use that to communicate with uh individuals that are either part of your admin group or your developers um reviewing flow designer access so while most access for app creation is controlled within um AES itself access for flow designer and catalog uh service catalog Builder can be configured separately um you can configure General access to flow designer and general access to the Builder within AES but from more nuanced control say I don't want people to be able to create subflows but I want them to be able to create flows you will have to do that separately and it does walk you through that in this step here and this step here um next is going through Health scans so through the pipelines application that again is included when you install AES you can automatically run instant scans um but you do have to configure what you want that instant scan to do so once you've configured all of these steps you move into the next one which is setting up user access so here you're setting up the administrator Group which already exists you're just adding individuals to it what those administrators do um is they receive notifications for application development uh this becomes even um even more important if you do set up AMC in production you'll want those group members in production not necessarily in your sub production but they're going to be the individuals that approve um the app intake requests that come in so I want to create a new app the individuals that approve them to move forward when a deployment request is submitted through AES so I've I've completed my app I'm submitting it now deployment request is created in production those individuals are the people who approve that and help it move forward um next we're configuring permissions for your existing developers so individuals who already you know you already want to have access you do not necessarily have to have them go create you know an intake you can just go ahead and give them access here and then down here we're talking about the same thing as far as access to app engine Studio there are two types of access for app engine Studio the first is full access which means they can create apps um if they have that group they can go create their own apps that does not mean that they can go into someone else's app and start doing work work if they're not granted access to it but they can create any apps that they want whereas the limited access users can only work on apps that they've been granted access to they cannot create new ones of their own last is something called coll uh collaboration descriptors these are what control the permissions for your individual users so obviously we have the groups up here that is just controlling access to whether or not you can create an app on your own the collaboration descriptors or what are are actually controlling the amount of access that they have out of the box we provide two collaboration descriptors which is owner and editor owner are the people that obviously create the app and can do just about anything within the app editors can only edit the app um you can also create your own though and so when you're creating your own and again the guided setup takes you through all of this but when you're creating your own you can name it whatever you want um you can determine whether or not you want that to be standard and then you give it the permissions that you want this particular descriptor to have I want them to be able to create you know service portals invite collaborators do workflows and workflow designer Etc now again when you grant them workflow access or flow designer access if there's no um Nuance controls like we talked about just a few minutes ago that grants them full access to flow designer um if you want to control that a little more specific specifically you do have to uh follow the steps up here in reviewing flow designer access um there is some documentation on how to create these collaborators so I won't get too deep into it because I could probably spend another 30 minutes explaining how to create those um so that is the basics of app engine studio if you just do this it will work it will definitely work um but you do lose out on a few things some of the automation that's available through things like pipelines and then the application intake so when you're setting up pipelines that that is basically the automation that allows you to go into app engine Studio say my app is done click submit and then it starts to do things uh it will create a deployment request in production that'll get approved once that's approved it goes up the pipeline that you've set up and it moves into the next sub production instance um it can run things like ATF and instant scan autom a atically and then it continues to move up from there um into production um again we won't get too in depth with this because there's a lot of information here but there's some really good training and in fact I don't have a timeline but there will be some new training out on now learning in the near future that takes you through exactly how to set all of this up um but as you can see there are a lot of steps some important things here is that you do configure your production instance differently than your test instance differently from all of your other sub production instances um and this just helps when you're creating the pipeline the order of events it helps all of your instances do what they're supposed to be doing correctly um the last thing is the application intake so this is that intake step on your your application life cycle uh it includes a catalog item and again does some automation so um when these items are input and accepted um it will automatically go and provision the permissions that you define for that user and so we'll kind of take a quick quick look at what that item looks like obviously this is from the admin's point of view oh well it's not going to let me pull that up sorry about that that I did not have this particular item prepared in advance but I bet we can do a preview there we go while this is loading I do see another question I can answer pretty quickly H as is it scoped for scoped apps only or Global 2 does it support working on Legacy scoped apps and also Legacy Global functionality it is only for scoped apps you cannot do um Global or Global scoped work in AES um so now you can create a scoped app that sits kind of on top of an itm function and allow access to that and modifications in that you do get a little bit of a hiccup with you know some cross scope privileges um but as far as just going into Global scope and doing things it it does not support that um so here's just a preview of what that item looks like uh there are some things that you can configure in this down here is what the administrators see so your end users who are putting this in do not actually see this but um if I were approving this were actually you know one that was submitted from here I'd have my development instances that I set up in the pipeline to pick from um and I would tell them what type of permissions I want to give them uh so the create edit goes back to what I said before you have a group where they can create and edit applications that they have access to or they can only edit specific applications they have access to or you're going to manually configure them in which case there will be no automation um so this item lives in production it does use again those pipelines and it uses flow to um to communicate with your development instances and will automatically provision those users into the group so again there's a couple of tasks that you do here um activating the catalog item setting up again the administrators in the group this particular one um you don't necessarily have to do this in production but this is something that lives in production whereas as and most of that configuration lives in Dev um again good idea to uh bring it into production so that you don't have to redo this but nobody's going to be do doing work in AES in production whereas this catalog item lives and works in production so um and then next again it's taking you to create those development environments because it can be used without fully setting up your pipelines you can just set up the development environments if you don't want to set up your pipelines um but either way whatever you set up either in pipelines or through here and Market's development instances they're going to show up on that drop down that we just saw um so that's kind of the basics of it I don't want to say that's all there is to it but that's kind of all there is to it once you've done all of that you have access to app engine studio um you can go and get started from there they can create their apps they can access apps that they've created um and then from there uh add experiences and things of that nature uh so and like I said earlier in the presentation each of these kind of opens in a builder and this is what I meant by it takes those Builders and it presents them in a logical way um so you don't have to know what Builder you need you just have to know hey I need to add data what kind of data am I adding and you can do so from there and it will open up the Builder that's relevant to what activity you're trying to do so um I won't I won't get too far into that so that we leave plenty of time for any additional questions um but that is pretty much the basics of how to install opin studio um at the end of the presentation the deck that will be shared there is and I will actually go ahead and pull that back up but there is um some resources so that you can uh so you can access some links that that walk you through step by step by step how to do the installation how to set it up how to use it um this back up I'll skip to that real quick just so I can show you so right here uh that very first one underneath technical app engine Studio system administrator guide that is going to walk you through all the things that I just talked to you about only it's going to do it in depth every step of the way exactly what it's doing um you'll also see some very similar diagrams to what you saw in this presentation so um all right that is the demo we do have one more poll um for those of you that have either not installed app engine Studio or you have installed it but you're not using it what challenges have prevented you from using it and while I will likely not be able to solve any of those challenges on this call it does help us to know um what kind of conversations we need to start having in the future so all righty um it looks like it's slowing down we can probably go ahead and shut down the pole and share the results so it does look like the vast majority it's just not been enough time to learn the tool um on that note there are a lot of really good videos out there on how to use the tool hopefully uh for the most part it's easy enough that that you know it should be pretty quick to learn it I will tell you if there are any of you on here who are pro developers um the best way that I found to learn the tool was just to use it so the next time I wanted to create an app I created it an app engine studio um it also helped me learn all the pain points so all the things I couldn't do as a you know lood developer and all the things I could do uh was was the the way that I learned the tool um so I have one more slide for you here before we get to Q&A and this is just a quick uh slide for a screenshot it kind of just covers the high points that we covered today um we thought you having to take a bunch of notes so and again this deck will also be available um after the presentation all right one more thing before we get to Q&A um so just a you know a couple of ways to kind of accelerate value and for their goals some more resources um obviously around service now impact the training and C ification so some really good information there on um you know kind of how to upskill what training is good uh and how to use that and then of course expert Services um so yeah thank you again for uh joining me and certainly let us know if you have any more questions